The Hidden "Price of a Permit"

Imagine buying a car but being told you won't be allowed to drive it for four years. During that time, you still pay the loan, insurance, and taxes while the car sits idle. That sounds absurd. But in housing development, something very similar happens all the time.
A February 2026 study by economists Evan Soltas and Jonathan Gruber examined what developers call the "price of a permit" in Los Angeles by studying the market for land with preapproved permits. The research struck a nerve, garnering over 134,000 views on X. They found developers pay roughly 50% more, about $48 per square foot, for land that already has Ready-to-Issue (RTI) permits.
In other words, the same parcel of land becomes dramatically more valuable simply because the permitting process is already complete. That premium reveals something crucial about housing constraints: it's not just the formal rules on the books. It's the de-facto regulatory burdens, the years of delay, the compounding costs, and the paralyzing uncertainty that comes with waiting. It's the cost of sitting idle while carrying the full weight of ownership. The permit itself is worth tens of millions of dollars, not because of what it costs to obtain, but because of what it costs not to have it.
The Regulatory Thicket
Modern buildings must comply with a dense network of safety, accessibility, and environmental rules. These requirements come from multiple sources, including international building codes, state environmental mandates, and local accessibility standards.
Individually, these rules are critical for public safety. Collectively, however, they create what many architects and developers experience as a regulatory thicket. The cost of navigating that thicket shows up in two ways: compliance work and pure wait.
1. Compliance Work
A typical mid-size multifamily project can generate thousands of pages of drawings and specifications. Each sheet contains thousands of data points that must align with hundreds of code requirements. Small inconsistencies trigger "plan-check corrections," adding review cycles and delays.
For example, in one project we analyzed, a correction came down to a seemingly minor issue. The corridor served an occupant load exceeding 50 persons and was shown as 42 inches wide. The calculated egress width for a sprinklered building using the egress component factor is 50 occupants × 0.15 inches per occupant = 7.5 inches (IBC 2024 Section 1005.3.2). Even though the calculated width is less than 44 inches, the IBC requires a minimum corridor width of 44 inches when the corridor serves an occupant load greater than 50 persons (IBC 2024 Section 1020.3). Therefore the floor plan, life safety plan, and related door schedule were revised prior to resubmission to provide the required 44 inch corridor width.
2. The "Pure Wait"
Even after drawings are submitted, projects spend months in plan check while city departments verify compliance. During this period, construction hasn't started, but the developer continues paying interest on land loans, property taxes, and consultant fees.
As Soltas and Gruber point out, this "pure wait" is responsible for roughly half of that 50% permit premium. It is essentially a "time tax" that adds no physical value to the building but significantly increases the cost for the eventual resident. For large projects, these carrying costs can reach millions of dollars before a shovel ever hits the ground. Research from NAHB confirms that permitting roadblocks are a major driver of rising housing costs.
Why Software Has Struggled Here
Why hasn't software solved this already? Because compliance sits at the intersection of three historically difficult domains:
- Drawings: Plans combine geometry, symbols, and conventions across hundreds of sheets.
- Codes: Regulations are written as legal text for human interpretation; not necessarily for machine execution.
- Local Variation: Cities frequently apply their own specific interpretations of national codes.
Until recently, software couldn't connect these layers reliably.
A New Kind of Tool
Recent advances in AI are changing what's possible. At Archidian, we've been building tools that help architects and city reviewers navigate compliance earlier and more predictably.
The goal isn't to replace human expertise; it's to reduce avoidable correction cycles. For architects, AI can analyze plan sets before submission to flag egress path lengths, ADA clearance conflicts, or missing documentation. In early pilots, our AI flagged these issues before submission, accelerating the review process and eliminating costly back-and-forth cycles that slow projects down.
For city reviewers, similar tools can automate repetitive checks like verifying dimensions and identifying conflicts. This enables reviewers to focus their limited time on higher-level safety decisions and complex engineering challenges.
Making Permitting More Predictable
The biggest cost in permitting isn't the regulations themselves. It's the uncertainty. When developers don't know if approvals will take six months or two years, that risk is baked into the cost of housing.
Technology can't eliminate regulations and it shouldn't. But it can make compliance faster, clearer, and more predictable. We built this tool because we've watched brilliant designs sit idle for months while developers and architects go through repetitive cycles.
By making the regulatory thicket navigable, we can ensure good projects get built faster, safely, and more affordably for the communities that need them. Explore the research behind permitting delays and compliance challenges on our Insights page.
The Archidian team builds AI-powered tools to automate building code and life safety reviews for architects and design professionals.
Continue Reading
Why Most Permit Comments Are Preventable (and Where They Come From)
How review structure, documentation drift, and coordination gaps shape plan review outcomes.
How Small Construction Firms Can Match the Documentation Reliability of Larger Practices
Why structured review habits and repeatability often matter more than organizational scale.