Why Entitlement Timelines Are a Coordination Problem, Not a Complexity Problem

The project that should have been easy

Every developer has one. Modest building, zoning already in place, no variance, no neighbors organized against it, and somehow it took nineteen months to get to a shovel. Meanwhile the ugly one, the project with a rezoning and a traffic study and a commission hearing, cleared in eleven.

When that happens, the explanation offered is usually luck or politics. It is neither. The second project ran three approval processes in a deliberate sequence. The first ran five in parallel, out of sync, with nobody tracking which one was waiting on which. Duration is set by the number of independent clocks a project is running and by how often one of them resets another. Difficulty barely enters into it.

This is an unpopular claim because it removes the excuse. If entitlement duration tracked complexity, a long timeline would be a fact about the project. If it tracks coordination, a long timeline is a fact about how the team ran it.

The published ranges say so out loud

The industry numbers are consistent enough to argue from. By-right projects that comply with existing zoning generally run three to six months. Rezonings and subdivisions in a cooperative market run six to eighteen. Complex or environmentally intensive work runs twelve to thirty-six months and up.

Those brackets are wide, and the width is the interesting part. A six-month spread on a six-month process is not a complexity gradient. It is the difference between a team that ran the process cleanly and a team that did not. The Terner Center's work on California approvals found timelines ranging from under a year to fourteen years, with little consistency by project type. Fourteen years is not a harder building. Something kept restarting.

And the cause most frequently named across the permitting literature is not environmental sensitivity or political opposition. It is an incomplete or inaccurate application package. That is a coordination failure at intake, and it happens before a single reviewer forms an opinion about the project.

The clocks, and how they reset each other

California's Permit Streamlining Act is the cleanest illustration in American land use law, because the reset is written into the statute rather than left to practice.

An agency has thirty days from receipt to determine whether a development application is complete and to tell the applicant. If it finds the application incomplete, it issues a list of what is missing. Here is the part that decides schedules: on receipt of any resubmittal, a new thirty-day period begins. Not the remainder of the old one. A new one.

So an application that goes out with one consultant's report attached in draft form, because the traffic engineer is two weeks behind and the team did not want to lose the submittal window, has not saved two weeks. It has bought a thirty-day completeness review, an incompleteness letter, a resubmittal, and a second thirty-day completeness review, none of which is substantive review of the project. Do that twice and the statutory clock that was supposed to protect you has cost a quarter.

Nobody experiences this as a delay at the time. Each step is short and each is somebody doing their job. That is exactly why it survives. The cost only becomes visible in aggregate, and by then the explanation on the record is that the city was slow.

Most jurisdictions have some version of this. The specifics change, the mechanism does not: a completeness determination gates the review clock, and anything incomplete restarts the gate rather than pausing it.

Design does not wait, which is where the money goes

The second reset is worse because it is not procedural. It is physical.

Design advances faster than entitlement clarity, always. The architect is on a fee and a schedule, the client wants renderings for the capital raise, and the planning conversation is unresolved in a way that feels temporary. So the drawings go from schematic to design development while the zoning interpretation is still open. Durata Advisory's entitlement sequencing work names the failure precisely: the regulatory timing window closes faster than teams realize, and it closes invisibly. There is no alert when a project has passed the point where an adjustment is cheap.

When the agency then asks for a change, and agencies ask for changes, it does not land on one sheet. It cascades through structural coordination, mechanical distribution, enclosure detailing, and contractor pricing. A setback comment that would have cost a week in schematic design costs a redesign cycle and a re-estimate six months later.

This is the mechanism behind the simple-project-took-longer story. The simple project had no forcing function. Nothing about it demanded that the team stop and confirm the regulatory path, so design ran ahead of clarity for months. The complicated project had a rezoning, which is a hard gate that nobody can pretend is resolved, so the team sequenced around it.

Difficulty imposes discipline. Ease removes it. That is the whole asymmetry.

What this changes about where you spend

The instinct when entitlements run long is to add capacity. Another land use consultant, a local expediter, more frequent check-ins with the planner. Sometimes that helps. More often it adds a participant to a process whose problem is that too many participants are operating on private schedules.

The buy-side read is that entitlement duration responds to three things, in this order. First, submitting complete, once, even if that means holding the package four weeks. Second, identifying which approvals are genuinely dependent and running the rest truly in parallel rather than nominally in parallel. Third, naming the design decision points that cannot be reversed cheaply, and refusing to pass them until the corresponding regulatory question is answered in writing.

None of those is software. We say this often enough that it should be expected by now: the entitlement tracking tools on the market are good at showing you the status of each clock and useless at telling you which one is about to reset another. A dashboard that displays five parallel processes in five lanes is an accurate picture of the problem, presented as though it were a solution. We have made the same argument about permit intake and review stages on the municipal side, and about what a permit actually costs a county to process, where the visible cost and the real one also sit in different places.

There is a version of this that is worth automating, and it is small: the dependency map. Which submittal blocks which clock, what resets on resubmittal, which design milestone is downstream of which approval. Most teams keep that in one person's head, which is the same failure we described in how planning consultancies lose margin to document assembly. When that person is on another project, the clocks drift.

We will admit the obvious joke and move on: in entitlements, you really can be out of sync and still be on the clock.

Where writing stops

The honest limit of an article is that we cannot tell you which of your clocks resets which. That depends on your jurisdiction's completeness checklist, your approval body's calendar, your consultants' actual lead times, and where your design is right now relative to the open regulatory questions. It takes a week inside a live project to map, and the map is worth more than any tool you would buy to display it.

If a project of yours is running long and nobody can point to the reason, the reason is almost always a reset nobody logged. Let's talk through your current entitlement sequence and find out which clock keeps starting over.