Consortium Agreement Template

In plain language: Defines exactly what the consortium exists to do — the named opportunity, project, or program — and the period during which the agreement is in force.

Common mistake: Defining the purpose too broadly — e.g., 'technology services' rather than a named tender. A vague purpose clause can make the agreement apply to future opportunities neither party intended to share, triggering exclusivity disputes.

In plain language: Lists each member, their designated role in the consortium, and their specific financial, resource, or service contributions — cross-referenced to a Schedule of Contributions.

Common mistake: Leaving contributions described only in general terms in the body and promising a schedule that is never attached. Courts treat missing schedules as omitted terms, making contribution obligations unenforceable.

In plain language: Grants the lead member specific powers to act on behalf of the consortium — signing the prime contract, issuing invoices, and managing client communications — while limiting those powers to consortium-approved decisions.

Common mistake: Granting the lead member unlimited authority to bind the consortium. This exposes passive members to obligations they did not approve — including scope changes, penalty clauses, and liability extensions.

In plain language: Establishes a Consortium Committee with one representative per member, defines meeting frequency, sets the voting thresholds for different categories of decisions, and provides a tie-breaking mechanism.

Common mistake: Requiring unanimity for all decisions. With three or more members, a unanimity requirement for routine matters creates deadlock and delays project delivery. Reserve unanimity for fundamental changes only.

In plain language: Sets out how consortium revenues are received and distributed, how shared costs are allocated across members, and the process for approving consortium expenditures.

Common mistake: Distributing revenue before deducting shared costs. Without a clear order of operations — deduct shared costs, then distribute — disagreements arise about whether distributions are net or gross, creating cash-flow disputes mid-project.

In plain language: Distinguishes background IP (each member's pre-existing IP, which remains theirs) from foreground IP (jointly created IP), allocates ownership of foreground IP, and grants each member any licenses needed to perform the project.

Common mistake: Defaulting to joint ownership of foreground IP without specifying each owner's exploitation rights. In most jurisdictions, joint IP owners can each exploit the IP independently — meaning a competitor member could commercialize jointly developed technology without sharing revenue.

In plain language: Requires members to keep confidential information shared within the consortium — technical data, pricing, client communications — and restricts use to consortium purposes only.

Common mistake: Using identical confidentiality language for a consortium agreement and a bilateral NDA. Consortium confidentiality must account for multi-directional disclosure — each member is simultaneously a discloser and a recipient — and must specify whether members can share information with their own subcontractors.

In plain language: Prevents members from participating in a competing bid or consortium for the same opportunity during the agreement's term, protecting the consortium's ability to present a unified offering.

Common mistake: Applying the exclusivity clause only to the primary bid without covering substantially similar opportunities. A member who bids independently on a closely related contract — or joins a competitor's consortium for a related lot — may not technically breach a narrowly worded clause.

In plain language: Specifies whether members have joint-and-several or several liability to the client and to each other, caps each member's maximum exposure, and requires each member to indemnify the others for losses arising from their own default.

Common mistake: Failing to specify several versus joint-and-several liability between members. If the prime contract with the client imposes joint and several liability on the consortium, members may assume their internal agreement does the same — leaving a defaulting member's shortfall to be absorbed by solvent partners.

In plain language: Defines the circumstances under which a member may voluntarily withdraw or be expelled, the consequences for project obligations, IP rights, and cost recovery, and the process for winding down the consortium at the end of the project.

Common mistake: No exit clause at all, or an exit clause that only covers voluntary withdrawal. Forced-exit triggers — insolvency, change of control, or acquisition by a competitor — are the scenarios most likely to destabilize an active consortium and must be addressed explicitly.

A consortium agreement is a legally binding contract among two or more independent organizations that agree to collaborate on a specific project or bid without forming a separate legal entity. It governs each member's roles, financial contributions, governance rights, IP ownership, confidentiality obligations, and exit rights for the duration of the shared objective. Unlike a joint venture, a consortium typically dissolves when the project or bid cycle ends.

A joint venture typically involves creating a new legal entity — a company or partnership — owned by the founding parties. A consortium keeps each member as an independent organization and does not create a new entity. Consortiums are common for single projects, joint bids, or research programs where the parties want to collaborate without the tax, regulatory, and administrative overhead of a new company. If the relationship is intended to be permanent or involves shared equity, a joint venture agreement is usually more appropriate.

This depends entirely on the terms of both the consortium agreement and the prime contract with the client. Many government contracts impose joint and several liability on consortium members externally, meaning the client can pursue any one member for the full value of a claim regardless of individual fault. Internally, the consortium agreement can allocate liability on a several basis — each member bears only its own share — and include indemnification obligations so the defaulting member reimburses solvent partners who are forced to cover its shortfall.

The lead member is typically the organization with the largest contribution, the strongest relationship with the client, or the relevant prime contractor license required by the procurement. The lead member signs the prime contract on behalf of the group, issues invoices, and manages day-to-day client communications. Because the role carries greater administrative responsibility and potential liability exposure, the consortium agreement should clearly define the limits of the lead member's authority to bind the other members.

The most common structures are: (1) joint ownership with explicit commercialization restrictions requiring co-owner consent; (2) ownership by the member who created the IP, with a license-back to the others for defined purposes; or (3) assignment to a single designated member with defined royalty or revenue-sharing terms. In research consortiums funded by government grants, the funder may mandate specific IP ownership arrangements. Defaulting to unqualified joint ownership is the riskiest option because each co-owner may independently exploit the IP without accounting to the others in most jurisdictions.

In most government and institutional procurements, yes — the solicitation documents typically require either a signed consortium agreement or a signed teaming declaration as part of the bid package. A missing or unsigned agreement is grounds for disqualification in many jurisdictions. Even where the client does not require it, executing the agreement before bid submission protects each member by establishing agreed terms before the stakes are highest.

A member can withdraw if the consortium agreement contains a withdrawal clause specifying the required notice period, the obligations that survive exit (typically completing work-in-progress and maintaining confidentiality), and the consequences for IP rights and cost recovery. Without a withdrawal clause, a member who leaves may be in breach of contract. Forced-exit triggers — insolvency, acquisition by a competitor, or loss of a required license — should also be addressed separately from voluntary withdrawal.

Yes, a properly executed consortium agreement is generally enforceable as a binding contract in most jurisdictions, provided it meets the standard requirements: offer and acceptance, consideration (typically each member's contribution), and intention to create legal relations. Courts in the US, Canada, the UK, and the EU have consistently enforced consortium agreements as commercial contracts. Clarity of terms — particularly on contributions, governance, and IP — significantly affects how quickly and cheaply disputes can be resolved.

Unless the agreement provides otherwise, an unsuccessful bid typically triggers termination of the consortium agreement, with each member retaining its own background IP and the parties settling any shared pre-bid costs. Some agreements include a re-bid clause allowing members to extend the agreement if the opportunity is re-tendered within a defined period. Post-termination confidentiality obligations and any exclusivity restrictions on re-bidding independently should be explicitly addressed in a termination consequences clause.