A Basic Ordering Agreement (BOA) is a written agreement between a federal agency and a contractor that establishes terms, clauses, and procedures that may apply to future contracts or orders. It is designed for situations in which the parties expect recurring acquisition activity but cannot establish all future requirements at the time the agreement is created.
A BOA is not itself a contract. FAR 16.703 expressly distinguishes the agreement from the contractual instruments that may later be issued under it. The BOA establishes a framework for future business, while an actual contractual obligation arises when an authorized order is issued and accepted or otherwise becomes binding in accordance with the agreement and applicable acquisition procedures.
The practical advantage is that the parties do not need to renegotiate the same administrative provisions every time a recurring requirement appears. They can establish common terms in advance and concentrate future acquisition activity on the specific supplies or services, quantity, price, delivery requirements, and other details relevant to each order.
What a Basic Ordering Agreement Establishes
BOAs are useful when an agency expects to purchase substantial quantities of supplies or services over time but cannot determine the exact items, quantities, or prices far enough in advance to establish a conventional contract covering all future requirements.
Instead of attempting to predict every future transaction, the agency and contractor establish a common contractual framework. FAR 16.703 provides that a BOA should contain terms and clauses applying to future contracts between the parties during its term, a description of the supplies or services to be provided, and methods for pricing, issuing, and delivering future orders.
The agreement may address matters such as:
- contract clauses expected to apply to future orders;
- a description of the supplies or services that may be ordered;
- methods for determining prices when orders are issued;
- procedures for issuing and accepting orders;
- delivery, invoicing, and administrative procedures;
- responsibilities of the parties when individual requirements arise.
This advance framework can be particularly valuable when similar requirements occur repeatedly. Administrative issues that would otherwise need to be negotiated for each acquisition can already be addressed in the BOA.
The agreement still needs enough specificity to provide a workable basis for future transactions. A BOA is not simply a general statement that an agency may buy something from a contractor later. Its terms should establish how future contracting activity will operate.
At the same time, the BOA cannot establish all elements of future acquisitions because some information is not yet available. Price, quantity, delivery schedule, funding, and detailed technical requirements may need to be established when a particular order is prepared.
A BOA Is Not a Government Contract
The legal status of a BOA is one of the most important aspects of the term. Signing the agreement does not by itself obligate the Government to purchase supplies or services, and it does not guarantee the contractor a particular amount of federal business.
No funds are obligated merely because the parties have established a BOA. The Government also does not promise to issue a minimum number of orders unless a separate contractual commitment provides otherwise.
This creates a clear separation between the agreement and the later contractual action:
| Instrument or Event | Creates Purchase Obligation? | Primary Function |
|---|---|---|
| Basic Ordering Agreement | No | Establishes terms and procedures for future contracting |
| Request for an Order or Proposal | No | Defines a prospective requirement and seeks contractor response |
| Accepted Order Under the BOA | Yes, when properly established as a contract | Creates an obligation for specific supplies or services |
| BOA Modification | Not by itself | Updates the framework for future transactions |
A contractor should not treat the potential value of anticipated BOA activity as awarded contract revenue. Even if the agency expects significant future requirements, those requirements remain prospective until appropriate contractual actions are completed.
This characteristic also distinguishes a BOA from an indefinite-delivery contract. An IDIQ contract, for example, is a contract and includes a contractual minimum that the Government is obligated to order. A BOA establishes no comparable minimum merely by existing.
The distinction affects internal planning. A contractor may maintain personnel, supplier relationships, or technical capabilities in anticipation of BOA orders, but those business decisions should account for the absence of a guaranteed ordering volume.
How Orders Are Established Under a BOA
When a requirement covered by the BOA arises, the agency can use the established agreement as the foundation for the transaction. The acquisition still requires an authorized contracting action, and the contracting officer must ensure that applicable competition, pricing, funding, and other requirements have been satisfied.
The BOA does not provide authority to bypass federal procurement rules. FAR 16.703 states that orders based on a BOA must comply with applicable competition requirements. The existence of the agreement does not automatically make the BOA holder the exclusive source for every requirement described by the agreement.
Before an order becomes binding, the contracting officer must address the elements necessary for the particular acquisition. Depending on the transaction, the process may involve:
- identifying a requirement that falls within the scope of the BOA;
- defining the specific supplies, services, quantities, or performance requirements;
- establishing or negotiating the price using the method contemplated by the agreement;
- satisfying applicable competition and acquisition requirements;
- confirming funding and contracting authority;
- issuing the order and obtaining acceptance when acceptance is required.
Pricing deserves particular attention because a BOA can be established before exact prices for future work are known. The agreement may define how prices will be developed rather than state a fixed price for every possible requirement.
For example, the BOA might establish labor categories, pricing procedures, cost principles, negotiation methods, or other mechanisms that can be applied when a specific requirement is identified. The contracting officer then uses the relevant method to establish the price for the resulting order.
An order should clearly identify which BOA provisions apply and specify any additional terms required for the individual acquisition. If a particular order conflicts with or supplements the underlying agreement, the contractual documents should make the relationship between those provisions clear.
When Federal Agencies Use BOAs
A BOA can be appropriate when an agency anticipates repeated contracting with a supplier but does not yet have enough information to negotiate complete contracts for all expected requirements. This often occurs when future needs depend on operational events, equipment conditions, technical developments, or demand that cannot be scheduled precisely.
Recurring repair requirements provide a useful example. An agency may operate specialized equipment that periodically requires components or technical services from a particular industrial source. The agency knows that requirements are likely to arise, but it cannot predict exactly which components will fail or what repairs will be required during the year.
A BOA can establish common contractual terms before those events occur. When a specific repair requirement later appears, the agency can focus on the scope, price, schedule, and funding associated with that transaction.
The arrangement can also support acquisitions involving:
- recurring supplies for which exact future configurations are uncertain;
- repair, maintenance, or overhaul work triggered by actual equipment conditions;
- specialized technical services requested as individual needs develop;
- repetitive purchases where advance agreement on administrative terms can reduce negotiation time.
The expected frequency of future transactions matters. Establishing and maintaining a BOA provides less benefit when the parties are unlikely to conduct recurring business. The mechanism is most useful when advance agreement on common provisions can materially simplify later acquisitions.
A BOA should also be reviewed periodically. FAR 16.703 provides for review before the beginning of each fiscal year and revision as necessary to conform to applicable requirements. Clauses, regulations, pricing approaches, agency procedures, or the nature of anticipated acquisitions can change over time.
Keeping the agreement current prevents future orders from relying on obsolete terms and reduces the amount of corrective work required when a new requirement arises.
Competition and the Limits of a BOA
A common misunderstanding is that establishing a BOA gives the contractor a standing right to receive all future work covered by the agreement. Federal acquisition rules do not treat the mechanism that way.
The agency must still comply with applicable competition requirements when placing orders. The BOA provides an established framework for contracting, but it does not independently justify directing work to a particular contractor without the competition or justification required for that acquisition.
Similarly, an agency should not use a BOA when an indefinite-delivery contract would be more appropriate. FAR 16.703 cautions against using a BOA to avoid establishing an indefinite-delivery contract when the circumstances support that type of contractual commitment.
The choice matters because the instruments create different obligations. A BOA provides administrative readiness for future contracts. An indefinite-delivery contract creates an existing contractual relationship under which orders are placed according to its terms.
For contractors, this means that the business value of a BOA depends heavily on future acquisition activity rather than the agreement alone. The company may have completed negotiations over important terms and positioned itself to respond efficiently when requirements arise, but it still needs to compete for or otherwise properly receive the resulting work.
The same principle applies to agencies. A BOA can shorten the path from a newly identified requirement to a completed contracting action because many recurring terms are already established, but each order must still rest on proper authority, funding, pricing, and acquisition procedures. Until that contractual action occurs, the BOA remains a framework for future business rather than a government promise to buy.
