AutoSitu gives planning and design firms one system of record across every jurisdiction they work in — the precedent, the scenarios and the cited site-plan review behind comprehensive plans on one side and entitlement-bound site plans on the other — so your planners spend their hours on the recommendation, not on getting back up to speed.
Dozens of jurisdictions in one plan, none of them talking to each other. The work is knowing what every one of them has adopted, proposed and approved — and what changed since the last time you looked.
Schematic design through design development, in front of staff before an architect touches a building permit. The work is getting the site plan through the hearing the first time, in a village you may have never worked in.
How a given city's staff actually applies their own ordinance lives in senior planners' heads and in old staff reports. A new jurisdiction means starting from zero on that institutional knowledge.
Pulling the ordinance, the overlays, the last approvals and the last hearing happens per site, per project, per planner. Little of it carries forward.
Site plan QA/QC today is a punch list and a senior reviewer's attention before the deadline — not a system that runs on every set, every iteration.
What the code allows and what a jurisdiction actually approves can differ. That gap is invisible until the comment letter comes back — or until a neighboring jurisdiction changes the rules and nobody told you.
AutoSitu maps how each jurisdiction actually works, researches precedent and hearings, runs your punch list and the zoning and civil checks against the site plan in parallel, and hands your planners a cited list of what needs a professional decision.
Spend the hours on the plan, not the paper trail.
Staff reports, public hearing video, what was approved nearby and why, what a third-story step-back cost the last applicant — researched before you're in front of the commission, not reconstructed after the comment letter. What's new in the jurisdiction surfaces on its own; mark it applicable or not and keep a clean record.
Start from the parcel, the district and the overlays, then reason through the paths: what by-right yields, what a PUD buys and what it costs in timeline, or disregard current zoning entirely and evaluate the amendment you're drafting for the client.
Upload the firm's own punch list — graphics, scale bars, text sizes, sheet setup, the things a principal checks before a set leaves the studio. AutoSitu digests it and walks every item on every iteration, at SD and again at DD. It's your standard, not a generic one.
Zoning and civil checks run against the actual site plan. Each finding cites the code section and the sheet, jumps to the page and draws the bounding box around what it read — legend first, then the drawing, the way a reviewer does. The footnote holds up when someone clicks it.
The jurisdiction hierarchy mapped at setup, the precedents found at insight, the scenarios you weighed — none of it is thrown away. The same context reviews the site plan and the resubmittal, inside a sandbox that belongs to your firm alone.
No. AutoSitu does the first pass — the research, the reading, the repetitive checks. A planner reviews every finding, decides, and signs. Checkpoints are built in because the person putting their name on the plan has to trust what's under it.
They're two distinct gates, not one black box. QA/QC checks the set against your firm's punch list — how the plan should look and read. Compliance checks it against the jurisdiction's zoning and civil requirements, with the code section cited. You see which gate flagged what.
Setup maps how the jurisdiction actually works — including a township that adopts county standards or a state law that overrides the local district. Then every run searches dynamically for the current documents. It's not a static code database that quietly goes stale.
Give us the names. The first 15–20 jurisdictions take a day or two; after that, about three more each week. No code documents to upload — mapping the hierarchy is on us.
Setup is a hands-on service: give us the names of the jurisdictions you already work in and we map the hierarchy — which code applies, which county standard a township adopts, which state law overrides the district.
See how jurisdiction research feeds entitlement strategy in the entitlement & site feasibility guide
Compare cited, page-level plan review approaches in the AI plan review buyer's guide
Bring us a site plan from a jurisdiction your team knows cold. If AutoSitu can't tell you something about that jurisdiction's precedent or your own set that you didn't already know, you've lost an hour.