The Stopwatch Contract: How to Audit Urgent Council Spending Before It Hardens Into Fact

Urgency is not a blank cheque. It is a legal and administrative route that councils can use when delay would cause genuine harm or lost service. The problem is not that emergency powers exist. The problem is that they are often exercised in the dark, recorded in scattered documents, and reviewed long after the money has gone. For campaigners, the waiver log is one of the most revealing documents a council holds. It is a diary of decisions taken quickly, often with limited competition, and frequently with little public explanation beyond the word urgent.

Start with the right asks

Do not begin with a broad request for everything. Build a precise Freedom of Information request under the Freedom of Information Act 2000 and send it to procurement, finance, legal services and democratic services. Ask for the council’s procurement waiver register or contract exception log for the current and previous financial years. Ask separately for emergency procurement authorisations, single-tender action reports, retrospective contract approvals, and delegated decision notices citing urgency or emergency powers. Specify the fields you need: date of waiver, department, supplier, contract value, duration, reason given, approver, procurement route used, contract reference number, and whether the decision was reported to a committee.

If the council says no such log exists, treat that as a finding. A council spending public money through exceptions should be able to list them. Ask whether waivers are recorded in individual decision notices instead. Ask for the constitution and procurement rules that set out who may approve an exception, at what value, and with what publication requirement. Those rules are the yardstick against which every entry should be measured.

Build the ledger before you build the argument

A waiver ledger is not a scandal file. It is a control document. Create a spreadsheet with one row per waiver and columns for the information above. Add a second tab for the contract register, a third for spending data over £500, and a fourth for committee reports and delegated decisions. Give every entry a unique reference so you can trace a waiver from approval to contract to payment.

Cross-referencing is where the patterns appear. A supplier that appears repeatedly in the waiver log but rarely in open tenders deserves a question. A department with a cluster of urgent awards in the last weeks of a financial year deserves a question. A value that sits just below a threshold requiring cabinet approval deserves a question. So does an emergency waiver that is renewed three times without a retrospective report. None of these are proof of wrongdoing on their own. Together they are evidence that the council’s procurement controls are being stretched, bypassed or simply not documented.

Read the pattern, not the excuse

Councils often explain waivers with phrases such as operational necessity, supplier continuity or statutory deadline. Some of those explanations will be true. Your task is to test whether the same explanation is being used repeatedly without evidence. Check whether the waiver records the specific risk of delay, the alternatives considered, the price reasonableness check, and the senior officer or member who approved it. Check whether the contract was subsequently advertised or extended. Check whether the waiver was reported to the audit committee, scrutiny committee or full council.

Pay attention to repeat suppliers. A single emergency award may be unlucky. A pattern of emergency awards to the same company, approved by the same officer, in the same service area, is a governance question. Pay attention to missing contract references. If a waiver cannot be matched to a contract in the register, ask how the council is monitoring performance, cost and exit. Pay attention to retrospective approvals. A decision taken first and authorised later is not necessarily unlawful, but it should be exceptional, recorded and explained.

Put the scrutiny machinery to work

Your ledger should be tested against the council’s own rules. Read the constitution, the financial regulations and the procurement strategy. Identify the threshold at which a waiver needs director, monitoring officer or cabinet approval. Identify what must be published and when. Then compare the rule with the record. Where the record is silent, ask for the missing decision notice. Where the decision notice is vague, ask for the officer’s written justification. Where the justification is commercial confidentiality, ask for the public interest test and a redacted summary.

Use the formal routes. Submit a question to the next scrutiny committee. Ask the audit committee to review the waiver log as part of its risk and governance work. Write to the section 151 officer and the monitoring officer. Ask the cabinet member responsible for procurement to publish a quarterly waiver report. These are not performative gestures. They create a paper trail and force a response that can itself be audited.

Turn the ledger into a public dossier

A good dossier is short, evidenced and hard to dismiss. Begin with a one-page summary of what you asked for, what you received, and what the pattern shows. Follow with an evidence table: waiver date, supplier, value, reason, approver, contract reference, committee scrutiny and your question. Add a chronology showing clusters of urgent spending around year-end, contract renewals or budget-setting. End with a small number of precise questions addressed to named officers and members.

Publish the dossier on a public page and send it to your local scrutiny members, audit committee chair, MP and local press. Do not overclaim. Say clearly what the evidence shows and what it does not show. The aim is not to prove a conspiracy. The aim is to make the routine use of emergency powers visible, comparable and contestable. As the 2026/27 budget year closes and the next settles, every waiver is a small decision about who gets paid, which services continue, and how much scrutiny the public is allowed to see. A ledger is a modest tool. Used well, it is also a lever.