? ?3
JD Jane Doe ?
Track A Government (Acquisition Workforce) Contracting Officer
Module 1

Acquisition Lifecycle Orientation and Mission Need Identification

Estimated time: 30-45 min Regulatory: FAR Part 7, FAR Part 10, NIST AI RMF 1.0
Lifecycle module illustration
Guided prerequisite flow

Welcome & Orientation

Start with what the lifecycle covers, why it matters, and where it fits before moving into operations, governance, and validation.

Step 1 of 8

Welcome & Orientation

This prerequisite module explains the full federal acquisition lifecycle from mission need through closeout, why each stage matters, which regulations govern the work, and how both government and contractor teams participate differently across the same process.

What this module covers
  • What the acquisition lifecycle covers from start to finish
  • Why early planning and downstream oversight are connected
  • Which outputs, artifacts, and reviews appear across the lifecycle
  • How FAR, DFARS, NIST, and OMB guidance shape AI-enabled work
Estimated time 30-45 minutes to complete the prerequisite and unlock the next role-based module.
What you will produce A lifecycle understanding that supports better planning, safer AI use, and cleaner handoffs into role-specific training.
Why this matters Lifecycle mistakes create downstream risk in competition, pricing, evaluation, security, performance, records, and auditability.
Key references FAR Parts 4, 5, 7, 8, 10, 11, 12, 13, 15, 16, 17, 19, and 39; DFARS cyber clauses; NIST AI RMF; OMB AI guidance.
Government perspective Government teams define the need, shape the acquisition strategy, publish and evaluate the solicitation, make award decisions, oversee performance, and preserve the official contract record.
Contractor perspective Contractors interpret market signals, qualify opportunities, capture requirements, propose and price solutions, transition into delivery, maintain compliance, and position for recompete.
Dual-perspective value The strongest practitioners understand both sides of the lifecycle so they can reduce friction, improve documentation quality, and align AI-assisted outputs to how acquisition decisions are actually made.
Step 3 of 8

Operational Overview

Walk through the lifecycle stage by stage to see what government teams do, how contractors respond, what documents matter, where AI can help, and what human approvals still control the work.

Stage Key references Government team impact Contractor impact AI-enabled workflow controls Evidence / platform artifact
1. Mission Need and Requirements Definition FAR Parts 7, 10, and 11; OMB A-11; OMB A-123; NIST AI RMF; OMB M-25-21; Section 508; Privacy Act; Paperwork Reduction Act. Define mission need, acquisition assumptions, accessibility, privacy, data sensitivity, and whether AI use is appropriate. Understand agency mission, buyer pain points, early requirements, constraints, and possible compliance triggers. Use-case intake, data sensitivity review, human approval, source grounding, prompt logging, and hallucination checks. Mission need statement, planning notes, requirements traceability matrix, and AI-use assessment.
2. Market Research and Acquisition Planning FAR Parts 7, 10, and 19; Competition in Contracting Act; Small Business Act; category management; GSA BIC guidance. Assess competition, small business strategy, vehicle options, pricing intelligence, and acquisition approach. Shape opportunity strategy, validate fit, monitor RFIs and sources sought, and prepare capability responses. Market scans must use cited sources, separate facts from assumptions, and preserve the audit trail. Market research report, sources sought response, vendor landscape, and bid or no-bid notes.
3. Acquisition Strategy and Procurement Method FAR Parts 8, 12, 13, 15, 16, 17, and 39; agency supplements; FedRAMP; NIST SP 800-53; EO 14028; OMB M-22-09 Zero Trust. Choose contract type, vehicle, evaluation method, competition strategy, cloud or cyber clauses, and baseline security controls. Align teaming, pricing, contract vehicle access, technical solution, and compliance posture. Document decision rationale, avoid unsupported recommendations, and flag missing or weak data. Acquisition strategy, vehicle analysis, risk register, pricing assumptions, and cyber applicability checklist.
4. Solicitation Development FAR Parts 5, 11, 12, 13, 15, 19, 22, 39, and 52; FAR 52.204-21; DFARS 252.204-7012 and 252.204-7021; Section 508; OCI rules. Draft RFP or RFQ Sections C, L, and M, evaluation factors, clauses, data rights, labor rules, cybersecurity, and reporting requirements. Analyze Sections C, L, and M, build compliance and clause matrices, and confirm instructions, flowdowns, and labor implications. AI summaries of solicitation content must always be validated against source documents and cited clauses. Solicitation shred, compliance matrix, clause matrix, question log, and proposal outline.
5. Proposal or Quote Development FAR Parts 15, 31, 44, 52; CAS where applicable; SCA or DBA where applicable; CMMC; FedRAMP; NIST SP 800-171 and 800-172. Prepare to evaluate only responsive offers against the stated criteria and protect procurement integrity throughout the process. Prepare compliant technical, management, past performance, pricing, subcontracting, and security volumes. AI may assist drafting, gap checks, compliance reviews, and structure, but all final content must be human-validated and source-grounded. Proposal compliance matrix, pink/red/gold review logs, pricing model, and past performance crosswalk.
6. Evaluation and Source Selection FAR 15.304, 15.305, 15.306, and 15.308; Procurement Integrity Act; OCI rules; GAO protest standards. Document strengths, weaknesses, risks, and rationale while protecting source selection information and avoiding bias. Respond to discussions, clarifications, or ENs and defend realism, responsibility, and technical merit where asked. AI cannot replace evaluator judgment; outputs must be explainable, auditable, bias-reviewed, and traceable. Evaluation worksheet, consensus report, source selection decision document, and debriefing record.
7. Award and Contract Formation FAR Parts 9, 16, 32, 42, 43, 44, 46, 49, and 52; SAM responsibility checks; CPARS; CMMC; FedRAMP ATO where applicable. Make the responsibility determination, finalize award, confirm reporting and security requirements, and set transition expectations. Confirm award obligations, staffing, insurance, security, subcontractor flowdowns, and kickoff readiness. AI-assisted award documentation must preserve rationale and never alter official contract language without review. Award file, responsibility determination, kickoff deck, transition plan, and subcontractor compliance plan.
8. Transition and Implementation FAR Parts 42 and 46; QASP; CDRLs; NIST SP 800-53; FedRAMP continuous monitoring; NIST SP 800-137; ITIL, PMI, or Agile practices where applicable. Establish oversight cadence, COR responsibilities, deliverables, quality metrics, and security monitoring expectations. Mobilize staff, systems, reporting, quality assurance, deliverables, and risk management practices. Use approved data boundaries, role-based access, logging, output monitoring, and human review before relying on AI-generated implementation support. Project management plan, QCP, QASP alignment, risk and issue log, and onboarding tracker.
9. Performance Management and Oversight FAR Parts 42, 46, and 52; CPARS; Prompt Payment Act; FedRAMP continuous monitoring; CMMC; NIST SP 800-171 and 800-172. Monitor performance, invoices, deliverables, cybersecurity, privacy, records, and contract modifications. Deliver services, report performance, maintain compliance, support audits, and manage subcontractors. Performance dashboards need source data controls, change logs, reviewer approval, and anomaly checks. Monthly status report, SLA/KPI dashboard, CPARS inputs, POA&M, and incident log.
10. Modifications, Renewals, and Recompete FAR Parts 43, 6, 15, 17, and 42; option exercise rules; J&A rules; competition requirements. Justify modifications, exercise options correctly, update requirements, and preserve competition integrity. Support contract changes, option readiness, pricing updates, recompete capture, and lessons learned. AI analysis must distinguish contract facts from assumptions and identify scope-change risk. Modification package, option memo, recompete strategy, lessons learned, and updated compliance matrix.
11. Closeout, Records, and Lessons Learned FAR Part 4, FAR 4.805, FAR Parts 45 and 49, NARA records rules, Federal Records Act, and FOIA considerations. Close contract files, resolve invoices and property, retain records, and document lessons learned. Submit final reports and invoices, complete property disposition and security closeout, and close subcontractors. AI-generated closeout summaries must retain source links, records classification, and approval history. Closeout checklist, final invoice, property record, records disposition file, and lessons learned report.
Step 2 of 8

Core Concepts

Before you work inside any acquisition phase, you need the shared vocabulary: who owns decisions, what the process produces, when reviews occur, where official evidence lives, and how AI supports work without replacing authority.

How to read this lifecycle
  • Big A acquisition is the government’s full lifecycle of planning, competing, awarding, overseeing, modifying, and closing the work.
  • small a execution is the contractor’s response cycle once opportunity signals become real work: qualify, capture, propose, price, transition, deliver, and recompete.
  • Both sides see the same procurement, but they own different decisions, approvals, risks, and outputs.
Government roles and authority
  • Program offices define need and outcomes.
  • Contracting officials maintain procurement authority, competition integrity, and contract file discipline.
  • Legal, budget, security, accessibility, and oversight functions validate risk, policy, and feasibility.
Contractor awareness and response
  • Contractors interpret opportunity signals, assess fit, build capture strategy, prepare proposals, price realistically, and execute after award.
  • Success depends on understanding the government’s process accurately rather than treating acquisition as only a proposal event.
  • AI must stay within approved data boundaries and cannot replace review, pricing accountability, or legal/compliance validation.
Step 4 of 8

Step-by-Step Workflow

Follow the operational sequence from identifying the mission problem through contract closeout. Each step shows what happens, who does it, why it matters, what evidence is produced, and where AI can support the work safely.

Step What happens Who Why it matters AI opportunity
1 Identify the mission problem Clarify the operational issue, the desired mission outcome, and the performance gap before choosing any solution. Program office, contracting, budget, legal, security, accessibility. Poorly framed needs create downstream problems in competition, pricing, evaluation, and protest defensibility. Summarize source documents and produce structured planning checklists.
2 Test the market and acquisition approach Assess the vendor landscape, small business strategy, available vehicles, and likely pricing realities. Contracting, market research, small business, program office. The market determines whether the strategy is realistic, competitive, and compliant. Compare vendors, summarize sources sought responses, and surface market patterns with citations.
3 Document strategy, method, and controls Set the contract type, evaluation logic, security posture, and risk rationale before publishing the work. Contracting officer, cost/price analysts, legal, security, program management. The strategy becomes the foundation for the solicitation, evaluation, and award record. Draft rationale summaries, compare contract types, and flag missing supporting evidence.
4 Publish and interpret the solicitation The government issues the package while contractors shred, map compliance, and organize proposal execution. Government contracting teams; contractor capture, proposal, pricing, contracts, and technical staff. Sections C, L, and M define how responsive proposals are built and judged. Clause extraction, compliance matrices, question logs, and proposal outline support.
5 Evaluate, award, and transition Published criteria are applied, award decisions are documented, and both sides prepare for execution. Evaluation boards, contracting authority, legal, program office, and selected contractor teams. This is where defensibility, procurement integrity, and transition readiness matter most. Organize evaluation evidence, summarize discussion themes, and build transition readiness checklists.
6 Oversee performance, modify, and close out Contracts are administered through delivery, modification, records retention, lessons learned, and closeout. CORs, contracting, finance, program staff, delivery teams, and closeout support roles. Performance evidence, records discipline, and closeout actions complete the lifecycle. Status summaries, compliance dashboards, risk logs, and closeout summary support with source traceability.
Step 5 of 8

Interactive Scenario

Practice how lifecycle work is structured with AI support. Start with a simple prompt you can use now, then mature it with ROCCCV, approved OKL inputs, AGEF-style review controls, and an audit-ready record before you move into the knowledge check.

Scenario A civilian agency wants to modernize its case management environment. The program office says, “We need a vendor to build us a new platform quickly.”
Task path
Task focus Rewrite the mission problem

Authoritative inputs (OKL)
    Expected output
    AI support boundary
    Maturity path
    Write or refine your prompt
    Prompt score
    0

    Write a prompt to score your lifecycle task work.

    Feedback and governance review
    Expected outputs and audit trail

    What a weak output may look like

    What a compliant output should look like

    Stronger prompt example

    Current audit capture

    Saved scenario records
    No saved scenario prompt records yet.
    Step 7 of 8

    Review & Key Takeaways

    Before you complete the prerequisite, reinforce the lifecycle ideas that will carry forward into every role-based module.

    What to remember
    • The lifecycle starts with mission need identification, not with a preferred solution.
    • Every downstream phase depends on how well planning, market research, and strategy are documented up front.
    • Government and contractor teams share the same acquisition, but their responsibilities are not the same.
    AI boundary
    • AI supports analysis, structure, summarization, and draft artifacts.
    • AI cannot replace procurement authority, evaluation judgment, pricing accountability, legal review, or security approval.
    • Traceability, source grounding, and reviewer approval are what turn AI output into usable acquisition evidence.
    What comes next
    • You’ll move into your role-based module path with a clearer understanding of where each phase fits.
    • The next module builds on this lifecycle foundation with deeper phase execution aligned to your perspective and role.
    • Completion here unlocks the recommended path and preserves your prerequisite status.
    Knowledge check

    Verify that you understand the lifecycle before moving on.

    Score at least 4 out of 5 to complete the prerequisite module and unlock the next step in your guided path.

    1. What is the main difference between Big A acquisition and small a acquisition?

    2. Which statement best describes what contractors do during the solicitation and proposal stage?

    3. Why is traceability important in acquisition work?

    4. What is the correct role of AI in this training program?

    5. Which reference set is most central to this lifecycle overview?

    Return to training path setup
    Award earned - Lifecycle Overview complete

    Prerequisite completed and saved.

    You can now continue directly into the next module in your recommended path.

    Continue to next module Return to training path