Compare the condition, the evidence, and the requested action. Groundbook findings and manual plan-check comments can identify shared concerns while expressing them at different levels of detail. Connecting those observations gives the project team a practical basis for coordinating revisions and documenting responses.
Plan review and construction document QA/QC
Construction document quality assurance and quality control (QA/QC) includes checking drawings, schedules, specifications, and calculations for completeness and coordination. Within that process, AI-assisted plan review can identify document discrepancies and organize findings for the design team to evaluate.
Manual plan review can include design-team reviews and permit plan check. In permit plan check, a plans examiner reviews the submitted construction documents against applicable requirements and issues comments for the team to address. This article compares recorded findings and requested corrections.
For related terminology and workflows, see the construction plan review glossary and construction document QA/QC checklist.
About this comparison
This article draws on selected findings from an AI-assisted review and a manual plan-check record.
The focus is how the review records describe conditions and support corrective action. This is an editorial comparison by Groundbook, not a performance benchmark or a claim that either review method identifies every possible condition.
What the comparison found
Groundbook's review record contained findings that directly matched 9 manual plan-check comments and markups, with 8 further entries showing partial overlap. It also documented 100 additional distinct review observations not explicitly stated in the manual summary, after consolidating repeated and closely overlapping records.
| Result | Count | What it means |
|---|---|---|
| Manual plan-check comments and markups with direct matches | 9 | The same condition and requested correction are represented in Groundbook's findings. |
| Manual plan-check comments and markups with partial overlap | 8 | Groundbook describes a related condition or part of a broader comment; these are counted separately from direct matches. |
| Additional Groundbook observation groups | 100 | Distinct technical or documentation observations without a specific counterpart in the manual summary. |
How the counts were determined
The direct-match count includes 7 numbered comments and 2 unnumbered highlights. Each manual comment or markup is counted once, even when it corresponds to several Groundbook records. Repeated manual comments remain separate entries in that count.
For the additional-observation count, records describing the same condition or a common correction were consolidated. This includes repeated labels, repeated specification wording, and a shared sheet-index correction. Groups with direct or partial counterparts were excluded from the additional count. A general request to demonstrate code compliance was not treated as a match to every code-related observation.
These counts use two units: manual plan-check comments and markups for overlap, and consolidated Groundbook observation groups for additional findings. Additional observations include technical coordination, code-reference, and drafting items. They describe the available review records; the responsible design professionals determine which observations require correction. The comparison does not establish which reviewer identified a condition first or a detection rate.
Compare AI findings with your own review
Upload a set you reviewed by hand and see what AI finds. Groundbook flags potential conflicts with links to the source sheets.
How AI plan review supports interdisciplinary coordination
The reviewed Groundbook findings also illustrate several forms of document checking that can support the team's response process.
Specifications and details
Groundbook identified inconsistencies between system specifications and related details. Comparing those documents helps the team determine which requirements need clarification and where revisions should be coordinated.
Coordination between disciplines
Groundbook connected mechanical equipment information with structural support documentation. This type of finding gives the responsible engineers a defined coordination question: do the equipment requirements, mounting details, and supporting structure describe a consistent design?
Energy documentation and scheduled assemblies
Groundbook identified differences between modeled assembly properties and information in architectural documents. The resulting review action is to reconcile the model inputs, schedules, and specifications.
Manual plan-check comments provide corresponding requests for clarification, supporting documentation, and demonstrated compliance. Together, the records give the team observations to evaluate and actions to track through the revision process.
Compare findings by their purpose
Useful review language distinguishes the nature of the observation:
- Coordination discrepancy: two or more documents describe a condition differently.
- Missing or unclear information: a drawing, schedule, or detail needs clarification to communicate the design.
- Potential code-compliance issue: a documented condition warrants evaluation against the applicable requirement.
- Supporting-document request: calculations, product data, assembly listings, or other evidence are needed to support the response.
This vocabulary gives each finding an actionable purpose. It also keeps document observations distinct from final compliance determinations.
For a meaningful comparison, consider the condition addressed, the supporting evidence, and the revision needed. The number of entries alone does not measure review quality: one comment may cover several actions, while another may describe one discrete condition. This article makes no numerical claims about detection rates, review speed, cost savings, or permit outcomes.
Prepare a response to comments and coordinated resubmittal
- Establish the review basis. Identify the drawing revision, reference documents, and applicable requirements.
- Connect related findings. Group comments that concern the same condition while preserving distinct requested actions.
- Assign responsibility. Identify the lead discipline and any coordination required with other consultants.
- Document the response. Prepare a response to comments that records each clarification or correction and references the revised sheets, details, or supporting calculations.
- Verify the revised documents. Check that the response is reflected consistently in the affected drawings, schedules, specifications, and calculations.
Groundbook supports this workflow by organizing document findings with references for review. Responsible design professionals evaluate and coordinate the response, and the authority having jurisdiction (AHJ) makes the applicable permit-compliance determinations.