The Evidential Chain: Why a Decision Is Only as Strong as Its Record

Public bodies do not usually fail because a decision was unlawful. They fail because they cannot show how the decision was made, who made it, what authority they relied on, and how it connects to the contract or service change that followed. The paper trail is not a memory aid. It is the evidential chain.

That distinction matters more in 2026 than ever. Auditors, information requesters, challengers and counterparties can all reconstruct a decision long after the meeting has ended. If the record is thin, inconsistent or disconnected from the contracting chain, the public body is left arguing from inference rather than evidence.

A record, not a recollection

Minutes are often written for readers who were in the room. That is the wrong test. A defensible minute should be intelligible to someone who was not present, does not know the personalities involved and is looking for the legal and financial basis of the decision. It should identify the decision, the decision-maker, the authority relied on, the information considered and any material reservations or conflicts.

This does not require a verbatim transcript. It does require enough substance to answer three questions: what was decided, by whom and on what basis. A minute that records only that a report was noted, or that a proposal was approved, may satisfy a meeting's procedural rules while leaving the public body exposed when the decision is examined later.

There is also a disclosure dimension. Minutes and board papers can be subject to freedom of information requests, subject access requests, litigation disclosure and audit review. They should be written on the assumption that someone outside the organisation may eventually read them. That does not mean suppressing legitimate discussion. It means separating the record of the decision from commentary that adds no evidential value and may create avoidable risk.

The authority question

A decision is only as strong as the power behind it. The record should show whether the decision was taken by the board, a committee, an officer under delegated authority, or a contractual mechanism such as a variation approval. Where delegation is relied on, the record should identify the delegation, its scope and any conditions attached to it.

A delegation register is necessary but not sufficient. It proves that authority existed in principle. It does not prove that the individual who exercised it was acting within the delegation at the time, that the delegation had not been amended, or that any financial threshold or consultation requirement was satisfied. The decision record must close that gap.

Sub-delegation deserves particular attention. It is easy for a scheme of delegation to be applied loosely, especially in large organisations where operational urgency is used to justify shortcuts. If a decision is challenged, the question will not be whether the outcome was sensible. It will be whether the person who took the decision had the legal power to do so. The record should make that clear without requiring the reader to assemble the answer from several unrelated documents.

Variations and the contracting chain

Contract variations are a common weak point because they sit between governance and commercial delivery. A variation may be approved in principle by a board, negotiated by officers, documented by lawyers and implemented by operational teams. Each step can generate its own record, but the records do not always align.

A defensible variation file should link the approval to the contract, the change, the value, the procurement position and the person authorised to sign. If the variation affects scope, price, risk allocation or service levels, the approval record should say so in terms that match the contract documents. A board minute that approves an increase in contract value is not, by itself, evidence that the variation was procured or executed lawfully.

Suppliers have a role here too. A supplier that keeps its own mirror of approvals, change control records and escalation decisions is better placed to respond to audit or dispute. More importantly, a supplier that asks the right questions before implementing a change helps the public body avoid creating a decision trail that contradicts the contract.

When scrutiny arrives

Different scrutiny routes ask different questions. An auditor may ask whether value for money and delegated authority were documented. An FOI requester may ask for the papers behind a decision. A procurement challenger may ask whether the award or variation followed the applicable regime. A counterparty in dispute may ask what the public body agreed, when, and with what authority.

The common thread is contemporaneity. Records created at the time carry more weight than reconstructions prepared after a challenge. That does not mean every decision needs a lengthy narrative. It means the key evidential points should be captured when the decision is taken, not pieced together months later from emails and recollection.

A practical checklist

• Record the decision in clear terms, including what was approved, rejected or deferred.
• Identify the decision-maker and the source of authority, including any delegation and conditions.
• Summarise the material information considered, including financial, legal and procurement advice where relevant.
• Note conflicts of interest and how they were managed.
• Link the decision to the contract, variation, grant or service change it authorises.
• Ensure the approval record and the signed contract documents tell the same story.
• Keep board papers, delegated decision records and contract change records retrievable together.
• Apply a consistent retention and disposal schedule, including to email and collaboration tools.
• Write with disclosure in mind, without turning minutes into a transcript.

Making the trail stand up

The strongest governance record is not the longest one. It is the one that allows a reader to follow the decision from authority to approval to implementation without gaps. Public bodies should test that chain before a challenge arrives, not after. A short internal review of a recent high-value decision can reveal whether the minute, the delegation record and the contract file actually connect.

LGSS Law advises public bodies and suppliers on governance records, delegated authority, contract variations and the evidential issues that arise in audit, information law and procurement challenges. The practical lesson is simple: if the decision matters, the record of it matters just as much.