A teaming agreement is a short document that decides who does what if you win, and most of them are written as if the point were to be signed rather than to be used. The prime wants four things out of the paper: certainty that the specialist is on this pursuit and not the one across the street, a workshare that is defined well enough to price, people who will actually be there at award, and terms that keep the deliverable clean when the government asks who owns what. A sub who arrives understanding those four things turns a two-week negotiation into a two-day one. This is the agreement written from your side of the table, clause by clause.
We build AI, data platforms, cloud systems and full-stack applications and put them into production inside federal agencies. We work as a specialist subcontractor and teaming partner to large primes, which means we have read a great many of these agreements and negotiated most of the clauses in them. What follows is what we look for when a prime sends one, and what we bring so that your contracts group can turn it around fast.
What the agreement is doing legally, and what it is not
A teaming agreement is an agreement to negotiate a subcontract if a specified award happens. It is not the subcontract. Courts have been unforgiving with agreements that promise to agree on terms later without any framework for what those terms are, and the practical consequence is that the more the teaming agreement leaves to a later meeting, the less it does. That cuts both ways. A prime who wants real protection has to write real terms. A sub who wants a real workshare has to accept real obligations before award.
So the useful test for every clause is whether it survives the moment it is needed. The pursuit ends three ways: the team wins, the team loses, or the prime decides mid-pursuit to change the technical approach and no longer needs the specialist. A well-drafted agreement says exactly what happens in all three, and the third is the one most agreements are silent about.
Exclusivity: what to ask for and what you will actually get
Exclusivity is the clause primes care about most and draft least carefully. The common version bars the sub from participating in the procurement with anyone else. That is reasonable and every serious specialist will sign a version of it. The three refinements that matter are scope, symmetry and duration.
Scope. Bind the exclusivity to the identified procurement, by solicitation number where one exists and by a described requirement where it does not. An exclusivity that covers a whole agency, a whole technology area, or every follow-on for three years will either be refused by any specialist worth having or accepted by one who cannot fill a pipeline. Neither outcome helps a capture team.
Symmetry. The strongest form of this clause runs both ways: the sub works only with you on this pursuit, and you do not add a second sub to perform the same defined scope without notice. Primes resist the second half out of habit. It is worth giving, because it converts a grudging signature into a partner who will put senior engineers on your proposal for free during the bid phase. A sub who might be replaced quietly staffs the proposal cautiously.
Duration. Tie the term to a defined end: award and subcontract execution, a no-award decision, cancellation of the solicitation, or a stated outside date. Open-ended exclusivity is the clause most likely to get struck by the sub's counsel, and striking it costs you a week.
One more provision belongs here, and it is the one that most reduces friction later. Say what happens if the prime's technical approach changes and the specialist scope goes away. A clean statement that the prime may release the sub in writing, that the exclusivity ends when the release issues, and that each party bears its own bid costs, removes the fear that drives most of the sub-side redlines.
Which clauses decide whether the paper takes days or weeks
Editorial weighting, illustrative rather than measured. The last row is low because it consumes negotiation time and almost never changes an outcome.
Workshare: the clause that determines whether the price is defensible
Most teaming agreements state workshare as a percentage of the estimated contract value, sometimes with a range and a phrase about good-faith efforts. That number does one useful thing, which is satisfy a small business subcontracting plan, and one harmful thing, which is give both parties a different picture of the same deal. A percentage of an unknown ceiling on an indefinite-delivery vehicle is not a commitment anybody can plan against.
The version that works is a description of scope by task. Name the work breakdown elements, the deliverables, the CDRLs the sub authors or contributes to, and the evaluation criteria the sub's section addresses. Add a percentage if the subcontracting plan needs one, but let the scope description govern. The advantage to the prime is direct: when scope is described by task, your basis of estimate has something underneath it, your pricing team can defend the sub's number against price realism, and your program manager knows on day one of performance who owes what.
There is a second reason. On task-order vehicles, the pursuit that gets signed is rarely the shape of the work that gets ordered. A scope-described workshare survives that drift because the tasks still map. A percentage-described workshare turns every task order into a renegotiation.
Three provisions make the workshare clause hold:
- A stated basis for adjustment. If the government reduces scope, cuts a CLIN, or descopes at negotiation, say how the sub's share moves. Proportional reduction across the affected tasks is the ordinary answer and it takes one sentence.
- A first-look right rather than a guarantee on follow-ons. Primes cannot promise future task orders and should not try. A first-look commitment on orders inside the described scope is honest, enforceable enough to be meaningful, and much easier to sign.
- An agreed subcontract type before award. Whether the eventual subcontract is firm-fixed-price by milestone, cost-reimbursement, or labor-hour changes the sub's price by more than most negotiators expect. Deciding it in the teaming agreement removes the single largest source of post-award delay.
Key personnel: the commitment that has to be real
Evaluators score key personnel on relevance, currency and availability, and they are good at spotting a résumé that was borrowed for the bid. The prime carries that risk, because the prime signs the proposal. So the teaming agreement should make the sub carry it too.
Ask for three things and expect a serious partner to give all three. First, named individuals with a written commitment to be available for a stated period after award, at a stated allocation. Second, a substitution provision that requires prior written consent and equal-or-better qualifications, mirroring the language your contract will carry from the government. Third, a notice obligation: if a named person becomes unavailable during the pursuit, the sub tells you within a set number of days rather than at award.
What a prepared sub brings to this conversation is a résumé package already in your format, a letter of commitment for each named person, and a bench deep enough that a substitution is a name change rather than a crisis. We keep résumés current in a standard structure precisely so a proposal manager is not chasing formatting during the last week of a bid.
Intellectual property and data rights, so the deliverable stays clean
This is the clause that quietly decides whether your program office is happy in year three. The government's rights in software and technical data are set by the contract clauses, and what the prime delivers has to match what the prime asserted. If a sub builds a component on top of tooling it owns and nobody wrote down the assertion, you find out during a data-rights review, which is the worst possible time.
The clean structure has four parts, and a specialist who has done federal work will propose it without being asked.
Background technology is listed by name. Anything the sub brings that predates the effort appears on a schedule to the teaming agreement, with the rights category asserted. An empty schedule is a red flag, not a convenience; every engineering firm has tooling, and the ones who claim otherwise have simply not looked.
Foreground work is assigned or licensed on stated terms. Work produced under the subcontract should carry a present assignment to the prime where the prime needs title, or a license broad enough to cover delivery, maintenance and follow-on competition where the sub retains ownership. Recitals about work made for hire are not sufficient by themselves for software, so the agreement should carry an explicit assignment where assignment is intended.
Open source is disclosed with licenses. A component list with license identifiers, delivered before the proposal goes out, prevents the discovery of a copyleft dependency in a system the government intends to reuse.
Markings match assertions. Whatever is asserted as limited or restricted gets marked that way in the delivered artifacts, consistently. Mismatched markings are the most common finding in a data-rights review and they are entirely preventable.
The reason a prime should care about this beyond compliance is competitive. A technical volume that can state plainly what the government will own, with the assertions already reconciled between prime and sub, reads as a team that has delivered before. The alternative reads as a team that will discover its own terms after award.
Flow-downs that will not surprise anyone at negotiation
The standard approach is a clause saying the sub accepts all flow-downs from the prime contract. It is fast to write and it is why subcontract negotiation takes six weeks. A specialist reading that sentence has to price for an unknown set of obligations, and prices conservatively or asks for the list.
The better approach costs a capture team one hour. Attach the anticipated flow-downs as an exhibit at the teaming stage, marked as anticipated and subject to the terms of the actual award. Include the clauses that carry real cost: cybersecurity requirements for controlled unclassified information, incident reporting timelines, supply-chain representations, accessibility obligations under Section 508 where the deliverable has a user interface, small business subcontracting reporting where applicable, and any agency-specific security or privacy requirements.
Three benefits follow. The sub prices the actual obligations instead of a worst case. Your compliance group sees any gap while there is still time to fix it, rather than during subcontract negotiation. And the sub's own subcontract and vendor terms can be aligned before award instead of after.
When we receive a flow-down exhibit at teaming, we return a written statement of how each requirement is met today, which controls apply to our environment, and which obligations attach only once we touch government data. That document usually becomes an attachment to the subcontract, and it removes the longest thread in most negotiations.
| Clause | The weak version | The version that holds | Why the prime benefits |
|---|---|---|---|
| Exclusivity | Sub may not work with any other party in this market | Bound to the named procurement, mutual, ending at award, no-award or written release | Signed in days; sub commits senior staff to the bid |
| Workshare | Approximately 25 percent of contract value, good-faith efforts | Named tasks, deliverables and CDRLs, with a percentage stated for the subcontracting plan | Basis of estimate is defensible; performance roles are clear at kickoff |
| Key personnel | Sub will provide qualified personnel | Named people, stated allocation, commitment period, consent-based substitution, notice of loss | The staffing narrative is credible and survives evaluation |
| Data rights | Ownership to be negotiated in the subcontract | Background schedule, foreground assignment or license, open-source list, matching markings | The deliverable is clean; assertions reconcile before submission |
| Flow-downs | All prime contract clauses flow down | Anticipated clauses attached as an exhibit, with the sub's written compliance statement | Subcontract negotiation shortens; cost surprises disappear |
| Termination | Silent on approach changes | Written release ends exclusivity; each party bears its bid costs | Capture keeps freedom to change the technical approach |
Proposal obligations, which are the part the sub actually performs first
Everything above is about award. The teaming agreement's first real test is the bid itself, and the clause that governs it is usually one sentence about cooperating in good faith. Replace it with specifics, because this is where a prime gets the value that justified adding the sub.
State what the sub owes and when: the technical text for named sections in your template and style guide, résumés and commitment letters in your format, a basis of estimate with the supporting rationale, past performance information the sub may cite, representations and certifications, the small business data your subcontracting plan needs, and participation in color reviews with a named person who will attend. Put dates on each one that sit before your internal reviews, not before the government's due date.
State what the prime owes back: the solicitation and amendments, the sections of the technical approach the sub must fit inside, the template and style guide, page allocations, the pricing model or at least its shape, the review calendar, and a point of contact who can answer a question in a day. Subs miss deadlines most often because they were waiting on something.
One provision here is worth more than the rest. Say who arbitrates a technical disagreement during the bid, and say it is the prime. A specialist who has strong views about architecture is exactly who you want writing the section, and also exactly who can burn three days of a compressed schedule if nobody has authority. A sub that accepts prime authority on the proposal's final content, in writing, is telling you something useful about how they will behave on the program.
Where the paper actually stalls, and how a prepared sub prevents it
Across a normal year of these negotiations, the delay is almost never in the concept. It is in four predictable places.
Indemnity and limitation of liability. A prime's standard template often carries commercial-scale indemnities and no liability cap. A specialist firm's counsel will not sign unlimited liability for a defined scope of engineering work, and the negotiation that follows takes two weeks. The fix is to propose the cap up front: a mutual limitation tied to a multiple of the subcontract value, with the usual carve-outs for intellectual property infringement, breach of confidentiality, gross negligence and willful misconduct. Most subs accept that structure the day they see it.
Insurance certificates. Ask for the certificates at teaming, not at subcontract. Professional liability, technology errors and omissions, cyber, and the ordinary commercial lines, at the limits your prime contract requires, with the right entity named. A partner who can produce these in a day is telling you they have done this before.
Confidentiality that conflicts with an existing agreement. If a nondisclosure agreement already exists between the parties, say which controls. Two overlapping confidentiality regimes with different terms create a question nobody can answer quickly.
Signature authority. Know who signs on the sub's side and make sure that person has seen the document before the last day. This sounds trivial and it is responsible for more missed teaming deadlines than any legal issue.
Where teaming negotiations actually lose days
Editorial weighting, illustrative rather than measured. The last row is low because the concept is rarely the problem.
How we work inside a prime's capture and program organization
Precision Federal builds AI systems, data platforms, cloud infrastructure and full-stack web and mobile applications, and we deliver them into production inside federal agencies. Inside your pursuit, we behave like a section of your team rather than a vendor with an opinion.
In the first week after a teaming agreement or even a signed nondisclosure agreement, you get a written technical scope for our portion, mapped to the work breakdown structure and the evaluation criteria; named engineers with résumés in your template and signed commitment letters; a basis of estimate with the task decomposition and the assumptions written out; a data-rights schedule listing our background technology and the asserted rights; and a compliance statement against your flow-down exhibit. That package is what your proposal manager needs and it is what most subs deliver in week four.
During the bid we write in your template and your voice, attend your color reviews, take comments without defending the draft, and hit the internal dates rather than the government date. If your technical approach changes and our scope goes away, we sign the release and there is no argument.
After award, the shape of the money is straightforward. We price fixed-price milestones where the scope is defined enough to write acceptance criteria as tests, and a committed team where the work is discovery or sustained engineering. You keep the client relationship, the program, the code and the data. Assignment or license terms are whatever the agreement says, agreed before submission rather than after.
The first step is one email with a one-page brief: the requirement or solicitation number, the technical gap you need filled, the shape of the workshare you have in mind, and the date that matters. We return a scoped, priced statement of work and a draft workshare description you can drop into your teaming agreement.
A working sequence for the paper
The sequence that produces a signed agreement in days rather than weeks is not complicated, and it is mostly about order.
- Nondisclosure agreement first, before any technical discussion. One day.
- A technical conversation between engineers, not business developers, to confirm the scope is real. One to three days.
- The prime sends the draft teaming agreement with the workshare description, the flow-down exhibit and the anticipated subcontract type already filled in. Same day.
- The sub returns redlines limited to liability, insurance and any conflict with an existing agreement, plus the data-rights schedule and named personnel. Two to three days.
- Signature, then immediately the proposal obligations calendar with dates that sit inside your review schedule.
What breaks the sequence is sending a template with blanks where the workshare and the flow-downs belong. The blanks come back as questions, the questions become a meeting, and the meeting becomes a week.
Bottom line
The teaming agreement a prime actually wants is short, specific and honest about the three ways the pursuit can end. Bind exclusivity to the named procurement and make it mutual. Describe the workshare as tasks and deliverables so your pricing team can defend it. Commit key personnel by name with a substitution path that mirrors your own contract. Settle background technology, foreground rights and open source before submission so the deliverable stays clean. Attach the anticipated flow-downs so the sub prices reality. Put the liability cap in the first draft instead of the third. Do those six things and the agreement takes days, the specialist puts senior people on your proposal, and the subcontract after award is a formality rather than a second negotiation.
Frequently asked questions
It binds what it actually states. A teaming agreement is generally an agreement to negotiate a subcontract if a specified award occurs, and the parts most likely to be enforced are the definite ones: exclusivity for a named procurement, confidentiality, the described scope, and the allocation of bid costs. Clauses that promise to agree on material terms later tend to be treated as unenforceable agreements to agree. The practical rule is that specificity is what makes the document do work, so write the workshare, the subcontract type and the flow-down expectations into it rather than deferring them.
Both, with scope governing. A percentage is useful for a small business subcontracting plan and for a quick internal view of the deal. It is not something either party can plan or price against, particularly on an indefinite-delivery vehicle where the ordered work rarely matches the pursued work. Describing the workshare as named tasks, deliverables and the contract data requirements the sub authors gives the pricing team something to defend under price realism and gives the program manager a clear division of responsibility at kickoff.
As much as is tied to the pursuit at hand. Exclusivity on the named procurement, for the period from teaming through award and subcontract execution, is normal and most specialists sign it without comment. Exclusivity that extends to an agency, a technology area or an unbounded set of follow-on work is usually refused, and refusing it is the correct behavior. Making the clause mutual, so the prime does not add a second sub to the same defined scope without notice, usually gets the agreement signed faster and produces a better proposal effort.
Four things, settled before proposal submission. A schedule listing the sub's background technology with the rights category asserted for each item. A statement of whether work produced under the subcontract is assigned to the prime or licensed, with a present assignment where assignment is intended, since recitals about work made for hire are not by themselves sufficient for software. A list of open-source components with their licenses. And a commitment that delivered artifacts carry markings matching the assertions. Mismatched markings are the most common finding in a data-rights review.
Usually because things that could have been settled at teaming were deferred. The four recurring causes are an unlimited liability provision the sub's counsel will not sign, flow-down clauses the sub is seeing for the first time and must price, a subcontract type nobody agreed on, and confidentiality terms that conflict with an existing nondisclosure agreement. Proposing a mutual liability cap in the first draft, attaching the anticipated flow-downs as an exhibit, naming the subcontract type, and stating which confidentiality agreement controls removes most of the delay.