01 · CHECK
Every item gets a verdict
All 224 items on the Fairfax County site plan checklist: pass, fail, needs review or not applicable, with a confidence.
Plan review for site plans, by the checklist
Plan review that cites the sheet.
ChkPlan is site plan review software that reads a submitted plan set against the jurisdiction's own applicant checklist, item by item. Every finding points to the sheet and the text it was found in, with a proposed fix. Your reviewer approves every comment before the letter goes out.
Access is by invitation. A person reads every request.
Line 1 ✕ Fail cited to Sheet C-1
02 · CITE
Every finding names the sheet
The checklist line, the requirement verbatim, the sheet, and the text it was found in.
03 · APPROVE
A reviewer decides every comment
Approve, change or reject with the evidence beside it. Nothing issues without a decision on record, or a reviewer's written override reason stored with the letter.
04 · ISSUE
Letter and county handoff
The comment letter in the order and wording your firm uses, and each issue as paste-ready fields for the county permitting system.
What it is
What is ChkPlan?
ChkPlan is site plan review software for the minimum submission review that plan review firms and building departments do on every first submission. It reads the plan set and the applicant's completed checklist, then gives every item on the jurisdiction's own checklist a verdict: pass, fail, needs review or not applicable. Each finding cites the checklist line, the requirement word for word, the sheet, and the text it was found in, with a proposed fix. A reviewer approves, changes or rejects every comment before the letter goes out. Today it covers the Fairfax County, Virginia site plan first submission checklist: 224 items on the July 2025 edition. A 30 to 40 sheet set usually runs in well under an hour.
How it works
How does ChkPlan review a site plan?
In four steps from upload to issued letter: the same minimum submission review your team does today, with the reading done before you sit down.
Upload the set
The plan PDF and the applicant's completed checklist. ChkPlan splits the sheets, reads the text, classifies each sheet, and checks the package itself: duplicate, unreadable or unnumbered sheets are flagged before any review starts.
Every line checked
Each checklist item is evaluated against the sheets it applies to. The result is Pass, Fail, Needs review or Not applicable, with a confidence, the evidence outlined on the sheet, and the applicant's own checklist reference cross-checked.
The reviewer decides
Recommendations arrive in a review queue. Approve, change or reject each one with the evidence beside it. Confident recommendations can be approved in bulk; the rest are one at a time. Nothing moves without a person.
Issue the letter
Approved comments become the comment letter in the order and wording your firm uses, with the requirement, the finding, the fix and the code reference. Export the issues as a spreadsheet shaped for the county system. Resubmissions are back-checked against the prior letter.
What you get
Built for the reviewer's desk, not a demo stage.
A cited deficiency report
Items that would make the plan non-acceptable come first. Every row names the checklist line, the requirement verbatim and the sheet, and opens straight to the evidence.
- Verdict counts by section, filters by verdict and * items, and search across requirements, code references and sheets
- Items the engine could not evaluate are listed, never hidden, and can be re-run alone
- Export as Excel or JSON, or print the report to PDF
A review queue with the evidence beside the decision
Move through findings with the keyboard. The sheet, the requirement, what ChkPlan found and how to fix it sit on one screen. Pass, Fail or Not applicable in a keystroke, with an optional comment that carries into the letter.
- Route items by discipline to the right reviewer
- Approve confident recommendations in bulk; lower confidence stays one at a time
- Every decision and override is written to a hash-chained log; every model request and response is kept in the run's own audit folder
A rule library you can read and argue with
The checklist lives in the product as items with their code references and the standard each one is checked against. Every item carries its edition date, every run records which edition it used, and when the jurisdiction or your firm rules on how an item is read, the ruling is recorded on that item where a reviewer can see it.
- Fairfax County site plan first submission checklist, 224 items, supported today
- Other checklists and jurisdictions can be added as rulebooks, not rewrites
- Each item shows whether it is checked from the sheets, checked by a fixed rule, or left to the reviewer
The comment letter and the county handoff
Approved comments become the letter: requirement, finding, fix and code reference, in the order and wording the firm uses. Beside it, each issue is laid out as the five fields the county's PLUS system asks for, with a Copy button on each, so entering a review takes minutes instead of an afternoon of retyping.
- Standard comment wording from the firm's library takes precedence over generated text
- Issue the letter and every file is recorded with its hash; resubmissions are back-checked against it
- Export for PLUS as Excel, marked-up plans as PDF
What changes
The reviewer still reads the plans.
The reviewer still decides every comment.
What changes is the order of work: the reading, the checklist cross-check and the first draft are done before the reviewer sits down.
And every finding opens to its evidence on the sheet.
Who it is for
Three seats at the same review.
The firm that reviews, the department that permits, and the team that submits all read the same checklist. ChkPlan gives each of them the same evidence.
01 · Plan review firms
Review more sets per reviewer, with the same rigor.
Third-party and private-provider firms reviewing for jurisdictions. The reading, the cross-check against the applicant's checklist and the first draft of every comment are done before your reviewer opens the set. Your reviewer's judgment is what goes out, under your name.
Built with a working review firmChkPlan was shaped on real first-submission reviews with a plan review firm in Northern Virginia, comment by comment.
02 · Building departments
Consistent comments, a complete record, shorter cycles.
County and city plan review offices. Every comment carries its checklist line, its code reference and its evidence, so applicants get the same answer no matter which reviewer picked up the set, and every decision is on an audit trail you can produce.
Your checklist, your editionsThe rulebook is the jurisdiction's own checklist. Each item carries its edition date, and when the jurisdiction or your firm rules on how an item is read, the ruling is recorded on that item where a reviewer can see it.
03 · Engineers, architects, developers
Find the comments before the county does.
Design firms and owners preparing a submission. Run the set against the same checklist the reviewer will use, fix the misses, and submit a set that clears minimum submission review the first time.
Pre-check, not approvalA pre-check is advisory. It does not replace the jurisdiction's review and never claims to.
What it is, and is not
Plain scope. No approval opinions.
ChkPlan does
- Minimum submission and completeness review against a published checklist
- Cite the sheet and the text behind every finding, so the reviewer can check it in seconds
- Cross-check the applicant's checklist references against the set
- Draft the comment letter and the spreadsheet for the county system
- Track resubmissions against the prior letter
ChkPlan does not
- Check engineering calculations or substitute for engineering judgment
- Approve, reject or issue anything on its own
- Interpret code beyond the checklist and the references it cites
- Train models on your plans, or send them anywhere except the model provider described on the security page
- Claim an accuracy number it cannot show you, item by item, on your own sets
Data and security
Your plans stay yours.
| Question | Answer |
|---|---|
| Where are plans stored? | In the United States, on encrypted storage in a single-tenant environment per customer. |
| Are plans used to train models? | No. Sheets go to the model provider's API under terms that exclude training; the provider keeps requests for a limited period for abuse monitoring and then deletes them. ChkPlan keeps every request and answer in the run's own audit folder. |
| Who can sign in? | Invited accounts only, with roles for administrators, reviewers and users. Sessions are server-side, expire, and can be revoked by an administrator. |
| What is logged? | Every verdict and model call in the run record; every reviewer decision and override in a hash-chained decision log; every issued file with its SHA-256. |
| What happens before a model sees a sheet? | The PDF is checked for integrity, encryption, page count and a readable text layer. Corrupt or encrypted files stop there. |
Questions
What people ask before they request access.
Which jurisdictions and checklists are supported?
Fairfax County, Virginia site plan first submissions are supported today, on the county's July 2025 checklist edition. Other site plan, subdivision and building checklists can be added as rulebooks. Tell us which jurisdiction you review for when you request access.
How accurate is it?
We do not publish a single accuracy number, because it depends on the checklist, the plan set and the reviewer's standard. Instead, every run records each item's verdict, confidence, evidence and the reviewer's final decision, and the analytics screen shows your own confirmed, overturned and flagged rates over time. Judge it on your sets.
Does the reviewer still have to read the plans?
Yes. The reviewer decides every comment. What changes is the order of work: the reading, the checklist cross-check and the first draft are done when the reviewer sits down, and each finding opens to its evidence on the sheet.
How does it get comments into the county's permitting system?
Approved comments export as a spreadsheet with one row per issue in the shape the county system expects: title, discipline, description with the checklist line and sheet, the sheet it is attached to, and the modification flag. The reviewer pastes rows in; nothing is written to the county system directly.
How long does a run take?
A 30 to 40 sheet site plan runs in the background while you work, usually well under an hour. You see progress sheet by sheet while the plan is read, then batch by batch while the checklist runs, and the review queue opens as soon as the run completes.
What does it cost?
Pricing is per firm or department, based on review volume and the number of rulebooks. Request access and we will send a quote with the invitation.
Can we run it inside our own environment?
ChkPlan runs as a hosted, single-tenant service in the United States today. A single-machine installation (one reviewer, no accounts) exists for pilots that cannot send plans off-site; ask when you request access.
Request access
See it on one of your own plan sets.
Tell us who you review for and how many sets a month. We will set up an account, load your checklist, and walk through the first run with your reviewer.