Catch what's missing before it's submitted.
CivWright pre-checks permit packages against your jurisdiction's own checklist. Applicants and staff see exactly what's missing or inconsistent, with the page, the evidence and the requirement behind every finding.
Pre-check record
Sample package · illustrative| CHECK | FINDING · EVIDENCE | RESULT |
|---|---|---|
| Required sheets | Site plan, floor plan and elevations foundA-0–A-4 | Match |
| Project address | Application says 101 Example Ln; plans say 109 Example LnApp p.1 · A-1 | Fix |
| Front setback | Application states 25 ft; site plan dimensions 22 ftApp p.2 · A-1 | Fix |
| North arrow | Scanned sheet; symbol not legible enough to confirmA-1 | Needs review |
| Scale notation | 1/4" = 1'-0" on floor planA-2 | Match |
Advisory only. Your staff confirm, dismiss or escalate each finding, and both records are kept.
Most permit delays start before review.
In Seattle's 2026 evaluation of AI prescreening, only 1 to 15 percent of applications were approved on the first pass, and intake averaged 4.5 review cycles per permit.
Most corrections asked for missing information, not code fixes. Every round trip costs the applicant weeks and costs your reviewers time they need for real review.
- Provide site plan with front and side setbacks dimensioned.
- Project address on plans does not match the application.
- Add north arrow and scale to sheet A-1.
- Title block missing preparer information.
One check before the counter.
Applicants fix problems before formal submittal. Your staff see the same findings when the package arrives.
Upload the package
The applicant uploads the application, plan PDFs and supporting documents through your pre-check page, before formal submittal.
Check it against your checklist
CivWright looks for required documents and sheets, mismatches between the application and the plans, and required plan information such as scale, north arrow and title block.
Correct and re-check
Each finding opens the exact page and region. The applicant fixes the package and runs the check again as often as needed, then submits.
Every finding is sourced and signed off.
Built for the public record. CivWright shows its work, and your staff keep the final word.
- Evidence on the page
- Every finding links to the document, page and highlighted region it came from.
- Your rules, your approval
- Checks come from your own checklist. Each ruleset version is reviewed, approved and dated by your staff.
- No guessing
- When the evidence is unclear, the result is "needs review" for a person to decide.
- Decisions on the record
- The system's finding and your reviewer's decision are stored separately, with who, when and why. Nothing is overwritten.
- Works with your system
- PDF in, report out. No integration with your permitting software is needed to start.
Start with a six-month pilot.
One permit category. Your checklist. Results measured against your own baseline, including what the tool missed.
- Weeks 1–2DiscoveryPick the category, pull baseline data, agree on success measures.
- Weeks 3–6ConfigureYour checklist becomes rules your designated expert approves.
- Weeks 7–10ValidateRun past permits and compare with your reviewers before anyone else sees it.
- Weeks 11–24Go liveVoluntary pre-check for applicants; staff use the reviewer view.
- Weeks 25–26ResultsA report you can take to your manager or council.
Included
- Checklist configuration and validation on your past permits
- A branded pre-check page and launch materials for applicants
- Training for staff and an applicant webinar
- Monthly check-ins and a final results report
Pricing
A fixed pilot fee sized for administrative approval. Most of it is credited toward year one if you continue. Grant-funded deployments are supported.
Book a pilot conversation