# Explain a permit delay without guessing at the review

A permit delay update states the verified status, the item under review, who owns the next action and when you will check again. Keep submission, intake, review, correction, resubmission and authorization to proceed as separate states. Never invent a jurisdiction response date. Never imply approval before the project record confirms it.

## Why does "the permit is delayed" tell the buyer so little?

Permit work is a chain of handoffs. Plans get assembled, submitted, received, routed, reviewed, returned with comments, revised, resubmitted or held for a separate approval. Calling all of that "at permitting" hides the action that matters.

The buyer needs to know where the application stands and whether the builder, the designer, the engineer, the owner or the reviewing office has the next move. That takes a current record, not an interpretation of a regulation or a guess at another office's workload.

Check the project's status labels, current forms, instructions and authorization requirements with the responsible permitting office through its official channel. Keep the official source with the project record. Do not copy a process from one location to another: an [infill lot](/glossary/infill-lot/) inside city limits and a county parcel may follow different paths, and the office that handles each one is the place to confirm it.

### What can you say about a review date?

Report a published or project-specific estimate only after checking the current official source, and label it as an estimate. An estimate is not an appointment or an approval date. When no reliable date exists, give the next follow-up point you control.

## Which permit statuses does the team keep apart?

Treat the table as a working communication model. Confirm the actual labels and sequence with the responsible permitting office, then keep its wording in the project log when you translate for the buyer. The translation must not change the meaning.

| Working status | Question to verify | Buyer update focus |
| --- | --- | --- |
| Package preparation | Are all builder-controlled inputs ready? | What remains before submission and who owns it |
| Submitted | Was the package sent through the approved channel? | Submission confirmation and next known step |
| Intake or routing | Has the package entered the stated review path? | Current verified status. No claim of technical review |
| Under review | Which review is active, if the record says? | Known stage and your next check point |
| Comments received | What response is requested and from whom? | Response owner and work underway |
| Resubmitted | Was the revised package received? | Resubmission record and current status |
| Authorized to proceed | Does the official project record confirm the required authorization? | Next builder-controlled mobilization step |

A fee receipt, a portal screen or an email proves one [handoff](/process/handoff/) and nothing about the next. Store the source record and its date with the status entry. A screenshot with no context gets misread once the portal changes.

## How do you prepare a permit-delay update?

From the application record, not a remembered phone call. If a conversation adds new information, write down who spoke, the date, the stated status and any requested action.

1. **Confirm the application identity.** Address, scope, application reference and current plan version.

2. **Verify the current status.** Through the official channel or the responsible project contact. Keep the source.

3. **Identify the open item.** Waiting on review, a correction, an outside document or a builder response.

4. **Name the action owner.** A role and the expected output.

5. **Review the schedule effect.** Known impact apart from impact still under assessment.

6. **Set the next check.** A date for another status check or update that you control.

7. **Approve the message.** The responsible project role confirms the technical wording and the schedule language.

A good update says review comments were received, the design team is preparing a named correction and the builder will check status after resubmission. It does not say approval is close unless the official record says so.

## How do you communicate correction comments without confusion?

Summarize the operating effect, not an unreviewed technical reading. Which discipline or document needs attention, who is responding and whether the schedule effect is known. Link the internal team to the full comment record.

Do not forward a dense correction notice to the buyer with no context. Do not shrink it either. Some comments are document clarifications. Some need design coordination. The responsible professional and the project team decide the response.

### What if the comment changes the plan set?

Run the revision through your plan-control process. Update the plan index, the affected specifications, the pricing review and the field distribution. A permit response never spawns an unofficial plan branch in an email attachment.

## How does a permit update connect to schedule communication?

The permit log records the review path. The [builder schedule update](/articles/process-and-documents/builder-timeline-communication/) records the effect on planned work. Keep them linked. Do not make the permit coordinator guess trade availability or the superintendent interpret review comments.

If weather or site access affects work after authorization, use the separate [weather delay record](/articles/process-and-documents/weather-delay-communication/). The [documented build process](/articles/process-and-documents/documenting-your-build-process/) names the owner and the source for every handoff.

AI agents monitor approved status inputs, compare a comment log with the response checklist and draft a plain-language update. A person verifies the official status, the technical response and the schedule effect before anything goes out. That reviewed workflow belongs in [AI operations](/process/ai-operations/).

The [build process guide](/guides/writing-down-your-build-process/) covers source control and role ownership. More connected records sit in the [process and documents library](/articles/process-and-documents/).

## What else comes up in a permit update?

### Should we tell the buyer who caused the delay?

No. Report the verified status, the next action owner and the known project effect. Blame and speculation stay out of the notice.

### Can we quote the review portal?

After checking its current official wording. Keep the source and date, then explain the project effect without changing what the status means.

### What if the jurisdiction gives no response estimate?

Say so. Then give the next follow-up point your team controls.

### Does submission mean work can start?

No. Confirm the required authorization to start with the responsible permitting office, using the official project record. A submission confirmation is not authorization.