Vol. 006: The Process Tax Receipt

Current Conditions

Impact fees get the attention. They’re disclosed upfront, they appear on settlement statements, and they’re easy to point to as a line item. But impact fees are predictable, and predictability has a different risk profile than uncertainty.

The harder cost to quantify is the discretionary approval process itself. Not the fees. The time. The conditions. The continuances. The neighborhood meetings. The revised site plans. The reduced density and the affordable set-asides offered in exchange for a yes vote. Each of those has a dollar value. Stacked together, they constitute a tax that never appears on a fee schedule.

We analyzed discretionary approval mentions across municipal political meeting records in five Triangle jurisdictions: Raleigh, Apex, Garner, Wake Forest, and Morrisville. The volume of discretionary discussion in the public record is a measurable proxy for process intensity. The cost math behind those discussions is straightforward arithmetic.

Signals Observed

Signal 1: The mention counts measure what you’d otherwise have to estimate.

Raleigh’s political meeting records contain 2,476 discretionary approval mentions, 1,916 of them specifically related to rezoning. Apex: 1,357 total, 941 rezoning. Garner: 1,093 total, 672 special use permits. Wake Forest: 829. Morrisville: 756.

These counts aren’t a ranking of difficulty, a single application generates multiple mentions across multiple meetings. But the volume reflects the institutional surface area that a discretionary approval must navigate. More mentions means more meetings, more staff reports, more public testimony, more conditions. That surface area has a carrying cost.

Signal 2: The time-cost math is not ambiguous.

By-right approval in jurisdictions that offer it: 1-4 weeks. Mid-range discretionary review: 6-12 months. Full discretionary review for multifamily in constrained jurisdictions: 24-33 months.

Construction carrying costs run approximately $4,400 per month. Land carrying costs run approximately $11,500 per month. The difference between a 3-month and a 24-month entitlement process: $50,000 to $240,000 per project in carrying costs alone. before conditions, concessions, or redesigns. That cost doesn’t disappear. It moves to the buyer.

Signal 3: The code-level burden is not uniform.

Oak Hill, Tennessee: 83% of residential uses require discretionary approval before they can be built. Morrisville, NC: 2%. That difference is not a zoning philosophy, it’s a cost structure. A developer entering Oak Hill is paying the discretionary tax on nearly every residential product. A developer entering Morrisville is largely operating on a fee schedule they can model.

The code-level discretionary burden is observable before any application is filed. It’s in the zoning ordinance, in the permitted use tables, in the conditional and special use designations. It’s also rarely analyzed as a cost input during site selection.

Signal 4: The give-to-get concession stack has a price.

Discretionary approvals in high-process jurisdictions typically require applicants to negotiate their way to a yes. Common concessions: affordable set-asides (2-10% of units at restricted rents), design modifications (reduced heights, added buffers, materials upgrades), infrastructure contributions (turn lanes, utility oversizing, traffic signal timing), traffic mitigation, and density reductions. Each concession is a real cost. Affordable set-asides reduce revenue per unit. Buffers reduce buildable area. Infrastructure contributions are off-balance-sheet until they show up in a conditions letter.

A rezoning that appears viable at initial proforma often looks different after conditions are negotiated. The $138,000 in process costs on a $466,000 home isn’t a single fee, it’s an accumulation of negotiated concessions that individually seem reasonable and collectively reshape the project economics.

Forecast

Jurisdictions with high discretionary process intensity will continue to produce fewer units than their demand environment warrants, not because the political will to build is absent, but because the approval structure itself limits throughput. Projects that are viable in Morrisville’s code environment are not viable in Oak Hill’s, even if the underlying demand is identical.

The municipalities with the highest discretionary mention counts (Raleigh, Apex, Garner) are also the ones where developers are most likely to underestimate timeline and condition risk. The process is not opaque; it’s just rarely modeled as a cost center before the application is filed.

Jurisdictions that simplify their approval structures (by expanding by-right permissions, reducing conditional use requirements, or establishing administrative approval pathways for qualifying projects) will see project economics improve before fee schedules change at all. The fee is visible. The process is where the real money is.

Watch Items

• NC HB 765. The bill would have mandated density minimums and 90-day auto-approval for qualifying projects. It didn’t pass cleanly, but the diagnostic it reflects is accurate: the state is watching how long local discretionary processes take. A version of this legislation will return.
• Raleigh UDO updates. Any revision to Raleigh’s conditional and special use structure changes the math for every application in the pipeline. Watch for staff-initiated code amendments following development review backlogs.
• Morrisville as a comparison point. Morrisville’s by-right-dominant code (2% discretionary burden) will continue to attract applications that leave neighboring jurisdictions. If its approval times and conditions remain favorable, expect it to serve as a policy reference in state-level reform discussions.
• Staff capacity at planning departments. Discretionary review timelines are partly a function of staffing. Vacancies at planning departments extend review periods independent of code structure. Monitor department hiring announcements as a leading indicator of timeline compression or expansion.

Confidence Level

Medium-High. The mention count methodology is consistent and replicable across jurisdictions. The time-cost math is based on industry-standard carrying cost assumptions applied to documented approval timelines. The Oak Hill / Morrisville comparison is a genuine code-level observation. The $138K receipt figure represents a reconstructed estimate, not a single transaction, the underlying components are documented but the aggregate carries approximation risk.

Aside: “Special use permit” appears in Garner’s meeting records 672 times. The phrase “by right” appears 14 times. That ratio is not a policy document, but it is a data point.

Why This Matters

Developers model impact fees at the beginning of a deal. They model carrying costs with a schedule assumption. What they rarely model is the expected cost of discretionary conditions, because those conditions aren’t knowable until the negotiation happens. The public meeting record changes that: the discretionary mention counts, the approval timelines, the pattern of conditions negotiated in comparable applications. all of it is in the record before the application is filed. The process tax isn’t invisible. It’s just not where most teams look.