Rivals at the Table: Board Guardrails for Competitor Collaborations

Competition and collaboration are often treated as opposites. In UK public services and regulated markets, they frequently coexist. A local authority may ask rival suppliers to deliver through a single consortium; an NHS programme may need competing providers to share capacity; a major framework bid may depend on firms that sell against each other every working day. The board’s task is not to pretend the rivalry has disappeared. It is to govern the collaboration so that it secures the opportunity without eroding commercial discipline, breaching confidentiality or creating legal and reputational exposure.

Co-opetition is a useful term because it holds both halves of the relationship in view. The parties remain competitors in the market even as they become collaborators in a defined venture. That duality needs structure. Boards should therefore approve competitor collaborations with the same care they would apply to any other strategic relationship: clear rationale, visible conflicts, defined decision rights and a credible route out.

Start with the commercial rationale

Boards sometimes approve competitor collaborations because a bid timetable leaves little alternative. That may be understandable, but it is not sufficient. Before committing, the board should be able to explain what each party brings, why the customer or service user benefits, what the organisation would lose by standing aside and how the collaboration supports its own strategy. The rationale should be recorded in the board minutes, not buried in a bid pack.

This matters for two reasons. First, a documented rationale gives future directors a benchmark against which to judge whether the relationship is still delivering. Second, it helps distinguish a genuine partnership from a defensive arrangement that merely postpones a commercial problem. Guardrails should be proportionate to risk, but they should begin with a clear answer to the question: why are we doing this with a competitor rather than alone, or with a non-competitor?

Separate the people who compete from the people who collaborate

Information firewalls are the most familiar control in co-opetition, and often the weakest in practice. A protocol that exists only on paper will not survive a deadline. Boards should ask for named individuals, defined roles and practical routines that keep competitive information away from the collaborative team.

In larger organisations, this may mean separate bid teams, clean teams for sensitive data, restricted shared drives and board papers that redact commercially sensitive material. In smaller organisations, where separation is harder, it may mean stronger escalation rules and a clear expectation that informal conversations do not become information channels. The governing principle is need-to-know, not need-to-be-in-the-room.

The board does not need to manage these arrangements day to day, but it should receive assurance that they are operating. A short quarterly report covering information incidents, access requests and breaches of protocol is usually more useful than a long policy that nobody reads.

Make conflicts visible before they become disputes

Competitor collaborations generate conflicts of interest that are predictable but easily overlooked. A director may sit on the board of another consortium member. A senior manager may hold shares in a rival. A partner may have a commercial relationship with a customer that affects how it behaves in the collaboration. These are not necessarily barriers, but they must be known and managed.

A conflict-of-interest register should be established at the outset and reviewed at each board meeting. It should capture directorships, material shareholdings, commercial relationships, previous employment and any other interests that could reasonably be seen to influence judgement. Declarations should be routine, not exceptional. The company secretary or equivalent should own the register and advise on recusal where necessary.

Conflicts should also be considered at bid stage, when partner selection is still fluid. A partner that is commercially close to the customer, or to a competing bidder, may bring advantages and risks in equal measure. The board should see both.

Agree what is shared, what is retained and who decides

Intellectual property is where co-opetition often becomes most delicate. Background intellectual property brought into the collaboration should remain with its owner. Foreground intellectual property created through the collaboration needs an agreed position on ownership, licensing, exploitation and future use. Data, customer relationships, pricing models and bid methodology may be just as valuable as formal intellectual property and should be treated with the same discipline.

The board should ask for a schedule that sets out what is shared, what is retained, what may be used after the collaboration ends and who can authorise variations. A decision-rights matrix is equally important. Which matters require unanimity? Which sit with a management group? Which can be decided by the board of the consortium or joint venture? What happens if the parties deadlock? These questions are easier to answer before a dispute arises than during one.

Build exit ramps into the relationship

Every competitor collaboration should have a credible exit route. That is not pessimism; it is governance. Exit ramps might be triggered by bid failure, contract expiry, a change of control, a serious breach, a reputational event or a material change in market conditions. The agreement should set out notice periods, transition assistance, return of information, wind-down costs and any continuing obligations.

Boards should also consider the softer side of exit. How will the relationship be brought to a close without damaging future cooperation? How will lessons be captured? How will staff be redeployed or supported? A well-designed exit ramp protects the organisation’s commercial position and its reputation as a reliable partner.

Keep oversight proportionate and live

Competitor collaborations do not need heavyweight governance in every case. They do need oversight that is proportionate, regular and connected to the risks that matter. A board dashboard might track milestones, declared conflicts, information incidents, intellectual property requests, partner engagement and exit triggers. An annual review can test whether the rationale still holds and whether the guardrails remain fit for purpose.

The relationship-led point is important. Guardrails are not there to signal distrust. They are there to make trust practical. When rivals sit at the same table, clear boundaries allow people to collaborate openly within them. That is the board’s contribution: not to remove the competitive tension, but to govern it so that the collaboration delivers what it was designed to achieve.