Government Decision Logs: Why Public Bodies Need Structured Decision Records

The COVID-19 public inquiry, the Grenfell Tower inquiry, and the Post Office Horizon inquiry share a common thread: the central challenge in each case has been reconstructing why decisions were made, by whom, and on what basis. In each case, the absence of structured decision records has made the reconstruction partial, contested, and less useful for the accountability and learning purposes that public inquiries are designed to serve.

The lesson is not that public servants made bad decisions. It is that good decisions made without structured documentation are almost as vulnerable as bad ones when subjected to retrospective scrutiny. A government decision log does not just protect decision-makers — it creates the contemporaneous record that public accountability requires.

What a Government Decision Log Must Capture

A government decision log has different requirements from a corporate one. The public accountability context means that the alternatives-considered field is not just useful — it is essential. Public inquiries and FOI requests consistently ask: what options did you consider, and why did you choose this one? Without a structured record of alternatives, the answer is always reconstructed, and reconstruction is always vulnerable to challenge.

The minimum fields for a government decision log are:

• The decision — precisely stated, specific enough to be unambiguous about the commitment made
• Legislative or policy basis — the specific authority under which the decision is made
• Evidence reviewed — what evidence or analysis informed the decision, and where it came from
• Alternatives considered — the other options that were available and the specific reasons they were rejected
• Stakeholders consulted — who was involved in the decision process, and in what capacity
• Confidence level — the degree of certainty at the time of decision, acknowledging known uncertainties
• Expected outcome — what the decision is intended to achieve, measurably stated
• Outcome review date — when the decision will be reviewed against its intended effect

The Accountability Function and the Learning Function

A government decision log serves two distinct functions that reinforce each other. The accountability function is the more obvious one: it creates the contemporaneous record that FOI responses, public inquiry submissions, and NAO reviews require. This function is served simply by logging decisions when they are made.

The learning function is equally important and more rarely discussed. Public bodies repeat the same types of decisions regularly — procurement cycles, policy interventions, resource allocation rounds. Without a structured outcome review process, the learning from each cycle does not accumulate systematically. The same diligence gaps recur, the same assumptions prove wrong, and the same costs are incurred. Outcome reviews at 30, 90, and 180 days — built into the decision log as scheduled checkpoints — create the closed loop that makes systematic improvement possible.

Implementing a Government Decision Log: Practical Considerations

The practical challenges in government decision logging are not technical. They are cultural and operational. Senior Civil Servants and policy teams are already working at capacity. Adding a documentation requirement is not received positively unless the value is clearly articulated and the implementation friction is minimal.

The implementation principles that work in practice are: scope narrowly to begin with (the 20% of decisions that create 80% of accountability exposure), integrate with existing workflow (the decision log entry is completed during the decision process, not as a separate step after), make the format as simple as possible (a structured tool is faster than a blank document), and demonstrate value early (use the first FOI response or audit preparation as a concrete demonstration of how much easier the process is with structured records).

The Post Office Horizon and COVID Inquiry Lessons

Both inquiries have demonstrated, in different ways, the cost of decision-making without structured documentation. In the Post Office case, decisions about how to respond to sub-postmaster complaints about Horizon were made over years without structured records of the alternatives considered or the evidence reviewed. In the COVID inquiry, decisions made during the pandemic’s first months have been difficult to reconstruct because WhatsApp messages and informal conversations were the dominant documentation medium.

The lesson for current public sector decision-makers is not historical. It is present-tense. The decisions being made today about public health, procurement, regulation, and policy will face similar scrutiny in the future. The contemporaneous record created by a structured decision log is the accountability infrastructure that makes that scrutiny navigable rather than catastrophic.