A teaming agreement and a subcontract agreement are not two versions of the same thing. They exist at different stages of a deal, they create different obligations, and confusing them is one of the most reliable ways to do a significant amount of work and end up with nothing enforceable to show for it.
This comes up constantly in government contracting, but it is not limited to that world. Any time two businesses agree to pursue a contract together, one as the prime and one as the support, the question of which document governs which phase of that relationship matters enormously. Most people sign a teaming agreement, win the bid, and assume the rest will sort itself out. It does not sort itself out. It becomes a dispute.
A Teaming Agreement Is a Promise, Not a Contract
The teaming agreement lives in the pre-award phase. It is the document that governs the relationship between a prime contractor and a prospective subcontractor while they are still competing for work. It says, in effect: we agree to pursue this opportunity together, and if we win, here is the general framework for how we intend to divide the work. That last clause is doing enormous legal lifting, and most teaming agreements do not draft it carefully enough.
Under FAR 9.601, a contractor team arrangement is defined as either a partnership or joint venture formed to act as a potential prime contractor, or an agreement between a prime contractor and one or more companies to serve as subcontractors on a specific government contract or acquisition program. The regulation recognizes these arrangements. It does not make them automatically enforceable. That part is your problem.
The critical thing to understand about a teaming agreement is what it is not. It is not a binding commitment to award subcontract work. Courts have repeatedly found that teaming agreements, particularly those with vague or aspirational language about future subcontracting, are unenforceable agreements to agree. If your teaming agreement says something like "the parties intend to negotiate a subcontract in good faith," you may have just written a document that a court will treat as legally meaningless the moment the prime decides to cut you out after award.
FAR 9.603 requires that contractor team arrangements be identified and fully disclosed in the offer, or before the arrangement becomes effective if it is entered into after the offer. This disclosure requirement exists to protect the government's interest in knowing who is actually doing the work. It does not protect yours. Your protection comes from the quality of the document you signed before the bid went in, and most people sign whatever the prime sends over without reading it carefully.
The teaming agreement is also where the relationship's power imbalance is most exposed. The prime controls the proposal. The prime controls the relationship with the contracting officer. The prime controls whether a subcontract gets executed after award. If your teaming agreement does not contain specific, enforceable language about the scope of work reserved for you, the percentage of contract value you are entitled to, and the conditions under which the prime's obligation to subcontract to you is triggered, you are operating on goodwill. Goodwill is not a legal theory.
What a Teaming Agreement Actually Requires to Hold Up
The threshold question any court will ask about a teaming agreement is whether it contains the essential terms of a contract: offer, acceptance, consideration, and definite enough terms to be enforceable. Most teaming agreements fail on the last element. They are full of intent and short on specificity.
If you want your teaming agreement to function as something more than a handshake with formatting, it needs to identify the specific procurement opportunity by name and solicitation number. It needs to state the anticipated work share, expressed as a percentage of contract value or a defined scope of deliverables, not as a vague allocation to be determined later. It needs to address what happens if the prime is awarded the contract and then decides not to subcontract to you, including whether you have a breach of contract claim and what your damages would be.
Exclusivity provisions matter too. A teaming agreement that does not prohibit the prime from teaming with your competitors on the same procurement is not protecting you. It is documenting your participation in your own exposure. If you are contributing proprietary technical approaches, past performance documentation, or key personnel commitments to a proposal, the teaming agreement needs to address what happens to that contribution if the relationship dissolves.
Intellectual property is a common casualty of poorly drafted teaming agreements. If you share proprietary methodologies, pricing models, or technical data as part of the proposal process, and the agreement is silent on ownership and permitted use, you have made a gift. The teaming agreement should specify that any proprietary information shared during the pursuit phase remains the property of the disclosing party and may not be used outside the scope of this specific procurement without written consent. That sentence, or something like it, is not optional.
The Subcontract Is Where the Real Obligations Begin
Once the prime is awarded the contract, the teaming agreement has done its job. The subcontract agreement is what governs everything that happens next. These are not interchangeable documents, and the subcontract does not simply pick up where the teaming agreement left off. It is an entirely new legal instrument with its own terms, its own obligations, and its own risk allocation.
The subcontract agreement defines the actual scope of work the subcontractor will perform, the payment terms, the schedule, the deliverables, the acceptance criteria, and the consequences of non-performance. It incorporates the prime contract's flow-down clauses, which in a government context can be extensive. FAR 9.604(e) makes clear that the prime contractor remains fully responsible for contract performance regardless of any team arrangement. What that means for you as a subcontractor is that the prime's obligation to the government does not become your obligation automatically. Your obligation is defined by your subcontract, and only by your subcontract.
This is where the distinction between the two documents has real financial consequences. A subcontractor who performs work in reliance on a teaming agreement, before a subcontract is executed, is performing work without a payment mechanism. If the prime disputes the scope, disputes the invoice, or simply decides the relationship is no longer convenient, you are in a breach of contract fight over a document that may not be enforceable to begin with. The subcontract is the document that gives you the right to be paid, the right to cure disputes through a defined process, and the right to pursue damages if the prime breaches.
Payment terms in a subcontract deserve particular attention. Many primes insist on "pay-when-paid" or "pay-if-paid" clauses, which condition the subcontractor's payment on the prime's receipt of payment from the government. These clauses are not the same thing, and the distinction matters. A pay-when-paid clause creates a timing mechanism. A pay-if-paid clause, if drafted and enforced as a true condition precedent, can eliminate your right to payment entirely if the government does not pay the prime. California courts have historically disfavored pay-if-paid clauses as applied to certain construction contexts, but outside of those specific statutory protections, the clause can be enforced as written. Read it before you sign it.
The Mistake That Costs People the Work They Won
The most expensive version of this confusion goes like this: a subcontractor invests months in a proposal effort, contributes technical expertise, key personnel commitments, and past performance data, the team wins the award, and then the prime either dramatically reduces the subcontractor's work share or cuts them out entirely. The subcontractor points to the teaming agreement. The prime points to the language that says the parties "intend to negotiate" a subcontract. The subcontractor has no subcontract. The subcontract was never executed.
This is not a hypothetical. It is a recurring fact pattern, and it is almost always preventable. The teaming agreement needed to contain enforceable work share commitments. The subcontractor needed to refuse to allow the proposal to go in without those commitments in writing. And the subcontractor needed to understand, before signing anything, that a teaming agreement is not a guarantee of future work. It is a framework for pursuing future work, and the enforceability of that framework depends entirely on how it was drafted.
The document is not the strategy. Both the teaming agreement and the subcontract agreement require deliberate drafting, not templates downloaded from a government contracting blog. The teaming agreement protects your position during the pursuit. The subcontract protects your position during performance. Neither one protects you if it was written by someone who did not understand what you were actually trying to preserve.
Delina works with contractors, founders, and professionals who need contracts that protect the deal they worked to win, not just the one they hoped for.
If you are entering a teaming arrangement or about to execute a subcontract and you want to know whether your documents will actually hold up, book a paid intake with Delina. This is not a free call. It is a focused, strategic session with an attorney who has read everything above and has specific opinions about your situation.
Ready to put this into practice? Tell us your situation.
Get Started →