City Revenue Projection: How to Do It Right

Property tax: your most predictable line

Property tax is the anchor of most city revenue forecasts because it is grounded in a defined, assessable base. Your projection starts with assessed valuation, multiplied by the tax rate, adjusted for collection rate, and then modified for any new development or reassessment activity expected in the fiscal year. The stability is real, but it comes with a lag: assessment cycles often lag market conditions by a year or more, which means property tax revenue can look healthy even as the local economy cools. Account for that lag when your economic outlook starts to shift.

New development adds to the taxable base, but it does so on a timeline that requires coordination with your assessor's office. Track building permits as a leading indicator, and don't credit new-development revenue until the properties are on the roll.

Sales tax and transaction-based revenues

Sales tax is the most economically sensitive line in a typical general fund projection. Its performance tracks consumer spending, local employment, and retail activity, which means it responds quickly to recessions and recoveries alike. When you build your sales tax forecast, tie your growth assumptions explicitly to local and regional economic indicators, using a sound tax revenue projection methodology, rather than averaging recent collections and calling it done.

Utility users tax and business license fees belong in the same general category: revenues tied to activity volume rather than asset valuation. Both require separate treatment from property tax because their trajectory follows economic cycles more closely, and a single growth rate applied across all revenue sources will misstate the risk profile of your forecast.

Intergovernmental revenues, fees, and permits

Grants, state shared revenues, and permit fees require a different approach because they carry policy risk and timing uncertainty that stable revenues don't. State aid can be adjusted mid-year. Competitive grants may not renew. Building permit volumes can collapse when interest rates spike. Project these lines conservatively and flag them separately in any council presentation so elected officials understand which revenues are reliable and which carry contingency risk.

Building permits are worth noting again as a leading indicator. A slowdown in permit activity today signals slower property tax growth over a multi-year horizon, since a meaningful lag commonly elapses before permit changes flow through to the valuation roll. Tracking that relationship gives your long-range forecast a diagnostic layer that pure trend analysis misses.

Using historical collections as your starting point

Three to five years of actual revenue history is your baseline foundation. The goal is to establish a clean trend by removing anomalies before you calculate any growth rate. One-time grants, pandemic-era relief funds, and years with major policy changes, rate increases, new fees, all distort the trend line if you leave them in. Identify and remove them first, document why, and then build your baseline from the adjusted series.

Trend analysis works well for stable revenues like property tax when economic conditions are consistent. It breaks down when conditions shift, which is exactly why it can't be your only method. When the environment changes, supplement trend analysis with econometric inputs or external economic anchors to avoid missing the inflection point until after it has already occurred.

Layering in economic indicators

Different revenue categories respond to different economic signals. Sales tax tracks wages, employment, and consumer spending. Property tax is influenced by housing market activity, home prices, and broader local economic conditions. Transaction-based revenues follow business activity and population trends. Match your indicator to your revenue source rather than applying a single regional growth rate across all lines.

Small and mid-sized cities typically don't build proprietary econometric models. The practical approach is to use state or regional economic forecasts from sources like Moody's Analytics or your state's revenue estimating conference as external anchors, then apply those assumptions to your city's revenue structure. Seattle's Office of Economic and Revenue Forecasts does exactly this, publishing three forecasts annually, in spring, summer, and fall, that use S&P Global Market Intelligence and Moody's Analytics scenarios to drive its city revenue outlook across baseline, downside, and stress cases.

Documenting your assumptions explicitly

Every growth rate, collection assumption, and economic input used in your city revenue projection should be written down in plain language, not embedded invisibly in a formula. Finance teams that document their sources produce projections that are far easier to explain and audit when actuals diverge from expectations. An assumption note that reads "2.8% sales tax growth based on state median wage growth forecast, Q1 2026" is defensible. A formula cell that returns 2.8% with no source is not. Consistent with GFOA best practices for revenue forecasting, outlined in the association's guidance on fiscal policy and budgeting, this revenue forecasting methodology is a standard worth holding to whether you're presenting to a council of five or a board of commissioners.

Trend analysis: best for stable, predictable revenues

Trend analysis is the simplest and most transparent method available to a city finance team. It extends historical patterns forward using time-series data and works well for revenues with long, consistent histories like property tax. Its core limitation is that it assumes the future resembles the past. During recessions, structural shifts in the local economy, or periods of rapid development change, trend analysis fails to capture the inflection point until it has already happened. In those conditions, supplement it with econometric inputs or scenario-based adjustments rather than relying on the trend line alone.

Scenario planning: the method that serves councils best

Scenario planning replaces a single fragile number with a range of defensible outcomes, and that makes it a useful method for presenting uncertainty to elected officials. A baseline, a downside, and a stress scenario give decision-makers a realistic picture of risk without requiring them to understand the mechanics of the underlying model. Seattle publishes three revenue scenarios tied to macroeconomic forecasts from S&P Global and Moody's. Its fall forecast presentations quantify the difference between scenarios in dollar terms, showing council members, for example, that a pessimistic case could reduce general fund revenue by roughly $33.5 million over two years compared to baseline. That kind of specificity transforms a projection from a procedural exercise into a genuine decision tool.

Scenario planning does not predict the future. It prepares the organization for multiple versions of it, and that distinction matters when you're sitting across a table from elected officials who want to know what happens if things go wrong.

Step 1: Gather and clean your historical revenue data

Start with five years of actual collections by revenue category, reconciled to your audited financials. Remove one-time items and flag years with policy changes that would distort a growth rate calculation if left in the trend line. The cleaner your baseline, the more defensible your growth assumptions become.

Step 2: Categorize revenues by volatility and forecasting method

Separate your revenue lines into three groups: stable revenues like property tax and certain fees; cyclical revenues like sales tax and permits; and policy-dependent revenues like grants and intergovernmental allocations. Each group warrants a different forecasting method and a different level of conservatism in your assumptions. Blending them into a single forecast without distinguishing their risk profiles is one of the most common structural errors in local government forecasting.

Step 4: Validate your projection against recent actuals

Before presenting, compare your projection against year-to-date collections and any mid-year revision your state or regional economic conference has published. A fiscal year revenue estimate that ignores recent divergence from trend is harder to defend than one that acknowledges it and explains it. Adjust where the data warrants it, document the reasoning, and you'll enter the council presentation on firmer ground.

Lead with your assumptions, not your numbers

Council members and commissioners are more likely to trust a projection when the finance director explains the logic before citing figures. Open your presentation with your key assumptions, the economic indicators you used, and the range of outcomes your scenarios cover. This signals rigor and invites better questions. It also shifts the conversation from "is this number right?" to "do these assumptions make sense?", which is a far more productive place for a council to engage.

Connect revenue projections to spending implications

A fiscal year revenue estimate that floats disconnected from spending is hard for non-finance officials to interpret. Tie your projection to reserve runway, fund balance policy floors, and any capital or debt decisions on the horizon. When council members see that a downside scenario would push reserves below the city's six-month policy floor, the projection becomes a decision tool rather than a line item on a budget template. That connection is where a city revenue projection earns its place in the room.

Building only one projection line

A single-point municipal revenue forecast signals false certainty. When actuals miss even slightly, the projection loses credibility and so does the finance team. Scenario modeling protects against this by setting honest expectations upfront. Actuals will commonly diverge from projections. The question is whether you've shown that you planned for it.

Optimism bias in growth rate assumptions

Many local government revenue estimates trend optimistic because finance teams face pressure to close budget gaps on paper. An over-optimistic city budget projection creates structural deficits when actuals arrive and leaves elected officials with fewer options mid-year. Use documented external benchmarks for your growth assumptions rather than internal targets. If the state forecasts 2.1% wage growth and you're projecting 4.5% sales tax growth, you need to explain the gap explicitly or revisit the assumption.

Leaving assumptions undocumented or buried in formulas

If a budget analyst leaves the organization and nobody can explain why the sales tax growth rate is 3.1%, the projection becomes a liability rather than a resource. Every assumption should live in a written record separate from the model mechanics. This is both a GFOA best practice and a practical necessity for any finance team that presents its work to rotating elected officials who weren't in the room when the projection was built.

A structured argument, not just a number

A well-built city revenue projection is a structured argument. It explains which revenues you are modeling, what assumptions drive each line, and what the realistic range of outcomes looks like for the fiscal year ahead. That argument, when presented clearly, gives elected officials the context they need to make better decisions about spending, reserves, and long-term obligations.