Emergency Procurement of AI: How Government Agencies Buy Fast When They Need To

Why Standard Competition Fails Urgent AI Needs

Full and open competition under FAR Part 15 is the default for federal acquisitions over the simplified acquisition threshold. The default is also slow by design: market research, draft solicitation, industry day, RFP release, proposal preparation, evaluation, source selection, debriefing, protest window, award. The sequence is structured to maximize competition and minimize challenge, and for most agency requirements those goals are correctly prioritized.

Urgent AI requirements break the default in three ways.

First, the operational clock runs faster than the procurement clock. When CMS issues a regulatory change with a 90-day implementation window, when a state Medicaid agency starts losing 100,000 enrollees per month to procedural disenrollment, when a VA medical center loses 30% of its call-center capacity in a single quarter to attrition, the agency cannot wait 14 months to begin competition for a new system. Either the operational problem gets worse or the agency stops meeting its statutory obligations.

Second, the technology itself is moving faster than the procurement process. AI voice capability that did not exist 18 months ago is now production-grade. Agencies that wrote AI requirements documents in 2024 are finding that those documents already specify obsolete approaches. Standard FAR Part 15 procurement is structured to evaluate stable specifications; rapidly evolving technology rewards agencies that can move in months rather than years.

Third, congressional and administration pressure is rarely patient. When OMB or HHS issues a memorandum on AI use cases, when a state legislator demands action on Medicaid procedural disenrollment, when a federal agency is publicly tagged for poor language access, the agency leader needs to point to operational change in months, not years. Standard competition makes that promise impossible.

The good news is that federal acquisition law anticipates exactly this category of need and provides specific authorities for it. The agency that knows which authority fits which situation, and the AI vendor that arrives with the documentation already prepared, can compress procurement timelines by 70-90% without compromising the integrity of the file.

The Six Fast-Track Mechanisms

• FAR 6.302-2 Unusual and Compelling Urgency. Permits limiting competition (sole source or limited sources) when the Government would be seriously injured by the delay required for full competition. Used for short-duration urgent contracts, often 12 months or less. The contracting officer documents the urgency, the steps taken to maximize competition within the time available, and the rationale for the source(s) selected, in a Justification and Approval (J&A) signed by the appropriate official based on dollar value. J&A is publicly posted on SAM.gov 14 days after award (or with redactions earlier).
• FAR Part 13 Simplified Acquisition. For acquisitions at or below the Simplified Acquisition Threshold (SAT - currently $250,000 for most acquisitions, with $750,000 available for certain commercial items). Permits shorter solicitation periods, simplified evaluation, government purchase cards, BPA call orders, and reduced documentation. Below the micro-purchase threshold ($10,000 for most categories), purchases can be made without competition by a warranted purchase card holder.
• FAR 16.703 / 16.704 BPA Call Orders. Where the agency has an established Blanket Purchase Agreement with one or more vendors (typically against GSA MAS), BPA call orders can be issued in days to weeks rather than months. The competition occurred at BPA establishment; calls under the BPA are streamlined.
• GSA MAS / Cooperative Vehicle Task Orders. Task orders issued against an existing GSA MAS contract or cooperative vehicle (NASPO ValuePoint, Texas DIR, Sourcewell, OMNIA Partners, NCPA, COSTARS) compress the procurement timeline because the master contract competition is already complete. State and federal agencies use cooperative vehicles routinely for urgent buys.
• Bridge Contracts. Short-duration contracts that bridge the gap between an expiring contract and the new full-and-open competition. Bridges typically run 6-12 months and are awarded to the incumbent under FAR 6.302-2 urgency or under a sole-source J&A. Bridges are common when an underlying re-procurement slips.
• Other Transaction Authority (OTA). Granted by Congress to specific agencies (DoD, DHS, NIH, NASA, FAA, ARPA-H, others). OT agreements are not subject to most FAR provisions and can be executed in weeks. For AI, OTAs are common in prototype and pilot phase, often through consortia such as DIU, Tradewind, IWRP, MD5, and several health-OTA vehicles. Production scaling typically transitions to a FAR-based vehicle.

How an Emergency AI Procurement Actually Runs

1. Operational trigger documented. The agency program office documents the operational event creating the urgency - the specific deadline, the specific harm to the Government if the standard competition timeline is followed, the affected population, the date by which the capability must be operational. This document becomes the foundation for any J&A.
2. Mechanism selection. The contracting office and program office select the mechanism that fits the dollar value and the operational profile. Under SAT? Simplified acquisition. Limited duration urgent? FAR 6.302-2. Existing BPA? Call order. Existing GSA MAS schedule with relevant vendors? MAS task order. OT agency with OTA available? OT.
3. Market research compressed. Even fast-track mechanisms require market research proportionate to the acquisition. For urgent AI buys, this means a focused review of FedRAMP-authorized AI voice vendors with specific past performance on the use case, capability statements gathered, and a documented basis for source selection.
4. J&A drafted (where required). For 6.302-2 sole source or limited sources, the contracting officer drafts the Justification and Approval. The J&A documents the urgency, the harm to the Government, the steps taken to maximize competition, and the source rationale. Approval level depends on dollar value (CO for under $750K, head of contracting activity for $750K-$15M, senior procurement executive for over $15M, agency head for over $100M).
5. Solicitation issued with compressed response time. Even on fast-track, agencies typically issue a solicitation to the selected source(s) requiring a written proposal. Response times of 5-10 business days are common for urgent requirements, compared to 30-60 days for standard acquisitions.
6. Proposal evaluation. Streamlined evaluation focused on technical capability, past performance, and price. Source selection statement documents the basis for award.
7. Pre-award compliance. SAM.gov registration verified, FAR clauses incorporated, security and IT compliance verified, Section 508 compliance confirmed, AI use-case inventory entry per OMB M-24-10.
8. Award. Contract executed. Performance start date set.
9. Post-award protest window. 5-10 calendar days for GAO protest filing depending on the path. Any protest stays performance unless an override is executed.
10. Performance kickoff. Initial deployment scoped to the urgent need. Continuous monitoring and reporting cadence established. Bridge transition plan documented from day one.

Use Cases That Justify Emergency Procurement

Medicaid Unwinding and Procedural Disenrollment Surges

States that experienced sudden spikes in procedural disenrollment during the redetermination wave used FAR 6.302-2 (at the federal grant level) and state-level emergency procurement authorities to deploy AI outbound recertification campaigns within 30-60 days. The operational harm - hundreds of thousands of eligible enrollees losing coverage procedurally - is documentable and quantifiable.

VA Crisis Line and Veterans Crisis Line Continuity

Capacity continuity for the Veterans Crisis Line (988 Press 1) and VA medical center call centers is mission-critical. Sudden capacity gaps - attrition spikes, BPO contract failures, surge events - have triggered urgent AI capacity adds under FAR 6.302-2.

CMS Reporting and Implementation Deadlines

When CMS issues a regulatory change with a fixed implementation deadline (eligibility verification system change, Section 1557 language access tighter requirement, MARS-E version update), affected contractors and state agencies face a hard wall. Emergency procurement authorities are commonly invoked to reach the deadline.

Disaster Recovery and FEMA-Funded Operations

Stafford Act-funded disaster operations carry emergency procurement authority directly. State and local agencies stand up disaster-specific call centers using FAR-equivalent or state emergency authority and increasingly include AI voice as a force multiplier.

Public Health Emergency Response

Pandemic response, vaccine campaign call centers, post-recall outreach, environmental health hotlines. Both federal and state emergency procurement authorities are activated; AI voice is often the only capability that scales fast enough.

Court Backlog and Justice-System Continuity

Court backlogs in jurisdictions affected by natural disaster, courthouse closures, or system outages have invoked emergency authorities to reach FTA reduction and case status capacity quickly.

Statutory Compliance Gaps Identified Mid-Year

HHS Office for Civil Rights findings, DOJ Title VI consent decrees, GAO findings - all create near-term compliance windows that emergency procurement authorities are appropriate to satisfy.

Cyber Incident Response

Where a cyber incident takes down a contact center or a self-service portal, emergency procurement authorities enable rapid stand-up of AI voice as a continuity capability.

Vehicles That Fit Inside Emergency Procurement Pathways

• GSA Multiple Award Schedule (MAS). SIN 54151S (IT Professional Services), SIN 541611 (Management Consulting). Task orders against MAS compress timelines because base-contract competition is already complete.
• 8(a) STARS III. 8(a)-only GWAC with $50B ceiling through 2029. Task orders to STARS III holders are common emergency procurement vehicles.
• CIO-SP4 (NIH NITAAC). IT services GWAC with HHS-heavy use; includes fast-track ordering procedures.
• SEWP VI (NASA). IT products and supporting services with rapid award capability.
• VA T4NG2 and VECTOR. VA's primary IT vehicle (T4NG2) and SDVOSB-focused vehicle (VECTOR).
• Agency 8(a) BPAs. Pre-established agency-specific BPAs that issue calls in days. CMS, VA, SSA, CDC, HRSA, IHS, and many other HHS agencies maintain 8(a) BPAs for recurring services.
• HHS Program Support Center BPAs. HHS-wide BPAs frequently used for contact-center scope.
• OASIS+ and OASIS+ 8(a) / SDVOSB / WOSB / HUBZone Pools. Multi-pool GSA vehicle with small business reserves; supports rapid task ordering.
• FedRAMP Marketplace inheritance. Vendors with current FedRAMP authorization compress security review from months to weeks during emergency procurement.
• State cooperative purchasing. NASPO ValuePoint, Texas DIR, Sourcewell, OMNIA Partners, COSTARS, NCPA, TIPS-USA. BetaQuick delivers Texas DIR scope through partner Compass Solutions, LLC (DIR-CPO-6057, active through October 2030).
• OT consortia. Defense Innovation Unit (DIU), Information Warfare Research Project (IWRP), Tradewind (DoD), MD5, ARPA-H consortia.

Documentation and Compliance Inside the Fast Path

Emergency procurement compresses time. It does not eliminate documentation. Every FAR clause, every security control, every privacy review, and every AI governance obligation that applies to a standard FAR Part 15 award also applies to a 6.302-2 sole source. The difference is that the documentation is staged and prioritized rather than completed end-to-end before award.

• FAR clauses. All applicable FAR clauses incorporated by reference. Commercial item determination if FAR Part 12 commercial item procedures are used.
• SAM.gov registration and SBA size certification. Verified before award. Active registration is non-negotiable.
• Cybersecurity baseline. NIST 800-171 for unclassified controlled information; FedRAMP Moderate or High for cloud-hosted AI; CMS ARS or MARS-E for CMS-related work; CMMC where DoD-adjacent.
• FAR 52.204-21 / 52.204-25 / 52.204-26. Basic safeguarding, prohibition on covered telecommunications, representation regarding covered telecommunications.
• Section 889 compliance. Prohibition on procurement of certain Chinese telecommunications and video surveillance equipment - vendor representation required.
• Section 508 accessibility. Voluntary Product Accessibility Template (VPAT) on file.
• OMB M-24-10 AI use-case inventory. Federal agencies must inventory AI use cases. Emergency procurement does not exempt the agency from this inventory; it must be completed at award.
• NIST AI Risk Management Framework alignment. Model governance documentation, risk assessment, human oversight documentation.
• EO 14028 supply chain. SBOM delivery in CycloneDX or SPDX format; signed artifacts; secure development attestation.
• HIPAA BAA, 42 CFR Part 2 QSOA. Where the AI handles PHI or SUD records, executed before any operational call.
• Privacy Impact Assessment. Required for federal AI systems handling PII; can be drafted in parallel with award but must be in place before performance.
• FOIA exposure. J&A becomes publicly posted on SAM.gov within 14 days of award. Agencies should redact source-selection sensitive material accordingly.
• Continuous monitoring obligations. Even short-duration urgent contracts carry continuous monitoring duties from go-live.

What Reviewers and Auditors Look For

Bridge Contracts and Transitions to Permanent Vehicles

Most emergency-procurement awards are intentionally short-duration. The agency uses the urgent path to begin operational delivery and runs full competition in parallel for the follow-on. The transition matters as much as the initial award.

• Document the transition plan at award. The contract file should include a documented plan for the follow-on - which vehicle, which solicitation timeline, when the transition begins.
• Parallel competition. Run the full and open competition for the steady-state requirement in parallel with the urgent contract performance.
• Build past performance during the urgent contract. The vendor's performance under the urgent award builds the past-performance record that informs the steady-state competition.
• Avoid serial bridge extensions. Single bridge extensions are routine; multiple sequential bridges trigger GAO and OIG attention. The presumption is full and open competition; bridges are exceptions.
• Plan for data and IP transition. If the steady-state vendor differs from the urgent vendor, the contract must include data return and AI model handoff provisions.
• Continuity of operations. The transition itself must be planned so service does not lapse during the cutover.
• Document lessons learned. Emergency procurement files frequently surface during agency procurement-process reviews. The agency's lessons-learned writeup is the artifact that justifies the use of urgency authorities and improves the next emergency response.

What an AI Vendor Must Have Ready

Emergency procurement compresses the agency's timeline, which means the agency is selecting from the small pool of vendors who can show up with documentation already prepared. A vendor that arrives with a complete package wins; a vendor that needs 60 days to assemble basic compliance artifacts gets passed over.

• Active SAM.gov registration with verified UEI and CAGE. Non-negotiable. BetaQuick: SAM.gov active, UEI MDBYCN83MT69, CAGE 86Y32.
• Capability statement, current and tailored. One-page and full versions, with specific past performance citations and NAICS code coverage.
• FedRAMP-authorized stack. Or clearly documented inheritance from FedRAMP-authorized providers (Amazon Connect FedRAMP High, Azure OpenAI FedRAMP High, AWS Transcribe FedRAMP, Azure Speech Services FedRAMP).
• Past performance dataset. Specific metrics (containment rate, abandonment reduction, languages supported) from comparable deployments.
• Pricing template. GSA MAS price list, cooperative-vehicle pricing, or readily-derivable rate card.
• Section 508 VPAT. Current.
• SBOM in CycloneDX or SPDX. Ready to deliver.
• NIST AI RMF documentation. Model governance, risk assessment, human-in-loop documentation.
• HIPAA BAA template. And, where applicable, 42 CFR Part 2 QSOA template.
• Section 889 representation. Documented.
• Subcontractor and partner letters. Where the vendor expects to team for the urgent scope.
• 30-day deployment plan. Concrete. With staffing, integration sequence, and risk mitigation.

Frequently Asked Questions