How to track entitlements across a development pipeline

Why entitlement tracking breaks down

Entitlements run longer than any other predevelopment workstream, involve more outside parties, and change shape mid-process. Research summarized by the Urban Institute found the planning phase of multifamily projects averages 15.3 months from project announcement to construction start, longer than the 12.3 month construction phase that follows. Most of that planning time is approvals and the design loops they trigger.

The volume of approvals is the first problem. In the NAHB and NMHC cost of regulations study, 93.9 percent of multifamily developers reported dedicating resources to rezoning to allow their project, and zoning approval costs average 3.4 percent of total development cost when present. Nearly three quarters of developers, 74.5 percent, reported encountering neighborhood opposition, which adds an average of 5.6 percent to development costs and delays delivery by an average of 7.4 months when it appears.

The second problem is that entitlement work does not sit on one calendar. The rezoning lives with the planning commission and council. The site plan lives with development review staff on their own comment clock. The traffic study lives with a consultant, and the variance lives with a separate board that hears cases once a month. Each track has its own dates, resubmittal cycles, and conditions, and a slip in one cascades into the others.

Most teams track all of this in a spreadsheet per project plus the project manager's memory. That holds for one project. At three to five projects across different jurisdictions it fails quietly, and the failure is usually discovered when a hearing window closes without a submittal or a condition of approval surfaces at permit intake that nobody scoped.

The entitlement workstreams and the timelines to budget

Four workstreams cover most entitlement paths. Review clocks vary by jurisdiction more than any national dataset captures, so treat the ranges below as planning budgets to validate against your city's published timelines and your own recent local experience, then hold your projects against them.

The only reliable national anchor is the 15.3 month planning average, and it hides wide regional spread. The same Urban Institute research found projects in the Northeast average about 3 months longer than the Midwest, projects in the West about 5.7 months longer, and mixed-use projects roughly 3 months longer than comparable multifamily-only buildings. If your pro forma assumes nine months of entitlement in a coastal discretionary jurisdiction, the data says to justify that assumption in writing.

The direct fees are the smaller cost. HelloData's predevelopment breakdown puts permitting and approvals at 0.5 to 1 percent of total project cost and legal at about 1 percent. The carry during the wait is what compounds.

What a slipped hearing actually costs

Put numbers on a single project. A $20 million development carrying $4 million of land debt at 9 percent pays $30,000 a month in interest. Add $6,000 a month in property taxes and insurance and $9,000 a month of consultant burn across civil, traffic, and legal, and the project carries $45,000 a month while it waits.

At that rate, the NMHC study's average opposition delay of 7.4 months prices out to roughly $333,000, before any hard cost inflation over the same period and before the extension payments many land contracts require. A single missed hearing cycle is smaller but entirely self-inflicted. In a jurisdiction where the commission meets monthly and resubmittals need six to eight weeks of lead time, missing one submittal window costs $68,000 to $90,000 of carry for a problem a tracking system would have surfaced three weeks earlier.

That is the economic case for treating entitlement tracking as a discipline rather than an inbox. The approvals themselves are slow for reasons you mostly cannot control. The self-inflicted cycle losses are the part you can.

The tracking process, step by step

Copy this into whatever system you run. Six steps, repeated per project.

1. Map the approval path before you file. List every approval the project needs, the body that grants each one, and the order of operations. Some jurisdictions allow concurrent review of the rezoning and site plan, others force sequence. The map tells you the critical path and it becomes the spine of everything you track.

1. Convert each approval into dated milestones. Every entitlement breaks into a submittal date, a review clock, a hearing or decision date, and an effective date, each with a status. Estimated dates count. A hearing that is "probably September" belongs on the board as September with a flag, then gets corrected when the agenda posts.

1. Assign one owner per workstream. The rezoning, the site plan, each technical study, and each variance gets a named person responsible for the next action. Consultants do most of the work, but a consultant is not an owner. The owner is the person on your team who notices the traffic engineer went quiet.

1. Log every submittal and review cycle. Record the submittal, the staff comment letter that comes back, and the resubmittal that answers it, with dates. The cycle count is your best forward-looking indicator. A site plan on round one behaves differently from one entering round four, and your timeline forecast should reflect it.

1. Run a weekly entitlement review. Once a week, walk every active project sorted by next critical date. For each open approval, confirm three things in one pass. What is the next action, who owns it, and what date does it have to happen by. Twenty minutes across five projects, every week, catches nearly every slip while it is still cheap.

1. Carry conditions of approval into permitting. An approved rezoning or site plan arrives with conditions, sometimes dozens. Log each one as its own tracked item with an owner and a deadline. Unmet conditions resurface at permit intake, at financing close, and at certificate of occupancy, and by then they are expensive.

What to track on each entitlement

The record for each approval needs fewer fields than most teams expect, but it needs them consistently.

• Application type, number, and jurisdiction

• Current status and current review round

• Last submittal date and the review clock it started

• Next hearing or decision date, with the agenda posting date ahead of it

• Resubmittal count and the open comment themes

• Conditions of approval, each with an owner and a due date

• The consultant and the internal owner

• Next action and its date

If a field does not change a decision or a date, drop it. The system survives on being updated in the meeting, in real time, by whoever owns the item.

Running entitlements in MotionCRE

MotionCRE gives development teams this structure without building it from scratch. Each project is a deal workspace with development-specific fields, and its key dates hold every submittal, hearing, and decision milestone with a status and a calendar view across the whole portfolio. Stage-triggered task templates generate the same entitlement checklist every time a project advances, so filing a rezoning spawns the notice, study, and submittal tasks with owners attached.

The pipeline board runs custom stages that mirror the approval path, from application filed through entitlements secured, with days-in-stage visible on every card. Comment letters, submittal sets, and approval documents live on the project record with versioning, and the contacts directory keeps the traffic engineer, land use counsel, and planner on the deals they touch.

Entitlements are one gate in a longer sequence. For the phase around them, start with what predevelopment covers, and for running several projects at different gates at once, see how to manage a development pipeline.