The Half-Life of a Declaration: Maintaining a Live Conflicts Register in UK Advisory Work

Most conflicts procedures in UK advisory firms are built for a single moment: the pitch. A form is completed, a box is ticked, an engagement letter carries a paragraph of boilerplate, and the file is closed. The declaration is treated as an event. In practice it is a record with a shelf life, and that shelf life is shorter than most firms assume.

Between the declaration and the delivery there are months of movement. A client acquires a competitor. A partner takes a non-executive seat. A subconsultant is engaged who already advises the other side of the transaction. A framework call-off brings a new contracting authority into view. None of this is captured by a form completed in February and never revisited.

Why a Declaration Decays

A conflict statement is accurate only for the facts that existed when it was written. Everything after that is drift. In smaller practices — a five-person consultancy, a sole practitioner with associates, a portfolio professional holding several non-executive roles — the drift is faster because the same individual appears across multiple client relationships simultaneously.

The usual failure is not dishonesty. It is arithmetic. Nobody has the time to reconstruct, from memory, which mandates touched which sectors in which quarters. Under pressure, a principal answers a conflict question by recall, and recall is generous with itself.

The regulatory backdrop reinforces the point without dictating the method. Solicitors have the SRA Codes; accountants have the FRC's ethical standard; FCA-authorised firms have SYSC and the conduct rules; public sector suppliers face the Procurement Act 2023 regime and its expectations around conflicts. Each imposes a duty. None supplies the working document. That is a matter of internal design.

What the Register Should Hold

A workable register is not a legal instrument. It is an operational ledger, and it should be short enough that people actually maintain it. Six fields will carry most of the weight.

The relationship. Client name, contracting entity, and the ultimate parent where they differ. Group structures matter: a mandate for a UK subsidiary can create an adjacency with a parent's competitor.

The nature of the mandate. Brief description, sector, counterparties named in the engagement, and the commercial interest at stake. A one-line description is enough if it names the parties.

Adjacent relationships. Anyone else in the register whose interests could be affected — competitors, suppliers, regulators, litigants, or the client's own customers.

The declared position. What was disclosed, to whom, in what terms, and on what date. Attach the wording rather than paraphrasing it. The exact phrasing is what a client will hold you to later.

The consent basis. Whether the client acknowledged the disclosure, gave informed consent, imposed conditions, or simply did not respond. Silence is a category and should be recorded as one.

The review trigger. The event that requires the entry to be revisited — a new mandate, a merger, a change of personnel, a contract renewal, or a fixed date.

Triggers Beat Diaries

Annual review cycles are better than nothing, but they tend to produce a flurry of activity in one month and twelve months of neglect. Triggers embedded in existing workflow are more reliable, because they arrive attached to work someone is already doing.

Useful triggers include: opening a new client matter; issuing a proposal above a defined value; adding an associate or subconsultant to a delivery team; a client announcing an acquisition or disposal; a principal accepting an external appointment; and any request from a client for a fresh conflicts statement.

The last of these is the most valuable. When a client asks, the answer should come from the register in minutes, with dates and prior wording, rather than from an afternoon of reconstruction.

A Wording Bank Saves Time and Protects Position

Firms tend to rewrite conflict disclosures from scratch each time, which produces inconsistency and occasional over-disclosure that alarms the client unnecessarily. A small bank of approved paragraphs — one for a clear position, one for a disclosed adjacency with safeguards, one for a position requiring consent, one for a declined mandate — reduces both risk and effort.

Each paragraph should state the facts plainly, identify the safeguards (information barriers, separate teams, fee separation, a nominated point of contact), and invite the client to raise concerns. Precision here is a commercial asset: a client who receives a clear, specific disclosure in writing tends to regard it as evidence of control rather than as a problem.

Retention, Access and the Data Question

A conflicts register holds personal data about principals and often about client personnel. Under UK GDPR the firm needs a lawful basis, a stated retention period, and access limited to those who need it. In practice this means the register sits in a controlled location — not a shared drive with open permissions — with a named owner and a defined review of access rights.

Retention should be tied to the purpose. Records of disclosures made in respect of an engagement are generally worth keeping for the life of that engagement plus the firm's usual limitation period, which for contract claims in England and Wales is typically six years. Records should be pruned on a schedule rather than by accident.

Making It Work in a Small Practice

The register fails when it is treated as a compliance artefact maintained by one person in isolation. It survives when it is a by-product of ordinary activity: a mandatory field in the matter-opening form, a line in the proposal sign-off, a standing item in the monthly partner meeting that takes four minutes rather than forty.

There is also a cultural point worth stating plainly. A register that is honest will occasionally record an awkward adjacency — a relationship that could have been handled better, or a consent that was never formally given. That is the point. A register that only records comfortable facts provides no protection at all, because the uncomfortable facts are the ones a client will eventually discover.

Starting a 2026 Conversation With Evidence

When a client asks how the firm handles conflicts, the strongest answer is not a policy document. It is a demonstrated process: here is the register, here is your entry, here is what we disclosed in March, here is what changed in September, here is why it was reviewed and what we concluded.

That answer does two things simultaneously. It satisfies the question, and it signals the operating standard of the firm. For smaller UK practices competing against larger houses with dedicated risk functions, a well-kept register is a proportionate and credible substitute — not a facsimile of institutional machinery, but proof that the question has been considered continuously rather than at the point of sale.

Objectivity is not a state a firm achieves. It is a position that has to be re-established as circumstances move. The register is simply the record of having done so.