Skip to content
CCO Field Desk

Purchasing Food and Water in a Contingency

A subsistence buy ends with someone eating or drinking. You are not solving it alone. Get the Force Support Squadron (FSS) at your hip from the first call, work the source priority in order, put the vet officer on any local source before money moves, and bring back a file that shows what the force actually ate or drank. Your job is to advise on the source path, then execute the buy your file can defend.

You are the appointed CCO at a forward airfield. A troop movement just doubled the headcount on the ramp, the dining-facility gap opens at 1800, and the FSS commander is standing at your desk with a 72-hour feeding requirement in hand. A local vendor outside the wire says he can have cases of bottled water and 240 boxed meals at the gate by sunset, cash on delivery. Three calls run before any cash moves: whether that source can safely feed the force, who is going to inspect what shows up, and whether your file can prove either one.

Classifier Reactive Field Buy Real need, short clock, and you keep the mission moving while you work the buy.
Branch Deliberate Local Buy Use this branch only after the approved source paths cannot reach the need in time.
Rhythm Recognize → fit-check → execute → evidence Do not let the speed of the buy erase the health and receiving trail.
Stop Point Source approval before consumption AR 40-657 / NAVSUP 4355.4H / MCO P10110.31H puts source approval on the vet officer.
Decision rhythm

The buy starts with who owns the feeding.

FSS owns the feeding mission. They run dining facilities, issue Meals Ready-to-Eat (MREs), and field the specialty trades that feed troops, so they ride with you from the first call to acceptance. Most subsistence problems are administrative. The fix is usually an AFCAP task-order mod, a bigger MRE pull, or a DLA route nobody called yet. The vet officer joins as soon as any local source enters the picture. The first vendor who can move today is rarely the right source, and subsistence buys go sideways when speed wins over source approval, inspection, and acceptance. Work the rhythm in four passes with the team. Each pass leaves evidence in the file.

01

Recognize

Who is the requiring activity, what is FSS already doing for them, how many people, for how long, at what delivery point, and what just changed?

02

Fit-check

Check the Air Force Contract Augmentation Program (AFCAP) or the theater life-support vehicle first, then the Defense Logistics Agency (DLA) Troop Support, then local purchase only if time closes the approved-source routes.

03

Execute

Lock the delivery point, receiving official, cold-chain or water controls, fund cite, purchase method, and payment path before the order goes out.

04

Bring Back Evidence

Save the source approval, inspection/acceptance, receiving report, invoice, payment support, and any rejected quantity or spoilage notes.

Source-priority waterfall

Work the subsistence sources in order.

Walk this in order before you talk to a local vendor. FSS rides every step with you. They run the feeding mission and usually have the fastest read on what is reachable. Each step closes if the one above it cannot reach the gap in time, and the file should show why you moved.

  1. AFCAP / theater life-support vehicle

    Food service, dining facilities, bottled water distribution, and base life support may already sit inside the theater augmentation contract or another life-support vehicle. Check this path first so you do not create a separate local buy for work the theater already paid someone to perform.

    KTHQ cross-links: AFCAP Vehicle Brief and AFCAP ACO Field Execution.
    What you ask

    Is the requirement already in scope? Who is the ACO/PCO or life-support lead? Can the contractor feed this headcount by the needed time? What change order, task-order direction, or customer handoff is required?

  2. DLA Troop Support (Subsistence)

    If the theater vehicle does not cover the gap, move to DLA Troop Support Subsistence. DLA is the approved subsistence supply chain for food, food-service support, operational rations, and related support. Use the regional contact path and make the requiring activity hand over enough detail for DLA to route the need.

    Official path: DLA Troop Support Subsistence and DLA Food Services regional contacts.
    What the customer brings

    Headcount, meals or water per day, duration, delivery point and hours, storage limits, receiving POC, fund cite, special diet or religious constraints, force-protection limits, and the date/time the gap opens.

  3. Plan Z: Local purchase with veterinary food-protection approval

    Open this path only after AFCAP and DLA cannot reach the need in time, and only with FSS in the room and the vet officer engaged. A market visit, a competitive price, and a vendor's confidence do not approve a source. The Army Veterinary Service is the DoD executive agent for food protection under DoDD 6400.04E, which is why the joint regulation AR 40-657 / NAVSUP 4355.4H / MCO P10110.31H carries source-approval authority across all the services, including the Air Force. On Air Force installations, Public Health personnel also operate under AFI 48-116; coordinate with both when both exist locally. Engage the food-protection officer before you commit to the vendor.

    Official path: DLA Troop Support Food Safety, Army Food Analysis and Diagnostic Laboratory, and AR 40-657 / NAVSUP 4355.4H / MCO P10110.31H (joint food-safety inspection regulation).
    Required stop (AR 40-657)

    No award and no consumption until the food-protection authority signs off on source, item, handling, delivery, and inspection path for this operation. Capture that decision in the file with name, rank, date, and how the source was evaluated.

  4. MREs / operational rations

    Put operational rations on the table early. A safe ration on time beats an unapproved local source. If the food-protection officer cannot clear the source fast enough, fall back to rations until the approved supply chain catches up.

    Official path: DLA Operational Rations.
    What the file says

    Why the approved feeding path was not available in time, who made the ration decision, how long the fallback covers, and what action is bringing the force back to the approved source.

Local-source branch

When local is the only timely answer, slow down the health decision.

Local purchase is Plan Z. Before you commit on food, ask one more time whether the real answer is an AFCAP mod, more rations, or a DLA route nobody has tried. For water, local is often the only timely answer, especially bulk potable. The water still gets tested before anyone drinks it. You do not run any of this alone. FSS stays the mission partner and helps weigh whether the option actually feeds the force. The base vet (AR 40-657 / NAVSUP 4355.4H / MCO P10110.31H) decides whether the source can feed it safely. You own the contract vehicle, file, and payment trail.

Food, bottled water, and bulk water each run a different path from here. The file has to show which one and how it cleared.

Food

Confirm the exact establishment, menu item, packaging, preparation time, transport method, receiving point, and rejection process. Save the vet food-protection source-approval memo beside the order and invoice. No approval memo, no consumption.

Bottled water

Bottled water is a packaged subsistence item. Pin down source, brand, lot, seal condition, heat and tamper protection on the trip in, and the DLA approved-source listing or food-safety screening that covers it (AR 40-657 inspection path).

Bulk potable water

Bulk water is a preventive-medicine and water-system problem governed by AFMAN 48-138_IP / TB MED 577. The file should show source, treatment, container or tanker sanitation, potability surveillance, distribution point, and the bioenvironmental or preventive-medicine sign-off accepting it for use.

Two calls outside the contracting office decide whether this buy can feed the force. AR 40-657 / NAVSUP 4355.4H / MCO P10110.31H puts source approval for food establishments supplying DoD on the military veterinary/medical food-safety function. For field water, AFMAN 48-138_IP / TB MED 577 puts potability and distribution on the preventive-medicine channel. Work them with FSS in the room. Do not invent that support structure locally, and do not award around it.

Pick the instrument that fits the buy.

Match the instrument to your appointment, the funding line, the threshold, and local theater procedure: theater vehicle direction (AFCAP task order or change), DLA ordering path, GPC, purchase order, manual contract, or SF 44. Whichever one you pull, the food-safety call still runs on its own track.

SF 44 fits a one-off pickup. Most subsistence buys run for days across multiple deliveries, and the file needs quality, cadence, and receiving terms hashed out in a purchase order or manual contract. When SF 44 is the right field instrument, work the book as a pocket contract file: order, invoice, voucher, fund cite, receiving evidence, payment support, and file evidence in one place. Current authority lives at RFO FAR 12.403 (and 12.403(b) for the SF 44 form listing). For DoD CCOs forward, work the current DoD RFO Part 12 / DFARS Part 212 deviation before you set an SF 44 ceiling. The deviation raises the SF 44 limit up to the simplified acquisition threshold for qualifying fuel and oil purchases and for overseas transactions by contracting officers supporting contingency, humanitarian, or peacekeeping operations. Use that ceiling when the operation qualifies. The source-approval requirement above still applies regardless of which instrument you pull.

RFO / FAR / DFARS working note

FAR and DFARS references for SF 44 sit inside the Revolutionary FAR Overhaul transition. Lead with Acquisition.gov RFO Part 12, section 12.403, and the Acquisition.gov forms listing for SF 44 at 12.403(b). For DoD, work the current Part 12 / DFARS Part 212 deviation material and DARS tracking posture for SF 44 ceilings before you carry a number from older simplified-acquisition framing. Confirm agency adoption, DoD deviation status, local policy, appointment limits, funding controls, and threshold posture.

Working contract file

The subsistence file has to show the health decision and the money decision.

The file has to prove two things together: that the requirement owner, source path, health controls, delivery, and acceptance all lined up before people ate or drank, and that the obligation and payment trace back to that same record. Either half alone is a finding.

1 Requirement owner and facts. Requiring activity, feeding authority, headcount, period of support, meal or water basis, delivery location, and operating constraint.
2 Source priority trace. AFCAP/theater vehicle check, DLA check, FSS feeding-mission input, reason local purchase or rations were needed, and who made the routing decision.
3 Approved-source proof. Directory listing, DLA food-safety path, veterinary/preventive-medicine approval, inspection note, or documented operational exception with risk controls.
4 Item identity. Menu, quantity, brand, lot, expiration, bottled-water source, bulk-water source, substitutions, and any rejected or shorted items.
5 Storage and delivery controls. Cold-chain notes, delivery time, temperature checks when required, tamper checks, storage limits, and who controlled the product after receipt.
6 Inspection, receiving, and acceptance. Name/title of receiver, quantity accepted, condition, rejection notes, receiving report, photos only if locally allowed, and time of acceptance.
7 Funds and payment support. Fund cite, price reasonableness, purchase instrument, invoice, voucher/payment record, paying-agent or finance coordination, and obligation/payment reconciliation.
Printable aid

Carry the field card, then build the file behind it.

The card is the quick version for the truck, tent, or customer huddle. The checklist beside it keeps the file from turning into a pile of receipts.

Validate

Requirement owner, headcount, duration, delivery point, storage, receiving official, fund cite, and the time the gap opens.

Source in Priority Order

AFCAP/theater life-support vehicle, then DLA Troop Support, then local source with required food-protection involvement, then rations as fallback.

Inspect / Accept

Approved source, product identity, cold chain or potability controls, delivery condition, receiving report, rejected quantities, and acceptance signature.

Document

Source decision, approval, order, fund cite, invoice, voucher/payment support, receiving evidence, and any return-to-approved-source plan.

Scenario self-check

Five quick calls before you sign.

Run these against the file you're about to release. Any answer that goes soft means the file is not ready to defend the buy.

1. The vendor can deliver dinner in two hours.

Your next move is not award. Check AFCAP/theater support and DLA first. If local is still the only timely path, get veterinary/food-protection approval before the food feeds the force.

2. DLA can deliver tomorrow morning.

Decide whether rations bridge the overnight gap. Do not feed the force an unapproved local meal just because the customer prefers it to MREs.

3. The customer says bottled water is just water.

Correct the file. Bottled water is a packaged subsistence item with source, brand, lot, seals, storage, and approval questions. Bulk potable water uses a different preventive-medicine trail.

4. The invoice is clean, but the receiver is vague.

Fix acceptance before payment. The file needs who received, what quantity and condition they accepted, and any rejected or missing items.

5. A unit commander tells you "no" is not an option.

Then "no" is not your answer either. Pull FSS in, walk the source priority with the team, name what each option costs in time, and execute the path the file can defend.

Official-source notes

Source checks and caveats.

Links below were verified on 2026-05-20. Confirm current source, theater guidance, agency adoption, local policy, appointment limits, funding controls, and threshold/deviation status before using this as a live file checklist.

DLA Troop Support Subsistence

Subsistence home and regional food-service contacts are the primary official DLA paths for routing subsistence support.

Verified 2026-05-20; confirm current.

DLA Food Safety / Approved Sources

DLA Food Safety points users toward the DoD approved-source program and food-safety support.

Verified 2026-05-20; confirm current.

Military Veterinary Food Protection

DoDD 6400.04E designates the Army as DoD executive agent for veterinary public and animal health, including food protection. AR 40-657 / NAVSUP 4355.4H / MCO P10110.31H is the joint food-safety and inspection source the Army Vet Service uses on behalf of DoD, including the Air Force. AFI 48-116 governs the AF installation food safety program in parallel.

Verified 2026-05-20; confirm current.

Food and Water Laboratory Path

Army Food Analysis and Diagnostic Laboratory describes official food, bottled water, and related veterinary public-health laboratory support.

Verified 2026-05-20; confirm current.

Field Water Surveillance

AFMAN 48-138_IP / TB MED 577 is the field-water sanitary control and surveillance source used here for bulk potable-water cautions.

Verified 2026-05-20; confirm current.

Operational Rations

DLA Operational Rations is the official path for MREs and other operational ration support.

Verified 2026-05-20; confirm current.

RFO / FAR / SF 44

RFO Part 12, RFO Part 18, Acquisition.gov FAR Forms, and DoD Part 12 / DFARS Part 212 deviation are the current anchor points for the SF 44/source-path note.

Verified 2026-05-20; confirm current, including agency/deviation status.

KTHQ Context

AFCAP Vehicle Brief and AFCAP Volume II provide local KTHQ context for the waterfall.

Local draft link check performed in review.