Solicit by phone, radio, or in person under simplified procedures. Document the conversation in the file: who you talked to, when, what they offered. Hard to do well on the move; harder to defend if the file is thin.
FAR Part 18 Flexibilities
The Part 18 and contingency support moves a CCO actually needs in the field. Know what is always available, what unlocks only under a declaration, and how those authorities show up when the mission needs food, water, partner support, bare-base operations, and a clean turnover.
What Part 18 actually is
Part 18 is a roadmap, not a creator of new authorities. It's the consolidated list of contracting flexibilities that already exist elsewhere in the FAR, gathered in one place so a CCO under pressure isn't flipping through five different parts to remember which authority lives where.
Subpart 18.1 covers flexibilities available on any acquisition. Subpart 18.2 covers the ones that only unlock when a contingency, emergency, or specific declaration is in place.
What it doesn't do
Part 18 does not raise thresholds on its own. It does not waive a clause your contract already incorporates. It does not give you new dollar limits without an underlying declaration or determination.
Treat each flexibility below as a pointer. Go to the FAR Part it lives under, confirm the current text, and document the determination that supports your use of it.
Always Available
Authorities a CCO can use any day of the week. No declaration required. Part 18 points back to the FAR homes for these tools so you can find them quickly when the clock is short.
Authorize the contractor to start work before final terms are negotiated. The Government commits to a not-to-exceed amount; the parties keep negotiating the definitive contract. Useful when mission timing won't wait.
Shorten the solicitation period when urgency is real and the market is known. Costs you bidders and competition strength, so be honest about the trade. Document the basis.
Contingency & Declared Operations
Flexibilities that unlock only when something is declared. Contingency operation, defense or recovery from certain attacks, major disaster, or qualifying humanitarian or peacekeeping operation. Each declaration carries its own scope; check what you're operating under before you reach for these.
Three ceilings move when a declaration is in place: Micro-Purchase Threshold, Simplified Acquisition Threshold, and the FAR Part 12 commercial procedure ceiling. The CONUS / OCONUS split matters. The declaration matters more. A stateside disaster without a Stafford Act declaration does not move a single number.
Acquisition and Cross-Servicing Agreements are not ordinary FAR contracts, but they matter fast in coalition operations. Know when to route logistics support, supplies, or services through the ACSA team, how cash reimbursement, replacement-in-kind, or equal-value exchange works, and what has to be captured in the system of record.
Specific flexibilities apply when the action supports defense against or recovery from chemical, biological, radiological, nuclear, or cyber attack. The declaration changes the threshold and procedure landscape sharply for those buys.
Major disaster or emergency declarations under the Stafford Act unlock acquisition flexibilities, including expanded set-aside provisions for businesses in the affected area. Local-area preference is a real thing here.
Qualifying humanitarian or peacekeeping operations carry their own subset of Part 18 flexibilities. Often paired with the increased MPT and simplified-procedure thresholds, plus eased domestic-source rules for in-theater purchases.
CCO Drills
These are the practical operating problems that make Part 18 matter. The authority is only half the work; the other half is turning a rough requirement into support the unit can actually receive, inspect, pay for, and hand off.
Validate the requirement owner, health and safety constraints, delivery point, storage limits, receiving process, and payment path. A simple local buy can become a force-health problem fast if the file ignores inspection and acceptance.
Build the daily rhythm around commander intent, requiring activity discipline, funding status, theater business clearance, local-law concerns, vendor communications, and contract files that can survive rapid movement.
Before the first urgent buy, learn the market, currency, banking, tax and customs posture, language support, security limits, vendor base, and host-nation constraints that can make normal procurement assumptions useless.
Leave the next CCO a usable map: open actions, vendors, funds, claims, disputes, expiring services, property, local contacts, recurring requirements, file gaps, and the quiet lessons that never make it into the official checklist.
Capture what broke, what worked, and what needs to change while the facts are still fresh. Turn firefighting into SOP updates, template fixes, vendor notes, risk calls, and training scenarios for the next rotation.
Go from empty room to functional CCO cell: intake channel, file structure, comms plan, funding tracker, battle board, signature controls, legal touchpoints, quality review rhythm, and a visible status picture.
No mature infrastructure means basic support comes first: power, water, sanitation, billeting, material handling, delivery routes, receiving points, generators, waste, and the base operations buys that keep the mission alive.