The NDA before the teaming agreement

The order of the documents decides the leverage

A pursuit runs through four documents in a fixed order: a nondisclosure agreement, then a capability exchange, then a teaming agreement, then a subcontract if the team wins. Each is signed with more information than the last. The NDA sits at the front, so it gets the least negotiation and carries the most uncertainty. A firm that spends two weeks arguing over a teaming agreement and thirty seconds signing the prime's form NDA has the order backwards, because everything of value moved across the table under the first document, not the third.

The asymmetry is structural. The prime needs to see enough of your work to believe you close the gap. You need the pursuit to be real before you show that work. Neither side can go first without risk, so both sign a confidentiality agreement and start the exchange. That agreement is the only thing standing between your engineering and a competitor's proposal, and it is drafted, in almost every case, by the party with more lawyers.

None of this is a reason to hold back. A firm that will not show technical substance does not get onto bids. Stage the exchange and read the document, because both failure modes are expensive: sharing everything under a weak agreement, or sharing so little the prime cannot tell whether you are real.

What the agreement actually protects

Confidentiality agreements exist because trade secret protection is not automatic. Under 18 U.S.C. § 1839(3), information qualifies as a trade secret only if the owner has taken reasonable measures to keep it secret and it derives independent economic value from not being generally known and not being readily ascertainable through proper means. Both halves matter. Value alone does not create protection, and neither does secrecy.

An executed NDA is the cleanest evidence of the first half. It shows a court the disclosure was conditional, deliberate, and documented. Handing the same architecture to the same prime over coffee with no agreement does more than leave you without a contract claim. It undercuts the argument that the information was a trade secret at all. The agreement protects the status of the information, not just your promise about it.

The same logic runs through patent strategy. A disclosure made in confidence is not a public disclosure, so it does not start the one-year clock under 35 U.S.C. § 102(b)(1) that follows an inventor's public disclosure. A conference talk, a public repository, or an unprotected demo does start it. Firms that intend to file later should know which conversations sit inside the confidence perimeter, and the perimeter is drawn by the agreement.

Dimension	Nondisclosure agreement	Teaming agreement	Subcontract
When it is signed	Before any technical exchange, often before the pursuit is named	Weeks before proposal submission, after the team is set	After award, when scope is funded
What it promises	Do not disclose, and in a good draft, do not use	Proposal support, an intended scope, sometimes exclusivity	Price, schedule, deliverables, remedies
What it does not promise	That the prime will bid with you, or bid at all	An enforceable work share, in many jurisdictions	Nothing. This is the enforceable document
Typical duration	Term of two to five years, with a survival period that can run longer	Expires at award, non-award, or a stated date	Period of performance plus flow-down survival
Government role	None	Disclosed in the offer under FAR 9.603; government is not a party	Consent to subcontract may apply under FAR subpart 44.2
Where a dispute goes	State or federal court	State court, usually on contract-formation grounds	Prime-sub dispute resolution, then court or arbitration

An NDA is a disclosure promise, not a business promise

The most instructive case is Navar, Inc. v. Federal Business Council, decided by the Supreme Court of Virginia in 2016. Two firms offered themselves as joint subcontractors to a prime pursuing an event-planning contract at the Defense Threat Reduction Agency. They signed both an NDA and a teaming agreement. The prime won and did not use them. A jury found for the plaintiffs on the NDA count and on one trade secret count under Virginia's Uniform Trade Secrets Act, and the trial court entered judgment totaling $1.25 million.

The Supreme Court of Virginia reversed both. Nothing in the NDA obligated the prime to hire the plaintiffs as subcontractors, and they had not proved how their confidential information was misused. The court also agreed the teaming agreement was unenforceable, amounting to an agreement to negotiate open issues in good faith without sufficient certainty about terms.

Two lessons. A confidentiality clause restrains disclosure and, if drafted well, use. It does not restrain the prime from bidding without you, and no standard NDA will; that restraint is a separate exclusivity term with its own price. And proving misuse is hard. When your material sits inside a competitor's proposal you will never see, the evidentiary problem is severe. That argues for staging what you disclose rather than relying on litigation you would rather not run.

The bars above are a reading order, not data. A redline that fixes the non-use clause and the definition of confidential information has done most of the work; one that only changes the governing-law paragraph has done very little. Firms tend to argue about the last row and sign the first.

The clauses that decide what you signed

Non-use, separate from non-disclosure. A promise not to disclose still permits internal use. A prime can honor a pure non-disclosure clause while its own engineers build from what they saw. The clause you want says the information will be used solely to evaluate and pursue the identified opportunity. That one sentence is worth more than everything else in the document.

The definition of confidential information. Two drafting styles exist. One protects anything a reasonable person would understand to be confidential. The other protects only what is marked in writing at disclosure. The second is common, defensible, and quietly dangerous, because most technical exchange happens on a call or a shared screen. If the marking style is used, insist on a follow-up window: oral and visual disclosures protected if confirmed in writing within a stated number of days. Then send the confirmations.

Permitted recipients. A prime will share your material with its capture team, its contracts staff, sometimes outside pricing consultants, sometimes other teammates. That is normal. What matters is that the categories are named, each recipient is bound by obligations at least as protective as yours, and the prime stays responsible for their compliance. A clause permitting disclosure to unnamed affiliates without a flow-down obligation is not a confidentiality agreement in any useful sense.

Term against survival. Different numbers. The term is how long new disclosures are covered. Survival is how long the obligation lasts for information already disclosed. A three-year term with three-year survival leaves your architecture unprotected in year four, roughly when a recompete arrives. Trade secrets should be carved out and protected for as long as they remain trade secrets.

Return or destruction. The practical version needs an exception for archived backups and counsel copies, with the obligation continuing for anything retained. Promising to destroy every copy including backups is something most firms cannot deliver, and an unkeepable promise is worse than a bounded one.

No license by implication, and injunctive relief. One sentence saying no license or ownership interest is granted or implied by the disclosure. One more acknowledging that a breach causes harm money damages cannot fix, so the disclosing party may seek equitable relief. Courts do their own analysis regardless, but the acknowledgement removes a contested step at the moment when speed is the entire remedy.

Governing law and forum. Federal trade secret law is uniform under the Defend Trade Secrets Act. State law is not. Forty-eight states and the District of Columbia have adopted a version of the Uniform Trade Secrets Act; North Carolina has its own similar statute rather than the uniform text, and New York still decides these cases under common law. A forum clause naming a court two thousand miles away is a real cost, because what it costs to appear there helps determine whether you ever enforce the agreement.

Residuals, and why the clause is worth reading twice

A residuals clause says the receiving party's personnel may use information retained in their unaided memory. It is common in technology agreements and not automatically unreasonable. Engineers cannot unsee an architecture, and no one wants a rule that sends a capture engineer out of the industry after a briefing.

What the clause does is convert a non-use promise into a non-copying promise. If the prime's team cannot copy your documents but may build from what they remember, everything you can explain on a whiteboard has effectively been given away. For a firm whose differentiation is a specific pipeline design, evaluation method, or way of structuring a hard problem, that is the entire asset.

Three positions are available. Strike the clause, which primes sometimes accept when the pursuit is real. Bound it, so residuals reach general skills and knowledge but never your identified trade secrets, source code, model designs, or measured results. Or accept it and stage the disclosure, so whiteboard-level material goes across and implementation detail waits for the subcontract. The third is often the practical one, and it requires deciding in advance which is which.

Primes frequently answer that the form is not negotiable. Sometimes that is true and sometimes it is a first position, and two requests usually survive either way: narrow the purpose statement to the named pursuit, and add a written-confirmation window for oral disclosure. Both are edits contracts staff can approve without escalating. If nothing can move, stage the disclosure more conservatively rather than walk away from the pursuit.

Clause in the prime's standard form	What it usually says	What to ask for instead
Purpose	Evaluating a potential business relationship	The named pursuit or program, so use for anything else is a breach
Mutuality	One-way, with your firm as the disclosing party only	Mutual. You will receive customer intelligence and pricing structure too
Marking	Written material must be marked confidential at disclosure	Add a written-confirmation window covering oral and visual disclosure
Recipients	Affiliates, subcontractors, and advisors, undefined	Named categories, need to know, flow-down obligations, prime remains liable
Residuals	Unaided memory of personnel may be used without restriction	Struck, or bounded to exclude identified trade secrets and source code
Survival	Obligations end with the term	Trade secrets protected for as long as they remain trade secrets

What happens to your material inside a proposal

Once your technical text is in the prime's volume, a second protection system takes over, and it is a government one. FAR 52.215-1(e) gives offerors a legend for data they do not want disclosed outside the government or used for anything other than evaluation: a title-page restriction plus a per-sheet legend on each restricted page. Two limits are worth knowing. If a contract is awarded as a result of the submission, the government gets the rights provided in the resulting contract, not the evaluation-only restriction. And the legend does not limit government use of the same information obtained from another source without restriction.

Alongside that sits the Procurement Integrity Act, 41 U.S.C. §§ 2101 to 2107, implemented at FAR 3.104, which prohibits covered persons from knowingly disclosing contractor bid or proposal information or source selection information before award. Separately, 18 U.S.C. § 1905 makes it a criminal offense for a federal officer or employee to disclose confidential trade information obtained in official duties, punishable by fine, imprisonment of up to one year, and removal from office.

Then there is FOIA. Exemption 4 at 5 U.S.C. § 552(b)(4) covers trade secrets and commercial or financial information obtained from a person that is privileged or confidential. In Food Marketing Institute v. Argus Leader Media (2019) the Supreme Court read "confidential" in its ordinary sense and rejected the older requirement that a submitter show substantial competitive harm, which made the exemption easier to rely on. Executive Order 12600, issued in 1987, requires agencies to keep procedures notifying submitters when records containing confidential commercial information may be released, so there is usually a chance to object first. Consistent marking is what makes all of this work, because an agency cannot protect what was never identified as confidential.

For delivered data on a DoD contract, the marking system changes again. DFARS 252.227-7013 governs technical data and DFARS 252.227-7014 governs noncommercial computer software, both keyed to restrictive markings that must be reproduced on any copy. Work performed under an SBIR or STTR award falls under DFARS 252.227-7018, where the protection period runs 20 years from the date of contract award and the government holds government purpose rights afterward rather than unlimited rights. If your material carries those rights, say so in the first technical conversation. It changes what the prime can plan to do with it.

An NDA is not an export authorization

Confidentiality and export control are separate systems, and the agreement satisfies only one. Under the ITAR at 22 CFR 120.50, releasing or otherwise transferring technical data to a foreign person inside the United States is an export. Under the EAR at 15 CFR 734.13, releasing technology or source code to a foreign person in the United States is a deemed export to that person's most recent country of citizenship or permanent residency. A signed NDA changes neither rule. If controlled technical data will move, the authorization question is answered before the call, not after.

The obligation runs the other way too. A prime sharing its own controlled unclassified information during the exchange puts handling obligations on your systems, and on a DoD pursuit that means DFARS 252.204-7012 territory. Ask what markings will be on what you receive, and route it to a system that can hold it, before it lands in a personal inbox.

The one place the government requires the agreement

The government stays out of teaming arrangements almost entirely. FAR 9.603 recognizes the integrity and validity of contractor team arrangements as long as they are identified and company relationships fully disclosed in an offer, or before the arrangement becomes effective if formed later. FAR 9.604 keeps the government's own rights intact and holds the prime fully responsible for performance.

One provision cuts the other way. FAR 9.505-4 addresses the case where a contractor needs proprietary information from other companies to perform a government contract and can use the leverage of that contract to obtain it. Subsection (b) requires a contractor gaining access to other companies' proprietary information while performing advisory and assistance services for the government to agree with those companies to protect it from unauthorized use or disclosure for as long as it remains proprietary, and to refrain from using it for any purpose other than the one for which it was furnished. If the firm across the table does advisory or assistance work on the same program, the confidentiality agreement is not a courtesy. It is a conflict-of-interest control the regulation contemplates, and its absence is itself a finding.

Stage the disclosure

The practical protection is sequencing. Each tier below buys the prime enough confidence to reach the next one, and nothing more. The timing is typical rather than fixed; the ordering holds on nearly every pursuit.

Tier three is where most firms overshoot. A capture manager needs to believe the capability exists and that a named person will do the work. That belief comes from measured results, a clear interface definition, and someone who answers hard questions in real time. It does not come from source code, and a prime asking for a repository before a teaming agreement wants something no stage of the decision requires.

Before you sign

• The agreement is mutual, because customer intelligence, pricing structure, and staffing plans will come back the other way.
• A non-use clause exists and is separate from the non-disclosure clause, tied to the named pursuit.
• Oral and visual disclosures are covered, with a written-confirmation window you can realistically meet.
• Permitted recipients are defined by category, bound by equivalent obligations, with the prime remaining responsible.
• Residuals language is struck or bounded so it cannot reach identified trade secrets or source code.
• Trade secrets survive the term for as long as they remain trade secrets.
• Return or destruction has a bounded exception for archival backups and counsel copies, with obligations continuing, and no license or ownership interest is granted or implied.
• The forum is one you can actually appear in, and the governing law is identified.
• Nothing in the document reads as exclusivity unless exclusivity is what you agreed to sell.
• Your own agreements with individuals carry the DTSA immunity notice, discussed below.

When it goes wrong, the forum is a court

Start with where the remedy is not. The Government Accountability Office has been explicit for decades that it will not resolve competing claims to proprietary data between private parties. In B-186958 it held it was not in a position to adjudicate the rights of private parties each claiming rights in contested data, and that until those rights are established in a proper forum it would not disturb an ongoing procurement or an award over such an allegation. A bid protest is not the tool.

The tool is a civil action. The Defend Trade Secrets Act at 18 U.S.C. § 1836 gives a federal cause of action for misappropriation of a trade secret related to a product or service used in interstate commerce. Exemplary damages of up to twice actual damages, plus attorney fees, are available for willful and malicious misappropriation. The ex parte civil seizure remedy at § 1836(b)(2) exists but is written for extraordinary circumstances and courts have kept it narrow. The limitations period is three years from when the misappropriation was discovered or should have been discovered by reasonable diligence. State law runs in parallel in most states.

One detail costs firms money and is easy to fix. Section 1833(b) gives individuals immunity for disclosing a trade secret in confidence to a government official or an attorney solely to report or investigate a suspected violation of law, or in a sealed court filing. It also requires an employer to include notice of that immunity in any contract or agreement with an employee that governs the use of a trade secret or other confidential information, and the statute defines employee to include any individual performing work as a contractor or consultant. Leave the notice out, and exemplary damages and attorney fees are off the table against a person who never received it. The notice is a paragraph. Put it in the employee, consultant, and individual confidentiality agreements now, not after an incident.

Bottom line

The confidentiality agreement is the highest-leverage document in the pursuit because it is signed first and governs everything that moves afterward. Read it for two things: whether it restrains use as well as disclosure, and whether it defines confidential information in a way that survives how technical conversations actually happen. Then stage what you share so each tier buys the prime exactly the confidence it needs to reach the next one. No agreement forces anyone to bid with you, and a court is a slow place to end up. Sequencing is the protection that works before anything goes wrong.

Frequently asked questions