Teaming Agreements and the Workshare Math That Keeps a Partnership Fair
A 40/60 workshare split sounds clean until the SOW tasks don't match. Here's how to structure teaming agreements that hold up at award.
June 22, 2026 · Winrove Team
Teaming agreements are legal instruments, but most small business proposal teams treat them as handshake documents with a signature block. This post covers the workshare math, the clauses that protect both sides, and the sequencing that prevents a partnership from collapsing between proposal submission and option year two.
The Three Numbers Every Teaming Agreement Needs
Before a single proposal section gets drafted, the prime and sub should agree on three figures and put them in writing.
- Floor percentage by CLIN or WBS element. This is the minimum the sub will perform, expressed in labor hours or dollars tied to specific deliverables. It is not a target. It is a floor with a cure mechanism if the prime falls below it.
- Proposal representation percentage. This is the number that goes into the subcontracting plan and the price volume. It should be equal to or higher than the floor. Federal Acquisition Regulation (FAR) 52.219-9 requires large business primes to submit subcontracting plans with goals; small business primes on set-aside contracts are not exempt from agency-specific subcontracting requirements, and many solicitations include a clause requiring the prime to flow down workshare commitments regardless of business size.
Exclusivity, Non-Compete, and the Bid Window
Teaming agreements routinely include an exclusivity clause: Sub A agrees not to team with a competing offeror on the same solicitation. That clause is standard and enforceable in most jurisdictions. What is less standard, and more important, is defining the bid window precisely.
"For the duration of this procurement" is ambiguous. Does it end at proposal submission? At award? At the end of the base period? A sub that signs an open-ended exclusivity clause and then watches the prime lose the award is locked out of a potential teaming relationship with the winner. The clause should read: "This exclusivity obligation expires 90 days after the government's notification of award, or upon written release by the Prime, whichever occurs first." That protects the sub's ability to pursue work if the prime does not win.
The non-compete provision, which typically prevents the sub from independently pursuing the same contract vehicle for a defined period, should be scoped narrowly. A blanket non-compete on an entire NAICS code for two years is unlikely to be enforceable and will poison future teaming relationships. Limit it to the specific solicitation number and any follow-on recompete within a defined window.
Flow-Down Clauses and What Subs Actually Inherit
When a prime signs a government contract, certain FAR clauses flow down to subcontractors by operation of law or by contract. Others flow down only if the prime includes them. The teaming agreement should specify, or at minimum acknowledge, which clauses the sub will be required to accept in the subcontract.
Common flow-downs that surprise subs at subcontract negotiation include: FAR 52.222-26 (Equal Opportunity), FAR 52.222-41 (Service Contract Labor Standards, if applicable), FAR 52.203-13 (Contractor Code of Business Ethics), and agency-specific clauses such as DoD's DFARS 252.204-7012 (Safeguarding Covered Defense Information). A sub that has not reviewed these before proposal submission may find the compliance cost changes their pricing assumptions. That renegotiation at subcontract execution, after award, is where teaming relationships fracture.
The practical solution is to attach a clause matrix to the teaming agreement as an exhibit. List the anticipated flow-downs, note which are mandatory and which are at prime's discretion, and confirm that both parties have reviewed them. It takes two hours before proposal submission and saves weeks of dispute after award.
Workshare Verification During Performance
A teaming agreement that specifies workshare but includes no verification mechanism is unenforceable in practice. The prime controls the invoicing, the task assignments, and the subcontract modifications. Without a reporting requirement, the sub has no visibility into whether they are tracking to their committed percentage.
Include a monthly or quarterly workshare reconciliation requirement in the teaming agreement. The prime should provide the sub with a summary showing: hours invoiced by CLIN, cumulative subcontract spend against committed floor, and any pending modifications that affect scope. This is not burdensome. Most primes are already tracking this data for their own project management and for compliance with subcontracting plan reporting under SF-294 and SF-295 (now replaced by the Electronic Subcontracting Reporting System, eSRS).
If the reconciliation shows the sub is tracking below floor, the agreement should specify a remediation process: the prime has 60 days to assign additional qualifying work, failing which the sub has the right to escalate to the contracting officer or pursue other remedies defined in the agreement. That escalation right is rarely exercised, but its existence changes the prime's behavior.
When the Teaming Agreement Becomes the Subcontract
Some primes, particularly on smaller awards, attempt to use the teaming agreement itself as the subcontract after award. This is a mistake. Teaming agreements are pre-award instruments designed to govern proposal collaboration. They lack the payment terms, invoice procedures, acceptance criteria, and dispute resolution mechanisms that a proper subcontract requires. Using a teaming agreement as a subcontract exposes both parties to ambiguity on every operational question that arises during performance.