What's the Difference Between an NDA, a Teaming Agreement, a CTA, and a Joint Venture for SDVOSB Federal Work?

A Mutual Non-Disclosure Agreement (NDA) enables information exchange between two parties. A Teaming Agreement (TA) binds the prime-sub structure before proposal submission. A Contractor Teaming Arrangement (CTA) is General Services Administration (GSA) Schedule-specific, with both parties prime to the agency. A Joint Venture (JV) is a separate legal entity governed by 13 CFR 125.18 for Service-Disabled Veteran-Owned Small Businesses (SDVOSBs). Each vehicle does one job. Using the wrong one creates real exposure.

This is a decision-tree spoke. For the broader picture of why primes team with SDVOSB IT subs and how to evaluate them, read the complete guide: How Do Primes Evaluate, Structure, and Contract with an SDVOSB IT Subcontractor?

When Do You Need a Mutual NDA?

The Mutual NDA is the entry point for any federal teaming conversation involving non-public information. The NDA binds the parties to handle Confidential Information disclosed in connection with the contemplated relationship and creates no obligation to team beyond confidentiality. It is the only vehicle in this list that is appropriate for a first conversation between parties that have not previously worked together.

The standard scope of an information-exchange NDA includes capability statements (when those statements include non-public past performance, key personnel, or pricing), labor rates, draft proposal content, customer-specific solution architectures, and pricing strategy. Two-year initial terms with five-year confidentiality survival are typical. Either party can walk after exchanging information, but obligations on already-disclosed information continue for the full survival period.

The NDA does not create exclusivity, does not commit either party to a proposal, and does not flow down any Federal Acquisition Regulation (FAR) or Defense Federal Acquisition Regulation Supplement (DFARS) clauses. It is a confidentiality instrument, not a teaming instrument. The most common drafting error is treating the NDA as if it implies a teaming commitment; it does not, and either party may team with anyone else after signing one.

The Procurement Integrity Act (41 USC 2101-2107) applies to any exchange of "source selection information" or "contractor bid or proposal information." NDAs in federal teaming contexts should include explicit Procurement Integrity Act representations from both parties to avoid inadvertent disclosure exposure.

When Do You Need a Teaming Agreement?

A Teaming Agreement is the binding pre-award contract between a prime and a subcontractor. The legal basis is FAR Subpart 9.6 (Contractor Team Arrangements). The TA defines workshare percentages, key personnel, labor rates, proposal-preparation responsibilities, exclusivity for the named solicitation, and the path to a definitive subcontract following award.

The TA is opportunity-specific. It applies to one named solicitation and terminates automatically if the prime is not awarded the contract. If the prime is awarded but the parties cannot reach a definitive subcontract within the negotiated window (typically 60-90 days), either party can walk and the TA terminates. A common drafting addition is an outside date (commonly 12 months from the Effective Date) after which the TA expires regardless of solicitation status, which protects both parties from being locked into a stale arrangement on a delayed acquisition.

The TA's exhibits are where the operational substance lives: a Subcontractor Scope (Exhibit A) defining the work the SDVOSB sub will perform, a Labor Rates schedule (Exhibit B) used in the prime's proposal, and a Key Personnel attachment (Exhibit C) naming the people who will be presented to the agency. Pricing, key personnel, and scope cannot be amended unilaterally after proposal submission without re-coordinating with both parties.

Section 8 of a defensible TA is a "no exclusivity" clause: the agreement binds both parties only on the named solicitation, and it explicitly preserves the right of each party to pursue other opportunities, including opportunities where the other party is a competitor. This clause is the primary defense against affiliation findings under 13 CFR 121.103. A TA without an explicit no-exclusivity clause is a TA that the SBA can use as evidence of undue reliance.

When Do You Use a Contractor Teaming Arrangement (CTA)?

The Contractor Teaming Arrangement is a GSA Schedule construct, governed by GSA guidance at gsa.gov. Both parties hold GSA Schedule contracts, both parties are prime to the agency, and both parties invoice the agency directly under their own Schedule pricing. There is no flow-down between the parties because there is no prime-sub relationship; both are primes to the agency on the same task order.

The CTA is operationally distinct from the prime-sub model. It is useful when both parties already hold relevant GSA Schedule contracts and want to combine their offerings on a task order without one party absorbing the other's scope as a sub. Each party retains its own Schedule pricing, its own contract administration, and its own performance accountability for the scope it delivers. The agency receives two invoices and pays each party directly.

Federal agencies use CTAs on Schedule task orders when the requirement spans capabilities that are not all available under a single Schedule contract. Common examples: a hardware-heavy Schedule contractor pairing with a managed-services Schedule contractor on a hybrid infrastructure task order; a cybersecurity assessor pairing with a software-licensing Schedule contractor on a tools-plus-services package. Outside the GSA Schedule context, CTAs are not available; agencies that buy via FAR Part 8 Schedule procedures can use them, agencies buying via FAR Parts 13, 15, or 16 cannot.

Note for SDVOSB IT firms: CTAs require both parties to hold a GSA Schedule. An SDVOSB IT firm that does not hold a Schedule cannot enter a CTA; the appropriate vehicle for that firm is a Teaming Agreement on a Schedule task order issued to the prime. TDS-IS does not currently hold a GSA Schedule, so we use Teaming Agreements rather than CTAs for Schedule-task-order pursuits.

When Do You Form a Joint Venture?

A Joint Venture is a separate legal entity formed by two or more parties to pursue federal contracts. The JV has its own UEI, its own SAM.gov registration, its own balance sheet, and its own contracts. SDVOSB JVs are governed by 13 CFR 125.18, which establishes specific requirements: the SDVOSB partner must own at least 51% of the JV, must designate a service-disabled veteran of the SDVOSB as the responsible manager, and must perform at least 40% of the JV's work.

JVs are heavier than Teaming Agreements. They require an operating agreement, separate accounting, separate tax filings, separate insurance, and separate registrations. The overhead is real. The trade-off is access to opportunities that a single firm cannot win alone: long-term IDIQ vehicles, multi-year recurring task-order pipelines, and prime positions on programs whose scope exceeds either firm's individual past performance.

The Mentor-Protege Program (MPP) at 13 CFR 125.9 is the safe-harbor structure for large prime + SDVOSB JVs. An SBA-approved Mentor-Protege Agreement, paired with a JV between the mentor (large) and the protege (SDVOSB), is exempt from affiliation. The All-Small MPP merged into a single program in 2020 and is now the primary vehicle for major IDIQ pursuits where the prime needs to bring scale capability and the protege brings the SDVOSB qualifying status.

For the regulatory deep-dive on SDVOSB JVs, including the three-in-two rule, populated versus unpopulated structures, and the 12 mandatory operating-agreement provisions under 13 CFR 125.18(b)(2), see SDVOSB Joint Venture Rules Under 13 CFR 125.18.

Decision Matrix: Which Vehicle Fits Your Situation?

The matrix below maps the most common federal teaming scenarios to the appropriate vehicle stack.

• Information exchange only, no commitment. Mutual NDA. No additional vehicle until the parties decide whether to pursue a specific solicitation together.
• Single solicitation, prime-sub structure. NDA, then Teaming Agreement before proposal submission. The TA binds the prime-sub structure for the named solicitation only.
• GSA Schedule task order, both parties on Schedule. NDA, then Contractor Teaming Arrangement. Both parties invoice the agency separately.
• GSA Schedule task order, only prime on Schedule. NDA, then Teaming Agreement. The non-Schedule party is a sub on the prime's Schedule task order.
• Multi-year competitive pursuit, repeat work expected. NDA, then JV operating agreement. Justify the JV overhead with the projected pipeline value.
• Mentor-Protege pairing on a major IDIQ. NDA, SBA-approved Mentor-Protege Agreement, then JV operating agreement. The MPA is the affiliation safe harbor.
• Sub-tier work on prime's existing contract. NDA, then a definitive Subcontract Agreement directly (no TA required if no proposal is being prepared together). The prime's flow-downs from the prime contract apply.

For the file-discipline checklist (what the prime should retain in the contracting file for any of these vehicles), see the "What Does a Defensible Teaming File Look Like?" section of the teaming pillar.

What Order Do You Sign Them In?

The signing order follows the lifecycle of a federal pursuit. Skipping a step does not save time and creates downstream exposure.

1. NDA first, always. Sign the Mutual NDA before any non-public capability information, pricing, or proposal content moves between the parties. This is the cheapest insurance in federal teaming and the most commonly skipped step.
2. Teaming Agreement before proposal submission. The TA must be executed before the prime submits the proposal. A submitted proposal that names a sub without an executed TA exposes both parties: the prime cannot enforce the named workshare, and the sub cannot enforce its proposal contribution. Some primes execute TAs during proposal preparation rather than at the last minute, which is the safer practice.
3. Definitive Subcontract Agreement after award. The TA's Section 5 typically requires the parties to negotiate a definitive subcontract within 60-90 days of the prime's award. The subcontract incorporates the prime's flow-down clauses (DFARS 252.204-7012, FAR 52.219-14, agency-specific clauses) and becomes the operational instrument for performance.
4. JV operating agreement before the joint proposal. If the parties form a JV, the operating agreement must be in place before the JV submits its first proposal. The JV must also have a UEI, SAM registration, and any required certifications (SDVOSB JV certification under 13 CFR 125.18 for SDVOSB set-aside competitions) at proposal time.
5. Mentor-Protege Agreement before the JV (if MPP-based). The SBA-approved MPA is the affiliation safe harbor for the JV. The MPA approval process at sba.gov takes time. Start it well before the first JV pursuit.

Frequently Asked Questions

Can the same parties move from a Teaming Agreement to a Joint Venture for the next opportunity? Yes. The Teaming Agreement is opportunity-specific and terminates with the named solicitation. Moving to a Joint Venture for a subsequent opportunity is a clean transition: the prior Teaming Agreement does not bind the new pursuit, and the parties can stand up a JV operating agreement under 13 CFR 125.18 with a new SDVOSB managing-member structure. Many large prime + SDVOSB relationships start with one or two Teaming Agreements and graduate to a Mentor-Protege JV when the pursuit set justifies the overhead.

Does a Mutual NDA expire if no Teaming Agreement follows? Most Mutual NDAs have a stated term (commonly two years from the effective date) and a separate confidentiality survival period (commonly five years from disclosure). If no Teaming Agreement follows, the NDA's term expires on its stated date, but the confidentiality obligations on information already exchanged continue for the full survival period. Either party can also terminate an NDA on written notice, which stops new exchanges of information but does not release prior disclosures from the survival period.

Is a Letter of Intent sufficient instead of a Teaming Agreement? No. A Letter of Intent (LOI) typically expresses non-binding intent to pursue a definitive agreement. A Teaming Agreement is the binding pre-award contract that defines workshare, key personnel, exclusivity for the named solicitation, and the path to a subcontract. Submitting a federal proposal that names a subcontractor without an executed Teaming Agreement creates exposure: the prime cannot enforce the workshare, and the sub cannot enforce its proposal contribution. LOIs are appropriate at the very early conversation stage; they are not a substitute for a TA at proposal time.