How to Read a City Budget Without Getting Lost

Start with four different questions

A budget is not the same thing as spending. To understand a city program, separate four questions: What did leaders propose? What did the governing body appropriate? What was actually obligated or spent? What result did residents receive? A headline that compares only the first and last numbers can be misleading because appropriations can change, projects can span fiscal years, and some money may be restricted to a particular purpose.

The useful unit of analysis is a traceable chain. Keep the adopted budget, amendments or transfers, expenditure records, contracts or project records, and performance measures together. If one link is unavailable, mark it unavailable rather than treating the gap as proof of waste.

Follow the money in order

Begin with the adopted budget and identify the department, fund, program, capital project, and fiscal year. Then look for amendments, supplemental appropriations, transfers, encumbrances, purchase orders, contracts, and actual expenditures. The terminology varies by jurisdiction, but the principle is stable: distinguish authority to spend from money that actually left the government.

If $13 million was appropriated for roads and only $9 million appears in expenditure records, the $4 million difference is a question—not yet a conclusion. It may represent an unfinished project, an encumbrance, a transfer, a grant timing issue, a canceled contract, or incomplete data.

Treat transfers as first-class evidence

Transfers matter because they can explain why the final spending pattern differs from the original plan. When records show money moved from one purpose to another, capture the amount, date, receiving purpose, authorizing document, vote or official, and stated reason. That creates accountability without guessing at motive.

A material transfer can deserve attention even when it was lawful. Residents may reasonably want to know why an infrastructure priority lost funding, what replaced it, and what consequence followed. The factual question is who had authority, what they approved, and what the records say—not which political label to attach to them.

Connect spending to results

A clean ledger is not the finish line. Spending should be connected to outputs and outcomes where comparable evidence exists. For roads, that might include lane-miles resurfaced, pavement condition, project completion, crashes, congestion, or maintenance backlog. For public safety, it might include response times, staffing, case workload, or other published service measures.

Do not force causation. A metric improving after spending increased does not prove the spending caused the improvement. A useful report states the sequence, shows the measurements, and identifies what additional evidence would be needed to make a stronger claim.

A repeatable CityScope-style checklist

For any major city expenditure, build the same evidence chain so different departments and jurisdictions can be evaluated consistently.

• Identify the adopted budget and fiscal period.
• Find appropriations, amendments, and transfers.
• Trace obligations, vendors, contracts, projects, and actual expenditures.
• Attach the stated reason for material changes when an official record provides one.
• Compare spending with measurable service or project outcomes.
• Name the responsible authority only when the record supports it.
• Label missing evidence as unavailable rather than zero or wrongdoing.