← Field notesPermit ReadinessPublished

§Sheet B-WHAT

What a permit precheck should catch before formal review

A practical look at the issues a precheck workflow should catch before a permit package ever reaches the city queue — and why each one matters.

Author
PermitOS Team
Read time
7 min read
Published
Date not set

Why precheck matters

Most permit delays do not come from genuinely difficult code questions. They come from preventable mistakes that surface only after the package enters the queue. A precheck workflow exists to catch those preventable issues before formal review begins.

The goal is simple: when the reviewer opens the package, the obvious problems are already gone.

Missing documents

Every jurisdiction publishes a checklist for every permit type. Submitters often miss items because checklists are scattered, version-mismatched, or written for in-person counter use.

  • Required forms not present
  • Owner authorization absent or signed by the wrong party
  • Engineering reports not attached when scope triggers them
  • Title sheet, code sheet, or general notes missing

Inconsistent project details

Inconsistencies across the package are easy to miss because each document looks correct on its own. They show up under review.

  • Address differs between cover sheet, site plan, and application form
  • Parcel APN differs between the deed and the site plan
  • Project name or scope language drifts between forms

Signature gaps

Signatures, stamps, and license numbers are easy to overlook on long packages. Reviewers will reject for them, even when the substantive content is fine.

  • Owner authorization unsigned
  • Architect or engineer stamp missing on a required sheet
  • License number absent next to a stamp

Sheet mismatches

The drawing set should reference itself cleanly. When references break, the reviewer cannot follow the package.

  • Sheet listed in the index but missing from the file
  • Detail callout refers to a sheet that is not in the set
  • Cover sheet count differs from the actual sheet count

Zoning risks

Zoning issues are the most expensive late discovery in permitting. A precheck cannot make a zoning determination, but it can flag risk patterns so an applicant can prepare a clean explanation, a variance request, or a scope change before submission.

  • Setback shown on plan looks tight against the district minimum
  • Use described in scope may not match the parcel's permitted uses
  • Overlay (historic, coastal, hillside) appears applicable but is not addressed

Correction-prone items

Some items get cited in correction letters across many packages. They are worth a precheck pass because catching them avoids an entire correction cycle.

  • Energy code path not identified
  • Accessibility scoping not addressed when triggered
  • Missing engineered details where prescriptive paths do not apply
  • Stair, guardrail, and handrail details that omit dimensioning

What a precheck is not

A precheck is not professional design review and not a zoning determination. It does not approve a permit. It catches the preventable issues so qualified reviewers can spend their judgment on the questions that actually need it.

Tagsprecheckreadinessapplicant

§Get started

Run a precheck on your next package.

Catch the preventable issues before formal review.