AFCAP Volume II: ACO Field Execution

The Field Side

From Appointment Letter to a Working File

If you haven't read AFCAP Volume I yet, that one covers what AFCAP is, who holds the contracts, and how a task order gets awarded. This volume picks up after the task order is on contract and you're the one administering it.

1 Who's Who in AFCAP (And Why It Matters)

AFCAP is run from Tyndall AFB, Florida, by the 772d Enterprise Sourcing Squadron. The Procuring Contracting Officer (PCO) sits there. So does the AFCAP Team Lead, the Flight Chief, and the buyers who actually award the task orders. As the Administrative Contracting Officer (ACO), you sit somewhere else: a forward base, an Area of Responsibility (AOR) location, or a stateside reachback site. You administer task orders the Tyndall team awarded.

That geographic split is the most important thing about your job, and it's the part most appointment briefings skim over. Every authority you have is delegated from Tyndall, every problem you can't solve gets escalated back to Tyndall, and every relationship you build with the people there is going to determine how fast you can move when something goes sideways.

          The cast of characters. Here's who you'll be working with regularly. Memorize the roles before you memorize the names. People rotate, the roles don't.
        

          PCO (Tyndall). The Procuring Contracting Officer. They awarded the task order and own the contract. Every modification you draft has to be reviewed and approved by their flight before you award it. Big issues, scope questions, and urgent changes all route back to the PCO.
        

          AFCAP Team Lead (Tyndall). The senior ACO/PCO who runs the AFCAP section. They sign your appointment letter. If you can't get answers from the PCO or the program managers, the Team Lead is your next call. From the source training: "If you're not getting the answers you need, then contact the AFCAP Team Lead."
        

          Flight Chief (Tyndall). Reviews and approves every modification before you award it. The chain is: You draft → Flight Chief reviews → You award, upload to KTFS, distribute. The Flight Chief isn't a rubber stamp; they're the guardrail on your authority.
        

          AOR Program Manager (PM). Works the requirement on the customer side. Coordinates with Shaw on funding, works with the COR/customer to finalize the Performance Work Statement (PWS), and brings new work or scope changes to you for execution. The PM speaks for the customer to the contracting team. They are not the customer themselves.
        

          COR / QAP. The Contracting Officer's Representative and the Quality Assurance Personnel watch performance on the ground. They submit the monthly PAR. They write up CARs. They are your eyes. On AFCAP, they rotate every six months, so you'll meet a lot of them.
        

          Contractor. One of the AFCAP V holders (Amentum, ECC, Fluor, KBR, RMS, or Vectrus) depending on which prime won the task order. Their site lead and program manager will be your daily contact. Stay professional, stay collaborative, and stay clear of any direction that wanders outside the contract.
        

2 Why You Should Know Your PCO Personally

You can do this job competently as a stranger to your PCO. You can't do it well.

The reason is structural. As an ACO under the AFCAP delegation, your modification authority caps at $2M for scope increases (or your warrant ceiling, whichever is lower). Anything above that line, anything that touches scope in a contested way, anything urgent that needs an exception path, and anything where the contractor is starting to push back all has to involve the PCO. You're going to be on Teams with this person every week. You're going to be drafting language they'll review. You're going to be asking them to reach into the contract on your behalf when a problem grows past your delegation.

          Make the introduction early. In your first week, set up a 30-minute call with your PCO. Not about a problem. Just so they know your face, your task orders, and your operating posture. The next time you call them at 2200 because a contractor walked off site, they'll already know who you are.
        

The same logic extends to the Team Lead, the Flight Chief, and the AOR PM. The source training puts it bluntly: "Communicate issues to the Tyndall PCO early." Early means before it's a crisis. Early means before the customer is on a call demanding answers you don't have. Early means while there's still room to maneuver.

          The pattern that hurts. ACO sees a problem, decides to handle it locally, the problem grows, finally surfaces it when it's already on fire, and now Tyndall is reacting under pressure with no context. The way to avoid that is to read the PCO in earlier, not to move faster after the fact. Routine status updates beat heroic late saves every time.
        

3 Your First 30 Days

You just got your appointment letter. The previous ACO is rotating out in two weeks. You have access to a SharePoint site, a contractor email thread you don't fully understand, and a stack of task orders nobody's walked you through. The clock is ticking.

From the Source Training

"I'm here, now what? What do I do first? Who do I go to for help?"

This is the exact question the AFCAP team poses to new ACOs in the official training. The answer below is built directly off their guidance, with the practical sequencing experienced ACOs use to actually get there.

Days 1–3: Get oriented. Read your appointment letter front to back, including the delegation language. Know your dollar limits. Get KTFS access from the AFCAP Team Lead. Identify your PCO, the AOR PM(s), the CORs and QAPs assigned to your task orders, and the contractor site leads.

Days 4–10: Read every PWS. Every task order, every modification, every attachment. As the source training says: "Read the PWS's & talk to the PCO and/or PM's about each Task Order. Which TO's have issues? What are the issues? What has been done up to this point?" Build an issue inventory while you read: open PARs, late PARs, open CARs, pending mods, equitable adjustment discussions, contractor disputes, and funding concerns.

          Issue inventory format. One row per task order. Columns: TO number, contractor, PWS title, COR name, last PAR date, open issues, last action date, who owns the next move. This single document is going to make every Wednesday AFCAP meeting easier for the rest of your tour.
        

Days 11–20: Meet the CORs. Verify each one has a current designation letter and COR training certificate uploaded to KTFS. Walk them through monthly PAR expectations. Confirm they know their PWS. From the source: "Contract issues almost always center around lack of proper oversight." If a COR doesn't know what's in their PWS, you don't have oversight, you have paperwork.

Days 21–30: Establish your battle rhythm. Weekly Wednesday AFCAP meeting prep, monthly PAR review cadence, file upload routine, a personal escalation rule (e.g., "any single issue I can't resolve in 5 business days goes to the PCO"). Get on a regular call cadence with your PCO and your AOR PM. By day 30, the file should already look better than when you took it over.

          The 6-month turnover problem. AFCAP CORs rotate every 6 months. ACOs often rotate on a similar cycle. That means everything you build in the first 30 days has to survive without you. Documented, in KTFS, where the next person can find it. You are always preparing for your own turnover.
        

4 KTFS, JAM/SPM, and Why AFCAP Uses Its Own File System

Across the rest of the contracting world, COR files live in JAM (Joint Appointment Module) and SPM (Surveillance and Performance Monitoring). AFCAP doesn't use those. AFCAP uses KTFS. There's a reason, and it's worth understanding even if you've never thought about it.

          The math problem. Most AFCAP task orders run for 5 years. CORs rotate every 6 months. That means a single task order will see at least 10 different CORs over its life, usually more.
        

JAM and SPM weren't built for that. In JAM/SPM, each COR creates their own file location, and a new COR can only see files they created. So on a 5-year task order, you'd end up with 10 separate file locations, none of which can see the others. The next COR comes in blind. The history is gone. Every six months, the institutional memory resets.

KTFS solves it by giving the task order one continuous file location that every COR (and the ACO) can access. Designation letters, training certificates, monthly PARs, CARs, mods, and contractor correspondence all live in one place, organized by task order rather than by COR. When the new COR shows in, they can read what the previous COR documented. Continuity actually exists.

          Your KTFS habit. Upload everything, even when you don't think you'll need it again. Designation letters, training certs, PARs, CARs, mods, meeting notes, decision rationale. The next ACO is going to thank you. So is the next COR. So is the lawyer six months from now reading the file because something went sideways.
        

          Don't run a parallel file. The one mistake that actively makes things worse: keeping "your own" copy of the file on a personal SharePoint or laptop instead of in KTFS. When you rotate, that file disappears with you. Put it in KTFS. That's where the institutional memory lives.
        

5 The Monthly Performance Acceptance Report (PAR)

The PAR is the COR's monthly evaluation of contractor performance. It's submitted to you, the ACO, within 5 days of the end of the performance period. It's also the primary documentary record of how the contractor is doing, which makes it the foundation for every CAR, every equitable adjustment, every past-performance crossflow, and every conversation you'll ever have with the PCO about whether this contractor is meeting the standard.

If the PAR is good, your file is strong. If the PAR is pencil-whipped, your file is fragile, and you'll find out the hard way the first time you try to take a real action against the contractor.

The form has four sections. Sections A and B are the COR's monthly entries. Section C is the contractor's response. Section D is yours, the ACO's, for cases where there's a deficiency that needs resolution. (See the Sample Documents tab for a full layout.)

          Section A: General Information (Boxes 1–4). Stays the same each month for each task order, except the date and the COR name when there's a turnover.
        

          Section B: Performance (Boxes 5–9). The COR checks deficiency type (New, Repeat, or None) and rates each performance objective: Excellent, Very Good, Satisfactory, Marginal, Unsatisfactory.
        

          Section C: Contractor Validation (Boxes 10–12). Contractor signs and can refute markdowns. No COR action needed.
        

          Section D: Deficiency Resolution (Boxes 13–15). ACO uses this when there's a markdown that drives a CAR or an EA. No COR action needed.
        

          The four common COR mistakes you'll see.
          Pencil-whipping: rating everything Satisfactory or higher because nothing exploded that month, without actually checking. Friendliness drift: the COR has been on site with the same contractor for months and doesn't want to "hurt them" with negative comments. Signature errors: forgetting to sign, signing in the wrong block. PWS unfamiliarity: rating performance against a vague memory of what the work should look like, instead of the actual PWS objectives.
        

          Your PAR review job. When a PAR comes in, read it against the PWS. If the COR rated everything Satisfactory but you know there were three contractor issues that month, that's a conversation. Coach the COR. Don't just file the PAR. The file is what it says it is, and a soft PAR makes every later action harder.
        

6 Corrective Action Reports (CARs)

A CAR is a tool to bring a problem to the contractor's attention and give them a chance to correct it. It's also the paper trail that supports more serious actions like cure notices, terminations, and past-performance ratings, if the contractor doesn't fix the problem.

DoD has four levels of CARs, and the level depends on the severity of the nonconformity and the level of supplier management you need to get attention from.

          Level I: Correctable on the spot. Issued for a nonconformity that can be fixed immediately and where no further corrective action response is needed. Documented and issued to the supplier management level responsible for taking corrective action. The contractor doesn't even owe you a written response.
        

          Level II: Can't be corrected on the spot. Issued when the nonconformity needs time and a written response. Critical Safety Items (CSI) and Safety of Flight (SOF) characteristics are issued at this level at minimum. Directed to the supplier management level responsible for initiating corrective action.
        

          Level III: To the supplier's top management. Issued when the nonconformity is serious enough that you want senior leadership eyes on it. Repeat nonconformities within one year for the same single-point-failure SOF characteristic are Level III. May be coupled with contractual remedies (progress payment reductions, cost disallowances, business management system disapprovals). You don't have to issue a Level I or II first. All Level III CARs must be coordinated with the Contracting Officer.
        

          Level IV: Top management, with remedies. Issued when a Level III didn't work, or when the nonconformity is serious enough to warrant immediate contractual remedies (suspension of progress payments, suspension of product acceptance). Addressed to the supplier's top-level management.
        

          How to actually use the CAR. The mistake is treating CARs as punishment. They're documented opportunities to fix a problem. A well-written Level II CAR (clear finding, clear PWS reference, clear expectation, reasonable suspense date) usually gets a real corrective action response and the problem goes away. A vague CAR with a missing PWS reference and a 24-hour suspense gets pushback from the contractor and your file looks worse than the problem.
        

          The format. The CAR template (Sample Documents tab) has 12 blocks. The two that determine whether the CAR holds up are Block 7 Finding and Block 7 Finding Impact. The Finding has to cite the actual PWS paragraph and quote what was supposed to happen. The Finding Impact has to connect the deficiency to mission impact. Not "the contractor missed a requirement," but "the contractor missed this requirement and the consequence to the mission was X."
        

7 Equitable Adjustments (EAs)

An equitable adjustment is the Government's tool for not paying for services it didn't receive. Each EA is unique and there's no single formula. The basis is usually some combination of an estimated full-time equivalent (FTE) salary for missing labor, materials or expenses that didn't get incurred, overhead, and profit.

You assess EAs when the contractor didn't meet the PWS requirement and can't re-perform, or when the contractor doesn't have enough manpower at the location to meet the PWS at all.

Worked Example

The contractor proposed to meet a PWS requirement with 10 FTEs. On the ground, only 5 FTEs are at the location, and the services aren't being met.

Your EA basis is the salary of the 5 missing FTEs, plus their proportional share of materials, overhead, and profit. The contractor doesn't get paid for labor they're not providing.

          The military-backfill scenario. Sometimes the contractor's manning shortfall is so bad that the Air Force has to reroute military personnel to the location to do the work. From the source training: "This is UNSAT and ultimately goes against why AFCAP is here." In that case, the contractor is responsible for the cost of the military labor that backfilled them. That cost gets included in your EA.
        

          Build the file before you build the number. An EA that surprises a contractor doesn't survive a dispute. The PARs should have already documented the manning shortfall. The CAR should have already given the contractor a chance to correct. The Section D entries on the PAR should have already flagged the deficiency for resolution. By the time you assess the EA, the file should be telling the same story the EA tells.
        

8 Modifications and the $2M Line

Your appointment letter spells out exactly what you can and can't do as an ACO. The number that drives everything else in there is your modification authority cap.

          The standard AFCAP delegation.
          Scope increases: capped at $2M, or your individual warrant limit if it's less than $2M.
          Scope decreases: unlimited, or in accordance with your warrant level.
          All modifications and direction to the contractor: requires review and approval by 772 ESS/PKD/FC. The PCO facilitates the review process.
        

That last clause is the part new ACOs sometimes miss. Every modification, regardless of dollar value, has to be reviewed and approved by the Flight Chief at Tyndall before you award it. You don't get to issue mods unilaterally because you have a warrant. The delegation is conditional on the review chain.

          The mod review process.
          Step 1. ACO drafts the modification.
          Step 2. Flight Chief at 772 ESS/PKD/FC reviews and approves.
          Step 3. ACO awards the modification, uploads the executed copy to KTFS, and distributes to the COR(s), contractor, AOR PM(s), and PCO.
        

          Make the mod easy to review. When you draft a mod, write a one-paragraph cover note for the Flight Chief: what changed, why it changed, what authority supports it, what funding is being used, and any open issues. The Flight Chief reviews many mods a week from many ACOs. The clearer the package, the faster it comes back approved. Vague mods get returned for clarification, which costs you a day.
        

For new requirements, added or deleted PWS items, and anything that touches scope materially, the path is the same but the conversation starts earlier. The AOR PM works with Shaw on funding and with the COR/customer to finalize the PWS. Funding gets approved. Under $2M, the ACO executes. Over $2M, the Tyndall PCO and PM execute. Your job is to recognize which lane the action belongs in and route accordingly.

9 Undefinitized Contract Actions (UCAs)

A UCA is what you reach for when the mission can't wait for full negotiation. It's a binding commitment to a contractor before final terms, specifications, and price are agreed. The contractor starts performing immediately. You and the contractor finish negotiating the rest of the deal in parallel, on a clock, with hard limits on how much money can move before the contract is definitized.

UCAs live under DFARS 217.74. They are powerful, and they are also one of the most heavily controlled contracting actions in the entire DoD. Every part of the structure exists because UCAs have a history of being abused, with long-running undefinitized actions where the Government burned through obligation authority without ever pinning down what it was buying. The current rules are tight on purpose.

          A UCA is more than a fast task order. A fast task order is a competitive task order with a compressed schedule. The price is agreed before performance begins. A UCA is a contract action where the price has not yet been agreed and the contractor is already at work. Different categories. Don't use UCA shorthand to describe a normal urgent action.
        

When can you use one? Only when both of these are true: (1) negotiating a definitive contract action isn't possible in time to meet the Government's requirement, and (2) the Government's interest demands that the contractor be given a binding commitment so performance can begin immediately. Examples include unforeseen urgent requirements and contingency, humanitarian, or peacekeeping operations. Be as complete and definitive as the circumstances allow. Starting work before the conversation finishes is the point. Leaving the work loosely defined is not.

          Approval authority. The Contracting Officer must obtain approval from the Head of the Contracting Activity (HCA) before entering into a UCA, before modifying its scope after performance has begun, and before increasing obligations above the approved NTE via UCA modification. SAF/AQC has delegated UCA approval to the Senior Contracting Official (SCO) under AFFARS MP 5301.601(a)(i)(53). For AFICC, that's the AFICC Commander or Director of Contracting. SCOs may redelegate down to no lower than the COCO if the value is $50M or less.
        

          The Management Control Document (MCD). Every UCA approval starts with a Request for Authority to Issue a UCA. When approved, that document becomes the MCD. It has to include: why a UCA is required, why performance has to begin before definitization, the adverse impact of delay, the risks and mitigation, the specific contractual instrument, the obligation limitation, and the definitization schedule. (Sample Documents tab has the section breakdown.)
        

          NTE: the not-to-exceed price. Every UCA has to have an NTE, anchored to an Independent Government Cost Estimate, prior buys, or contractor proposal. The Purchase Request should obligate only enough funds to complete the undefinitized portion of the work. The NTE is a ceiling, not a budget.
        

          The 50 / 75 percent obligation limits. Before definitization, you cannot obligate more than 50 percent of the NTE. Once a qualifying proposal is received, you can go up to 75 percent. If the qualifying proposal comes in at less than the NTE, the 75 percent is calculated against the proposal price, not the NTE. No profit or fee is authorized for payment before definitization.
        

          The 180-day definitization clock. The UCA has to be definitized by the earlier of: (a) 180 days after the contractor submits a qualifying proposal, or (b) the date when obligated funds exceed 50 percent of the NTE. The 180-day clock cannot be extended beyond an additional 90 days without HCA approval (non-delegable).
        

          What's a "qualifying proposal"? A proposal with enough information that DoD can conduct meaningful analyses and audits. Only the Contracting Officer makes the determination that one has been received, in concert with the technical team, price analyst, policy, and legal advisor. If the proposal is incomplete, return it immediately for rework.
        

          Required clauses. Every UCA gets FAR 52.216-24 (Limitation of Government Liability) and DFARS 252.217-7027 (Contract Definitization). If you're incrementally funding, also include FAR 52.232-22 (Limitation of Funds). These clauses are the ones a court or board will look at if anything goes wrong.
        

          Reporting. UCAs at or above $5M have to be entered and updated in the UCA Reporting Tool semi-annually (NLT 10 April and 10 October). Anything more than 30 days behind its definitization schedule needs an entry explaining what's being done to get back on track. UCAs at or above $100M also require Weighted Guidelines documentation in the tool.
        

10 A UCA Walkthrough

This scenario comes straight from the source training and walks you through the UCA timeline as it would actually unfold. The dates are what you need to internalize. Everything else flows from how you manage the clock.

The Scenario

You're the CO. An urgent user request lands with an Independent Government Estimate to support services for individuals fleeing life-threatening conditions. You have 10 days to start performance. You identify an available IDIQ contract and simultaneously prepare and submit a $100M NTE UCA Request and an Exception to Fair Opportunity. $80M is funded; you obligate $49M. Period of performance is 1 year. Your definitization schedule shows: Day 30 for contractor qualifying proposal; Day 210 to complete definitization (the maximum 180 days after a qualifying proposal at Day 30).

The SCO (or applicable PEO) approves the MCD. You issue the task order and enter the action in the UCA Reporting Tool. Now the clock is running.

Day 30

Updated contractor spend plan received. Burn rate looks fine, funding is sufficient. But no proposal. Working with the mission partner, you may suspend or reduce progress payments under FAR 32.503-6 or take other appropriate action.

Day 45

An incomplete contractor proposal comes in. You identify the deficient areas and immediately return it to the contractor for rework. Engage Legal support and start the action to suspend or reduce progress payments. Don't sit on this. The next deadline is days away.

Day 55

Contractor submits a qualifying proposal for $95M. Just before the 60-day point where you'd have had to update the Reporting Tool with corrective actions. Recalculate your funding amount: 75% of $95M = $71.25M. Make sure current obligations haven't already exceeded that. The 180-day definitization clock starts ticking.

Alt. Day 55

If the qualifying proposal had come in at $110M instead, the UCA approval authority would need to know. You'd process an MCD revision to get approval for the higher NTE. Until that revision is approved, your allowed funding stays at 75% of the original $100M, not 75% of $110M.

Day 60

Updated contractor spend plan received. If the burn rate is going to exceed your obligation limits, engage the mission partner and approval authority to figure out the path forward. Limits: 50% of NTE before a qualifying proposal, 75% after.

Days 60–235

The work to definitize: technical evaluation of the qualifying proposal, Pre-Price Negotiation Memorandum (see DFARS 217.7404-6 and PGI for profit guidelines), legal review, clearance, and execution of the definitizing modification. Keep the UCA Reporting Tool current the whole time. Slippages of more than 30 days from the original schedule require a Tool entry explaining the corrective action.

If You Slip

If you're going to miss the 180-day clock, the SCO can approve an extension up to 90 days. Anything beyond 90 days has to come from the HCA, and that authority cannot be redelegated. Don't show up to that conversation late.

          The takeaway. The UCA isn't hard math. It's calendar management. The Day 30 / Day 55 / Day 60 / Day 235 milestones are the ones that get COs in trouble when they drift. Put them in your calendar the moment the UCA is awarded. Set 7-day and 14-day reminders. The Reporting Tool entry deadlines (10 April / 10 October) go in too.
        

          When not to add funding. Consider not adding funding when the contractor isn't timely providing the qualifying proposal, spend plan updates, or proposal revisions, or when the contractor isn't making sufficient progress. Funding is a lever. Use it.
        

11 Where Things Usually Go Sideways

Most AFCAP problems aren't about the FAR. They're about the human relationships and the file. After a tour as an ACO, the same handful of failure patterns show up over and over.

          Late PCO communication. Issue smolders for two weeks because the ACO is trying to handle it locally. By the time Tyndall finds out, it's an emergency. Fix: routine weekly status, not just exception reporting.
        

          COR doesn't actually know the PWS. Performance ratings are based on vibes instead of objectives. CARs don't survive contractor pushback because the cited paragraph doesn't say what the COR thought it said. Fix: PWS walkthrough with every new COR.
        

          File lives outside KTFS. ACO keeps "their own copy" on a personal SharePoint. When they rotate, the next ACO finds an empty KTFS folder and has to rebuild. Fix: KTFS is the file. Personal copies are scratch.
        

          Mod awarded without Flight Chief approval. ACO assumes the warrant carries the authority. Award gets unwound. Fix: every mod, regardless of dollar value, goes through the review chain.
        

          UCA obligation creep. Funding gets added piecemeal without anyone tracking the 50% / 75% limits against the current NTE or qualifying proposal price. ACO discovers they're already over the line. Fix: the moment a UCA is awarded, track current obligation as a percentage of the relevant ceiling on the file's first page.
        

          EA ambushes the contractor. First the contractor hears about an equitable adjustment is when the assessment letter arrives. They dispute it, the file doesn't support it, and the ACO ends up backing off. Fix: the PARs, the CARs, and the Section D entries should have already told the story before the EA letter goes out.
        

Sample Documents

What These Forms Actually Look Like

Layouts for the documents you'll be reading and writing every week. These are training mockups based on the AFCAP source material. Verify against the current official templates before using them on a live action.

Performance Acceptance Report (PAR)

Submitted by the COR to the ACO within 5 days of the end of each performance period.

Performance Acceptance Report (PAR)

Section A: General Information

Block 1. Contract / Task Order Number	FA8051-XX-D-XXXX-00XX
Block 2. Contractor	[AFCAP V Holder Name]
Block 3. Performance Period	[Month / Year covered]
Block 4. COR Name & Signature	[Signature, date]

Section B: Performance Evaluation

Block 5. Deficiency Type	□ New □ Repeat □ None
Block 6. PO #1 Rating	□ Excellent □ Very Good □ Satisfactory □ Marginal □ Unsatisfactory
Block 7. PO #2 Rating	□ Excellent □ Very Good □ Satisfactory □ Marginal □ Unsatisfactory
Block 8. PO #3 Rating	(continue per PWS performance objectives)
Block 9. COR Comments	[Narrative supporting ratings; cite PWS paragraphs.]

Section C: Contractor Validation

Block 10. Contractor Acknowledgment	[Signature, date]
Block 11. Contractor Refutation	[Optional: contractor response to any markdowns]
Block 12. Contractor POC	[Name, title, contact]

Section D: Deficiency Resolution (ACO)

Block 13. ACO Determination	□ CAR Issued □ EA Pending □ Resolved □ No Action
Block 14. ACO Comments	[Disposition rationale; reference any associated CAR control number or EA action.]
Block 15. ACO Signature	[Signature, date]

Corrective Action Report (CAR)

12-block format. The two blocks that determine whether the CAR holds up are Block 7 Finding and Block 7 Finding Impact.

Corrective Action Report (CAR)

1. Contractor	[Contractor Name]
2. Contract Number	FA8051-XX-D-XXXX-00XX
3. Type of Services	[Contract name / type of services]
4. Functional Area	[BOS, Life Support, Engineering, etc.]
5. Suspense Date	[Date contractor response is due. Typically 10 working days for Major findings.]
6. Control Number	[2-letter site code, last 2 digits of year, 3-digit sequence. E.g., AD26-001]

7. Deficiency: □ Major □ Minor

Finding: [Clear statement of the deficiency, followed by reference to the contractual requirement. Cite the part, section, paragraph, and subparagraph. Quote the contract reference briefly.]

Finding Impact: [State the impact the finding has or could have on accomplishment of the mission the contract supports.]

8. QAP Name & Grade	[Signature, date]
9. Issuing Authority	[Name, grade, signature, date. Functional commander/director.]
10. QAP Response to Contractor Corrective Action	[Comments on acceptance or rejection of the contractor's response. Note any follow-on inspections.]
11. QAP Determination	□ Accepted □ Rejected
12. Close Date	[Date Issuing Authority concurs the response is acceptable]

UCA Management Control Document (MCD)

Section breakdown for the Request for Authority to Issue a UCA. When approved, this becomes the MCD. Source: AFCC Knowledge Exchange template (verify current version before use).

Request for Authority to Issue a UCA: MCD Outline

Section A: General Information

Contracting activity, action description, contract/order number, contractor, dollar value, period of performance.

Section B: Description of the Acquisition

Plain-language description of what is being acquired, with reasonable flexibility built in. The undefinitized character means the description can't be too tight, but it shouldn't be a blank check either.

Section C: Supporting Rationale

Why a UCA is required (for letter contracts, see DFARS 216.603)
Detailed explanation for the need to begin performance before definitization
Adverse impact on agency requirements that would result from delay
Identified risks and the means by which the Government will mitigate them
Justification for the specific contractual instrument selected

Section D: Funding

Not-To-Exceed (NTE) Price:supported by IGCE, prior buys, or contractor proposal
Contractor Spend Plan (if available)
Purchase Request: obligate only enough funds to complete the undefinitized portion of the contractor proposal
Limitations on the obligation of funds (50% pre-qualifying-proposal, 75% post)

Section E: Most Recent Acquisition

Reference to the most recent comparable acquisition, prior award history, and any pricing history that supports the NTE.

Section F: Definitization Schedule

Agreed-upon events that support timely definitization. Must include the due date for submittal of a qualifying proposal and the target definitization date (within 180 days of qualifying proposal receipt).

Section G: Coordination and Approval

Routing slip: contracting, legal, comptroller, mission partner, requirements activity, and the SCO (or PEO, as applicable) for approval signature.

Required Clauses (in the UCA itself)

FAR 52.216-24: Limitation of Government Liability
DFARS 252.217-7027: Contract Definitization
FAR 52.232-22: Limitation of Funds (if incrementally funding)
Any other Contract/Task Order specific clauses

References

Look It Up

The regulatory and policy citations behind the Vol II material. Verify against current versions, particularly under the Revolutionary FAR Overhaul, where Part numbers and specific paragraphs are still moving.

DFARS 217.74: Undefinitized Contract Actions

The full DFARS subpart governing UCAs. Approval thresholds, NTE rules, definitization clock, obligation limits, reporting. The primary reference for any UCA action.

Open DFARS 217.74

DFARS PGI 217.7404: UCA Procedures

Procedures, Guidance, and Information for UCAs. Includes the requirements for the request-for-authority package and the supporting analyses.

Open DFARS PGI 217.7404

FAR 52.216-24: Limitation of Government Liability

Required clause in every UCA. Caps the Government's liability at the NTE for the undefinitized period.

Open FAR 52.216-24

DFARS 252.217-7027: Contract Definitization

Required clause in every UCA. Establishes the definitization schedule, the qualifying-proposal expectation, and the consequences for failure to definitize.

Open DFARS 252.217-7027

FAR 52.232-22: Limitation of Funds

Required when incrementally funding. Notifies the contractor of the funded ceiling and triggers notice obligations as that ceiling is approached.

Open FAR 52.232-22

FAR 32.503-6: Suspension of Progress Payments

The authority you reach for when a UCA contractor isn't producing the qualifying proposal or making sufficient progress.

Open FAR 32.503-6

AFFARS MP 5301.601: Approval Authority

Air Force FAR Supplement Mandatory Procedure on contracting authority delegations. Includes the SAF/AQC delegation of UCA approval to the SCO.

Open AFFARS MPs

Revolutionary FAR Overhaul

RFO is rewriting the FAR. Several Parts that touch UCAs and UCA-adjacent actions are in flux. Always cross-check against the current RFO posture before relying on a citation.

Open FAR Overhaul

AFCAP Vol I: Vehicle Brief

The companion training. What AFCAP is, who holds the contracts, the ordering paths, and how task orders get awarded. Read first if you haven't already.

Open AFCAP Vol I

Contingency Contracting Hub

The broader CCO field-desk hub. OCS for Dummies, FAR Part 18 flexibilities, manual contracts deployed, FOO program, ACSAs, and other contingency-relevant training.

Open CCO Hub