Budgets are the least glamorous documents in local government and often the most revealing. A council can hold a press conference about transparency while the numbers in the annex quietly show a department funded in one undifferentiated lump, a contract that nearly doubled after award, or a vendor whose registered address is a house belonging to somebody’s cousin. The skill is knowing which patterns deserve a second look.

What follows is a working checklist: ten flags that auditors, finance staff and experienced reporters treat as invitations to dig. None of them proves wrongdoing. Each one is a reason to request a document, make a call, or ask a question on the record and write down the answer.

Get your comparison right before you read a single number

A budget on its own says very little. One year’s figure for road maintenance tells you nothing until you set it against last year’s figure, the year before that, and — most importantly — what was actually spent.

So build the baseline first. Ask for the current budget book, the previous two, and the audited financial statements or year-end reports that show real spending against plan. Those year-end documents are where optimistic projections go to die, and where you will often find a project that was funded but never started, or a department that overspent by a margin nobody mentioned in public session.

Check too whether the format has changed. Councils sometimes reorganise departments between years, which can make a cut look like a rise. Ask the finance office for a mapping between the old structure and the new one. If they cannot supply it, that is already a useful question.

The ten red flags

1. Vague line items. “Professional services,” “miscellaneous,” “other operating costs,” “contingency” — with six figures attached and no breakdown. A single catch-all line should always prompt a request for the supporting schedule. Sometimes the answer is boring. Sometimes it is a consultancy nobody tendered.
2. Lump sums instead of unit costs. A department funded as one block, with no split between staff, vehicles, fuel and supplies, is nearly impossible to audit from outside. Compare with how peer departments are presented in the same document. Inconsistent presentation is a flag in itself.
3. One line item growing much faster than everything around it. Departmental budgets tend to move together, within a few percent. When a single programme, vehicle fleet or “communications” line jumps while the rest stays flat, ask who signed off and what changed.
4. Optimistic revenue. A grant counted as income before it has been awarded. Property tax revenue assuming development that has not broken ground. Fees projected to rise sharply with no change to the fee schedule. If the revenue does not arrive, something else gets cut later — and that is a story.
5. Quiet mid-year amendments. Transfers between departments, supplementary budgets tabled late in a meeting, adjustments buried in a consent agenda. Pay particular attention to the final months of the fiscal year, when unspent money has a habit of being spent quickly to protect next year’s allocation.
6. Contracts amended upward after award. A tender of one size that becomes another. Look at the cumulative value of change orders against the original contract price, and at how often the same supplier benefits. Repeated “scope changes” are worth a document request and a phone call.
7. Split contracts. Three separate jobs for the same supplier, each just under the threshold that would trigger competitive bidding, can add up to one contract that should have been tendered. Add the numbers. The arithmetic is your evidence.
8. Recurring sole-source awards. Emergency procurement is legitimate and sometimes genuinely urgent. The same department declaring emergencies, or writing thin justifications that say “specialised expertise” without naming it, is a pattern worth documenting across several years.
9. Overlapping footprints between vendors and officials. A company registered weeks before winning its first municipal contract. A supplier sharing an address with a council employee’s business. A former official now advising a firm that bids for the same services. Verify these carefully through public registries before you write a word.
10. Process shortcuts. The budget published days before the vote. A revision posted after the meeting without notice. Public comment cut to two minutes. Minutes that record decisions but not discussion. Procedural flags are often the easiest to prove and the hardest for an institution to explain.

Reading a budget in an afternoon

You do not need an accounting qualification to do useful work here. You need patience and a highlighter.

• Print the summary tables. Read the narrative sections of the budget document — the mayor’s letter, the department introductions — and mark every promise that has a number attached.
• Trace three or four large numbers back to their detail pages. If you cannot get from the summary to the detail, note where the trail stops.
• Compare this year to last year line by line, in a spreadsheet, with the difference expressed as a percentage. Sort by size of change.
• Read the capital plan separately from the operating budget. Projects can be funded in one and delivered by the other, and the timing is where overruns hide.
• Keep a running list of questions in the order you would ask them, most basic first. Ask the ones you can answer from public documents before you call anybody.

Turning a flag into a story

A flag is a hypothesis. Before it becomes a paragraph, do three things: get the underlying documents, understand the technical reason the number looks the way it does, and give the people involved a real chance to explain.

That order matters. Ask the finance office to walk you through how a line item is constructed; more often than you would expect, the explanation is mundane and the story dies. When it does not die, you will understand the mechanism well enough to describe it plainly, which is what separates a report from an insinuation.

Then put the specific findings to the council, the department and, where relevant, the supplier — in writing, with enough time to respond and enough detail that the reply is meaningful. Quote the response fairly, including the parts that weaken your thesis. If a story turns on a technical accounting or legal question, run it past someone who does this work professionally before publishing; good reporting is not a substitute for specialist advice, and a second pair of eyes has saved many careers.

Questions to keep in your notebook

Ten flags are not a scandal. They are a map of where to look. Carry a short list of questions into every budget meeting and you will rarely come away empty-handed.

• What exactly is in this line, and can I see the schedule behind it?
• What did we budget last year, and what did we actually spend?
• Who approved this change, when, and in which meeting?
• Which suppliers benefited, and how were they chosen?
• What would have to be true for this revenue figure to arrive?
• What is not in this document that used to be?

Ask them in public, ask them in writing, and publish the answers alongside the questions. That habit, repeated across a few budget cycles, is how local accountability gets built — one dull annex at a time.

Photo: stevepb / Pixabay