Field Ordering Officer Program

A Field Ordering Officer (FOO) is a delegation of purchase authority. Somebody on the ground needs to be able to walk into a local market and pay cash for the things the unit needs to live and work. A warranted CO can do that, sure, but a warranted CO is often overkill for the simple stuff, and just as often there is not one within reach. The FOO program is what you stand up so a named person at the unit can make those simple purchases inside a defined lane, under the contracting office's umbrella, without needing the full warrant.

A FOO is not a contracting officer. The FOO has narrow purchase authority for specific supplies and non-personal services, inside a dollar cap set on the appointment letter, paid in cash drawn against an imprest fund and documented on an SF 44. Everything outside those four lines (named individual, named scope, named cap, named instrument) is unauthorized. The flip side: when the program is set up cleanly and the FOO stays inside the lanes, this is the fastest legitimate way to put cash on a problem forward.

This page is the practitioner walkthrough. The build is ten steps. The boundary between the FOO and the Paying Agent (PA) is the one that breaks programs. The forms are simple once you have seen them once. And the hard limits will get a CCO in real trouble if the appointment letter is sloppy or the cadence is loose. This training stays focused on the cash flavor of a FOO program, because that is where most CCOs actually use the authority forward.

Step 1. Write down the mission case. Before you draft anything, get one paragraph on paper that explains why a FOO program is the right answer for this requirement. Not a warrant, not a BPA, not the GPC. The regulations treat FOO appointments as exception-based, so when the inspector general or your own command shows up six months from now and asks why you didn't just push everything through the regional warranted CO, the answer needs to already be in the file. The mission case does not have to be long. It has to be honest and concrete: timeline, location, the type of buys, why the existing options can't reach.

Step 2 and Step 4 in parallel. These two slow the program down more than anything else, so start them on the same day. Step 2 is finding the appointing authority. Step 4 is bringing finance in. Both take at least a week, often two, and neither one waits well.

Step 2: trace the appointing authority chain. A regular warranted CO is not automatically the appointing official for a FOO. The local delegation chain runs from the Head of the Contracting Activity (HCA) to the Senior Contracting Official (SCO) to the Chief of the Contracting Office (COCO), and FOO appointment authority sits at one of those tiers depending on local delegation. Pull the current delegation memo before you draft the appointment letter. If you cannot find it, that is your first action item. Drafting an appointment letter signed by the wrong person is the cleanest way to invalidate the whole program.

Here is where I will tell you what I actually believe, having scoured every regulation I could find on this. Army regs, Air Force regs, WarU, DAU material, anything I could pull. A FOO is a delegation of purchase authority. That is the cleanest way to read it across all the source material. If the FOO is going to be a GPC holder and execute with a credit card, follow the GPC delegation chain. But if they are spending cash, my read is the delegation must come from the COCO. That is the call I make when I draft these letters. If your local guidance says different, follow your local guidance, but make sure the answer holds up against the actual regs.

Step 3: pick the instrument and the cap. The appointment letter names what the FOO can use and the dollar limit. For a cash FOO program the instruments are cash drawn against an imprest fund and the SF 44 (Purchase Order, Invoice, Voucher). The cap I usually go with is the Micro-Purchase Threshold (MPT). It is the cleanest line to draw, it lines up with the simplest acquisition methods, and the training the FOO gets should reflect what the MPT is and how it moves under the RFO and any active deviations. The letter also names the supplies, equipment, and non-personal services the FOO can buy. Be specific about scope. "Class I and life support consumables" is better than "supplies."

Step 4: bring finance in early. Loop in the Disbursing Officer (DO) and your Financial Management (FM) shop the day you start working on Step 2. If the FOO will use cash or imprest funds, you need a Paying Agent (PA), and the DO has to agree to advance the cash. The PA appointment is a separate action from the FOO appointment, lives in FM's lane, and uses FM's forms. Joint training between contracting and finance is the documented best practice and it pays off when the program goes live, because the FOO and the PA will be in the same vehicle on day one and they need to already know how the handoff works.

Step 5: pick the right people. The FOO needs to be operationally credible (so the unit takes them seriously), disciplined enough to keep clean files, and willing to push back on a commander who tries to bend the appointment letter. The PA needs to be steady, careful with cash, and comfortable saying no to a vendor who tries to renegotiate at the table. The FOO and the PA cannot be the same person. Pick alternates for both up front, because leave, illness, and PCS rotations will hit your program inside the first 90 days, and a program with no alternates is a program with a single point of failure.

Step 6: train them, together. Cover procedures, ethics, procurement integrity, contract action reporting, funds availability, file assembly, invoice and receipt requirements, DD 1081 and DD 2665 handling, and unauthorized commitment (UC) prevention. Run scenario drills on the actual mission buys the unit is about to make. Train the FOO and the PA in the same session whenever you can, because most field-side problems happen at the handoff, not inside either role.

Step 7: issue the appointment letter. The letter names the individual, declares that the authority is non-delegable, lists the instruments permitted, names the subject-matter scope, sets the dollar cap, sets the effective period, and references the file requirements. Get a signed acknowledgment back. Distribute copies to the appointee, to disbursing and the imprest cashiers, to the unit commander, and to anyone who will need to recognize the authority at a vendor's counter. The PA gets a separate appointment letter from FM. Both letters live in the program file.

Step 8: build the file architecture before the first transaction. Set up the purchase-file template now, not after the first buy. One folder per transaction. Checklist for purchase request, funds certification, market or pricing support as required, vendor receipt and invoice, SF 44 or order documentation, PA receipt documents, DD 1081, DD 2665, review memo, and retention schedule. If you wait until the first transaction to design this, the first transaction will be missing pieces and you will spend the next six months chasing them.

Step 9: pilot narrow, then watch closely. Run a small first cohort. Review every transaction in the first 30 days, regardless of what the regulatory minimum says. Air Force rules require 100% surveillance within 30 days plus annual review; Army rules require at least annual. Run the Air Force cadence either way. Tight early review catches the pattern problems (split buys, scope drift, missing receipts) while the program is small enough to course-correct without major surgery.

Step 10: migrate steady-state demand out. The FOO lane is built for the unpredictable expeditionary buys, not for the regular ones. If a requirement turns out to be steady-state (recurring IT consumables, monthly fuel deliveries, weekly billeting buys), push it back to the contracting office to stand up a proper vehicle for it. The exact vehicle is a problem for the rear shop. Leave the FOO lane open for the things you cannot see coming.

The same ten steps as a quick-reference card:

The reason the rule exists is the same reason auditors separate ordering, receiving, and paying in any system that touches money: a single signature on all three creates a fraud surface that nobody can review against. Two people on a transaction means a vendor can't quietly inflate an invoice without the second signature noticing. A single person, even an honest one, leaves no second set of eyes for the disbursing officer to lean on when something looks off.

In day-to-day operations, the FOO identifies the source, picks the item, signs the SF 44, and accepts the supply or service. The PA holds the advanced cash, makes the disbursement, gets the vendor's signed receipt, returns the vouchers, and settles the account back with the DO. Both build pieces of the same file from different ends. When the cash is settled and the file is complete, the transaction closes.

Build alternates for both roles when you stand the program up. Not when you need them. Leave, illness, and rotations will hit, and a program that depends on two specific people with no fallback breaks the first time one of them takes a four-day pass.

0700. The PA walks to the disbursing office. The DO has the cash ready against an approved DD 1081. The PA signs for the advance, counts the cash, and confirms the amount on the form. The PA's copy of the 1081 goes in the transaction folder. The cash stays in the PA's accountable custody from this point forward. It does not get split, does not get lent, and does not get held overnight under any normal scenario.

0830. The FOO and the PA roll out to the vendor together, and I strongly recommend bringing the technical expert from the requiring activity with them. Whoever owns the requirement. There is nothing worse than buying what you think they need only to drive back out and buy it again because you bought the wrong thing. Sometimes operational reality means the expert cannot ride along, and I get it. But I normally insist. The FOO has a blank SF 44 from the controlled book and a copy of the purchase request. The PA has the cash. They have already agreed on the maximum acceptable price.

0915. At the vendor. The FOO confirms the supply matches the requirement. The FOO inspects, accepts, and writes the SF 44: date, vendor name and address, item description specific enough that a file reviewer can identify what was bought, quantity, unit price, total, and the FOO's signature. The FOO does not split the buy across two SF 44s to fit under any threshold. If the total exceeds what the FOO is authorized to spend, the FOO walks away and the unit goes through a different vehicle.

0930. The PA counts out the cash, gets a signed and dated receipt from the vendor (separate from or on the SF 44, depending on local procedure), and confirms the amount matches the SF 44. The vendor's copy goes with the vendor. The FOO's and PA's copies come back with them. The supply gets loaded, the receiving witness signs, and the team rolls back to the unit.

1100. Back at the contracting tent. The FOO builds the transaction file: SF 44, vendor receipt, purchase request, funds certification, the price note, any market research, the receiving signature, and a short MFR for anything unusual that happened at the counter. The folder goes in the open-transactions drawer.

By 1500 (or within 24 hours, whichever comes first). The PA returns to disbursing with the residual cash, all paid vouchers, and the closed DD 1081. The DO reconciles, settles the account, and the PA gets a clean signature back on the settlement side of the 1081. That settled 1081 goes in the same transaction file. The transaction is now closed on the obligation side and the disbursement side.

Same week. The reviewing CCO pulls the transaction file as part of the 100% surveillance review (Step 9). Checklist runs against the architecture set up in Step 8. If anything is missing or looks off, the CCO talks to the FOO and the PA inside 48 hours, not at the end of the month. That's the loop. Repeat it cleanly for every buy.

Itemize every line

Splitting a buy to fit under a threshold

Breaking one buy into smaller pieces to stay under a cap, a threshold, or any other control is splitting. It is forbidden whether the cap is the appointment-letter cap, the Micro-Purchase Threshold (MPT), the Simplified Acquisition Threshold (SAT), or any other control. The rule looks at the requirement, not at how the paperwork got cut. Two SF 44s an hour apart for the same vendor, same supply, same day is a single requirement on paper that the FOO carved in half.

Drift outside the named scope

If the appointment letter names "Class I and life support consumables," and the FOO buys a small generator because the unit needs it and the dollar value is inside the cap, the buy is unauthorized regardless of how reasonable it sounds. The cap is one boundary. The named scope is another. The FOO has authority only for the buys that pass both tests.

This is why being specific about scope in Step 3 matters more than people think. A scope that is too broad ("supplies, equipment, and services") invites drift. A scope that is too narrow forces the unit to bypass the FOO program every time the mission shifts a quarter inch. Aim for the actual operational picture and revise the letter formally when the mission picture changes.

Personal services

A FOO appointment covers non-personal services. Personal services are a different acquisition authority with different controls and different oversight requirements. If the appointment letter accidentally reads broadly enough to cover personal services, it has been drafted wrong. When you draft the letter in Step 7, say "non-personal services" explicitly and avoid open-ended language that could be read either way.

Sub-delegation

A FOO can't hand the authority off to a buddy for the afternoon. The appointment runs to a named individual and is non-delegable. If the FOO is going to be out, the alternate FOO (appointed under a separate letter in Step 5) covers the period. The primary doesn't sub-delegate to anyone, ever. Same applies to the PA: alternates are appointed, not delegated.

"Just use cash" doesn't change the rules

If a buy would be questionable on the GPC or on a formal contract, the same buy is questionable on cash or an SF 44. Paying in cash doesn't sanitize a buy that violates competition, ethics, set-aside rules, or any other compliance question. The instrument is the form. The underlying requirement and conduct are what get reviewed.

DD 1081 (Statement of Agent Officer's Account). This is the form the DO uses to advance cash to the PA, and the same form the DO uses to settle the account when the PA returns paid vouchers, negotiable instruments, and residual cash. The PA's copy of the 1081 lives in the transaction file from cash pickup through settlement. PAs cannot commingle funds, cannot advance cash to anyone else, and cannot normally hold advanced cash overnight. Turn-in is generally within 24 hours of the transaction. Scanned submissions are usually allowed in remote locations if the parent DO has approved that workflow.

DD 2665 (Daily Agent Accountability Summary). This is the contingency turn-in document. The PA prepares it on the day they turn in business to the DO. It is required for contingency PAs and it is day-of-turn-in, not retroactive. If the day's business is one transaction, the 2665 covers that one transaction.

Review cadence. Air Force rules require 100% transaction review within 30 days of each transaction plus an annual review of all FOO program records, with written findings retained three years. Army rules require at least an annual examination with findings retained one year. The right answer for any deployed CCO running a FOO program, regardless of service, is the stricter Air Force cadence. Monthly 100% review (or better, weekly while the program is new) catches trends before they become incidents, gives the FOO and PA fast feedback, and means the surveillance file is built as you go instead of being reconstructed at the annual.

A FOO program lives or dies at the appointment letter and the FOO/PA boundary. If those two are right, the rest of the program is administration and discipline. If either one is wrong, the cleanup is bigger than the program ever was. So when the commander walks into your tent and says "I need a FOO," your first hour is not on the letter, the cap, or the forms. Your first hour is on the appointing authority chain and on getting finance on the call. The rest follows.

Stand it up tight. Appointment letter names the individual, the instrument, the cap, and the scope. FOO and PA stay on different letters held by different people. File architecture built before the first transaction. Pilot narrow, run the Air Force review cadence regardless of service, and push steady-state demand back to the contracting office as soon as a pattern shows up. Verify the supplement text before you sign anything. The RFO is moving citations around as it rolls out, and this is the kind of paperwork where the version stamp matters.