A federal teaming agreement usually runs four to eight pages, and most of it will never matter. The confidentiality recitals, the notices section, the counterparts clause: none of that decides anything. What decides everything is a handful of sentences about work share, intellectual property, exclusivity, flow-downs, and payment, and those are almost always the shortest and vaguest lines in the document. If a draft is open on the desk right now, stop reading front to back and go straight to the clauses that decide what happens eleven months from now, when the award lands and the scope has moved. Have counsel paper the final document. What follows is the capture-side read of where the money sits.
Nobody at the agency is going to referee this
FAR 9.601 defines a contractor team arrangement two ways: companies forming a partnership or joint venture to act as a potential prime, or a potential prime agreeing with other companies that they will act as its subcontractors on a specified contract or acquisition program. Almost every teaming agreement an AI, data, or software firm signs is the second form.
FAR 9.603 is the policy and it is one paragraph. The government will recognize the integrity and validity of contractor team arrangements, provided the arrangements are identified and company relationships are fully disclosed in an offer, or before the arrangement becomes effective if formed after submission. It adds that the government will not normally require or encourage dissolution of a team arrangement. That is the whole endorsement.
FAR 9.604 is the part that matters to a subcontractor, because it lists what the arrangement does not do. It does not authorize anything violating antitrust statutes, and it does not limit the government's rights to require consent to subcontracts under Subpart 44.2, to determine the prime's responsibility, to control data rights the government owns, to pursue its policies on competitive contracting and component breakout, or to hold the prime fully responsible for contract performance regardless of any team arrangement with its subcontractors. Read that from the subcontractor's chair. No one at the agency will adjudicate a dispute over scope. The document between two companies is the entire remedy, and a loosely written remedy is no remedy.
One note on the citation itself, because it moved. Under the Revolutionary FAR Overhaul, Subpart 9.6 was removed from the Part 9 model deviation text and the contractor-team-arrangement material went into the FAR Companion Guide, which is guidance rather than regulation. Agencies have been running on class deviations while the FAR Council works through rulemaking, a phase it entered with a Federal Register publication on June 23, 2026. A negotiator who opens with "FAR 9.604 says" may be quoting text the buying activity no longer carries. The substance is unchanged: the government stands outside the arrangement, and the prime owns performance.
Where the money actually sits
The ranking below scores how much each clause moves the economics for the smaller party. A 96 means the clause can decide whether the deal is worth signing at all; a 69 means it costs real money but rarely kills the arrangement. This is editorial judgment from published case law and standard clause text, not a measured statistic.
Clause severity for the subcontracting party — editorial 0–100 scale
Red flag one: a percentage with no scope behind it
The most common teaming agreement in circulation promises a work-share percentage and then says the parties will negotiate a subcontract in good faith after award. Courts in Virginia, where a large share of federal teaming disputes land, have repeatedly held that construction to be an unenforceable agreement to agree.
In Cyberlock Consulting, Inc. v. Information Experts, Inc., decided in the Eastern District of Virginia in 2013 and affirmed by the Fourth Circuit in January 2014, a teaming agreement promising Cyberlock 49 percent of the work on an Office of Personnel Management award was held unenforceable because the subcontract terms were left to future negotiation. The prime won, the work share did not follow, and the courts found nothing to enforce.
The Supreme Court of Virginia landed in the same place in Navar, Inc. v. Federal Business Council, 291 Va. 338 (2016), on a Defense Threat Reduction Agency award. That agreement conditioned subcontracts on the parties "arriving at prices, terms and conditions acceptable to the parties." The court found it did not contain a sum, or any reasonably certain method for determining a sum, and treated the whole of it as an agreement to agree to negotiate later.
The lesson is not that teaming agreements are worthless. It is that the promise fails at exactly the point where the numbers are missing. Three fixes close that gap, and none is an unusual ask. Attach the scope as an exhibit: a statement of work naming the CLINs, tasks, or proposal sections the subcontractor will own, at the detail the technical volume will use. Attach the labor categories and rates: named categories with unit rates and an escalation assumption, which supplies the reasonably certain method for determining a sum the Virginia courts found missing. Set a definitization deadline with a default: the parties execute a subcontract within a stated number of days after award, and the exhibit governs if they do not. Without the default, the deadline is one more agreement to agree.
| What the draft says | What it does when the award lands | What to ask for instead |
|---|---|---|
| "Prime intends to subcontract approximately 30% of the work." | Intent is not obligation, and the percentage has no denominator. | Named scope in an exhibit, rates attached, definitization deadline with the exhibit as the default. |
| "The parties shall negotiate a subcontract in good faith." | The construction two Virginia courts declined to enforce. | The subcontract form attached as an exhibit, unsigned, with only the funded value blank. |
| "All prime contract clauses are incorporated by reference." | Obligations nobody has read, some written for firms with audited indirect rates. | An enumerated schedule, plus a rule that clauses inapplicable at the subcontract value or type do not apply. |
| "All work product developed hereunder shall be the property of Prime." | Read literally, anything touching pre-existing technology lands in the prime's column. | Background IP stays with its owner. Foreground IP defined narrowly, licensed for this program only. |
| "Payment is conditioned on Prime's receipt of payment." | The prime's invoicing pace becomes the subcontractor's cash-flow problem, with no ceiling. | Net terms from receipt of a proper invoice, plus FAR 52.232-40 language as written. |
| "Subcontractor shall not solicit or hire any Prime employee for 24 months." | A broad, untargeted hiring restraint, in an area federal enforcers are watching. | Narrow to people who worked this pursuit, cap at 12 months, carve out general job postings. |
| "This Agreement terminates upon award of the prime contract." | Protections expire in the window between award and subcontract execution, where disputes happen. | Survival through subcontract execution or a stated number of days after award, whichever is later. |
Red flag two: exclusivity with no edges
Exclusivity is usually one sentence, it costs the prime nothing to type, and it is often the most expensive thing a subcontractor gives away in a quarter. The problem is rarely that a prime asks. It is that the clause carries no boundary on the three dimensions that matter: which pursuit, for how long, and across what technical scope.
Bounded three ways, exclusivity is cheap to grant and still gives the prime what it needs. Scoped to a single named solicitation, expiring on a date certain or on non-award, and confined to the technical area the team is bidding, it protects the prime's investment without taking the subcontractor off the board for a whole domain. Unbounded, it is a free option written by the party holding it. Treat it as a scoping negotiation rather than a yes-or-no question; the full trade is covered in exclusivity in teaming agreements. And watch for the version that binds one side only, which is not exclusivity but an option.
Red flag three: the IP clause that reaches your background technology
"All work product developed hereunder shall be the property of Prime" means very little in a pre-award document and a great deal later. During the proposal phase the parties exchange architecture, benchmark results, and sometimes running code, and a clause assigning everything "developed hereunder" without defining background technology can be read to sweep in improvements to a product the subcontractor already owns.
Three definitions fix it. Background intellectual property, anything a party owned or developed outside this pursuit, stays with its owner and is licensed rather than assigned. Foreground intellectual property, what is created specifically for this pursuit, is defined narrowly and allocated explicitly. Deliverable data, what will actually be delivered under the eventual government contract, is governed by the prime contract's data rights clauses rather than by the teaming agreement.
For firms holding SBIR or STTR data rights the stakes are higher. DoD revised DFARS 252.227-7018 in January 2025 to adopt a single, non-extendable 20-year SBIR/STTR data protection period, replacing an older five-year period that could be extended, and when the period ends the government receives perpetual government purpose rights rather than unlimited rights. That protection is often the most valuable asset a research-driven firm holds. It is not something to license away in a four-page pre-award document signed under deadline pressure.
The other half of the question is what the prime may do with the proposal. FAR 52.215-1(e) restricts government disclosure and use of proposal data through a title-page legend and per-sheet markings. That governs the government's handling and does nothing about the prime. Say plainly in the agreement that technical material furnished for the proposal may be used for this proposal and no other, and is returned or destroyed if the team does not bid or does not win.
Red flag four: flow-downs incorporated by reference
"All terms and conditions of the prime contract are incorporated herein by reference" is one line that can obligate a firm to hundreds of pages nobody has read. Some of those clauses belong on a subcontract. Some are written for entities with audited indirect rate structures. Some do not apply at the subcontract's dollar value at all.
Ask for an enumerated schedule. A prime with a mature subcontracts function has one. Then add a governing rule: clauses inapplicable at the subcontract type or dollar value do not apply, and clauses mandatory by regulation flow down as written rather than paraphrased. Two thresholds moved on October 1, 2025 under the FAR Council's inflation adjustment: the simplified acquisition threshold from $250,000 to $350,000, and certified cost or pricing data from $2 million to $2.5 million. A schedule built from an older template can attach obligations at levels that no longer apply.
The cyber flow-downs deserve their own read. DFARS 252.204-7012 already reaches any subcontractor handling covered defense information, carrying the NIST SP 800-171 control set and 72-hour incident reporting. DFARS 252.204-7019 and 252.204-7020 put the self-assessment score in the Supplier Performance Risk System, where a prime can see both the score and how old it is. The DoD final rule integrating CMMC into contracts took effect November 10, 2025, adding DFARS 252.204-7021 as the requirement clause and DFARS 252.204-7025 as the solicitation provision that makes CMMC status a condition of award eligibility. Flow-down is required where the subcontractor will process, store, or transmit federal contract information or controlled unclassified information on its own systems; subcontractors post their own affirmations in SPRS, and the prime stays responsible for the outcome. A teaming agreement committing a firm to a level it does not hold, on a schedule it has not planned, trades the prime's schedule risk against the subcontractor's balance sheet. State the posture, state the plan, put the date in the document.
Red flag five: payment with no clock
Pay-when-paid language shifts the prime's invoicing performance onto the subcontractor's cash position. It is common, it is often negotiable, and the fix is to attach a clock: net terms running from receipt of a proper invoice, with a defined format and a named approver. That converts an open-ended wait into a schedule a firm can finance against.
One federal clause is worth naming. FAR 52.232-40 requires a contractor that receives accelerated payments from the government to make accelerated payments to its small business subcontractors within 15 days of receipt, to the maximum extent practicable, after a proper invoice, and to do so without further consideration from or fees charged to the subcontractor. It flows down to subcontracts with small business concerns. The clause creates no new rights under the Prompt Payment Act, so it is a standard rather than a remedy, and asking for it as written rather than paraphrased into something softer is a specific, reasonable request. Read the setoff clause in the same section: a broad right to withhold against "any amounts owed under any agreement between the parties" turns an unrelated commercial dispute into a stopped payment on federal work.
Red flag six: a non-solicitation clause that outlives the pursuit
Restrictions on hiring each other's people are standard, and usually drafted far broader than the pursuit requires: two years, all employees, both directions, surviving termination. The commercial rationale is real. A prime that introduces a subcontractor to its program staff does not want to lose them. But the exposure has grown.
The federal picture moved twice. The FTC's non-compete rule was set aside by a federal district court in Texas in August 2024, the Commission voted to abandon its appeal in September 2025, and it removed the rule from the Code of Federal Regulations in a February 2026 Federal Register action. That is not a green light. The FTC created a Joint Labor Task Force in February 2025 aimed at case-by-case enforcement against non-compete, no-poach, non-solicitation, and no-hire agreements. On the criminal side, the Justice Department won its first jury conviction in a labor-market antitrust case in April 2025, a wage-fixing prosecution in Nevada, after several years of acquittals.
None of that makes a narrow non-solicit unlawful between two firms collaborating on a specific bid. It does mean a broad, long, untargeted no-hire clause is a worse trade in 2026 than it was in 2019. Narrow it to individuals who actually worked the pursuit, cap the term at twelve months, and carve out responses to general public job postings. A prime with experienced counsel usually agrees, because the narrow version is the one that holds up.
Red flag seven: rights that only run one way
Read the term and termination section against the exclusivity section. The pattern to catch is a prime that may terminate for convenience on ten days' notice while the subcontractor stays exclusively bound through award and beyond. That hands one party an option and the other an obligation. Two clauses nearby deserve the same treatment. A substitution right, some version of "Prime may substitute another subcontractor in its discretion," is a proposal integrity question as well as a business one when the subcontractor's named people are in the technical volume; ask for notice and a chance to cure. And an agreement the prime may assign freely, including to an acquirer, while the subcontractor may not assign at all, is worth making mutual. The mirror test settles most of these fast: read the clause with the party names swapped, and if it would be unacceptable that way, it earns a redline this way.
The red flags that come from your own status
Two of the most expensive problems in teaming have nothing to do with the prime's draft. They come from the small business rules, and they bite hardest when the smaller firm is the prime.
Limitations on subcontracting. Under FAR 52.219-14 and 13 CFR 125.6, a small business prime on a set-aside for services other than construction may not pay more than 50 percent of the amount paid by the government for contract performance to subcontractors that are not similarly situated entities, and work a similarly situated entity further subcontracts counts against that 50 percent. A teaming agreement handing a large partner the majority of the technical labor can put the prime out of compliance on day one.
The ostensible subcontractor rule. Under 13 CFR 121.103(h), SBA finds affiliation where a subcontractor that is not similarly situated performs the primary and vital requirements of a contract, or where the prime is unusually reliant on it. SBA looks at all aspects of the relationship, and the teaming agreement is one of the documents examined. The consequence is not a penalty, it is ineligibility as a small business concern for that award. Clauses giving a large partner control over technical direction, key personnel selection, or management of the work are what show up in these determinations.
From the other chair, know your size status under the solicitation's NAICS code before the first call. Under FAR 19.702 a prime that is not small must submit a subcontracting plan on awards expected to exceed $900,000 where subcontracting opportunities exist, raised from $750,000 effective October 1, 2025. That plan is the machinery behind the socioeconomic questions in a diligence packet.
Reading a flow-down schedule built from an older template
The FAR Council's inflation adjustment, published August 27, 2025 and effective October 1, 2025, raised the micro-purchase threshold to $15,000, the simplified acquisition threshold to $350,000, certified cost or pricing data to $2.5 million, and the subcontracting plan floor to $900,000, with construction at $2 million. Older clause matrices attach obligations at the previous levels.
The levers a subcontractor actually has
The picture so far is one-sided by design, because the drafting party writes for itself. There is real counterweight on the other side, and the strongest piece sits in FAR 52.219-9, the small business subcontracting plan clause. It obligates a prime to make a good faith effort to acquire the work from the small business concerns it used in preparing the bid or proposal, in the same or greater scope, amount, and quality used in preparing and submitting that proposal. The clause defines "used in preparing" two ways: identifying the concern as a subcontractor in the proposal or the associated subcontracting plan, or using its pricing, cost information, or technical expertise where there is written evidence of an intent or understanding that it will receive a subcontract for the related work. If the prime does not follow through, it owes the contracting officer a written explanation within 30 days of contract completion.
Two things follow. Being named in the proposal or the subcontracting plan is materially different from being an informal helper, so confirm in writing which is happening. And "written evidence of an intent or understanding" is exactly what a teaming agreement with an attached scope exhibit creates: the document that protects a subcontractor commercially is the same one that triggers the prime's regulatory obligation. Three smaller levers sit alongside it. Disclosure of the team arrangement in the offer is the prime's obligation, not a favor. Consent to subcontracts under FAR Subpart 44.2 and FAR 52.244-2 means the contracting officer may look at the arrangement on certain contract types. And a prime cannot name a firm, its people, or its past performance without permission, which is real control in the days before submission.
The read-before-signing pass
A working order for the last hour with the document.
- Is there a scope exhibit naming tasks or CLINs rather than a percentage? If it is missing, fix that before anything below.
- Are labor categories and rates attached, with a definitization deadline and a stated default?
- Does the agreement survive past award, or expire into the gap before the subcontract is signed?
- Is exclusivity bounded on all three axes: this pursuit, a date certain, a defined technical scope?
- Is background intellectual property defined and excluded from any assignment? Check SBIR and STTR data rights specifically.
- Is proposal material limited to this proposal, returned or destroyed on a loss?
- Is there an enumerated flow-down schedule, and does the cyber commitment match the posture the firm can hold at award?
- Do payment terms run from receipt of a proper invoice, and is the setoff right limited to this agreement?
- Read every unilateral right with the party names swapped. Termination, substitution, assignment, and audit are the usual four.
Bottom line
A teaming agreement is the only instrument standing between a subcontractor and a scope that moves after award, and the government is not a party to it. Published decisions keep saying the same thing in different words: the promise fails at the point where the numbers are missing. Attach the scope, attach the rates, set a deadline with a default, bound the exclusivity, protect the background technology, and run every unilateral right through the mirror test. A prime that has done this before reads all of those as the requests of a firm that knows the work.
Frequently asked questions
Parts of it usually are, and the part most subcontractors care about often is not. Confidentiality, exclusivity, and proposal-support obligations are typically enforceable. A promised work share frequently is not, because it is written as an agreement to negotiate a subcontract later. Two Virginia decisions held exactly that: Cyberlock Consulting v. Information Experts (E.D. Va. 2013, affirmed by the Fourth Circuit in 2014) and Navar, Inc. v. Federal Business Council, 291 Va. 338 (2016). A scope exhibit, rates, and a definitization deadline close the gap.
No. FAR 9.604 preserves the government's rights and holds the prime fully responsible for performance regardless of any team arrangement, and the government does not adjudicate disputes between team members. Where a subcontracting plan applies, FAR 52.219-9 requires a prime to make a good faith effort to use the small business concerns it used in preparing its proposal, and to give the contracting officer a written explanation if it does not. That is a real lever, and a weaker one than enforcement.
Not by blanket reference. Ask for an enumerated schedule and a rule that clauses inapplicable at the subcontract type or dollar value do not apply. For defense work the cyber set matters most: DFARS 252.204-7012 reaches subcontractors handling covered defense information, and the CMMC final rule effective November 10, 2025 added DFARS 252.204-7021 and 252.204-7025.
It can, when the smaller firm holds the prime position. Under 13 CFR 121.103(h), SBA examines the teaming agreement among other documents in applying the ostensible subcontractor rule, which finds affiliation where a subcontractor that is not similarly situated performs the primary and vital requirements, or where the prime is unusually reliant on it. Separately, FAR 52.219-14 and 13 CFR 125.6 cap payments to subcontractors that are not similarly situated at 50 percent of the amount paid by the government for services other than construction.