Signed Off in Silence: Auditing the Decisions Your Council Never Voted On

Public meetings are the visible part of local democracy. They are filmed, minuted and occasionally crowded. But a great deal of council business is concluded without a show of hands: an officer signs a decision notice, a cabinet member approves a portfolio action, or an urgent procedure is invoked to bypass the usual timetable. These decisions can be lawful, necessary and efficient. They can also be difficult to see. For residents, the question is not whether delegation exists — it does, and it must — but whether the record of each decision is complete enough to be tested.

The Architecture of Delegation

Every council operates under a constitution. Within it sits a scheme of delegation: the document that sets out which powers belong to full council, which to the executive, which to committees, and which to named officers or portfolio holders. Executive arrangements in England commonly allow cabinet members or individual portfolio holders to take decisions within an agreed budget and policy framework. Officers may hold delegated authority for operational matters, contracts, licences and routine approvals.

The scheme usually distinguishes between key decisions and others. A key decision often means one with significant financial consequences or substantial effects on a ward or community. Councils must publish forward plans or notices of key decisions, giving advance warning of what is coming. The existence of a forward plan is a useful accountability tool: it allows residents to see a decision before it is taken, not only after the paperwork has been signed.

Urgency procedures are the exception. They exist so that councils can act when delay would harm services or finances. But urgency should be exceptional, recorded and explained. The record should say why the normal timetable could not be followed and what consultation, however brief, took place.

Where the Paper Trail Begins

The first stop is the council's constitution and scheme of delegation. These are often buried in a governance section of the website, but they are the rulebook against which any decision can be measured. The second stop is the forward plan or notice of key decisions. The third is the delegated decision record — sometimes called a decision register, officer decision log or executive decision notice.

Councils vary in how they publish these records. Some provide a searchable register with fields for the decision-maker, date, power exercised, reasons, financial implications and call-in arrangements. Others publish PDFs with little standardisation. Urgency notices may appear separately. Committee reports can also reveal decisions that were later formalised by an officer or portfolio holder.

A useful habit is to check publication dates. Access-to-information rules generally require key decisions and certain executive decisions to be published within a set period. A decision that appears months after it was taken, or not at all, is worth questioning. The record may still be lawful, but the gap between action and publication is part of the accountability picture.

Reading a Decision Record

When you find a decision notice, read it as an auditor would. Identify the decision-maker and the date. Identify the power being used — not the general service area, but the specific delegation in the constitution. Look for the reasons: what evidence, advice or consultation supported the choice? Check whether legal, financial and equality implications were recorded. Look for any declared conflict of interest.

Then compare the record with the scheme of delegation. Does the officer or portfolio holder actually hold that power? Is the decision above the financial threshold that would require a cabinet or full council decision? If the decision is described as urgent, does the notice explain the urgency in concrete terms, or does it merely assert it? If call-in applies, when does the call-in period end, and has the decision been published in time for scrutiny to be meaningful?

Four Tests for the Paperwork

A resident does not need legal training to ask structured questions. Four tests can expose most weaknesses in a delegated decision record.

First, the authority test: does the constitution permit this person to take this decision? Second, the procedure test: was the decision on the forward plan, was consultation carried out as required, and was the record published on time? Third, the urgency test: if normal procedures were bypassed, was the reason genuine and documented? Fourth, the scrutiny test: could councillors or residents have challenged the decision before it took effect, and was the call-in route open?

If the answer to any of these is unclear, ask. A written request to the council's monitoring officer or the relevant scrutiny committee can be enough to prompt a correction or an explanation. Where records are missing, a Freedom of Information request can be used to ask for the decision notice, the delegation relied upon, and any advice recorded. The Local Government Ombudsman can consider complaints about maladministration, though not the merits of a decision itself.

A Resident's Audit Trail

Start with a single decision that affects your street or service. Locate the record. Save a copy. Compare it with the scheme of delegation and the forward plan. Check the consultation and equality evidence. Check the call-in window. Then write to the council with specific questions: which delegation was used, when was the decision published, what advice was recorded, and what opportunity existed for scrutiny?

This is not an exercise in suspicion. It is an exercise in representation. Delegated decisions are part of the machinery that turns budgets and policy into real effects. When the paperwork is clear, residents can see who decided and why. When it is not, the invisible meeting becomes a closed door. Better representation depends on keeping that door open — not only in the chamber, but in every decision record that follows.