One Signature, No Meeting: What Council Urgency Logs Conceal in Plain Sight

At 4.12pm on a Friday in September, a metropolitan borough published a notice on its website confirming a contract award worth £3.1m. The decision had been taken that afternoon by a single executive director under delegated authority. No committee had seen the papers. No public meeting had been held. The published notice ran to 140 words. It was lawful, and it was almost entirely unrevealing.

The notice is the kind of document that local government calls an urgency notice, an emergency decision record or a special urgency notification. It exists because councils sometimes cannot wait for the normal cycle of cabinet reports, scrutiny committees and forward plans. A flooded leisure centre, a failed care contract or a software system on the point of collapse may genuinely require a decision within hours. The question for anyone interested in scrutiny is not whether such powers should exist. It is how they are used, how often, by whom, and what the published record leaves out.

The legal shortcut, and its intended safeguards

In England and Wales, the executive decision-making regulations allow councils to depart from the usual 28 clear days' notice for key decisions in two main ways. The first is often called the general exception: compliance with the notice requirements is impracticable, and the chair of the relevant scrutiny committee agrees that the decision should proceed. The second is special urgency: the decision cannot reasonably be deferred, and the scrutiny chair again agrees.

The safeguards are supposed to be procedural rather than substantive. A notice must be published. It must state why the normal rules are being bypassed. It must identify the decision-maker. In many authorities, the constitution also requires the decision to be reported retrospectively to the next available scrutiny meeting. In Scotland the statutory architecture differs, but the underlying tension is familiar: urgent executive action versus the slower work of public accountability.

The weakness sits in the gap between those requirements and the evidence needed to test them. A notice can satisfy the law while telling the reader almost nothing about why urgency was real, what alternatives were considered, or who advised whom.

What the log actually records

Across the urgency and delegated decision pages of a sample of English and Welsh councils reviewed by The Ferret, the same patterns recur. Many notices are short. A title, a date, a decision-maker, a paragraph of reasons and a reference number are common. Some are more forthcoming. A minority attach a business case, a risk assessment or a financial appraisal. Fewer still publish the original request for urgency, the legal advice or the equalities assessment.

The published reason is often a phrase rather than an explanation. Commercial urgency, operational necessity, supplier failure, statutory deadline, health and safety. Each may be true. Each is also elastic. A notice that says a decision cannot wait because of a contractual deadline does not show whether the deadline was known months earlier, whether a waiver was sought, or whether the contract should have been procured differently in the first place.

The identity of the signatory matters. Some notices are signed by a cabinet member, some by a chief executive or executive director, some by a section 151 officer or monitoring officer. The constitution usually sets out who may exercise which delegated power, but the published notice rarely shows the chain of advice. Did the monitoring officer see it? Did the finance director sign off the funding? Did the scrutiny chair agree before or after the decision was taken? The log often records that a chair was consulted without saying when, or on what information.

A register in name only

Comparing councils is harder than it should be. There is no single statutory register of urgency decisions in the form that a reader could search across authorities. Some councils publish a running table. Others upload individual PDFs with titles that vary between departments. Some notices sit under committee papers, others under freedom of information pages, others under a heading that has changed name twice since 2020.

That fragmentation has a practical consequence. A resident cannot easily ask how many urgency decisions their council took last year, what they cost, or whether the same director signed most of them. A scrutiny committee cannot benchmark its authority against neighbours without manual work. A journalist cannot test a pattern without spending days assembling a dataset that should already exist.

The absence of a cumulative view also makes it difficult to assess what might be called urgency creep. One emergency decision in a year is a sign of a functioning council responding to events. Dozens can be a sign that the normal machinery is being routed around. Year-end spending, contract extensions, IT renewals and building repairs are recurrent subjects in urgency logs. That does not make them improper. It does make them worth counting.

The documents that never travel with the signature

When The Ferret asked councils for the papers behind a selection of urgency notices, the most common missing items were the ones that would allow an outsider to test the judgment. The request for urgency. The options appraisal. The procurement route and any waiver. The equality impact assessment. The record of consultation with the scrutiny chair. The conflict of interest declarations of those involved. The retrospective report that may or may not have reached a committee.

Some authorities publish a proforma that captures much of this. It lists the decision, the reason for urgency, the alternatives considered, the consultation undertaken, the financial and legal implications, the equality considerations and the date the scrutiny chair agreed. Where that exists, the log becomes a usable accountability document rather than a receipt. It is not the norm.

Why the gaps matter

Emergency powers are not a scandal in themselves. They are a necessary part of running a large organisation. The concern is that the published record of their use is often too thin to distinguish between a genuine crisis and a decision that was simply inconvenient to route through scrutiny. Both can produce a compliant notice. Only one is what the regulations were designed for.

For residents, the practical effect is that some of the most consequential decisions a council makes, including large contracts and service changes, can appear online with less explanation than a planning application. For scrutiny councillors, the retrospective report can arrive months later, after the money is committed. For auditors, the notice is rarely the document that reveals whether value was secured.

Questions worth asking of your own council

How many urgency notices did it publish in the past financial year? How many were signed by officers rather than elected members? In how many cases did the scrutiny chair agree before the decision, and is that agreement published? Does the council publish the original request for urgency, the options considered and the equality assessment? Does it report every urgency decision to scrutiny, and does it record what the committee did with it?

The answers will vary. The fact that they have to be asked one council at a time is itself part of the story. A decision taken in an afternoon may be unavoidable. A decision recorded in a way that cannot be scrutinised afterwards is a choice.