The Corridor Verdict: Auditing Decisions That Never Reach the Record

The decision that was never minuted

Most UK organisations have a formal decision-making system. Papers are circulated, meetings are held, minutes are taken, and actions are assigned. Yet ask a project team how a particular choice was really reached and a different account often emerges. The decisive conversation happened in a corridor, on a video call that was not recorded, or in a chat thread that has since been archived. The minutes reflect the outcome, not the deliberation.

This is not necessarily a failure of individual conduct. It is a predictable consequence of how work gets done. Hybrid patterns, compressed schedules and the reasonable human desire to avoid escalation all push discussions into informal channels. The difficulty is that these shadow channels can quietly reshape decisions without the scrutiny, authority checks or record-keeping that formal governance is designed to provide. For change programmes and operational improvement work, that gap is a governance risk worth auditing.

Why the meeting after the meeting matters

The informal follow-up is not inherently problematic. A brief conversation between a project lead and a finance business partner can resolve a sticking point faster than another scheduled meeting. The risk arises when the informal conversation becomes the place where the decision is actually made, while the formal meeting merely ratifies it. At that point, three things can go wrong.

First, delegated authority may be bypassed. A decision that should have been taken by a director, a board sub-committee or a programme board is agreed between two managers and presented as a fait accompli. Second, the rationale is lost. When the decision is later questioned, no one can reconstruct the options considered or the trade-offs accepted. Third, downstream dependencies are missed. A choice made in isolation may create consequences for teams that were not in the room, or the corridor.

In 2026, with many organisations still operating mixed on-site and remote patterns, these shadow channels are more dispersed than ever. A decision may form across a sequence of direct messages, a brief phone call and a passing comment at a desk. The audit question is not whether informal conversation happens, but whether the organisation can see where consequential decisions are being made and whether they remain within the boundaries set by governance.

Mapping the shadow channels

A practical audit begins with observation rather than accusation. Select a recent change initiative or operational process with a known decision history. Gather the formal record: minutes, decision logs, project board papers and action trackers. Then interview a small cross-section of people involved, including those who attended formal meetings and those who did not. Ask a simple question: where was the decision really made?

The answers will help map the informal channels. Common patterns include the pre-meeting between senior sponsors, the functional huddle that agrees a position before the board, and the bilateral conversation that resolves an impasse. Note the medium as well as the people: a recurring calendar hold with no agenda, a standing chat group, a weekly call that is not minuted. The aim is not to eliminate these channels but to understand which ones carry decision weight.

A useful test is to trace a sample of decisions from proposal to outcome. For each one, identify the point at which the choice became effectively irreversible. If that point sits outside a forum with a record and a mandate, the decision has travelled through a shadow channel. Repeat the exercise across several decisions to distinguish a one-off from a pattern.

Testing authority and consequence

Mapping the channels is only the first step. The audit should then test whether outcomes still sit within delegated authority. Take the decisions identified and compare them with the organisation's scheme of delegation, programme governance terms of reference or financial thresholds. A decision agreed informally may still be within authority, but the audit should confirm that the right people endorsed it and that any required consultation took place.

Equally important is the consequence test. For each shadow decision, ask who downstream was affected and whether they knew. A change to a service model agreed in a corridor may alter workloads for operational teams who were not consulted. A revised timeline agreed between two managers may undermine a supplier commitment made elsewhere. The audit should surface these connections, not to assign blame but to reveal where informal speed has created formal rework or unmanaged risk.

The output of this stage is a short risk register, not a lengthy report. It should identify the decisions that lack a clear authority trail, the functions that were surprised by an outcome, and the informal channels that routinely carry material choices. That register becomes the basis for a proportionate response.

Lightweight logging that people will use

The temptation after an audit is to impose a heavy new process. That rarely works. A decision log that requires a full paper for every choice will be ignored or completed retrospectively. The better approach is lightweight logging tied to thresholds. Define what counts as a material decision, whether by financial value, operational impact or irreversibility, and require a short entry for those decisions only.

The entry need not be elaborate: date, decision, decision-maker, authority reference, options considered and affected parties. A shared register or a simple form linked to the programme board papers is sufficient. The discipline lies in the expectation, not the technology. Teams should know that material decisions, however they are reached, are recorded within a short window, ideally the same working day.

Leaders also need to model the behaviour. If senior sponsors continue to settle matters in unrecorded conversations and then present them as settled, the logging requirement will be treated as a bureaucratic overlay. The audit should therefore include a review of sponsor behaviour alongside team behaviour. The goal is not to make every conversation formal, but to ensure that the organisation can answer a basic question: who decided this, on what basis, and with whose authority?

A proportionate control, not a culture change

The corridor verdict is a symptom, not a sin. It reflects a gap between how decisions are formally governed and how work actually happens. Closing that gap does not require eliminating informal conversation or adding layers of approval. It requires visibility, a clear threshold for what must be recorded, and leaders who treat the record as a working tool rather than an afterthought.

For UK organisations managing change and operational improvement, the audit described here can be completed in a few weeks and with minimal disruption. It replaces assumption with evidence and gives governance committees something more useful than minutes: a realistic view of where authority is exercised. That is a practical route to accountability that does not slow the organisation down.