A teaming agreement is a pre-award contract between two or more companies that agree to pursue a specific federal procurement together, usually with one acting as the prime contractor and the others lined up to receive subcontracts if the team wins. The Federal Acquisition Regulation recognizes these arrangements under Subpart 9.6 as a way for companies to “complement each other’s unique capabilities” and give the government “the best combination of performance, cost, and delivery.”1Acquisition.GOV. FAR 9.602 – General The document itself is straightforward to draft and dangerous to draft badly. Whether it actually binds the prime to issue the promised subcontract after award depends on language choices that most participants underestimate until the contract is won and the subcontractor is cut out.
What the FAR Recognizes
FAR 9.601 defines a contractor team arrangement two ways: two or more companies form a partnership or joint venture to serve as prime, or a potential prime agrees with other companies to have them act as subcontractors on a specified government contract.2Acquisition.GOV. FAR Subpart 9.6 – Contractor Team Arrangements The second structure is the common one. One company leads, holds the direct relationship with the government, and bears full responsibility for performance. The others contribute specialized skills, past performance credentials, or workforce capacity through subcontracts.
Under FAR 9.603, the government will “recognize the integrity and validity” of team arrangements provided the relationships are fully disclosed in the offer.3eCFR. 48 CFR 9.603 – Policy Teams typically form before proposal submission, though they can form after award. The prime remains fully responsible for performance regardless of the arrangement. It cannot deflect responsibility for missed deliverables or quality problems onto a teammate.
What the Agreement Needs to Cover
A teaming agreement sets the ground rules for the proposal phase and for what happens if the team wins. The essentials are narrow but non-negotiable.
- Roles and structure. Identify which company is prime and which are subcontractors, name the specific solicitation or program, and describe the capabilities each party brings.
- Work share. Express the split as a percentage of contract value or labor hours, with labor categories and rates locked in before the proposal goes out. These figures feed the cost proposal, so they need to be realistic.
- Duration. Most agreements run from execution through contract award. If the team loses, the agreement typically expires. If it wins, the agreement bridges the gap until a formal subcontract is executed.
- Subcontract commitment. The agreement should state that the prime will enter into a subcontract with the teammate upon award and that the subcontract terms will be substantially consistent with the work share and rates in the proposal.
Vague language is where teams get burned. A statement that the parties “intend to work together” is close to worthless. The more specific the agreement is about scope, pricing, and deliverables, the more likely a court will treat it as a real commitment rather than a preliminary handshake.
Why Many Teaming Agreements Are Unenforceable
Courts routinely distinguish between a binding contract and an “agreement to agree,” and teaming agreements land on the wrong side of that line with alarming frequency. The leading case is Cyberlock Consulting, Inc. v. Information Experts, Inc., where the Fourth Circuit upheld a ruling that a teaming agreement was unenforceable. The agreement required the parties to “exert reasonable efforts to negotiate a subcontract” and allowed termination if negotiations failed. The court found that language made it an agreement to agree rather than a binding obligation.4Justia. Cyberlock Consulting, Inc. v. Information Experts, Inc. The agreement described the subcontract as “contemplated,” the work share as “anticipated,” and Cyberlock’s role as being “as presently understood by the parties.” Tentative wording was enough to sink it.
The consequence was concrete. The prime won a major contract using Cyberlock’s capabilities in the proposal, then refused to issue the promised subcontract. Cyberlock had no remedy.
Drafting for Enforceability
To avoid that outcome, the agreement should read like a commitment. Use mandatory language. “The prime contractor shall enter into a subcontract” carries weight that “the parties will negotiate in good faith toward a subcontract” does not. Attach a draft subcontract as an exhibit so the essential terms already exist. Lock in scope, pricing, period of performance, and dispute resolution. Minimize termination triggers, because every exit ramp is a reason a court might find the agreement was never really binding. A clause saying the agreement terminates if the parties “cannot agree on subcontract terms after good-faith negotiations” is precisely the kind of provision Cyberlock pointed to as evidence of an unenforceable agreement.
Some teams add a liquidated damages provision: a fixed sum the prime must pay if it fails to issue the subcontract after winning. This gives the subcontractor a concrete remedy and signals to a court that the parties meant the agreement to have teeth. To be enforceable, the figure must be a reasonable estimate of harm caused by breach, not a penalty.
Exclusivity: Value and Risk
Both sides usually want commitment. The prime wants assurance that a key teammate isn’t also teaming with a competitor on the same solicitation. The subcontractor wants assurance that the prime won’t swap it out for a cheaper alternative. Exclusivity clauses address that, but they carry real risks.
Antitrust regulators watch exclusivity because it restricts competition. The DOJ and FTC have signaled that while government contracting often requires collaboration between competitors, exclusive arrangements that reduce competition or raise prices draw scrutiny. Some agencies go further. NAVAIR has used supplemental FAR clauses requiring offerors to disclose exclusive teaming arrangements and explain why they don’t inhibit competition. If the government determines an exclusive arrangement restricts competition, the proposal can be disqualified.
For a subcontractor, exclusivity is a gamble. If the prime loses the bid or decides not to propose at all, the subcontractor may have locked itself out of teaming with anyone else on that solicitation. The agreement should specify what happens to the exclusivity obligation if the prime fails to submit a proposal or the team loses.
Small Business Traps: Affiliation and the Ostensible Subcontractor Rule
For small businesses, teaming carries a specific trap that can cost eligibility for set-aside contracts. The SBA determines size by looking at a company and its affiliates. Under 13 CFR 121.103, concerns are affiliates when one controls or has the power to control the other, and the SBA evaluates the “totality of the circumstances,” including contractual relationships like teaming agreements.5eCFR. 13 CFR 121.103 – How Does SBA Determine Affiliation
The bigger danger is the ostensible subcontractor rule. Under 13 CFR 121.103(h)(3), a small business prime is ineligible for a set-aside if it has an ostensible subcontractor, defined as a subcontractor that is not a similarly situated small business and either performs the “primary and vital requirements” of the contract or is a company the prime is “unusually reliant” upon.5eCFR. 13 CFR 121.103 – How Does SBA Determine Affiliation If a small prime teams with a large business that ends up doing most of the meaningful work, a competitor can file a size protest and knock the team out.
This rule interacts with limitations on subcontracting. Under FAR 52.219-14, a small business prime on a services contract cannot pay more than 50% of the government’s payment to subcontractors that aren’t similarly situated small businesses. For general construction that ceiling rises to 85%, and for specialty trade construction, 75%.6Acquisition.GOV. FAR 52.219-14 – Limitations on Subcontracting Allocating too much work to a large teammate can violate both the ostensible subcontractor rule and the subcontracting limitations at once.
The mentor-protégé program provides one exception. Joint ventures between an SBA-approved mentor and its protégé receive an exclusion from affiliation rules, allowing a large mentor to participate without the protégé losing its small business status. The exception applies only to approved mentor-protégé relationships, not to ordinary teaming agreements.
Antitrust Limits When Competitors Team
When two companies that could bid independently choose to team, they’ve reduced the number of competitors in the procurement. That alone doesn’t violate antitrust law, and the DOJ and FTC acknowledge that government contracting often requires collaboration. But the line between legitimate teaming and illegal collusion can be thin.
The DOJ and FTC joint guidelines on competitor collaborations identify categories that are treated as per se illegal: price fixing, output restrictions, market allocation, and bid rigging.7Federal Trade Commission. Antitrust Guidelines for Collaborations Among Competitors An arrangement between competitors that divides markets, along the lines of “you take this solicitation, I’ll take the next one,” falls in that category. So does agreeing on pricing outside the scope of the specific joint proposal.
Penalties are severe. Under Section 1 of the Sherman Act, bid rigging is a felony carrying fines up to $100 million for corporations and $1 million for individuals, plus imprisonment of up to 10 years.8Office of the Law Revision Counsel. 15 USC 1 – Trusts, Etc., in Restraint of Trade Illegal The FTC notes that fines can reach twice the gain or loss from the offense, which on large government contracts often exceeds the statutory maximum.9Federal Trade Commission. Bid Rigging
Agreements outside the per se categories are evaluated under the rule of reason, which weighs procompetitive benefits against competitive harm. Regulators look at whether the collaboration is reasonably necessary to achieve efficiencies and whether less restrictive alternatives exist. Sharing competitively sensitive information such as cost data, pricing strategies, or future bidding plans beyond what the specific proposal requires is a red flag that can prompt investigation even when the teaming itself is legitimate.
Intellectual Property, Confidentiality, and Personnel
A joint proposal requires sharing technical designs, proprietary methods, cost structures, and other sensitive information that neither party would normally hand over. The agreement should include non-disclosure provisions that restrict use of shared information strictly to the pursuit being bid.
Ownership of pre-existing intellectual property, often called background IP, stays with the party that created it. New work product developed jointly during the proposal phase needs clear ownership rules. Without them, both parties may claim rights to the same technical approach, and resolving that later is expensive and uncertain. The agreement should specify whether jointly developed IP is co-owned, licensed, or assigned.
Non-solicitation clauses are also common, since close collaboration exposes each side to the other’s key personnel. Courts are more likely to enforce these provisions when they’re narrowly drawn, prohibiting direct recruitment rather than preventing an employee from independently applying to the other company. Overly broad restrictions face enforceability challenges in many jurisdictions.
Conflicts of Interest That Can Disqualify the Team
FAR Subpart 9.5 governs organizational conflicts of interest, and those rules can disqualify a team before the proposal is filed. If one team member has an advisory or evaluation relationship with the procuring agency, having helped develop the requirements or evaluated other offers, that relationship can taint the entire team.10Acquisition.GOV. FAR Subpart 9.5 – Organizational and Consultant Conflicts of Interest A contractor that helped draft the technical requirements for a solicitation generally cannot compete for the resulting contract, and teaming with that contractor can extend the conflict outward.
Before formalizing a teaming arrangement, both parties should disclose any existing or recent advisory relationships with the procuring agency. Discovering a conflict after months of proposal effort is a costly mistake that due diligence prevents.
Termination Provisions
The agreement should spell out how and when the relationship ends. Common triggers include:
- Loss of the bid, in which case the agreement typically expires.
- The prime deciding not to submit a proposal, freeing the subcontractor to pursue other options.
- Government disapproval of a proposed subcontractor.
- Material breach, such as missed proposal deadlines or a failure to provide committed resources.
- Execution of the subcontract, which supersedes the teaming agreement.
The termination clause is where enforceability concerns resurface. A trigger for termination “if the parties cannot agree on subcontract terms despite good-faith negotiations” is common, but as Cyberlock showed, that language can be used to argue the entire agreement was never binding.4Justia. Cyberlock Consulting, Inc. v. Information Experts, Inc. Subcontractors should push to minimize these exit ramps. Primes want flexibility. The negotiation over termination provisions often reflects the underlying power dynamic between the parties.
The Bait-and-Switch Risk
A recurring fear for subcontractors is that the prime will use their capabilities and past performance to win the contract, then drop them after award. The teaming agreement is the primary protection, which is why the enforceability drafting matters so much. The government also treats certain bait-and-switch conduct as a procurement integrity problem. The GAO has sustained protests where an offeror proposed specific personnel it did not reasonably expect to provide during performance, calling that a material misrepresentation that undermines the integrity of the procurement. The remedy can be exclusion from the competition.
FAR 9.603 provides some structural protection by stating that the government “will not normally require or encourage the dissolution of contractor team arrangements.”3eCFR. 48 CFR 9.603 – Policy That’s a long way from “will enforce your teaming agreement for you.” The government is not a party to the agreement and generally stays out of disputes between team members. Your protection comes from the agreement itself and the state contract law that governs it, which turns everything back on how well the document was drafted.