Pre-screen a submittal against the jurisdiction's own intake and preliminary review requirements — so applications get accepted the first time and reviewers spend their time reviewing, not chasing paper.
Why it matters
Missing sheets, unsigned forms, absent studies and incomplete narratives are the most common reason a submittal stalls. They are also the easiest to catch before it is filed.
Agencies can screen every incoming application against their own checklist in minutes, so plan checkers open sets that are actually ready for substantive review.
Applicants see the same requirements the counter uses. That single shared list removes most of the back-and-forth from the first two weeks of a project.
Capabilities
Requirements are drawn from the jurisdiction's published submittal checklists, application forms and preliminary review requirements for the relevant permit type — not a generic template.
AutoSitu reads the set and reports what is present, what is missing and what is present but incomplete — sheets, schedules, details, plans, reports, forms and attachments.
Traffic, drainage, geotechnical, environmental, arborist, acoustic and similar submittals are checked against what this application type actually triggers.
Beyond “is the sheet there”: required notes, legends, north arrows, scales, data tables, tabulations and stamps that intake staff verify page by page.
Project data on the application should match the cover sheet, and the cover sheet should match the plans. Mismatched addresses, parcel numbers, areas and unit counts get flagged.
Findings come back as a clear, item-by-item list with the location in the set and the requirement behind it, so an applicant can resolve them without a phone call.
Cities can run intake screening as a standard step, keep a record of what was checked and when, and hand applicants a consistent completeness letter every time.
Resubmittals are compared against the prior run, so staff can see exactly what was addressed instead of re-reading the whole set.
How it works
The applicable intake and preliminary review requirements are assembled for that agency and application type.
Drawings, reports, forms and attachments go in as they would be filed — no reformatting or tagging required.
Each requirement is checked against the set, with the page and location recorded for anything present, missing or incomplete.
Work the list, re-run it, and submit knowing the package matches what the counter is going to look for.
Coverage
Completeness review covers the administrative and documentation layer that decides whether an application is even accepted for review.
Developments analyzed
Requirements checked
Issues identified
FAQ
Every solution runs on the same project model, so the work you do here carries forward into everything that follows.
Schedule Private Demo