Package completeness
Compare the drawing index, referenced details, schedules, and deferred-work notes. Identify information that is called for but not clearly included.
Pre-permit plan review
Send a more coordinated set
Review the drawings, specifications, and supporting references together before a permit submission. Give your team a focused list of potential issues to resolve while the package is still in your hands.
Where to focus
What to bring into the review
Conflicting requirements
Review door and wall information, equipment requirements, levels, and discipline interfaces for statements that cannot all govern at once.
Project and code references
Include the project checklist and applicable code-reference PDFs in the review scope. Check the cited edition, local amendments, and project context before accepting a finding.
An actionable response list
Review each potential issue beside its evidence, then record the responsible designer and the information needed to resolve it in your team’s review record.
Inside Groundbook
Set the scope before the review starts
Choose the files to check, add supporting references, and explain the submission milestone in the review instructions. State known exclusions and deferred packages so the review can be assessed against the intended scope.
A practical workflow
From the first pass to a decision
Assemble the intended submission
Use the current issue and include the referenced specifications, consultant drawings, and project requirements needed for the review. Keep older issues clearly identified as references.
Review what Groundbook found
Start with findings that could change the design or prevent a complete submission. Open the source references and check whether missing context or an exception resolves the question.
Close the loop across the set
Have the responsible designers reconcile affected documents. Check the resulting revision and the local submission requirements before sending the package.
From a published project review
Deferred fire-protection packages are not fully listed
Notes and approval conditions required sprinkler, alarm, and waterfront standpipe systems, but the deferred-submittal list identified only a different system.
Read the findingDefine the scope with your team
A pre-permit review helps your team prepare a submission. Permit acceptance, required approvals, and the jurisdiction’s review remain separate steps. Confirm the current local requirements with the relevant authority.
Download the review checklist (CSV)Questions, answered
FAQs
Does an AI review replace the building department’s plan check?
No. Groundbook identifies potential document issues for review. The jurisdiction’s process and required professional approvals still apply.
Which documents should we include?
Start with the intended submission set, then add the specifications, schedules, consultant information, code sources, and project checklists needed for the stated scope. Clearly distinguish current files from supporting or superseded references.
When should we run a pre-permit review?
Run it when the disciplines are coordinated enough to review together and your team still has time to verify findings and revise the package. The useful milestone depends on the project and submission requirements.
Keep exploring
Continue your review
Prepare a set the reviewer can follow
Prepare a coherent drawing package for AI review: current revisions, readable PDFs, complete references, file roles, and clear project-specific instructions.
ExploreConstruction document review checklist
Use a practical checklist with ownership and closure fields.
ExploreHow to review construction documents
Run a construction document review from scope and document register to source-backed comments, designer responses, and verified closure. Includes a free review log.
ExploreBring your next set into focus
Set up a review or talk through your project with our team.