Executive Purpose
This library teaches federal acquisition professionals and government contractors how to operationalize AI responsibly across the acquisition lifecycle using structured prompting, ROCCCV methodology, governed AI workflows, validated knowledge inputs, and human-in-the-loop review.
What this is
- Acquisition-aware AI operations
- Governance-driven AI usage
- Mission-aligned decision support
What this is not
- Generic prompt engineering without acquisition context
- Unreviewed automation of contract decisions
- Substituting AI for warranted authority or legal judgment
Important Security Warning
Never copy and paste unknown prompts
- Prompts can contain hidden instructions, malicious prompt injections, embedded extraction logic, data exfiltration attempts, or manipulation instructions.
- This becomes dangerous when working with CUI, procurement-sensitive data, source selection information, pricing data, proprietary technical solutions, financial information, export-controlled data, or classified references.
Never input protected acquisition data into public AI tools
- Do not paste proposal pricing, source selection documents, proprietary customer information, teaming agreements, acquisition-sensitive information, or protected operational data into public AI systems.
- Use FedRAMP-authorized environments, enterprise AI platforms, approved organizational AI systems, Azure Government, GCC High, or secured internal AI environments.
Human-in-the-loop governance
AI assists professionals. It does not replace Contracting Officers, legal counsel, program leadership, pricing authority, acquisition executives, source selection authority, or executive decision-makers. All outputs must be reviewed, validated, verified, and approved by qualified personnel.
What maximizes AI results
AI quality depends heavily on the quality of the inputs. Better inputs produce more relevant, consistent, proposal-ready, and review-ready outputs.
Best Inputs and the Organizational Knowledge Layer (OKL)
| Input Type |
Why It Matters |
| Solicitation (Sections C/L/M) | Provides the core acquisition requirements, instructions, and evaluation logic. |
| PWS / SOW / SOO | Defines operational requirements, scope, and expected outcomes. |
| Agency Strategic Plans | Aligns AI outputs to mission priorities and executive intent. |
| Past Performance and CPARS | Supports relevance, differentiation, and operational credibility. |
| Technical architecture documents | Improves technical accuracy and implementation realism. |
| Pricing assumptions and contract vehicles | Enables realistic analysis and acquisition strategy alignment. |
| Risk registers and transition plans | Improves operational awareness, sequencing, and execution planning. |
| Customer pain points and security requirements | Sharpens capture, proposal, and compliance alignment. |
What is OKL?
OKL is a governed enterprise knowledge environment used to provide AI with authoritative documents, policies, procedures, templates, historical data, lessons learned, and validated references. Examples include SharePoint, Confluence, Teams, OneDrive, proposal repositories, PMO knowledge bases, SOP libraries, contract repositories, wikis, and structured RAG systems.
Why OKL matters
Without OKL, AI operates mostly on generalized public knowledge. With OKL, AI can reason using organizational standards, historical lessons, validated content, and operational context. This improves relevance, consistency, proposal quality, governance, and institutional alignment.
ROCCCV Framework
| Element |
Purpose |
| Role | Defines who the AI is acting as. |
| Objective | Defines the mission, task, or deliverable. |
| Context | Provides acquisition and operational background. |
| Constraints | Defines rules, limitations, and no-go areas. |
| Criteria | Defines success expectations and evaluation logic. |
| Validation | Requires verification, traceability, and human review. |
Temperature Guidance
| Temperature |
Best Use |
| 0.1-0.3 | Compliance-heavy work, pricing, evaluations, and controlled analysis. |
| 0.4-0.6 | Proposal writing, strategy development, and decision-support drafting. |
| 0.7-1.0 | Brainstorming, ideation, and exploratory thinking where creativity matters more than tight determinism. |
Phase 1 - Strategic Planning & PPBE
Government Role - Budget Analyst
What
Supports strategic funding planning, modernization forecasting, and acquisition prioritization.
When
Used during PPBE cycles, strategic planning, budget formulation, and acquisition forecasting.
Why
Helps agencies align budgets to mission, reduce acquisition risk, forecast modernization needs, and prioritize investments.
Recommended inputs
Agency strategic plan, OMB guidance, budget forecasts, historical obligations, existing contract inventory, modernization roadmaps, PMO operational reports, and OKL budget lessons learned.
ROLE:
You are acting as a [FEDERAL BUDGET ANALYST].
OBJECTIVE:
Your objective is to [DEVELOP A 3-YEAR ACQUISITION FUNDING ROADMAP].
CONTEXT:
Agency:
Mission:
Programs:
Modernization priorities:
Budget constraints:
Operational gaps:
Historical obligations:
Technology initiatives:
CONSTRAINTS:
Align with appropriations law and acquisition policy.
CRITERIA:
Analyze:
- modernization priorities
- funding dependencies
- acquisition sequencing
- operational impacts
VALIDATION:
Identify assumptions and areas requiring leadership review.
COMPLETE SAMPLE PROMPT
ROLE:
You are a senior federal budget analyst supporting DHS modernization planning.
OBJECTIVE:
Develop a 3-year acquisition funding roadmap for cybersecurity modernization initiatives.
CONTEXT:
Agency:
Department of Homeland Security
Mission:
Protect critical infrastructure and modernize cybersecurity operations.
Programs:
Enterprise SOC modernization
Cloud migration
Zero Trust implementation
Budget Constraints:
Flat operational budget over next 2 fiscal years.
Operational Gaps:
Legacy infrastructure
Limited automation
Fragmented visibility across systems
Historical Obligations:
$220M annually across cybersecurity contracts.
Technology Initiatives:
AI-enabled threat monitoring
Cloud-native SIEM
Automated compliance monitoring
CONSTRAINTS:
Align with federal appropriations law and acquisition policy.
Do not assume future congressional funding increases.
CRITERIA:
Analyze:
- modernization priorities
- funding dependencies
- acquisition sequencing
- operational impacts
- contract consolidation opportunities
VALIDATION:
Flag assumptions requiring CFO and acquisition executive review.
Expected output
Strategic funding roadmap, modernization prioritization matrix, risk analysis, acquisition sequencing recommendations, operational dependency analysis, and budget exposure assessment.
Phase 2 - Market Research
Government Role - Acquisition Analyst
Recommended inputs
Existing market research, SAM.gov data, contract vehicle information, vendor capability statements, industry day notes, historical contract awards, socioeconomic goals, and OKL acquisition lessons learned.
TEMPLATE
ROLE:
You are acting as a [FEDERAL ACQUISITION ANALYST].
OBJECTIVE:
Your objective is to [DEVELOP A MARKET RESEARCH REPORT].
CONTEXT:
Agency:
NAICS:
Contract type:
Security requirements:
Operational needs:
Incumbents:
Small business goals:
CONSTRAINTS:
Do not fabricate vendor capabilities.
CRITERIA:
Analyze:
- vendor landscape
- contract vehicles
- industry trends
- competition
- pricing considerations
VALIDATION:
Identify assumptions and intelligence gaps.
COMPLETE SAMPLE PROMPT
ROLE:
You are a federal acquisition analyst conducting FAR Part 10 market research.
OBJECTIVE:
Develop a market research report for an enterprise IT help desk procurement.
CONTEXT:
Agency:
Department of Labor
NAICS:
541512
Contract Type:
Hybrid FFP/T&M
Security Requirements:
CMMC Level 2 equivalent controls
FedRAMP Moderate cloud support
Operational Needs:
24/7 help desk support
Remote user support
Cloud application support
Incumbents:
Large incumbent with 7-year tenure.
Small Business Goals:
SDVOSB preference if capable vendors exist.
CONSTRAINTS:
Do not fabricate vendor capabilities.
Use evidence-based analysis only.
CRITERIA:
Analyze:
- available vendors
- contract vehicle alignment
- industry pricing trends
- operational risks
- socioeconomic participation
VALIDATION:
Identify intelligence gaps and assumptions requiring CO review.
Expected output
Market research report, vendor analysis, contract vehicle recommendations, competitive landscape summary, socioeconomic analysis, and operational risk findings.
Phase 3 - Capture Strategy
Contractor Role - Capture Manager
Recommended inputs
Incumbent analysis, customer pain points, agency strategic plans, competitive intelligence, past performance, partner capabilities, pipeline notes, call reports, and OKL proposal lessons learned.
TEMPLATE
ROLE:
You are acting as a [CAPTURE MANAGER].
OBJECTIVE:
Your objective is to [DEVELOP A CAPTURE STRATEGY].
CONTEXT:
Agency:
Incumbent:
Competitors:
Contract vehicle:
Customer pain points:
Past performance:
Differentiators:
CONSTRAINTS:
Do not fabricate customer intelligence.
CRITERIA:
Develop:
- win themes
- discriminators
- teaming recommendations
- pricing considerations
- customer engagement strategy
VALIDATION:
Identify assumptions and intelligence gaps.
COMPLETE SAMPLE PROMPT
ROLE:
You are a senior federal capture manager.
OBJECTIVE:
Develop a capture strategy for a VA enterprise cloud modernization opportunity.
CONTEXT:
Agency:
Department of Veterans Affairs
Incumbent:
Large systems integrator with strong incumbent relationships.
Competitors:
Guidehouse
Leidos
Booz Allen
Small cloud-focused SDVOSBs
Contract Vehicle:
T4NG2
Customer Pain Points:
Slow modernization
Fragmented cloud governance
Operational silos
Legacy infrastructure
Past Performance:
DOL enterprise modernization
FDIC data modernization
State Department cloud support
Differentiators:
Strong PMO governance
AI-enabled operational analytics
Cloud modernization experience
FedRAMP-aligned delivery
CONSTRAINTS:
Do not fabricate customer intelligence.
CRITERIA:
Develop:
- win themes
- competitor assessment
- teaming recommendations
- customer engagement strategy
- pricing considerations
VALIDATION:
Identify intelligence gaps requiring additional customer engagement.
Expected output
Capture strategy, SWOT analysis, competitive positioning, win themes, customer engagement recommendations, risk analysis, and teaming strategy.
Phase 4 - Proposal Development
Contractor Role - Proposal Manager
Recommended inputs
Full solicitation, Sections C/L/M, attachments, PWS, proposal outline, past performance, resumes, staffing plans, compliance templates, and OKL proposal repository.
COMPLETE SAMPLE PROMPT
ROLE:
You are a federal proposal manager.
OBJECTIVE:
Develop a compliance matrix and proposal outline.
CONTEXT:
Agency:
Department of State
Solicitation:
Global IT Service Desk Support
Evaluation Criteria:
Technical
Past Performance
Price
Key Requirements:
24/7 support
Tier 1-3 escalation
ITIL alignment
FedRAMP support
Page Limits:
Technical volume limited to 75 pages.
CONSTRAINTS:
Do not omit mandatory requirements.
CRITERIA:
Extract:
- instructions
- evaluation factors
- staffing requirements
- certifications
- deliverables
- submission instructions
VALIDATION:
Flag ambiguities and missing attachments.
Expected output
Compliance matrix, proposal outline, requirement extraction, proposal risks, evaluation mapping, and staffing requirement summary.
Phase 5 - Program Execution
Contractor Role - Program Manager
Recommended inputs
KPI reports, SLA reports, staffing reports, risk registers, financial data, customer feedback, PMO dashboards, transition plans, and OKL operational lessons learned.
COMPLETE SAMPLE PROMPT
ROLE:
You are a federal program manager.
OBJECTIVE:
Develop an operational performance assessment for executive leadership.
CONTEXT:
Contract:
Enterprise IT Operations Support
KPIs:
98% SLA compliance
4% ticket backlog increase
Improved first-call resolution
Risks:
Staffing shortages
Cloud migration delays
Customer Concerns:
Escalation responsiveness
Reporting consistency
Financial Performance:
Within budget but margin compression increasing.
CONSTRAINTS:
Do not conceal operational risks.
CRITERIA:
Assess:
- staffing health
- operational trends
- customer satisfaction
- delivery risks
- financial impacts
VALIDATION:
Identify escalation items requiring executive review.
Expected output
Operational assessment, KPI analysis, staffing analysis, risk assessment, executive summary, and corrective action recommendations.
Universal Reusable ROCCCV Template
ROLE:
You are acting as a [ROLE/TITLE].
OBJECTIVE:
Your objective is to [TASK OR DELIVERABLE].
CONTEXT:
Agency/Organization:
Mission:
Program:
Acquisition Phase:
Contract Type:
Stakeholders:
Operational Environment:
Known Challenges:
Budget Constraints:
Security Requirements:
Relevant Documents:
Past Performance:
Schedule Constraints:
Customer Pain Points:
Technology Environment:
Compliance Requirements:
CONSTRAINTS:
- Align with FAR/DFARS and agency policy.
- Do not fabricate information.
- Distinguish assumptions from facts.
- Maintain professional acquisition language.
- Flag areas requiring human review.
CRITERIA:
Develop or analyze:
- risks
- dependencies
- compliance requirements
- operational impacts
- strategic recommendations
- staffing implications
- governance concerns
- measurable outcomes
VALIDATION:
- Identify missing information.
- Flag ambiguities.
- Recommend SME/legal review.
- Ensure traceability to acquisition requirements.
TEMPERATURE GUIDANCE:
- 0.1-0.3 = compliance/pricing
- 0.4-0.6 = proposals/strategy
- 0.7-1.0 = brainstorming/innovation
EXPECTED OUTPUT FORMAT:
Specify:
- matrix
- briefing
- roadmap
- SWOT analysis
- proposal section
- compliance checklist
- executive summary
- acquisition strategy
- staffing plan
- risk register
Recommended References
Federal acquisition
- Acquisition.gov
- Federal Acquisition Regulation (FAR)
- DFARS
- Defense Acquisition University (DAU)
- NCMA
- APMP
AI governance and security
- NIST AI RMF
- NIST SP 800-53
- NIST SP 800-171
- FedRAMP
- CMMC Program
