How to govern a consortium tender response

Structure

Fix the buyer-facing consortium structure before assigning work

Start with the exact categories in the procurement. A group member, subcontractor and entity whose capacity supports selection may have different declarations, evidence, liability and substitution rules. Record the full legal name, registration identifier, buyer role, proposed contract role, scope and evidence duties for every organization. Confirm whether the consortium already exists, will be formed upon award or is represented by an agreement or letter of intent. Do not call the largest work-package owner the lead until the buyer’s authority and portal implications have been checked.

The submission system can make structure operationally binding. The European Commission’s eSubmission guide, for example, distinguishes a sole submission from a joint submission, requires a group leader and group members to be identified, and warns that changing the structure or leader after the relevant step requires a new draft with prior data removed. Each participant may also need its own registration and documents. This does not set the rules for every portal, but it shows why consortium design cannot remain a slide. Test the intended structure in the actual procurement channel while there is time to correct registrations and approvals.

Authority

Delegate bid operations while reserving member exposure

Create a written bid mandate early. The lead can normally administer the plan, convene reviews, consolidate content, correspond through permitted channels and execute decisions already approved. Reserved matters should capture actions that change a member’s exposure: its scope, price, margin, liability, guarantee, intellectual property, exclusivity, evidence, key personnel, contract deviation or binding representation. State the approval level and response time for each class. “All major decisions require consensus” is too vague to run under deadline and too broad to distinguish an editorial correction from a new commercial obligation.

The buyer’s documents may impose an external authority model. Recent World Bank standard procurement forms can require all joint-venture members to be jointly and severally liable and one member to be authorized to incur liabilities and receive instructions for all. An EBRD standard document similarly uses a lead partner with authority to conduct business for the participating entities. Those provisions only apply when included or otherwise governing, and their legal effect needs counsel. Internally, the consortium must make sure any buyer-facing lead authority is supported by valid member approvals and is not contradicted by a side agreement.

• Name the decision, required evidence, approver and response time.
• Separate delegated administration from authority to create obligations.
• Define when silence means rejection rather than assumed consent.
• Use an executive escalation pair or panel with authority across members.
• Set a no-bid or withdrawal trigger for unresolved material exposure.

Evidence

Control evidence at entity level and commitments at interfaces

Break each criterion into its application rule. Some requirements must be met by every member, some by the leader, some collectively and some by the entity performing a named activity. Assign a producer and verifier accordingly. Keep declarations signed by the correct entity and person. For case studies, name which member performed the work, in what role, during which period and with what attributable result. A consortium cannot improve evidence by removing provenance. If reliance on another entity’s capacity is permitted, map the required commitment and delivery role rather than adding its turnover or personnel informally.

Delivery integration happens at interfaces. For every boundary between members, record input, output, technical standard, decision right, schedule dependency, acceptance evidence, price treatment, risk owner and fallback. A systems member may deliver a platform while an implementation member owns migration and a local partner owns training. The response must show who validates source data, who accepts a migrated record, how platform delay affects training and which entity carries the recovery effort. Shared responsibility without a named interface owner is usually an unowned risk.

Execution

Operate one bid without pretending the members are one company

Use one requirement register, decision log, assumptions register, integrated plan, price baseline and final manifest. Keep entity ownership visible inside each. A member author submits evidence and proposed commitments through a controlled review, not directly into the final answer. The lead checks question coverage and consistency; the member checks factual and corporate authority; cross-member reviewers test interfaces; commercial and legal owners approve exposure. Apply a deadline for member comments after which the issue escalates, not an automatic acceptance rule unless the agreement validly provides one.

Before final approval, reconcile the joint story in both directions. Every named capability has a delivering entity and evidence. Every work package appears in price, resources, schedule, risk and contract allocation. Every portal participant matches the approved structure and required declaration. The lead presents a decision-ready final pack to the member authorities, identifying unresolved assumptions and changes since their prior review. The submission operator acts only under the approved mandate. Return the buyer-generated receipt and final submitted package to every member’s designated record holder, then preserve the consortium decision trail for clarification, evaluation and mobilization.

• Preserve legal-entity ownership inside shared bid controls.
• Route late disagreement to authority rather than reopening all drafting.
• Issue a change summary with every member approval request.
• Reconcile portal identities and attachments before the final session.
• Provide all members with the submitted package and receipt evidence.