Most new CCOs will never issue one. Good. A letter contract is a rare emergency tool for the moment when the mission needs a binding start now and there is not enough time to finish a definitive contract. Your first job is not to make one work. Your first job is to know when a definitive buy or unpriced purchase order is cleaner.
Can we define the work, price it, and award a normal action in time? If yes, do that. Do not use a letter contract just because the customer is loud, late, or uncomfortable with uncertainty.
If only the exact price is uncertain and the buy fits simplified acquisition rules, think about an unpriced purchase order before you think about a UCA.
A verbal go-ahead, text message, or email saying "start and we will paper it later" is not a letter contract. It is how a team creates an unauthorized commitment.
A real letter contract is written, signed, funded, limited, approved, and scheduled for definitization before performance outruns the file.
Brand-new CCO rule: use the simplest lawful instrument that solves the mission problem. Letter contracts and UCAs are control problems. They are not speed hacks.
Use this when you can describe the requirement, compete or justify the action, price it, fund it, and award before the mission breaks.
Use this for limited simplified-acquisition situations where the exact price is not available yet, but the work is narrow enough to control.
Use this only when the Government needs a binding start now and there is not enough time to negotiate a definitive contract first.
If you remember nothing else, remember the relationship: a DoD letter contract is usually a UCA, but an unpriced PO is not just a tiny UCA.
| Term | What it means | New CCO translation |
|---|---|---|
| Letter contract | A written preliminary contractual instrument that lets the contractor begin immediately before all final terms are settled. | Emergency written start, then definitize quickly. |
| UCA | In DoD, an undefinitized contract action is the control framework for actions where terms, specs, or price are not fully agreed before performance begins. | The DoD rules layered on top: approvals, NTE, obligation limits, proposal clock, and profit risk. |
| Unpriced PO | A simplified-acquisition purchase order used in limited cases when a firm price cannot be established in advance. | Small, controlled, and often the better answer if only exact price is unknown. |
If legal, leadership, and the mission all point to a letter contract, do not freeze. Build a signed letter-contract package that can stand on its own, then move it into the contract-writing system and definitize it as fast as the facts allow.
The first executable document can be a Word-built letter converted to PDF for signature. It still has to behave like a contract: number it, fund it, approve it, sign it, and get contractor acceptance.
Title: Letter Contract / UCA No. [number]
Contractor: [legal name, UEI/CAGE if known]
Requirement: [plain-English mission need]
Authority: [approval memo / urgency record]
Funds: [accounting line and obligated amount]
Ceiling: [NTE price and liability limit]
Exit: [definitization schedule]
The letter tells the contractor exactly what starts now and where the stop signs are. Nobody should need a side conversation to know the scope, money, or clock.
"You are authorized to begin only the work described in Attachment 1."
"The Government's maximum liability before definitization is $[amount]."
"The not-to-exceed price for this action is $[amount]."
"The contractor shall submit its qualifying proposal by [date]."
"Only the contracting officer may change scope, price, schedule, or terms."
The signed PDF should include enough material that the next CCO can administer it without guessing what happened during the emergency.
Attachment 1: SOW/PWS or minimum work description.
Attachment 2: CLINs, funding, NTE, liability limit.
Attachment 3: Definitization schedule.
Attachment 4: Required clauses and local provisions.
Attachment 5: Inspection, acceptance, invoice instructions.
Attachment 6: COR/ACO designation or interim surveillance plan.
The PDF gets the mission moving. The contract-writing and funding records keep the audit trail alive. As soon as practicable, mirror the action in the local system and definitize by modification.
Commercial products/services: SF 1449 may be right.
Construction definitive action: SF 1442 may be right.
Negotiated definitive action: SF 26, SF 33, OF 307, or system award.
Order / BOA / IDIQ action: system order, DD 1155, OF 347, SF 1449, or local format.
Definitization: usually bilateral SF 30 or system modification.
| Build Order | What the CCO does | What right looks like |
|---|---|---|
| 1. Prove the emergency | Write the mission harm if performance waits for a fully definitive award. | A reviewer can see why the normal route failed the mission, not just that the customer was loud. |
| 2. Try to avoid it | Check definitive award, bridge, order, BPA/BP, GPC, or unpriced PO first. | The file explains why the simpler tool did not solve this specific problem. |
| 3. Get approval | Pull legal, policy, funding, leadership, and current local delegation before signature. | The approval package is signed before the letter is signed. If the mission cannot wait for normal staffing, elevate until the authorized path is clear. |
| 4. Set the money | Separate the funded obligation, maximum Government liability, and NTE ceiling. | Everyone knows what is funded now, what the contractor cannot exceed, and what ceiling the action cannot pass. |
| 5. Control the work | Define the first authorized slice of performance, acceptance point, invoice path, and who can give direction. | The contractor can start, but cannot drift into unapproved work. |
| 6. Build the exit | Put the qualifying proposal due date, negotiation date, and target definitization date in the letter. | The UCA has a clock on day one. Definitization is not left for the next person. |
| Clause / control | When it goes in | Executioner note |
|---|---|---|
| Definitive-contract clauses | Every letter contract. | Include the clauses required for the definitive contract type you expect to end up with, plus any additional clauses already known to be appropriate. |
| FAR 52.216-23 Execution and Commencement of Work | Letter contracts, except it may be omitted when awarded on SF 26. | Contractor acceptance and authority to proceed. If using SF 26, the signature mechanics may make this unnecessary. |
| FAR 52.216-24 Limitation of Government Liability | Letter contracts and DoD UCAs. | This is the "do not exceed this dollar amount" control. Complete the dollar amount carefully; it is not decoration. |
| FAR 52.216-25 Contract Definitization | Non-DoD letter contracts. | Use Alternate I if award is based on price competition. In DoD, do not use this as the primary definitization clause. |
| DFARS 252.217-7027 Contract Definitization | All DoD UCAs, including DoD letter contracts. | Replaces FAR 52.216-25 for DoD. Fill in the contract action type, proposal type, definitization dates, and NTE ceiling. |
| FAR 52.216-26 Payments of Allowable Costs Before Definitization | When a cost-reimbursement definitive contract is contemplated, except specified ship work. | Use only when cost-type mechanics are expected. Pair this with invoice/acceptance discipline. |
| Inspection / acceptance / changes / disputes / termination | As required by the contemplated definitive contract type. | Pick the clauses that match what you are buying: supplies, services, construction, commercial, cost-type, fixed-price, etc. |
Approved requirement, funding, competition/exception record, UCA approval, NTE support, liability limit, definitization schedule, clause review, acceptance process, and COR/ACO plan must all exist before the contractor starts.
Track the qualifying proposal due date, 50 percent obligation point, possible 75 percent limit after a qualifying proposal, invoice support, acceptance records, and the SF 30 definitization modification.
You do not need to memorize every UCA citation before deployment. You do need to know when to stop, elevate, and build the file around these controls.
RFO FAR 16.603 requires a written determination that no other contract is suitable. DoD UCA rules add an approval package before award. For DAF training, teach this plainly: check the current delegation memo. As of May 6, 2026, DAF approval commonly routes through SCO/COCO lanes for actions below $50M, not straight to a general officer.
RFO FAR 52.216-24 caps Government liability before definitization. DoD UCA rules separately require a not-to-exceed price and limit obligations before definitization. Train the distinction: liability cap, NTE price, and funded obligation are related controls, but they are not the same sentence in the file.
RFO FAR 16.603 points to definitization within 180 days after the letter contract or before 40 percent completion, whichever comes first. DoD adds a UCA schedule tied to a qualifying proposal and obligation limits. New CCO translation: the schedule is not admin cleanup. It is the heartbeat of the action.
A letter contract or UCA does not create a competition exception. Use the competition rules that match the action: FAR Part 6, FAR 16.505 fair opportunity, or simplified-acquisition procedures. If urgency limits competition, document why and solicit as many sources as practicable.
This is the missing middle: not just what a letter contract is, but how a deployed CCO would move when the mission really cannot wait for a fully priced action.
A forward operating airfield takes storm damage during a beddown surge. The unit needs emergency power, temporary billeting repairs, debris removal, fuel bladder support, latrines, and limited dining support running within 72 hours.
The commander can describe the outcome, but the final quantities are not known. Engineers have not finished the damage assessment. The labor mix depends on what the contractor finds on Day 1. Waiting two weeks for a fully priced action will interrupt flight-line operations.
Get the requirement owner, funding path, operational consequence of delay, required start date, acceptance point, and first period of performance. Write down why waiting for a definitive award fails the mission.
Ask whether a definitive contract, task order, bridge, GPC buy, BP/BPA call, or unpriced PO can solve the actual problem. If one can, use the cleaner tool.
Bring in legal, policy, funding, leadership, and the current DAF/local delegation memo. For DAF training, do not assume a 3-star approval lane; current matrices commonly route sub-$50M actions through SCO/COCO lanes depending on delegation.
Solicit as many sources as practicable. If using a multiple-award vehicle, use fair opportunity unless an exception applies. The letter contract label does not erase competition.
Set the most complete scope you can, initial funded amount, NTE/liability cap, clause set, reporting, inspection, acceptance, COR/ACO roles, and a real definitization schedule.
Track proposal due date, negotiation start, obligation burn rate, and final bilateral modification. Definitization is not closeout paperwork; it is the exit route.
| File element | What right looks like | New CCO check |
|---|---|---|
| Urgency narrative | Specific mission harm, not generic urgency language. | Can I explain the consequence in one sentence? |
| Tool-choice record | Shows why definitive award, unpriced PO, or other vehicle was not suitable in time. | Did we prove the UCA was necessary? |
| Approval package | Uses current FAR/DFARS/DAF/local delegation and identifies the actual approval authority. | Did we pull the latest memo? |
| NTE / liability support | Supported by IGE, competition, historical data, market research, or price analysis. | Is the ceiling defensible? |
| Performance controls | COR/ACO roles, inspection, acceptance, and invoice support are live on Day 1. | Who says the work is acceptable? |
| Definitization schedule | Proposal date, negotiation date, target definitization date, and owner for each suspense. | Who is watching the clock? |
| Final mod | Bilateral SF 30 definitizes scope, price, funding, clauses, and any settled adjustments. | Did the emergency tool become a normal contract? |
These are the pieces a new CCO should expect to see on the desk before the action moves.
Explain the mission harm, why a definitive action cannot be negotiated in time, what alternatives were considered, and why no other contract is suitable.
Do not write: "urgent requirement."
Write: "Delay beyond 72 hours stops [mission effect] because [specific consequence]."
Support the liability limit, NTE price, and initial obligation with an IGE, competition, historical data, market research, or a documented price-reasonableness basis.
Bad file smell: ceiling copied from the contractor's ROM with no Government support.
The definitization schedule should include proposal due date, negotiation start, target definitization date, and who owns each suspense.
If nobody owns the proposal suspense, the UCA owns you.
Set COR/ACO roles, inspection, acceptance, invoice support, and scope-change guardrails immediately. Surveillance does not wait for definitization.
Only the contracting officer changes scope, price, schedule, or terms.
The failure pattern is usually not exotic. It is ordinary contracting discipline breaking under operational pressure.
The team starts with a real emergency, then lets paperwork chase the mission. Build the approval, competition record, NTE support, and schedule before or contemporaneously with award.
An NTE set too high hides risk. An NTE set too low creates a funding crisis. Either way, the file needs Government support for the number.
The customer, COR, or field lead starts directing new work because everyone is moving fast. That can become an unauthorized commitment or a claim.
Invoices arrive before receiving records catch up. The fix is boring and critical: no certification without linked receiving and acceptance support.
The contractor mobilizes and proposal prep becomes tomorrow's problem. In DoD, late qualifying proposals can trigger withholding and other consequences.
Definitization is pricing and final terms. It is not a chance to rewrite the award rationale after performance has started.
Use these as the current official anchors. DAFFARS is included as a DAF implementation note, not the core government-wide rule.
Unpriced purchase orders and commercial buying under the RFO model.
Letter-contract baseline: immediate start, suitability determination, liability, and definitization.
UCA approval, NTE, qualifying proposal, and obligation controls.
Current DAF delegation matrix. Check local delegation before use.
References verified May 6, 2026. RFO and agency deviations are moving targets; always check the current text and local policy before issuing real file guidance.