You're two weeks into what was supposed to be a six-week build. The crews are ready, the material plan is open, and the permit is still sitting in building permit plan review. On a 14,000-square-foot tilt-up in a mid-size jurisdiction, the GC's schedule float has already disappeared into mobilization, while subs start moving crews to a competing job.
That waiting period is where preconstruction money leaks out. Estimators keep answering questions, revising scope, checking drawings, and protecting a bid that can't generate revenue until the permit clears. Treat plan review as paperwork and you'll react late. Treat it as a timeline gate and bidding signal, and you can price, staff, and approach the right work before competitors see a public bid.
Table of Contents
- The Waiting Game Every Contractor Knows Too Well
- What Building Permit Plan Review Actually Covers
- Typical Timelines for First Review and Resubmittals
- Where the Time Really Goes Inside Plan Review
- Common Reasons Plans Get Sent Back and How to Prevent Them
- Reading Plan Review Activity as an Early Signal for Bids
- A Project From First Submittal to Issuance
- Turning Review Windows Into Pipeline
The Waiting Game Every Contractor Knows Too Well
Plan review determines whether a won bid can start on the date the owner expects. It affects procurement, subcontractor availability, mobilization, cash flow, and the credibility of the schedule you gave the GC. A permit can be technically active in a municipal system while the job remains commercially immobile.
San Francisco's published performance metric makes this distinction clear. Its “median days to approve” runs from permit application filed to permit issued and includes both city review and the applicant's resubmittal and fee-processing time. That's materially different from quoting only the department's first-review duration. San Francisco's permit performance metrics show why contractors need to separate review time from the full approval cycle.
Stop treating the queue as dead time
Start with the permit status, not the owner's verbal schedule. Confirm whether the application has been accepted, whether fees have been paid, whether the file has been routed, and whether comments have been issued. Those events tell you whether the project is still forming or has crossed into execution.
Then record the date of every status change. A first submittal gives you an early project marker. A correction cycle tells you the design is still active. A second review suggests the applicant has invested enough effort to keep moving. Issuance changes the conversation again because field mobilization can now be scheduled against an actual permit.
Practical rule: A permit queue isn't an empty calendar. It's a live forecast of when work may become actionable.
The trade value is straightforward. Every avoidable review cycle consumes estimating attention and pushes procurement closer to the field start. A clean submission protects margin because it reduces uncertainty before crews, equipment, and long-lead materials are committed. Your job isn't to wait politely. Your job is to identify which projects are advancing, which are stalled by applicant corrections, and which deserve an early call to the GC or design team.
What Building Permit Plan Review Actually Covers
Building permit plan review begins before a reviewer makes a technical comment. The jurisdiction first checks intake, application completeness, required fees, signatures, ownership information, and the documents needed to open the file. A complete-submittal acceptance only means the package is sufficient to enter the workflow. It doesn't mean the design has been approved.
After intake, the permit routes to the disciplines that apply to the project. That can include structural, fire, mechanical, electrical, plumbing, accessibility, zoning, civil, energy, and special inspections. A commercial project may also involve outside agencies or separate approvals, so the permit number alone won't tell you how many review paths are active.
Read the document gates correctly
At intake, reviewers may verify the application, site plan, civil drawings, architectural set, and basic project information. During substantive review, they examine the items that establish whether the proposed work complies with adopted requirements:
- Site and civil documents: Access, grading, drainage, utilities, setbacks, and site constraints.
- Architectural drawings: Occupancy, use, dimensions, assemblies, finishes, and coordination with other disciplines.
- Structural package: Drawings, calculations, load paths, foundation design, framing, and connection information.
- Life-safety material: Occupancy, fire protection, exiting, egress diagrams, travel paths, rated assemblies, and emergency access.
- Energy compliance documents: Required forms, calculations, equipment information, envelope data, and supporting compliance documentation.
- Special inspections: The inspections matrix, responsible parties, structural observations, materials testing, and other required field controls.
The review cycle ends with a correction list or comment letter, not necessarily an approval. The applicant responds with revised drawings, narratives, calculations, and a response matrix. Reviewers then determine whether the corrections are resolved or whether another cycle is required.
The final gate is approval followed by issuance. Don't let a green intake status drive a material order or crew commitment. Ask whether the file has passed technical review, whether all disciplines are cleared, and whether fees or conditions remain before issuance.
The visual process is useful, but the status language matters more than the color on the dashboard.
Typical Timelines for First Review and Resubmittals
Stop building schedules around the fastest published turnaround. Jurisdictions publish different targets because staffing, project class, review depth, and workflow design vary widely.
A 2026 dataset covering 741 U.S. cities reported a national average initial building permit review time of 22.9 days and a median of 14 days. The same dataset found that 51% of cities completed first plan review in 14 business days or less, while 11% took longer than 30 days. Those figures describe initial review, not the complete path from filing through issuance. The 2026 Permit Speed Index provides the cross-city comparison.
Coral Springs states that traditional paper review can take up to 15 business days, while electronic review takes up to 7 business days, because multiple disciplines can review plans simultaneously. Coral Springs' plan review timelines illustrate the operational advantage of parallel routing.
Published targets also show how project class changes the clock. Kansas City lists 20 business days for new buildings and additions, 10 business days for tenant finishes and remodels, and 7 business days for one- and two-family dwellings. Salinas lists 15 working days for the first review of new commercial projects with structural or stormwater issues, then 10, 5, 3, and 1 working day for successive resubmittals. Those are jurisdiction-specific targets, not universal promises.
Use a planning baseline, then adjust it
For a normal commercial pursuit, carry three cycles, 25 business days for first review, and 7 business days per resubmittal, with eight weeks before issuance as the working allowance. That baseline is an editorial planning rule, not a published national standard. Increase it when the project has several reviewing disciplines, third-party review, complex life safety, public-agency coordination, or a jurisdiction with a long queue.
| Project Class | First Review (Business Days) | Resubmittal (Business Days) | Total Cycles Expected | Notes |
|---|---|---|---|---|
| Simple residential or small commercial | 7 to 14 | 5 to 7 | 2 to 3 | Confirm the local target before promising a start date |
| Standard commercial | 20 to 25 | 7 to 10 | 3 | Carry the full approval cycle, not only first review |
| Backlogged commercial | 25 to 30 or longer | 7 to 10 or longer | 3 or more | Staffing and queue position can dominate |
| Large commercial, healthcare, or school work | 6 to 12 weeks | Qualitatively shorter, but project-dependent | 3 or more | Expect multi-discipline coordination and deeper comments |
Seattle describes initial review for simple and medium-complexity work as 2 to 4 weeks, with complex projects typically taking 8 to 12 weeks. Its due date is set at the midpoint of those targets, 3 weeks for simple or medium projects and 10 weeks for complex projects. Seattle's review guidance gives estimators a useful reminder: complexity deserves its own schedule line.
Where the Time Really Goes Inside Plan Review
The review clock has three practical windows. First comes intake and completeness screening. Next comes technical review across the applicable disciplines. Then the applicant prepares and submits a response to the comments.
Don't collapse those windows into one number. Public dashboards increasingly separate pre-screen time, staff review time, applicant response time, and final issuance, which lets you identify who owns the delay. Portland's permit dashboard announcement describes a dashboard that distinguishes staff time from applicant time, while Dallas separates first prescreen, first plan review, and total review.
Build your delay log around ownership
A file that clears intake quickly but waits for technical assignment has a department-side queue. A file with comments outstanding has a design coordination problem. A file that has sat with the applicant since comments were issued is on your side of the clock if your team is responsible for the response.
The table below is a management framework, not a national statistical distribution. Use the jurisdiction's dashboard or published target to replace qualitative labels with local observations.
| Window | Typical Share of Total Days | Owner of the Clock |
|---|---|---|
| Intake and completeness screening | Early portion of the cycle | Shared, with the applicant responsible for a complete package |
| Technical discipline review | Often the largest active queue | Building department and assigned reviewers |
| Applicant response and correction package | Variable and directly controllable | Applicant, architect, engineers, and GC coordination |
| Final approval and issuance processing | Closing portion after clearance | Building department, applicant, and fee-processing parties |
Structural, fire, zoning, accessibility, and energy comments don't carry the same coordination burden. Structural and life-safety issues can force drawing, calculation, and detail changes across the set. A zoning correction may be narrow, but it can still block issuance until resolved.
Your response window deserves the same discipline as the reviewer queue. If the design team takes two weeks to assemble a correction package, then adds clarifications during coordination, the calendar expands without any building-department backlog. Track the comment date, responsible discipline, response owner, and resubmittal date. That record tells you whether the next escalation belongs with the reviewer, the architect, or your own project team.
Common Reasons Plans Get Sent Back and How to Prevent Them
Most plan-review corrections aren't mysterious. They come from coordination gaps that a disciplined pre-submission review should catch.
An incomplete application form can stop intake before technical review begins. Missing energy documentation can create a targeted correction that still holds the permit. Structural calculations that don't match the drawings undermine reviewer confidence and often force a coordinated revision rather than a simple note.
Match prevention to the failure
Use a checklist built from the jurisdiction's published submittal requirements. Don't rely on the architect's general checklist if the local portal asks for different naming, forms, calculations, or discipline packages.
- Incomplete application forms: Run every field, signature, ownership item, and fee requirement against the jurisdiction's checklist before uploading.
- Missing energy compliance documentation: Bring the energy modeler into the submission review early and verify that the forms match the architectural and mechanical design.
- Structural calculations that conflict with drawings: Have the licensed PE coordinate the calculation package, structural set, details, and revisions before drop-off.
- Unclear egress diagrams: Show the path of travel, widths, exits, common paths, occupancy assumptions, and the relationship between plans and life-safety narratives.
- Unidentified fire-rated assemblies: Use the correct listed assembly reference and coordinate the wall, floor, penetration, and door details.
- Zoning conflicts: Check lot coverage, height, setbacks, use, parking, and site constraints before the application enters the queue.
- Missing accessibility details: Review accessible routes, clearances, fixtures, entrances, and dwelling-unit requirements where applicable.
Make the QA pass look like the review
Review the package in the same order a reviewer will encounter it. Start with intake and zoning, move through civil and architectural coordination, then check structural, fire, energy, accessibility, and trade drawings. Finish by confirming the response process, file naming, revision clouds, and document index.
The cheapest schedule lever is quality at submission. Every correction cycle adds coordination, review time, and potentially another fee. A PE review, discipline-by-discipline QA pass, and complete response matrix cost less than discovering a missing life-safety note after the project has entered the queue.
Field standard: Never submit a set that your own team can't navigate quickly. If the response owner can't find the detail, the reviewer won't either.
Reading Plan Review Activity as an Early Signal for Bids
A property listing is a weak lead. A demolition rumor is better, but still uncertain. A submitted building permit application entering plan review is the first dependable sign that ownership, design intent, and permitting effort have moved beyond conversation.
Don't treat the permit record as a final outcome. Treat each status event as a confidence update:
- Application accepted: The package has cleared the jurisdiction's intake gate.
- Fees paid: The applicant has funded the next step and shown commitment to advancing the file.
- Reviewer assigned: The project has been routed to an identifiable group of disciplines.
- First comments issued: The design has reached substantive review and the project team is actively responding.
- Second review or resubmittal logged: The applicant has kept the project alive through the first correction cycle.
- Permit issued: The project has cleared the approval path and can move toward field execution.
Turn each signal into a sales decision
Use early activity to decide how much effort the opportunity deserves. An accepted application may justify a light-touch introduction. A reviewer assignment supports a more targeted message to the owner, applicant, or GC. A second review is a stronger reason to refresh your scope, check material availability, and ask when trade pricing will be requested.
The signal also helps you avoid bad timing. If the scope changes materially between review cycles, don't carry an old estimate into the next conversation. If comments show that the project is resolving structural or life-safety issues, expect downstream changes to trade quantities and sequencing.
For a practical workflow on finding these records and connecting them to active opportunities, use this guide to finding building permits. The point isn't to collect permit numbers. It's to identify projects early enough that your outreach can influence who gets included before the bid list closes.
A Project From First Submittal to Issuance
A representative commercial project enters the jurisdiction on day 1. The architect submits the drawings, application, calculations, energy material, life-safety package, and supporting documents. Intake routes the file to the relevant disciplines, but acceptance doesn't yet mean the design has passed technical review.
On day 14, the first comments arrive. Structural reviewers flag coordination between calculations and drawn details. The life-safety review identifies a missed note affecting the egress package. The contractor should not treat those comments as isolated paperwork. They indicate which parts of the design may change quantities, installation details, and trade sequencing.
The architect and engineers issue a corrected set on day 28. A clean response matrix links each comment to a sheet, detail, calculation, or narrative revision. Deferred submittals create back-and-forth because the team must define what remains deferred, what the permit set already establishes, and which later documents require approval before fabrication or installation.
The calendar only works when ownership is clear
By day 38, the reviewers approve the corrected package. The missed life-safety note reset part of the review effort, but the organized response packet kept the second cycle short. On day 42, the permit is issued.
That sequence gives the contractor a usable benchmark: first submission, first comments, corrected set, approval, then issuance. It also shows why a status change matters commercially. Before issuance, crews can be tentatively aligned and pricing can be refreshed. After issuance, the GC can discuss mobilization, procurement, and field sequencing with less uncertainty.
Use a construction intelligence platform to connect the permit event to the project identity, applicant, owner, and likely trade opportunity. The record becomes valuable when it tells you not only that a permit moved, but who controls the next decision.
Turning Review Windows Into Pipeline
Review time becomes pipeline intelligence when your team tracks the right events and assigns an action to each one. Don't monitor every permit equally. Focus on projects that match your trade, geography, capacity, and likely bid timing.
Track four signals on every qualified project:
- First submittal date: Start a project record and send a low-pressure introduction to the GC, architect, or applicant.
- Resubmittal count: Increase priority when the project survives its first correction cycle. That's the point to ask about trade outreach and pricing dates.
- Scope changes between cycles: Recheck quantities, exclusions, alternates, and long-lead materials before you update your number.
- Time-stamped reviewer comments: Use the comment pattern to identify design risk, likely changes, and the disciplines most likely to affect your scope.
Decide when to call
Send an email when the application has just entered review and the relationship is cold. Call when a second review is logged, when comments indicate a material scope change, or when issuance is approaching and the GC is likely locking trade coverage. Sitting on a resubmittal signal costs the chance to shape the bid list. Sitting on an issuance signal costs the chance to win work that is moving into procurement now.
Your operating checklist should be simple:
- Monitor: Submittal date, review status, resubmittals, comments, scope changes, and issuance.
- Classify: Separate early interest from active design and near-field opportunities.
- Act: Email at initial movement, call at meaningful progression, and refresh pricing after scope changes.
- Automate: Use permit tracking software to reduce manual checking and keep estimators focused on qualified opportunities.
Platineer is one option for connecting permit and plan-review activity with project details, decision-maker contacts, trade fit, territory, and pipeline status. It also offers tools for rendering a job and estimating permit-related costs, which can help teams move from project discovery to early qualification without waiting for a bid posting.
Platineer helps contractors identify active and upcoming construction opportunities by tracking permits, plan reviews, plats, and owner records, then routing qualified projects by trade and territory. Visit Platineer to see how earlier review signals can become a more actionable bidding pipeline.
