Teaming agreement insurance is often treated as an afterthought, but the insurance section of a teaming agreement can determine who absorbs catastrophic risk. Many contractors focus on the work share percentage, the exclusivity clause, and who leads the proposal. That’s where the attention goes. Insurance gets a paragraph near the end and a signature from legal. That’s a mistake with real consequences.
The insurance section in a teaming agreement isn’t boilerplate. It defines what you must carry, what happens if coverage lapses, and who absorbs the financial impact when a claim surfaces during performance. Understanding it before you sign is the difference between a protected subcontract relationship and an exposure you didn’t see coming until it was too late to address cleanly.
At Risk Reconnaissance LLC, which works exclusively in the GovCon space, this pattern comes up routinely in client intake: a contractor signs the agreement, then calls a broker. By then, the insurance clause is locked. The conversation that should have happened before signature is now a damage-control exercise. Here’s what’s actually inside those clauses, why primes write them the way they do, and what you need to verify before any agreement is executed.
Teaming agreement insurance: what clauses are actually embedded
Most teaming agreements include a short but dense insurance section. That language is usually pulled directly from what the prime is required to carry under the underlying government contract, not invented from scratch. It flows down from FAR-based templates or the prime’s in-house legal boilerplate built around real contractual obligations, and it carries weight.
The core clause package typically requires each party to maintain specific policy types, carry defined minimum limits, and keep coverage in force throughout the entire period of performance. The most common required policies are workers’ compensation and employer’s liability, commercial general liability, and automobile liability. FAR-referenced minimums for these policies, as specified in FAR 28.307-2, are approximately $100,000 for employer’s liability, $500,000 per occurrence for general liability, and $200,000 per person/$500,000 per occurrence for automobile bodily injury. These aren’t suggestions. They’re contractual obligations with real teeth.
Beyond the basic coverage requirements, the clause typically requires each party to name the other as an additional insured on its commercial general liability policy. This gives the prime direct access to the sub’s coverage for claims arising out of the sub’s work. Alongside that sits waiver of subrogation language, which prevents the sub’s insurer from pursuing the prime after paying a claim on the sub’s behalf. Both of these protections must be confirmed by endorsement. A statement in the agreement that they exist is not sufficient.
Notice provisions round out the package. These require the insured party to give prompt written notice of any claim, cancellation, non-renewal, or material change in coverage. “Prompt” often has a defined window in the agreement, and missing that window can compromise indemnity rights. A prime that doesn’t know a sub’s policy was canceled mid-performance is exposed without recourse, and the notice provision is the mechanism designed to prevent exactly that scenario.
Why primes set specific limits on their teaming partners
Primes aren’t setting insurance limits based on preference. They’re managing a liability chain that runs from the government, through them, and down to every team member performing work on the contract. When a sub underinsures and a claim exceeds that coverage, the gap doesn’t disappear. It flows upward.
The mechanics are straightforward. The prime is accountable to the government for contract performance and compliance. If a sub’s general liability policy carries a $500,000 limit but a claim comes in at $1.2 million, that $700,000 gap either lands on the prime’s policy or on the prime’s balance sheet. That’s why limits aren’t truly negotiable in most flow-down arrangements. The prime isn’t being difficult; they’re protecting their own exposure.
FAR Subpart 9.6 recognizes contractor team arrangements (CTAs) and requires disclosure in the offer, but it doesn’t create a universal insurance mandate for the teaming structure itself. The real mandate comes from the underlying contract. When the prime’s agreement with the government requires $2 million in general liability coverage, per FAR 52.228-5 and applicable flow-down rules, that requirement doesn’t stop at the prime’s door. It flows to whoever is performing that scope of work, and the teaming agreement is the vehicle that carries it there. CTA insurance requirements, in practice, derive directly from those contract-level mandates.
One distinction worth understanding: the minimums in a teaming agreement typically come from the solicitation or the agency’s standard contract terms, and primes often require limits above that floor as a risk buffer. Meeting the solicitation baseline may not be enough to satisfy the prime’s flow-down clause. The solicitation sets the floor; the prime’s risk tolerance sets the ceiling.
The coverage types most teaming agreements require
GovCon teaming agreements have a fairly predictable coverage floor, and understanding the insurance obligations in these agreements starts with knowing what each policy type actually covers.
Workers’ Compensation and DBA
Workers’ compensation is typically required in every agreement, state law usually mandates it regardless, but the teaming agreement generally requires employer’s liability above the statutory minimum. Defense Base Act (DBA) insurance enters the picture the moment any performance happens outside the United States on a federal contract. Standard workers’ compensation coverage doesn’t apply overseas. DBA does, per FAR 52.228-3. A sub that doesn’t know its work share includes potential overseas deployment, or that the prime could later redirect scope internationally, may find itself without required coverage when it’s needed most.
General Liability and Auto Liability
Commercial general liability covers bodily injury and property damage arising from the sub’s operations. Automobile liability applies whenever employees operate vehicles as part of contract performance. These two, combined with workers’ compensation and employer’s liability, form the baseline in virtually every agreement.
Professional Liability
Professional liability, or errors and omissions, gets added for technical, IT, or advisory roles where the risk is a bad deliverable rather than a physical incident. The agreement may not always specify it explicitly, but the scope of work often demands it. The sub’s coverage must reflect what it’s actually doing under the agreement, not just what the template lists. A sub performing network architecture on a DoD contract has different risk exposures than one providing facility maintenance services. The teaming agreement may require the same minimums for both, but the actual policy should be structured around the specific work. Smaller GovCon subs often miss this: the certificate gets issued to match the agreement’s language, but the underlying policy isn’t built for the actual work being performed.
What a coverage lapse mid-performance actually triggers
A lapse in coverage isn’t an administrative inconvenience. It’s a material breach of the teaming agreement, and the consequences move fast. The moment a sub’s policy cancels or lapses, the prime is carrying risk it didn’t price for. If an incident occurs during that gap, the claim may land directly on the prime’s policy, or remain uncovered entirely.
Most teaming agreements give the prime the right to issue a cure notice when a sub goes out of compliance on coverage. The sub typically has a defined cure period, measured in days as specified in the agreement, to reinstate coverage and provide updated proof. Failure to comply within that window triggers termination rights. Losing position mid-performance isn’t just a contractual setback. It can affect past performance ratings, and past performance follows a contractor for years.
The government’s position on this is clear: the contracting officer expects the prime to manage its teaming chain. If the prime can’t demonstrate that its subs maintain required coverage, that’s the prime’s compliance failure, not just the sub’s. This is why some primes now require periodic certificate of insurance updates, quarterly or at policy renewal, rather than a one-time certificate at agreement execution. The compliance pressure is real, and it runs in both directions.
Verifying a teammate’s COI: what it confirms and what it doesn’t
A certificate of insurance is the most consistently misunderstood document in the contracting relationship. It confirms that coverage exists at the time of issuance. It does not modify the policy, guarantee limits, or prove that your organization is actually protected under that policy. Treating it as the final step in verification is a common and costly mistake.
The certificate shows policy types, limits, effective dates, and the named insured. That’s it. If the policy has an exclusion or a gap that doesn’t appear on the face of the certificate, the certificate does nothing to protect you from it. Additional insured status and waiver of subrogation must be confirmed by endorsement, not by a line on the COI. In most jurisdictions, courts treat the endorsement as controlling and the certificate as informational. That distinction matters when a claim is in dispute.
A practical COI verification process for teaming agreement insurance covers these points before any agreement is executed:
- Confirm policy dates cover the full period of performance, not just the date the COI was issued
- Verify the certificate holder name matches your organization’s legal entity name exactly
- Check that required coverages and limits match the teaming agreement’s insurance requirements precisely
- Request endorsements for additional insured and waiver of subrogation and verify they reference the correct policy number and dates
- Set a tracking reminder before policy expiration so renewal proof is received before the gap opens
A blank endorsement form attached to a COI isn’t sufficient. The endorsement must be completed, current, and consistent with the agreement’s language, and that’s worth confirming in writing with the insurer before you countersign anything.
Getting coverage structured before you sign
Many contractors call a broker after the teaming agreement is fully executed. By then, the insurance clause is locked. If the required limits exceed what a broker can bind quickly, or if the scope triggers DBA or professional liability that wasn’t already in force, the sub is technically in breach before the first task order drops. That’s not a hypothetical. It’s a common starting position for smaller subs entering their first significant teaming arrangement.
Mid-agreement coverage changes require underwriter approval, updated endorsements, and revised certificates, all on a timeline that doesn’t match government contracting urgency. A sub that needs to achieve compliance in 48 hours before onboarding starts is in a genuinely difficult position. Retroactive coverage modifications are rarely available and expensive when they are.
This is where working with a broker who reviews the insurance clause before signature changes the process entirely. At Risk Reconnaissance LLC, the starting point is the teaming agreement itself, not a generic coverage checklist. Some generalist brokers may not be familiar with the distinctions between a standard commercial subcontract and a GovCon teaming arrangement with DBA obligations, additional insured requirements, and FAR flow-down language. For a deeper primer on those distinctions see Navigating the Complex World of Commercial Insurance for Government Contractors. A broker operating in this space already knows what the clause means and what the coverage must do, no onboarding required.
Before you countersign, ask your broker these questions directly: Does my current general liability policy include contractual liability coverage for this type of agreement? Will my policy support an additional insured endorsement in the form the prime requires? Do I need DBA if any work could involve overseas deployment? Will my professional liability cover the deliverables listed in my work share section? A broker who can’t answer those questions quickly isn’t working in this space.
Review the clause before it’s set in stone
Teaming agreement insurance clauses are short. The exposure they represent is not. Every provision in that section, the additional insured requirement, the waiver of subrogation, the notice window, the coverage minimums, has a function. That function is to define who is protected and who absorbs the loss when something goes wrong during performance.
Coverage lapses mid-performance, unverified certificates, and limits that don’t match the actual contract scope are the problems that end teaming relationships and create liability exposure that follows a contractor’s record for years. These aren’t abstract risks. They’re the problems that surface when the clause wasn’t read carefully before the agreement was signed.
Review the teaming agreement insurance section before you execute it. Get your broker on a call with the agreement in hand. The right coverage structure isn’t complicated when you address it early. Review your teaming agreement insurance clauses before you sign, that’s the one step that keeps every other protection in place.