A conflicts register cannot make a procurement impartial

A procurement conflicts register is useful only when it changes how decisions are made. For an England-led public procurement, the practical question is whether a declared interest can influence specifications, access to information, evaluation or contract management—and what evidence shows that the risk has been controlled.

A completed declaration is the start of that assessment. It cannot establish that the subsequent competition was impartial. This briefing separates the current statutory context from an original method for testing whether the recorded controls actually operated.

The Cabinet Office conflicts guidance, updated 13 July 2026, explains duties under the Procurement Act 2023 for covered procurement. Authorities must identify and review actual and potential conflicts, mitigate them, and address perceived conflicts. An assessment is required before the relevant tender, transparency or dynamic-market establishment notice and must remain under review. Confirming preparation in relevant notices does not mean publishing the complete assessment. The specific conflicts provisions do not apply to below-threshold procurement, although other duties and internal rules remain relevant.

This is not a single rule for every UK purchase. Check the procurement's legal regime and transitional position. The devolved-authorities guidance explains that devolved Scottish authorities are generally excluded, with qualifications, and that arrangements involving other authorities can change the applicable rules. Overseas bidders need the regime governing the actual procurement, not the location of their own headquarters.

Start with the decisions that shape the result. Who can write a requirement, select a shortlist, see a competitor's information, moderate scores or approve a variation? Map those opportunities to the people involved, including advisers. An employee's job title may reveal less than their access to documents and informal influence over a colleague.

Then distinguish the interest from the possible effect. A relationship is a fact to assess, not an automatic conclusion of misconduct. Record what the relationship is, where influence could arise, the evidence considered and who assessed it. Avoid collecting irrelevant personal information merely to make the register look comprehensive.

The useful unit of control is a decision and its exposure. A single declaration can relate to several decisions with different risks. Conversely, a person outside the formal evaluation panel may still shape the specification or brief the panel. Keep the record connected to the actual work.

If the proposed control is removal from evaluation, retain evidence of the changed panel and access arrangements. If it is an additional independent check, identify the checker, the material checked and the conclusion reached. A sentence saying “managed by the team” gives a later reviewer little to test.

Use a short control record with five fields: decision affected, exposure identified, mitigation owner, completion evidence and next review trigger. This is an editorial implementation aid, not a statutory template. It helps distinguish an intention to mitigate from a control that was completed before the affected decision.

Consider residual exposure after the control. Removing someone from a meeting may be insufficient if they have already supplied one bidder with useful information. Assess that specific consequence with the procurement and legal teams. The Act's exclusion consequence is conditional: the guidance addresses an unfair supplier advantage that cannot be avoided, or refusal to take necessary steps. It does not say every declared relationship automatically excludes a supplier.

In a fictional procurement, an adviser discloses a relationship with a bidder after contributing to the specification. Removing that adviser from the scoring panel addresses future scoring access, but does not explain what happened during specification development.

These are fictional entries in a proposed operating record, not statutory fields or a finding of misconduct. Do not mark the overall issue resolved merely because panel membership changed.

The decision owner needs to consider the remaining exposure and obtain the applicable procurement or legal assessment. That assessment may require further measures; this example does not determine supplier exclusion or eligibility. Keep sensitive relationship details in the restricted evidence file and record only what the authorised reviewer needs in the decision summary.

The practical output is a control whose completion can be checked, with unresolved earlier influence still visible. It is stronger evidence than a register entry that only says “interest declared.”

A new adviser, ownership change or contract variation can alter the original judgement. Set review triggers that the contract manager can recognise and assign responsibility when procurement hands the contract to operations. The initial register should not become an archived attachment while decisions continue elsewhere.

For consequential decisions, connect the conflicts assessment to the record of decision reasoning. The related article concerns decision evidence, not a substitute procurement-law test. Preserve the reasons for accepting a mitigation and the evidence available at that time.

The immediate action is to select one active procurement and trace one declared interest into the actual decision record. If the control exists only as a promise, resolve that gap before relying on the register as assurance. Obtain specialist advice where impartiality, supplier exclusion or legal scope is uncertain.

AI assistance was used in research and drafting. No client engagement, firsthand test or independently verified outcome is claimed.

This article is general information. Verify current requirements and seek qualified advice for your specific circumstances.

Spotted an issue? Contact our editorial desk.