The Two-Hat Problem: A Conflict Register That Stands Up to Challenge

Conflicts of interest are often treated as a compliance formality: a declaration at the start of a meeting, a line in an appendix, a box ticked before a procurement proceeds. That approach is fragile. Where public and private roles overlap, the real risk is not the declaration itself but the decision that follows it. A conflict register should be a live governance instrument, not a filing cabinet.

Why the register matters more than the declaration

Public bodies are accountable for both probity and outcomes. A register that records interests but does not show how those interests were managed gives auditors, bidders and the public little assurance. It may even create a false sense of control. The stronger question is not whether an interest was declared, but whether the decision-maker recognised its significance, took an appropriate step and recorded why that step was proportionate.

That distinction matters in procurement, contract management, board appointments and joint delivery. In each setting, the same person or organisation may wear more than one hat. A consultant advising on service design may later bid for the contract. A non-executive director may sit on a public board and hold a private sector role. A delivery partner may second staff into a client team while retaining commercial interests elsewhere. A register should make those overlaps visible before they become a challenge.

Spotting the two-hat problem early

Conflicts are easiest to manage before positions harden. Procurement teams should screen proposed evaluation panel members, technical advisers and specification authors for prior involvement with likely bidders. Contract managers should consider whether supplier-side staff embedded in the client team have access to information that could advantage their employer. Board secretaries should test whether appointments create competing loyalties, particularly where the appointee has a commercial interest in a supplier or a joint venture.

Joint delivery arrangements deserve particular attention. A company limited by guarantee, a joint committee or a shared service vehicle may bring public and private actors into the same governance structure. The register should capture interests at entity level as well as individual level. A private partner may not have a named individual with a conflict, but the organisation itself may have a commercial interest that colours how a decision is viewed.

The UK public sector already has reference points. The Nolan principles of public life set expectations of integrity, objectivity and accountability. Local authority codes of conduct, the Localism Act 2011 framework and the Procurement Act 2023 all point towards transparent, defensible decision-making. The practical task is to translate those expectations into a register that people actually use.

From declaration to decision: a four-step test

A defensible register usually follows four steps. First, identify the interest in enough detail to understand its relevance. Second, assess materiality: is the interest direct or indirect, financial or non-financial, current or historic? Third, decide on a management measure. Avoidance is the strongest response where the conflict is material. Mitigation may be appropriate where the interest is peripheral, for example by separating duties, using an independent reviewer or limiting access to papers. Fourth, record the rationale and set a review date.

The fourth step is where many registers fall down. A note that a member declared an interest and took no further part is useful. A note explaining why a less restrictive measure was chosen is stronger. It shows that the decision-maker weighed the risk rather than simply defaulting to a procedural step.

Designing register fields that work

A register should be proportionate, but it needs sufficient fields to support scrutiny. Useful entries include the individual or organisation, the role held with the public body, the nature of the external interest, the date the interest was identified, the matter affected, the assessed risk, the management measure, the decision-maker and the review date. Where a private partner is involved, the register should also record how the partner was informed and what contractual notification obligations apply.

Registers should be updated when circumstances change. A declaration made at appointment may be stale by the time a contract variation is discussed. Contract terms can require suppliers to notify material changes in ownership, control or key personnel. Public bodies should mirror that discipline internally, with a prompt for contract managers to refresh declarations before major decisions, extensions or variations.

Board appointments and the private-sector non-executive

Board appointments are a common source of blurred roles. A non-executive director with private sector experience can add real value, but the same experience may create a commercial interest in a supplier or a competitor. Directors also owe duties under the Companies Act 2006 where they sit on subsidiary or joint venture boards. Those duties can sit awkwardly alongside a public appointment.

The answer is not to avoid such appointments but to manage them openly. Appointment papers should require a written declaration of interests. Board agendas should include a standing item on conflicts. Minutes should record not only the declaration but the action taken. Where a conflict is material, recusal from discussion and decision is usually the safest course. Where it is not, an independent chair or a separate sub-group may provide sufficient distance.

Testing the register before challenge

A register is more credible if it is tested. Internal audit can sample entries and trace them to minutes, procurement records and contract management files. Scenario exercises can ask managers what they would do if a bidder appointed a former colleague or if a board member acquired shares in a supplier. Freedom of Information requests may also expose whether the register is maintained and whether redactions are justified.

Contemporaneous records matter. If a challenge or complaint arrives months later, a clear minute explaining the interest, the assessment and the mitigation is far more persuasive than a reconstructed account. The register should therefore be treated as part of the decision trail, not a separate administrative exercise.

A practical checklist

• Map roles across procurement, contract management, boards and joint delivery vehicles.
• Require declarations from individuals and, where relevant, organisations.
• Record the nature and materiality of each interest, not just its existence.
• Choose a management measure that matches the risk: avoid, mitigate, recuse or independent review.
• Minute the rationale and the review date.
• Build contractual notification duties into supplier and partner arrangements.
• Refresh declarations before major decisions, variations and extensions.
• Audit a sample of register entries against decision records.

A conflict register will not eliminate awkward overlaps. It can, however, turn them into managed risks with a clear audit trail. In public-private delivery, that is the difference between a procedural nod and a governance control that stands up when it matters.