Construction documentation has two common meanings. In design, it is the construction document (CD) set: the coordinated drawings and specifications issued for permit, bid, and construction. In project management, it also covers the records produced while building: RFIs, submittals, daily reports, and change orders. This guide is about the set itself, because that is what gets reviewed, priced, and built from.
Two things people mean by construction documentation
Architects and engineers use the term for the construction documents phase and its deliverable: the drawings and project manual that follow design development. Contractors and software vendors often use the same words for the paper trail of the build: requests for information, submittals, meeting minutes, daily logs, photographs, and closeout records.
Both matter, but they answer different questions. The CD set says what the finished building should be. Project records say what happened while building it. When a document set is described as complete, coordinated, or issued for construction, the first meaning is intended. That is the meaning used throughout this guide, and it is the material Groundbook reviews.
What a complete construction document set contains
The exact contents depend on the project, the delivery method, and the agreement, but most sets built from the same components. The right-hand column is the reviewer's test: what each component must agree with before the set can be relied on.
| Component | What it contains | What it must agree with |
|---|---|---|
| Cover sheet and drawing index | Project name, team, code summary, sheet list, and issue dates. | The sheets actually in the set, and their current revisions. |
| General notes, symbols, and abbreviations | Requirements that apply across sheets, legends, and the meaning of tags and hatches. | The specifications and the way each discipline uses the same symbols. |
| Civil and landscape drawings | Site plan, grading, utilities, paving, drainage, and planting. | Building footprint, finished floor levels, and utility entries on the architectural and MEP sheets. |
| Architectural drawings | Plans, elevations, sections, reflected ceiling plans, wall types, details, and the door, window, and finish schedules. | Structural framing, ceiling-space services, fire-separation requirements, and the schedules that describe each tagged element. |
| Structural drawings | Foundation and framing plans, sections, connection details, and general structural notes. | Architectural dimensions and levels, openings, equipment loads, and the structural specifications. |
| Mechanical, electrical, plumbing, and fire protection drawings | System plans, risers, diagrams, equipment schedules, and control sequences. | Space for the equipment shown, structural support, penetrations, power requirements, and the corresponding specification sections. |
| Specifications (the project manual) | Written requirements for products, materials, quality, and execution, usually organized by division, plus bidding and contract conditions. | Products, assemblies, and performance values shown or scheduled on the drawings. |
| Addenda, bulletins, and revisions | Changes issued after a set is released, with revised sheets or narrative instructions. | The drawing index, revision blocks, and every sheet the change affects. |
| Reference and supporting documents | Geotechnical report, survey, owner standards, energy and code reports, and deferred-submittal lists. | The assumptions and requirements stated on the drawings and in the specifications. |
The plan review glossary defines the terms used above, including the drawing index, revisions, addenda, and the project manual.
How the documents depend on each other
A set is not a pile of independent files. Drawings show where something goes; specifications say what it is and how well it must perform; schedules connect a tag on a plan to a row of requirements; the index and revision blocks establish which sheets are current. A statement made in one place is usually repeated, in a different form, somewhere else. Review is largely the work of finding the places where those repetitions disagree.
Three findings from Groundbook's published, anonymized project reviews show the pattern. In the hotel set, the door schedule marked entry doors unrated while the surrounding separation called for protected openings. In the mixed-use set, structural and mechanical plans showed different elevations for the same floor area, and equipment data did not reconcile across plans, diagrams, schedules, and specifications. Each is a case of two documents describing one thing differently.
None of these findings can be settled by reading one sheet. Deciding which document governs, and whether the design needs to change, belongs to the responsible designers. The reviewer's job is to put both sources in front of them.
What “complete” means at each stage
Completeness is relative to the decision the set is meant to support. A design development set can be complete for its purpose while omitting connection details that belong to the construction documents. A permit set must be complete for the jurisdiction's review, which may not require every finish schedule. An issued-for-construction set must be complete enough to build from, with deferred submittals identified rather than silently missing.
Agree the expected contents for each milestone before reviewing against them. The 30/60/90 design review guide suggests a way to set those expectations, and the DD-to-CD change narrative explains how to document what changed between issues. Record known exclusions in the set itself, on the cover sheet or in a narrative, so a later reader does not mistake a deliberate deferral for an omission.
Documentation errors reviewers find most often
The errors below are the ones that recur across projects and disciplines. They are worth checking on every issue, whatever the project type.
- Index and set disagree. Sheets listed but not issued, sheets issued but not listed, or an index that shows an older revision than the sheet carries.
- Unclear governing revision. Two sheets show different information for the same location and neither the revision blocks nor the issue record says which is current.
- Tags without a home. An equipment tag, door number, or wall type on a plan with no matching schedule row, or a schedule row that appears on no plan.
- Drawings and specifications name different products. A rating, material, or model on a detail that the specification section does not include, or a performance value that appears in two places with two numbers. The drawing versus specification guide covers these in depth.
- Callouts to nowhere. A section or detail reference that points to a sheet or detail number that does not exist, often after sheets were renumbered.
- Levels and datums that differ by discipline. Structural, architectural, and mechanical sheets using different elevations or reference points for the same floor.
- Superseded references still in the set. An old geotechnical report, code edition, or owner standard cited after a newer one governs.
For a longer list organized by discipline interface, see the guide to cross-discipline coordination errors.
Keeping the documentation reviewable
A set is easier to review when the team can answer three questions quickly: which files are in the package, which issue governs, and where each requirement is stated. Keep a document register that lists every file, its issue date, and its status. Use consistent sheet numbering and file names. Issue addenda and bulletins with a list of affected sheets, and update the index when sheets are added or removed.
Keep one review log across milestones so a question raised at design development is still visible when the construction documents are issued. The construction document review checklist starts with a document register section and provides a downloadable version, and the review process guide explains how to run comments through to verified closure.
If the set will be reviewed with software, export readable PDFs, separate the files to check from the references, and state the milestone and known exclusions. The guide to preparing PDFs for AI review covers the details.
Where AI review fits
Groundbook reads the drawings, specifications, schedules, and references in a set together and returns potential conflicts and omissions with the pages they came from. It is a way to find the disagreements described above across a large set quickly, so the people responsible for the design can spend their time deciding what governs rather than hunting for the second source.
It does not prepare the documentation, manage project records, or replace the designers' and reviewers' judgment. See AI construction document review for the scope, published examples, and pricing.