The Honest Answer
Why Permit Timelines Vary So Much
Permit review time depends on a combination of factors that vary by project and by location:
- Project type: a straightforward interior remodel typically reviews faster than new construction or a project involving structural changes, and a ground-up new build with sitework and utility connections reviews on a longer timeline than either
- Jurisdiction and municipality: some jurisdictions maintain dedicated fast-track review for commercial tenant improvements, while others route every submission through the same general queue
- Project complexity: additional systems, such as full kitchen equipment, grease interceptors, or significant electrical upgrades, typically trigger additional review, and each additional system typically means an additional department has to sign off before the permit is issued
- Zoning: a use that requires zoning confirmation or a variance adds time that a permitted-by-right use does not
- Building and fire review requirements: separate fire marshal review, common for restaurants, can run on its own timeline alongside building review
- Number of review cycles: each round of comments and resubmittal adds time, and the number of cycles varies widely by jurisdiction and submission quality, which is why two projects submitted on the same day in the same jurisdiction can still finish weeks apart
- How quickly the applicant responds to comments: a jurisdiction with a fast internal review can still produce a slow overall timeline if responses to comments sit for weeks
How These Factors Combine
None of these factors operates in isolation. A complex project in a standard-review jurisdiction, submitted with a complete package on the first try, might move through in the same timeframe as a simple project handled poorly in a fast-track jurisdiction. That is why comparing a permit timeline against a single generic number rarely produces a useful answer. The more useful comparison starts with identifying which of these factors apply to a specific project, then checking that combination against a realistic range for that jurisdiction type, which is exactly what the benchmark table below is built to do.
Realistic Benchmarks by Jurisdiction Type
Rather than one number, it helps to compare your project against a general range for the type of jurisdiction you are working in.
| Jurisdiction Type | Typical Timeline | What Drives the Range |
|---|---|---|
| Streamlined / business-friendly jurisdiction | 30 - 60 days | Dedicated commercial TI review track, fewer review cycles |
| Standard-review jurisdiction | 60 - 100 days | General queue, 1 - 2 review cycles typical |
| High-scrutiny / complex jurisdiction | 90 - 180+ days | Historic district, coastal, or high-volume urban jurisdictions with multiple review cycles |
A 90-day timeline that would be a clear warning sign in a streamlined jurisdiction may be entirely on pace in a high-scrutiny one. Comparing your project against the right benchmark, not a generic industry number, is the first step.
How to Identify Which Bucket Your Project Falls Into
Most jurisdictions will state, if asked directly, which category they fall into. A planning or building department can usually confirm whether commercial tenant improvements go through a dedicated expedited track, a general queue, or a more involved review process for the type of use being proposed. An architect or permit expediter who has worked in that specific jurisdiction recently is often the fastest way to get an honest answer, since posted timelines on a municipal website tend to reflect the target rather than the current reality. Asking for the current average review time for a comparable project, not the timeline printed in a fee schedule, gives a more accurate starting benchmark.
Is Your Timeline Jurisdiction-Driven or Project-Driven?
Once you know the general range for your jurisdiction type, the next question is whether your specific project is on pace or has actually stalled. The distinction matters because the response is different in each case: a jurisdiction-driven timeline calls for patience and periodic check-ins, while a project-driven delay calls for direct action on whatever is actually stuck. A few warning signs suggest the delay is project-driven rather than simply how long that jurisdiction normally takes:
- Repeated resubmittals addressing the same category of comment more than once
- Comments that remain unresolved for weeks without a documented response
- Missing information in the original submission that could have been anticipated
- Long periods with no documented movement in either direction
On the other hand, some circumstances make a longer review period legitimate rather than a red flag: a jurisdiction genuinely known for thorough, multi-cycle review, a project with unusual complexity, or a submission that arrived during a documented seasonal volume spike at the permitting office. Distinguishing between these two categories is less about the number of days elapsed and more about whether there is a clear, documented reason the review is taking as long as it is.
A Diagnostic Checklist Before You Escalate
Before concluding that a project is simply "taking too long," it is worth getting direct answers to a short set of questions:
- What specific review cycle is the project in right now, and how many cycles is that typical for this jurisdiction?
- Are there any open comments the design team has not yet responded to?
- Has the permitting office documented any requested revisions that have not been addressed?
- Is this jurisdiction currently experiencing a documented backlog or volume increase?
- What is the realistic next milestone, and what is the expected date for it?
The goal of this checklist is to replace uncertainty with a clear framework: wait if the timeline matches the jurisdiction's normal range and the project is actively moving, intervene if there are open items the design team can resolve, or escalate if the project has been stalled without documented progress. Running through this checklist takes fifteen minutes and usually produces a clearer answer than another week of simply waiting to see what happens.
Why This Matters More Once You Are Opening Multiple Locations
A single delayed permit is frustrating. A pattern of delayed permits across several locations in a rollout is a process problem worth solving directly, because it compounds: each stalled permit pushes back construction start, FF&E delivery windows, staffing plans, and marketing launch dates tied to an opening date. Comparing each new project against the realistic benchmark for its jurisdiction, rather than reacting individually to each one, is what allows a development team to tell the difference between a jurisdiction that is simply slower and a project that genuinely needs intervention. Tracking permit status against the realistic benchmark for each jurisdiction, rather than against a single company-wide expectation, makes it possible to flag the one project that has genuinely stalled without treating every jurisdiction's normal pace as a problem to be solved.
Building Permitting Into the Overall Rollout Timeline
Permitting rarely happens in isolation from the rest of a rollout. Construction cannot mobilize until the permit is issued, FF&E delivery windows are often scheduled around an assumed permit date, and staffing and marketing plans are typically built backward from an anticipated opening. Treating the permit timeline as a fixed input decided entirely by the jurisdiction, rather than as a range that a development team can influence through submission quality and responsiveness to comments, tends to produce more conservative and more accurate opening-date projections. Brands that build a buffer into their planning based on the realistic range for each jurisdiction, rather than the best-case number, are far less likely to have to walk back a publicly announced opening date. That buffer does not need to be large. It needs to reflect the actual variability of the jurisdiction the project is in, not a single company-wide assumption applied everywhere.
Frequently Asked Questions
How long does a restaurant permit normally take?
It depends heavily on jurisdiction, but a general range is 30 to 60 days for streamlined jurisdictions, 60 to 100 days for standard review, and 90 days or more for high-scrutiny jurisdictions or complex projects. These ranges assume a complete, well-prepared submission; an incomplete package can push any of them longer regardless of jurisdiction.
Why is my restaurant permit taking 90 days?
A 90-day timeline can be entirely normal in a standard or high-scrutiny jurisdiction. It becomes a concern if it includes repeated resubmittals on the same issues, unresolved comments, or long periods with no documented progress. The fastest way to find out which situation applies is to ask directly which review cycle the project is currently in.
What should I ask my architect if my permit seems delayed?
Ask which review cycle the project is currently in, whether there are open comments still unaddressed, and what the realistic next milestone and date are. Clear, specific answers indicate an active process; vague answers are a signal to look closer. If the answers are vague more than once, that pattern itself is useful information.
When should I escalate a slow permit review?
Escalate when the project has gone through more review cycles than typical for the jurisdiction, when comments have sat unresolved for an extended period, or when there is no documented movement at all over several weeks. Escalating does not need to be adversarial; it can be as simple as requesting a direct status call with the reviewing department.
Can a franchise brand speed up a restaurant permit review that has genuinely stalled?
Sometimes. Responding quickly and completely to open comments, requesting a status call with the reviewing department, and confirming nothing in the original submission was overlooked can all shorten a stalled review, though a jurisdiction's own queue and staffing ultimately set the outer limit on how fast any project can move.