Signed once, filed forever: why conflict of interest declarations fail when they are needed most
Almost every contracting authority collects conflict of interest declarations. Far fewer maintain them. The official declaration form is explicit that it is a live document to be updated across the whole commercial lifecycle, from planning through award and contract management to expiry or termination. In practice it is usually treated as a signature to be gathered before the tender goes out and then forgotten, which is precisely the pattern that leaves an authority exposed when someone asks awkward questions two years into a contract.
The definition of Individual is much wider than most lists
Read the template's definition carefully and it covers anyone acting for or on behalf of a contracting authority who influences a procurement decision. The examples run from the project management team and the senior responsible officer through to specification writers, tender assessors, contractors, external experts, private sector secondees, consultants, non-executive board members, special advisers and Ministers.
That is a materially different list from the one most authorities actually circulate. The people with the closest commercial history with a bidder are frequently the technical specialists brought in to write the specification or sit on the panel, and they are exactly the people a departmental distribution list built from the org chart tends to miss.
The practical fix is to build the list from decision points rather than job titles. Who shaped the requirement? Who set the evaluation criteria? Who scores? Who signs off? Anyone who answers yes to one of those needs a form.
Perceived conflicts are the ones people quietly decide not to declare
The template's three categories are not equally comfortable. Actual conflicts get declared because they are obvious. Potential conflicts get declared because the trigger is concrete. Perceived conflicts get skipped, because the test is what a reasonable person might wrongly believe, and nobody enjoys writing down that their circumstances look bad even though they are not.
That instinct is the problem. The whole point of the perceived category is that it does not depend on the individual's own assessment of their own integrity. The guidance tells individuals to discuss circumstances that may give rise to a perceived conflict with an Authorised Individual, which moves the judgement to someone whose decision can be recorded and defended.
The cheapest version of this is a short conversation and a line in Part Two. The expensive version is an undeclared relationship that surfaces during a challenge, when the absence of any record looks worse than the relationship itself.
Part Two is the part that gets skipped, and it is the part that protects you
A signed Declaration B on its own proves only that someone disclosed something. What demonstrates that the authority acted is Part Two: the impacted supplier, the specific mitigation steps taken or to be taken, and the Authorised Individual's decision on whether those mitigations are sufficient and what role the individual will therefore have.
The template forces a binary. Either the mitigations are sufficient and the role is described, or they are not sufficient and the individual has no role in the procurement. There is no third option of noting the interest and carrying on unchanged, which is what informal practice often amounts to.
Recording the role also matters operationally. If someone has been kept out of scoring a particular lot, the people running the panel need to know that, and a signed form sitting in a folder does not tell them.
Treat it as a lifecycle control, not a gate
The form's own guidance notes name the refresh points: planning, assessment and contract award, contract management, and contract termination or expiry. Circumstances change. People move employers, relationships form, incumbents get acquired, and the person managing the contract in year three is rarely the person who ran the tender.
There is also a disclosure dimension. Signatories acknowledge that the conflicts assessment may be disclosed to a third party if investigations or proceedings are brought against the authority. That is a good discipline to keep in mind when writing entries: they should read as if a stranger will read them, because one day one might.
Finally, remember the confidentiality half of the form. It is not decoration. Individuals accept that unauthorised disclosure of bid documents or supplier evaluations could damage the procurement and will attract disciplinary action, and that any disclosure needs written authorisation in each and every case.
The takeaways
- Build the declaration list from decision points, not job titles: specification writers, evaluators, experts, secondees and consultants all count.
- Perceived conflicts are judged by what a reasonable person might wrongly believe, so the call belongs to an Authorised Individual, not the individual.
- Part Two is the evidence that the authority acted: record the impacted supplier, the mitigation and the individual's resulting role.
- The form is a live document with refresh points at planning, award, contract management and expiry.
- Write entries on the assumption they may be disclosed to a third party if proceedings are ever brought.
Want the full breakdown?
The complete explainer covers the key facts, the requirements in detail and a practical action list, free and printable in the Procurement Library.