Every experienced reviewer has a mental list. It works, and it has two problems. It is shaped by whatever burned that person personally, and it leaves with them.
I have watched a preconstruction director find a rooftop unit weight conflict in about ninety seconds because a similar condition cost her a steel revision fifteen years earlier. She went straight to the equipment schedule, then to the framing plan, then to the penthouse detail. Nobody taught her that sequence and she had never written it down. When she retired, it left the building with her.
A written checklist converts that into an asset. Not a generic one, because generic drawing review lists tend to be either so broad they say nothing useful or so tied to one discipline they miss the findings between disciplines. What follows is organized the way review actually gets divided up: general checks that apply to any sheet, then discipline by discipline, then the cross-discipline pairs, then specification correlation, then constructability by building area, then code, then a final pass on the quality of your own comments.
One clarification before you use it. This checklist inspects the design team’s documents, asking whether they are correct, complete, coordinated, and buildable. Checking those same documents for scope assignment is a different exercise, and reviewing a scope exhibit you drafted yourself is a third. Different targets, different lists.
How to Use This Checklist
Run it by discipline, with people who know that discipline. Nobody should run all of Part 3. Distribute the blocks to reviewers who have built the work, and have one person own the log.
Every check produces a finding or a null result, never a checkmark. The two useful outcomes are a logged comment or a recorded confirmation that the condition was examined and is acceptable. A tick tells you somebody looked at a line on a list.
Match the depth to the milestone. At design development, most of Part 3 is premature. At 90 percent construction documents, run everything. Table 1 gives the mapping.
Do not submit everything you find. The checklist generates findings at every severity. Batch the clerical ones and separate the consequential ones, or you will train the design team to discount your log.
Table 1. Checklist Parts by Design Milestone
| Part | SD | DD | 50% CD | 90% CD | Permit | Bid | IFC |
|---|---|---|---|---|---|---|---|
| 1, Set integrity | Light | Light | Full | Full | Full | Full | Full |
| 2, Universal sheet checks | No | Light | Full | Full | No | Light | No |
| 3, Discipline checks | No | Strategy only | Full | Full | No | Light | No |
| 4, Cross-discipline pairs | No | Full | Full | Full | No | No | Light |
| 5, Specification correlation | No | No | Partial | Full | No | Full | No |
| 6, Constructability by area | Full | Full | Full | Full | No | No | No |
| 7, Code and life safety | Full | Full | Full | Full | Full | No | No |
| 8, Comment quality | Always | Always | Always | Always | Always | Always | Always |
| FIELD REALITY Compliance with any review checklist decays fast, usually by the third project, because the list starts feeling like a formality. Two things prevent it. Assign discipline blocks to named individuals rather than to the team, and convert Part 5 into standing queries against your document platform so the correlation check runs without anyone remembering it. |
Key Definitions
Finding. A condition worth logging. Becomes a comment when it is written up with a location, category, and severity.
Null result. A check performed with no defect found. Worth recording on high-severity checks so the review is auditable.
Dead reference. A callout pointing to a detail, section, sheet, or specification section that does not exist in the set.
Correlation defect. A conflict between drawings and specifications, in either direction, including conflicting instruction and missing detail references.
Constructability finding. A condition drawn coherently that cannot practically be built, sequenced, or accessed.
Severity. Four levels: critical for life safety, structural adequacy, code, or occupancy exposure; high for significant cost or schedule impact; moderate for contained cost; low for clerical.
Objectives
- Give every reviewer the accumulated pattern knowledge of the organization, not just their own
- Cover the defect classes that discipline-shaped reading habits systematically miss
- Produce comments specific enough that the design team can act on them without a phone call
- Make the review auditable, so coverage can be demonstrated rather than asserted
- Feed closeout findings back so the list sharpens each project
Part 1: Set Integrity
Run this before anyone reads a sheet for content. It takes about half a day and it determines how to allocate the rest of the review.
Table 2. Set Integrity Checks
| # | Check | Why It Matters |
|---|---|---|
| 1.1 | Sheets received reconciled against the drawing list on G-001 | Missing and extra sheets are invisible without reconciliation |
| 1.2 | Revision number and date recorded per sheet; all sheets from the same issue or exceptions documented | Reviewing a superseded sheet invalidates the findings on it |
| 1.3 | All addenda and bulletins received and incorporated; affected sheets and sections identified | Revisions reassign and redefine work silently |
| 1.4 | Specification table of contents reconciled against sections actually provided | Missing sections make correlation impossible |
| 1.5 | Every detail callout points to a detail that exists | Dead references indicate set maturity |
| 1.6 | Every section cut and enlarged plan reference resolves | Same |
| 1.7 | Every specification citation on drawings exists in the project manual | High-frequency defect, easy to check |
| 1.8 | Sheet numbering and discipline series internally consistent | Numbering gaps often mean withheld sheets |
| 1.9 | Dead reference count tallied and reported | Above roughly 40 on a mid-size set, expect widespread internal inconsistency |
| 1.10 | Scales stated and consistent between plans and the details they reference | Scale conflicts produce dimensional errors downstream |
| 1.11 | Model and drawing versions reconciled where both are issued | Divergence between the two is common and consequential |
| 1.12 | Prior milestone comment log available for backcheck | Without it, comments recur |
| WARNING Check 1.9 is diagnostic rather than merely clerical. A high dead reference count tells you the set was assembled under pressure without internal quality control, which should shift reviewer hours toward Parts 3 and 5 and away from the assumption that the documents were self-checked. |
Part 2: Universal Sheet Checks
These apply to any sheet in any discipline. Fast, and they catch a surprising amount.
Table 3. Universal Sheet Checks
| # | Check |
|---|---|
| 2.1 | Title block complete: project, sheet title, number, scale, date, revision, and seal where required |
| 2.2 | North arrow present and consistent across all disciplines and all levels |
| 2.3 | Key plan present on partial plans, with the correct area highlighted |
| 2.4 | Match lines align between partial plans, with no gap or overlap in coverage |
| 2.5 | Gridlines present, labeled consistently, and dimensionally identical across disciplines |
| 2.6 | Legends and symbol keys present, and every symbol used appears in the legend |
| 2.7 | Abbreviations used appear in the abbreviation list |
| 2.8 | General notes do not contradict specific notes on the same sheet |
| 2.9 | General notes do not contradict the specifications |
| 2.10 | Revision clouds and deltas present where the sheet has been revised, and the revision description matches what changed |
| 2.11 | No superseded information left un-clouded after revision |
| 2.12 | Level and elevation datum consistent across disciplines |
| 2.13 | Room names and numbers consistent between plans, schedules, and finish documents |
| 2.14 | Drawing orientation consistent between plans and the enlarged plans of the same area |
Check 2.8 and 2.9 deserve emphasis. General notes are where scope-affecting requirements get inserted late, and they are read by fewer people than any other content on a sheet.
Part 3: Discipline Checklists
Distribute these blocks to reviewers with relevant experience. Each list targets the recurring defects in that discipline rather than describing everything on the sheets.
Table 4. Civil and Site Checks
| # | Check |
|---|---|
| 3.1.1 | Finished floor elevation agrees with architectural and structural |
| 3.1.2 | Finished grades at building perimeter support the drawn waterproofing and flashing conditions |
| 3.1.3 | Accessible route slopes within limits, including cross slope at all landings and crossings |
| 3.1.4 | Utility inverts at the building line agree with plumbing and electrical service entry points and depths |
| 3.1.5 | Utility separations and cover depths meet requirements and clear structural footings |
| 3.1.6 | Site plan building footprint agrees with the architectural site plan and dimensioned setbacks |
| 3.1.7 | Storm structures clear building foundations, footings, and grade beams |
| 3.1.8 | Pavement sections consistent between plan, detail, and specification |
| 3.1.9 | Retaining wall design references and delegated design responsibility identified |
| 3.1.10 | Erosion control phasing consistent with the construction sequence and permit conditions |
| 3.1.11 | Site lighting bases, conduit, and circuits coordinated with electrical |
| 3.1.12 | Existing utilities shown, with survey basis and known accuracy stated |
Table 5. Structural Checks
| # | Check |
|---|---|
| 3.2.1 | Gridlines and dimensions identical to architectural in both directions |
| 3.2.2 | Column and beam schedules agree with plan callouts |
| 3.2.3 | Slab edges, depressions, and thickenings agree with architectural and MEP requirements |
| 3.2.4 | Floor elevations and slab thickness agree with architectural finish assemblies |
| 3.2.5 | Openings shown match MEP requirements in size and location, including future openings |
| 3.2.6 | Design loads stated, including allowances for MEP equipment shown on mechanical and electrical drawings |
| 3.2.7 | Equipment weights on mechanical and electrical schedules within the framing capacity indicated |
| 3.2.8 | Connection details exist for every member type and condition shown |
| 3.2.9 | Delegated connection design scope and criteria stated |
| 3.2.10 | Foundation elevations agree with civil grades and geotechnical recommendations |
| 3.2.11 | Penetration limits stated for beams and joists, with reference details |
| 3.2.12 | Hanger and attachment provisions defined for MEP loads |
| 3.2.13 | Expansion and control joint locations coordinated with architectural |
| 3.2.14 | Special inspection requirements stated and consistent with the specifications |
Table 6. Architectural Checks
| # | Check |
|---|---|
| 3.3.1 | Dimension strings total the overall dimension on every plan |
| 3.3.2 | Wall type keys on plans exist in the wall type schedule, and graphic thickness matches the assembly |
| 3.3.3 | Door schedule agrees with plans in count, swing, size, and location |
| 3.3.4 | Door frame depths compatible with the wall types they occur in |
| 3.3.5 | Hardware sets consistent with door function, rating, and egress requirements |
| 3.3.6 | Every tagged opening appears in the schedule and every scheduled opening appears tagged |
| 3.3.7 | Window and storefront schedule agrees with elevations and plans |
| 3.3.8 | Rated assemblies on plans agree with the life safety plans and the rated assembly schedule |
| 3.3.9 | Rated assembly details show continuity to structure, including head-of-wall conditions |
| 3.3.10 | Reflected ceiling plans agree with sections on ceiling height and with structural on available depth |
| 3.3.11 | Reflected ceiling plans coordinate diffusers, sprinkler heads, lights, and devices without conflict |
| 3.3.12 | Interior elevations agree with plans on casework, fixtures, and accessory locations |
| 3.3.13 | Finish schedule covers every room appearing on plans, with consistent room numbers |
| 3.3.14 | Accessibility clearances at doors, fixtures, and turning spaces verified against plan dimensions |
| 3.3.15 | Exterior wall sections show continuous air, water, thermal, and vapor control layers with transitions detailed |
| 3.3.16 | Roof plan agrees with structural framing, slopes drain to the drains shown, and overflow provisions exist |
| 3.3.17 | Details referenced from plans and sections exist and depict the condition shown |
| 3.3.18 | Vertical alignment of shafts, stairs, and chases consistent across all levels |
| 3.3.19 | Casework and specialty schedules agree with plans and interior elevations |
| 3.3.20 | Signage, specialty, and equipment items have specification sections and mounting requirements |
Table 7. Mechanical and Plumbing Checks
| # | Check |
|---|---|
| 3.4.1 | Equipment schedules agree with plans in quantity, tag, size, and location |
| 3.4.2 | Equipment weights and dimensions stated, and coordinated with structural capacity |
| 3.4.3 | Electrical characteristics on equipment schedules agree with the electrical panel schedules in voltage, phase, and load |
| 3.4.4 | Airflow schedules agree with duct sizes and terminal device counts on plans |
| 3.4.5 | Ceiling space depth available per architectural sections accommodates the ductwork, piping, and structure shown |
| 3.4.6 | Equipment room layouts provide code and manufacturer service clearances |
| 3.4.7 | Access provisions defined for dampers, valves, terminal units, and concealed equipment |
| 3.4.8 | Rated assembly penetrations show dampers or firestopping consistent with the assembly rating |
| 3.4.9 | Roof penetrations and curbs coordinated with structural framing and the roof plan |
| 3.4.10 | Control sequences reference equipment that appears in the schedules |
| 3.4.11 | Hangers, supports, and seismic restraint requirements identified with delegated design criteria |
| 3.4.12 | Plumbing fixture schedule agrees with architectural plans and interior elevations |
| 3.4.13 | Pipe sizing consistent with fixture counts and demand shown |
| 3.4.14 | Invert elevations at the building line agree with civil |
| 3.4.15 | Floor drains, trench drains, and slab depressions coordinated with structural and architectural |
| 3.4.16 | Equipment pads and bases shown with dimensions and coordinated with structural |
| 3.4.17 | Medical gas, lab gas, and process piping systems have certification and verification requirements stated |
| 3.4.18 | Insulation extent on plans consistent with the specification requirements |
Table 8. Electrical, Fire Protection, and Low Voltage Checks
| # | Check |
|---|---|
| 3.5.1 | Panel schedules agree with the one-line diagram in capacity, feeder size, and designation |
| 3.5.2 | Connected loads on panel schedules reconcile with the equipment shown on mechanical and plumbing schedules |
| 3.5.3 | Device counts and locations agree between plans, panel schedules, and architectural elevations |
| 3.5.4 | Lighting fixture schedule agrees with the reflected ceiling plans in type and count |
| 3.5.5 | Fixture types compatible with the ceiling types they occur in |
| 3.5.6 | Emergency and standby circuits identified, with generator and transfer scheme consistent |
| 3.5.7 | Electrical room clearances meet working space requirements against architectural dimensions |
| 3.5.8 | Grounding and bonding requirements shown or referenced, with the extent defined |
| 3.5.9 | Fire alarm devices coordinated with reflected ceiling plans, and interfaces to mechanical shutdown defined |
| 3.5.10 | Fire alarm sequence of operations consistent with the mechanical control sequences |
| 3.5.11 | Sprinkler head layout coordinated with the reflected ceiling plans, including rated ceilings |
| 3.5.12 | Hazard classification consistent with occupancy and stored materials |
| 3.5.13 | Standpipe and fire department connection locations coordinated with egress and site access |
| 3.5.14 | Fire pump power, controls, and monitoring coordinated between electrical and fire protection |
| 3.5.15 | Low voltage pathway, backbox, and grounding requirements defined with a responsibility boundary |
| 3.5.16 | Communications and security device locations coordinated with architectural and door hardware |
| 3.5.17 | Equipment room power and cooling coordinated with mechanical |
| 3.5.18 | Owner-furnished equipment connection requirements defined |
Table 9. Specialty Systems Checks
| # | Check |
|---|---|
| 3.6.1 | Hoistway dimensions and tolerances stated and agree with architectural and structural |
| 3.6.2 | Elevator pit depth, sump, overhead clearance, and machine room requirements coordinated |
| 3.6.3 | Elevator power, lighting, cooling, communications, and fire alarm interface defined |
| 3.6.4 | Kitchen equipment schedule coordinated with mechanical exhaust, plumbing, and electrical |
| 3.6.5 | Grease exhaust routing, shaft rating, and rooftop termination coordinated |
| 3.6.6 | Laboratory casework, fume hood, and utility rough-in coordinated across disciplines |
| 3.6.7 | Fume hood exhaust, makeup air, and controls consistent between mechanical and lab documents |
| 3.6.8 | Process equipment foundations, supports, and utility connections coordinated with vendor documents where available |
| 3.6.9 | Generator pad, fuel, exhaust, cooling, and sound attenuation coordinated |
| 3.6.10 | Loading dock levelers, seals, and restraints coordinated with structural and electrical |
| 3.6.11 | Window washing anchors, roof tie-off points, and fall protection anchors shown with structural support |
| 3.6.12 | Lightning protection system coordinated with roofing and structural |
| EXPERT TIP If you can only run one block from Part 3 on a commercial building, run the architectural door checks, 3.3.3 through 3.3.6. Doors carry information that also appears in the wall type schedule, the hardware sets, the life safety plans, the electrical drawings for access control, and the finish schedule. On a set with 300 openings I have never seen fewer than a dozen findings, and several are usually rating or egress issues at severity 1. |
Part 4: Cross-Discipline Pair Checks
Run each pair as a deliberate batch and review the results together. The pattern across ten findings is usually more valuable than the ten individual comments, because it typically reveals that one consultant worked from a superseded background.
Table 10. Cross-Discipline Pair Checks
| # | Pair | Verify |
|---|---|---|
| 4.1 | Architectural to structural | Gridlines, floor elevations, slab edges and depressions, openings, shaft and stair enclosure dimensions, expansion joints |
| 4.2 | Mechanical to structural | Equipment weights against capacity, roof curbs against framing, openings and sleeves, hanger attachment, penetration limits |
| 4.3 | Mechanical to electrical | Voltage, phase, and connected load agreement; disconnect locations; control power; motor data |
| 4.4 | Mechanical to architectural | Ceiling space depth, equipment room clearances, louver and grille locations, access provisions, rated penetrations |
| 4.5 | Plumbing to structural | Sleeves and penetrations, slab depressions, chase dimensions, equipment pads, invert clearances at footings |
| 4.6 | Plumbing to architectural | Fixture locations against plans and elevations, floor drain locations against finishes and slopes |
| 4.7 | Electrical to architectural | Device and panel locations against wall types and casework, fixture types against ceiling types, room clearances |
| 4.8 | Fire protection to architectural | Head layout against reflected ceiling plans, rated assembly penetrations, concealed versus exposed conditions |
| 4.9 | Fire protection to structural | Attachment to structure, standpipe openings, seismic bracing provisions |
| 4.10 | Civil to architectural and structural | Floor elevation to finished grade, accessible routes, utility entry points, foundation clearances |
| 4.11 | All disciplines to life safety plans | Rated assembly continuity, egress width and path, smoke compartmentation, and every penetration of each |
| 4.12 | All disciplines to reflected ceiling plans | Every ceiling-mounted element from every discipline present without conflict |
| 4.13 | All disciplines to the roof plan | Curbs, supports, penetrations, walkway pads, anchors, equipment, and their flashing conditions |
| 4.14 | Vertical transportation to all | Hoistway, pit, overhead, machine room, power, cooling, and fire alarm interface |
| 4.15 | Specifications to all disciplines | Requirements stated in one discipline’s specification that another discipline’s drawings must accommodate |
Checks 4.11 through 4.13 are consolidation checks rather than pair checks, and they are among the most productive on the list. Reflected ceiling plans and roof plans both concentrate elements from five or six disciplines onto one plane, which makes them the highest-density coordination surfaces in the set.
Part 5: Specification Correlation Checks
Four defect classes, each requiring a different direction of reading. This is the part most often skipped and one of the two most productive.
Table 11. Specification Correlation Checks
| # | Direction | Check | High-Yield Targets |
|---|---|---|---|
| 5.1 | Specified not drawn | Requirements in the specifications with no graphical representation | Hangers and supports, seismic restraint, grounding and bonding, insulation extent, firestopping locations, testing and balancing, commissioning participation, special inspections |
| 5.2 | Drawn not specified | Items on drawings with no governing specification section | Specialty items on architectural details, site features on civil and landscape, anything added by addendum |
| 5.3 | Conflicting instruction | Drawings and specifications both address the item and disagree | Fastening and attachment methods, insulation thickness, finish levels and tolerances, product substitution language |
| 5.4 | Missing detail reference | Notes or specification paragraphs referring to content that does not exist | Delegated design criteria, load bases, referenced schedules, referenced details |
| 5.5 | Delegated design completeness | Every trigger states performance criteria, load basis, submittal requirement, and inspection requirement | Framing over height limits, mechanical and plumbing restraint, sprinkler layout, curtain wall, precast, handrails, ceiling suspension, equipment anchorage |
| 5.6 | Standards enforceability | Referenced standards paired with an acceptance criterion and an inspecting party | “Per manufacturer’s recommendations,” “industry standard,” “as directed” |
| 5.7 | Product availability and lead time | Specified products currently available and compatible with the schedule | Sole-source items, long-lead equipment, proprietary systems |
| 5.8 | Testing and inspection allocation | Every required test and inspection has a responsible party and a cost basis | Special inspections, third-party testing, retesting after failure |
| 5.9 | Division 01 requirements traceable | General requirements obligations appear where the affected work is described | Temporary facilities, cleaning, hoisting, waste, closeout, commissioning |
| 5.10 | Specification internal consistency | Part 2 products consistent with part 3 execution; no product specified twice differently | Sections revised at different times |
| BEST PRACTICE Run 5.1 against the ten targets listed rather than attempting comprehensive correlation on a first pass. Those ten account for the large majority of specified-not-drawn exposure on commercial work, and they can be checked in a day. Comprehensive correlation on a full project manual is a multi-week exercise that most teams will abandon partway through, which is worse than a focused pass completed. |
Part 6: Constructability Checks by Building Area
Organized by area rather than by discipline, because constructability problems are spatial and sequential. Walk each area with a superintendent and the relevant trade foremen.
Table 12. Constructability Checks by Area
| Area | Checks |
|---|---|
| Below grade and foundations | Excavation limits against property lines and adjacent structures; shoring and underpinning requirements; dewatering; waterproofing sequence and access; utility crossings at footings; backfill access |
| Structural frame | Erection sequence and crane access; connection access for bolting and welding; temporary bracing; camber and tolerance accumulation; deck edge and safety anchorage |
| Exterior wall and enclosure | Installation sequence against structural tolerance; access for installation and sealing; transition detail buildability at corners, heads, sills, and interfaces; scaffold or swing stage access; weather sequencing against enclosure milestones |
| Roof | Sequence of curbs, penetrations, equipment, and membrane; crane picks and staging; walkway and access provisions; flashing buildability at congested penetrations; warranty inspection hold points |
| Ceiling plenums and corridors | Installation clearance versus finished clearance; order of installation among duct, pipe, conduit, and sprinkler; access for future service; whether the drawn arrangement can be lifted into place |
| Mechanical and electrical rooms | Equipment delivery path and door and opening sizes; rigging access; service and code clearances; pipe and conduit routing without blocking access; future equipment replacement path |
| Shafts and chases | Dimension adequacy for the systems shown plus insulation and supports; access for installation and inspection; rated enclosure continuity and penetration sequence |
| Interior partitions and finishes | Blocking and backing coordination before closure; substrate acceptance sequence; tolerance interfaces at casework and equipment; rated assembly closure sequence |
| Vertical transportation | Hoistway tolerance achievability; delivery and installation access; temporary use provisions and protection |
| Site and exterior works | Phasing against occupancy and traffic; laydown and access; utility tie-in outage windows; restoration sequence |
| Occupied and phased areas | Interim life safety measures; temporary partitions and infection control where applicable; noise, vibration, and outage constraints; temporary system provisions |
| Commissioning and startup | System completeness required for functional testing; seasonal testing windows against the schedule; access for testing and adjustment |
Two questions to ask repeatedly during the walkthrough. How would your crew actually install this? And what has to be finished before you can start, and does the schedule allow it? Closed sequence loops, where trade A must precede trade B and B must precede A, are more common than people expect and almost never visible in a model.
Part 7: Code, Life Safety, and Regulatory Checks
A contractor is not the code official and should not present itself as one. The value here is flagging apparent noncompliance and, more importantly, conditions where the local jurisdiction’s known interpretation differs from what is drawn.
Table 13. Code and Regulatory Checks
| # | Check |
|---|---|
| 7.1 | Occupancy classification and construction type stated and consistent across the set |
| 7.2 | Egress widths, travel distances, common path, and dead-end limits verified against plan dimensions |
| 7.3 | Rated assembly continuity from floor to structure above, including at head-of-wall and through plenums |
| 7.4 | Every penetration of a rated assembly shows an appropriate damper or firestop condition |
| 7.5 | Smoke compartmentation and smoke control provisions consistent between architectural, mechanical, and fire alarm documents |
| 7.6 | Stair and elevator pressurization consistent between mechanical and life safety documents |
| 7.7 | Accessibility clearances, reach ranges, slopes, and routes verified dimensionally |
| 7.8 | Accessible unit or room counts and distribution match the requirement |
| 7.9 | Energy compliance path stated, with envelope continuity and equipment efficiency consistent with it |
| 7.10 | Deferred submittals identified and consistent with jurisdictional requirements |
| 7.11 | Special inspections identified and consistent between drawings and specifications |
| 7.12 | Alternative means and methods items identified where the design departs from prescriptive requirements |
| 7.13 | Local amendments and known AHJ interpretations reflected in the documents |
| 7.14 | Permit sequencing and phased permit requirements addressed where the schedule assumes them |
| 7.15 | Utility company requirements and standards reflected at service points |
Check 7.13 is where a local contractor adds value a design team working outside its home market cannot. AHJ interpretation varies substantially, particularly on smoke compartmentation, rated assembly continuity, and accessibility in renovation work.
Part 8: Comment Quality Checks
Run this on your own comment log before submitting. It is short and it determines whether the review has any effect.
Table 14. Comment Quality Checks
| # | Check | Why |
|---|---|---|
| 8.1 | Every comment cites a sheet or specification section and a location on it | An unlocatable comment gets dismissed |
| 8.2 | Every comment describes the condition factually, not the desired solution | Preserves the design professional’s authority and avoids assuming design liability |
| 8.3 | Suggested resolutions, where offered, are marked as suggestions and separated from the condition | Helpful without directing design |
| 8.4 | Every comment has a category and a severity | Category tells the consultant who resolves it; severity tells them when |
| 8.5 | Severity 1 and 2 comments are separated from clerical batches in the submission | Prevents critical findings from being buried |
| 8.6 | No duplicate comments describing the same condition from multiple reviewers | Duplicates inflate the count and irritate the recipient |
| 8.7 | Comments verified against the current revision before submission | Submitting a comment already resolved costs credibility |
| 8.8 | No comment is a matter of preference presented as a defect | The fastest way to have the entire log discounted |
| 8.9 | Comments requiring only information are labeled as clarifications, not errors | Different response type; different urgency |
| 8.10 | Prior milestone comments are cross-referenced where the condition persists | Makes recurrence visible |
| 8.11 | The log states the total, the severity distribution, and which lanes were run | Makes coverage auditable |
| 8.12 | Comments unresolved at bid are each converted to an RFI, a proposal qualification, or a priced contingency | Open comments are unpriced risk |
| COMMON MISTAKE Check 8.8 is the one that quietly destroys review programs. A log containing preference comments, meaning things the reviewer would have designed differently but which are not defects, trains the design team to treat the entire submission as opinion. One or two of those in a log of ninety is enough to change how the next log is read. |
Importance: What the Checklist Is Preventing
Design errors and omissions on commercial building work generally account for somewhere between two and six percent of construction cost, with document-related rework making up a substantial share. Rather than adopting any published figure, run the arithmetic on your own history: pull the last three completed projects, categorize the change orders and early RFIs by cause, and count how many trace to something a careful reader could have found.
Most teams that do this find the dominant categories are unremarkable. Missing details. Dimensional conflicts. Schedules disagreeing with plans. Specification requirements never drawn. Conditions that could not be built in the sequence the schedule demanded. Every one of those has a check on this list.
The second effect is on the design relationship, and it runs in whichever direction your comment quality sends it. A log of 400 comments, mostly clerical and some wrong, teaches an architect to skim the next one. A log of 90 specific, correctly located, properly categorized findings gets read carefully and incorporated. Part 8 exists because that difference compounds across a project and across a career.
Stakeholders
Table 15. Who Runs Which Part
| Part | Owner | Contributors | Approver |
|---|---|---|---|
| 1, Set integrity | VDC or document control | Preconstruction | Preconstruction manager |
| 2, Universal sheet checks | Project engineer | Any reviewer | Preconstruction manager |
| 3, Discipline checks | Discipline-experienced reviewer per block | Estimating, trade partners | Preconstruction manager |
| 4, Cross-discipline pairs | VDC or BIM manager | Trade partners, superintendent | Project manager |
| 5, Specification correlation | Preconstruction manager | Estimating, project engineer | Preconstruction manager |
| 6, Constructability by area | Superintendent | Trade foremen, VDC | Project manager |
| 7, Code and regulatory | Project manager | Code consultant where warranted | Project executive |
| 8, Comment quality | Comment log owner | All reviewers | Preconstruction manager |
The superintendent owning Part 6 and trade foremen contributing to Parts 3, 4, and 6 is deliberate. Installation questions require installation experience, and on negotiated or CMAR delivery, involving key trades during design is the single most underused advantage that delivery method provides.
Required Documentation
Table 16. Documents Required to Run This Checklist
| Document | Parts It Supports | Consequence If Absent |
|---|---|---|
| Complete drawing set with sheet-level revisions | All | Findings cannot be located or defended |
| Drawing list and sheet index | 1 | Missing sheets undetectable |
| Complete project manual | 3, 5, 7 | Part 5 impossible; much of Part 3 unverifiable |
| Addenda and bulletins with affected content identified | 1, 4 | Review describes a set that no longer exists |
| Life safety and code plans | 4, 7 | Highest-severity checks unsupported |
| Federated model where available | 4, 6 | Spatial coordination unverified |
| Project schedule | 6 | Sequencing checks have no basis |
| Site logistics plan | 6 | Access and phasing checks unsupported |
| Geotechnical report | 3.1, 3.2, 6 | Foundation and earthwork conditions unchecked |
| Prior milestone comment log | 8 | No recurrence tracking; comments repeat |
| Local amendments and AHJ interpretations | 7 | Jurisdictional exposure invisible |
| Owner program and equipment criteria | 3, 6 | Cannot verify design against requirement |
| Vendor documents for process or specialty equipment | 3.6, 6 | Specialty coordination unverifiable |
Technology Integration
Table 17. Checklist Execution by Method
| Part | PDF Markup | Collaboration Platform with Issue Tracking | Model Coordination | Document Search and AI Interrogation |
|---|---|---|---|---|
| 1, Set integrity | Manual, tedious | Better; markup tied to a log | Version control only | Automated indexing and dead reference detection |
| 2, Universal checks | Manual | Manual | Partial | Partial |
| 3, Discipline checks | Manual | Manual | Schedule and parameter validation | Retrieval for comparison; judgment stays human |
| 4, Cross-discipline pairs | Very difficult | Difficult | Strong on spatial only | Strong on informational pairs |
| 5, Specification correlation | Very difficult; usually skipped | Difficult | Not supported | Strong; this is the largest gain |
| 6, Constructability by area | Not applicable | Not applicable | Supports visualization | Not supported |
| 7, Code and regulatory | Manual | Manual | Partial on geometry | Retrieval of code references only |
| 8, Comment quality | Manual | Supported by log structure | Not applicable | Partial |
Parts 6 and 7 are barely supported by any technology, and they carry the highest-severity findings. That is worth saying plainly, because it argues against reducing reviewer hours when tooling is introduced. Redirect the hours instead.
Part 5 is where the picture changes most. Comparing a 1,200 page project manual against a 400 sheet drawing set in both directions is a volume problem, which is why it is the part most often skipped, and volume problems are the ones automation solves.
AI-Assisted Opportunities
The structural constraint on drawing review is that a commercial document set is too large to read exhaustively in the available window. Every team samples. Most sample implicitly, shaped by discipline habit, which is exactly why Parts 4 and 5 receive the thinnest coverage.
Conversational AI over the document set addresses that. Platforms built for construction documents, iFieldSmart AI among them, index every sheet and specification section, extract each note with its exact location on the drawing, and let a reviewer interrogate the full corpus. A reviewer asks which specification sections are cited on drawings but missing from the project manual, or which notes reference details that do not exist, or where equipment weights appear so they can be compared against structural capacity, and receives a sourced answer that links back to the drawing location.
That capability does not perform the review. It answers questions about the documents at a completeness no reviewer can match, which converts Parts 1, 4 informational, and 5 from sampled to comprehensive and leaves the judgment where it belongs.
Table 18. Checklist Parts Mapped to AI Capability
| Part or Check | AI Contribution | What Still Requires You |
|---|---|---|
| 1, Set integrity | Sheet indexing, revision differencing, dead reference detection across the full set | Confirming the set is what the owner issued |
| 1.7, Specification citations | Verifies every cited section exists | Judging consequence of missing sections |
| 3, Schedule-to-plan checks | Retrieves scheduled items and plan references for comparison | Judging which is correct |
| 4.2 to 4.3, Informational pairs | Surfaces equipment weights, voltages, loads, and clearances across disciplines | Judging adequacy and materiality |
| 4, Spatial pairs | Not addressed; use model coordination | All of it |
| 5.1, Specified not drawn | Compares specification requirements against drawing representation | Materiality and cost exposure |
| 5.2, Drawn not specified | Identifies drawn items with no governing section | Getting a section or stating the standard |
| 5.3, Conflicting instruction | Flags where both address an item differently | Which should govern |
| 5.4, Missing detail reference | Detects callouts pointing to nonexistent content | Judging consequence |
| 5.5, Delegated design | Detects triggers and whether criteria are stated | Assigning engineering, submittal, inspection |
| 6, Constructability | Retrieves conditions by keyword for review only | All judgment |
| 7, Code and regulatory | Retrieves code references and inspection requirements | All interpretation |
| 8, Comment log | Drafts comment text with location and source citation | Category, severity, and every judgment |
| LESSONS LEARNED Teams that get the most from document interrogation are the ones who ran this checklist manually first and know which checks matter in their market. Tooling multiplies existing discipline. Applied to a team without a review process it produces a large volume of retrieved information nobody converts into comments, which is less useful than a short focused review somebody actually completed. |
Implementation
- Run Part 1 on your next set received. Half a day, no preparation, and the dead reference count alone will tell you how much scrutiny the rest of the set needs.
- Assign Part 3 blocks to named individuals by discipline. Not to the team. A block owned by everyone is checked by nobody.
- Customize Part 3 to your market and project types. Go through the blocks with your two most experienced people and mark which checks have actually produced findings for you. Add what is missing.
- Add Part 5 with the ten targets from check 5.1 only. Resist comprehensiveness on the first pass.
- Schedule Part 6 as a meeting. A constructability walkthrough with a superintendent and three trade foremen, with a defined area list and an agenda, produces more than any number of open invitations to comment.
- Adopt Part 8 immediately and without exception. It costs twenty minutes per submission and it determines whether anything else on the list has an effect.
- Institute backcheck against the prior comment log, using check 8.10 to make recurrence visible.
- At closeout, map every document-related change order and early RFI back to a check on this list. Add what is missing, remove what never produces findings.
Table 19. Implementation Roadmap
| Phase | Weeks | Activities | Deliverable | Gate |
|---|---|---|---|---|
| Baseline | 1 to 3 | Categorize past change orders and early RFIs against checklist parts | Defect profile by part | Weakest parts identified |
| Assign | 3 to 4 | Name owners for each Part 3 block and each of Parts 1, 4 to 8 | Review assignment matrix | Every part has a named owner |
| Customize | 4 to 6 | Senior reviewers mark productive checks; add local patterns | Customized checklist v1 | Signed off by preconstruction |
| Pilot Part 5 | 6 to 10 | Run check 5.1 against the ten targets on a live set | Correlation findings | Part 5 run on a live project |
| Pilot Part 6 | 8 to 10 | Constructability walkthrough with superintendent and trades | Constructability findings | Walkthrough held with an agenda |
| Comment discipline | 6 to 12 | Part 8 applied to every submission; log format standardized | Standard comment log | Design team accepting the format |
| Backcheck | 12 to 18 | Recurrence tracking; resolution rate reported | Resolution rate at each milestone | Two milestones with backcheck |
| Improve | Ongoing | Closeout mapping; annual revision | Annual checklist revision | Two consecutive retrospectives |
Best Practices
Table 20. Checklist Discipline Best Practices
| Practice | Why |
|---|---|
| Run Part 1 before anyone reads for content | Protects reviewer attention and calibrates the rest of the review |
| Assign discipline blocks to named individuals | Shared ownership means no ownership |
| Use reviewers who have built the work | Discipline checks require installation experience, not familiarity |
| Review cross-discipline pairs as batches | Patterns reveal root causes that individual comments hide |
| Start Part 5 with the ten targets, not comprehensively | A completed focused pass beats an abandoned exhaustive one |
| Schedule constructability as a meeting with an agenda and an area list | Open invitations produce nothing |
| Bring trade foremen into Parts 3, 4, and 6 wherever delivery permits | They see what no office reviewer sees |
| Bring local code knowledge to Part 7 | AHJ interpretation varies and outside design teams often lack it |
| Apply Part 8 to every submission without exception | Determines whether the review has any effect at all |
| Batch clerical findings separately from severity 1 and 2 | Protects the credibility of the findings that matter |
| Cross-reference persisting comments from the prior milestone | Makes recurrence visible and holds the design team to dispositions |
| Convert every open comment at bid into an RFI, qualification, or contingency | Open comments are unpriced risk |
| Map closeout findings back to checks annually | The only mechanism by which the list improves |
Common Mistakes
Table 21. Common Checklist Failures
| Mistake | Consequence | Fix |
|---|---|---|
| Using a generic checklist without customization | False findings erode trust; real patterns still missed | Customize Part 3 with senior reviewers |
| Running the checklist before set integrity is confirmed | Findings against superseded sheets | Part 1 as a gate |
| One reviewer running all of Part 3 | Two blocks done well, the rest superficially | Distribute by discipline competency |
| Skipping Part 5 | The highest-yield part produces nothing | Start with the ten targets in 5.1 |
| Constructability reviewed in the office | Access, sequence, and tolerance findings missed | Walkthrough with superintendent and trades |
| Treating model coordination as sufficient for Part 4 | Informational conflicts missed entirely | Run the informational pairs separately |
| Submitting everything found | Design team discounts the whole log | Batch by severity; apply Part 8 |
| Preference comments presented as defects | Entire submission read as opinion | Check 8.8, enforced |
| Writing solutions instead of conditions | Assumes design liability; consultant resists | Check 8.2, enforced |
| No backcheck against prior comments | Same findings recur for three milestones | Check 8.10 plus a resolution rate |
| Comments left open at bid | Risk enters construction unpriced | Check 8.12, enforced |
| Never revising the checklist | Same defects recur; the list becomes a ritual | Annual revision from closeout data |
Applied Examples
Class A office tower, 340,000 square feet, core and shell. Check 4.2 produced the finding that mattered. Rooftop unit weights had grown through design development and the penthouse framing still reflected the earlier schedule. At 90 percent construction documents it was a framing revision. After fabrication release it becomes a long-lead schedule event.
Regional hospital expansion, 190 beds, occupied campus. Checks 7.3, 7.4, and 7.13 together. Rated corridor assemblies showed mechanical penetrations without dampers on two levels, and the jurisdiction’s interpretation of smoke compartmentation at the connector to the existing building differed from what was drawn. Both raised at design development, when they were drawing revisions rather than inspection failures gating occupancy.
Hyperscale data center, 60 MW. Check 5.1 justified the entire review. Seismic restraint and hanger support engineering for mechanical and electrical distribution appeared in the specifications with no drawing representation, carrying delegated engineering, a deferred submittal, and a special inspection. At that equipment density the exposure was substantial and entirely invisible to anyone reviewing drawings alone.
Advanced manufacturing facility, food grade. Part 6, ceiling plenums and shafts, with the panel installer present. The hygienic wall panel system required installation before overhead process piping, and the piping needed support from structure the panels concealed. A closed sequence loop, invisible in the model, obvious to the installer in four minutes.
University science building, 11 floors. Checks 3.3.3 through 3.3.6. The door schedule listed 61 openings with hardware sets inconsistent with the rated assemblies on the life safety plans, and 14 openings appeared on plans but not in the schedule. This is the most productive single block in Part 3 and this set was typical rather than exceptional.
Multifamily podium, 240 units. Checks 1.3 and 2.14. Two unit type plans were revised by addendum while the corresponding enlarged plans and interior elevations were not, leaving three versions of one bathroom in the set. On repetitive residential work an unresolved unit type conflict multiplies by the unit count, which makes Part 1 unusually valuable there.
Highway interchange, design-bid-build. Checks 3.1.4 and 4.10. Conduit shown on the signal plans conflicted in depth with drainage structure inverts on the civil plans. Found in review it is a coordination revision. Found during trenching it is a stop-work with traffic control implications.
Historic warehouse to hotel, 140 keys. Part 6, below grade and existing conditions, plus check 3.3.17. New mechanical distribution ran through an existing structural bay whose field-measured clear dimension was three inches tighter than the record drawings the design team had used. Focusing on Reuse Course Defects, Verification is best placed within review rather than after it, as Adaptive Reuse will concentrate these issues.
Frequently Asked Questions
How long does this checklist take on a commercial project?
For a 90 percent construction document review of a 300 to 500 sheet set, budget 80 to 160 person-hours across all parts and several reviewers, spread over three to four weeks of calendar time. Part 1 is half a day. Part 3 is 30 to 60 hours distributed across disciplines. Part 5 is 20 to 40 hours done properly, or about a day if limited to the ten targets. Part 6 is a half-day walkthrough plus preparation. Part 8 is twenty minutes per submission.
Which checks should we adopt first if we can only do some?
Part 1 entirely, the architectural door checks 3.3.3 through 3.3.6, cross-discipline pairs 4.2 and 4.11, check 5.1 limited to the ten targets, and all of Part 8. That combination is roughly two days on a mid-size set and it covers set integrity, the most productive single-discipline block, the highest-severity coordination pair, the life safety consolidation check, the highest-yield correlation direction, and the comment discipline that makes any of it matter.
How is this different from a scope gap analysis checklist?
Different question about the same documents. A gap analysis checklist asks who is contractually responsible for each obligation. This checklist asks whether the documents are correct, complete, coordinated, and buildable. A set can be perfectly assigned and full of dimensional conflicts, or perfectly coordinated with half its obligations unassigned. Both reviews are necessary and neither substitutes for the other.
Is this appropriate for small projects?
Yes, scaled. Under ten million dollars, run Part 1, the relevant Part 3 blocks for the disciplines actually present, pairs 4.2 and 4.11, check 5.1 on the ten targets, and Part 8. That is perhaps a day and a half. Small projects carry less contingency to absorb document defects, which makes the review more valuable per dollar of fee, not less.
How do we adapt this for renovation and adaptive reuse?
Three changes. Add existing conditions verification throughout Part 3, because record drawings are frequently wrong and field measurement belongs inside the review. Emphasize Part 6 below grade and existing conditions heavily, since that is where the defects concentrate. And add a specific check for “match existing” and “field verify” language, which proliferates on renovation documents and defines nothing.
Should we share findings with the design team as we go or in one submission?
Both, at different severities. Severity 1 findings should go immediately by phone and then in writing, because waiting to batch a life safety issue serves nobody. Everything else goes in a scheduled submission at the milestone, batched by severity. Continuous informal commenting is difficult for a design team to track and produces no auditable record.
Does using this checklist increase our liability?
This is worth confirming with your own counsel, since it varies by jurisdiction and contract form. Generally, contractors under standard forms have a duty to report discovered discrepancies and do not assume design responsibility by reviewing documents. What can create exposure is directing a design solution rather than reporting a condition, which is precisely why check 8.2 exists. Describe the condition; let the design professional resolve it.
What if the design team ignores our comments?
Track the disposition rate and the resolution rate at backcheck, and report both to the owner if they stay low. A design team that declines to disposition comments is creating documented risk on the owner’s project, and that is an owner conversation rather than a contractor grievance. For unresolved severity 1 findings on life safety or structural adequacy, escalate in writing rather than absorbing them.
How many findings should this checklist produce?
At 90 percent construction documents, 40 to 120 comments per 100 sheets is a reasonable band, with 15 to 30 percent at severity 1 or 2. Below about 30 per 100 sheets usually means the review was shallow. Above 200 usually means clerical padding, which costs credibility. The severity distribution matters more than the total.
Can this be run against a model-only delivery?
Most of it, with method changes. Part 1 becomes model version and federation control. Part 3 becomes schedule and parameter validation against modeled geometry. Part 4 spatial checks are well served by coordination, and the informational checks remain manual because they involve parameters and specifications rather than geometry. Parts 6 and 7 are unchanged. Part 5 is unchanged and remains the hardest, because specifications are documents regardless of how geometry is delivered.
How should addenda during construction be checked?
Difference the revision against the prior issue to identify what changed, then rerun the relevant Part 4 pairs on the changed content only. An hour or two per addendum. Revisions issued to fix one condition create new coordination conflicts often enough that this should be routine rather than exceptional.
What is the single most commonly missed check across all commercial projects?
Check 5.1, specified not drawn, particularly for hangers, supports, and seismic restraint. It sits in specification text with no drawing representation, it carries delegated engineering and special inspection, and estimators quantifying from drawings never see it. Second would be check 4.11, the life safety consolidation check, because rated assembly continuity and its penetrations span every discipline and belong to no single reviewer.
How do we keep this list from growing until nobody uses it?
Prune it annually using closeout data. Any check that has produced no findings across several projects comes off, and anything discovered in the field goes on. A checklist that only grows becomes a ritual. The target is a list where most checks have earned their place by catching something.
Expert Recommendations
Assign every Part 3 block to a named individual before your next set arrives. Shared ownership is the most common reason discipline checks go unrun, and it costs nothing to fix.
Run Part 1 on the next set you receive and report the dead reference count to your project executive. It is a single number, it takes half a day to produce, and it predicts how much trouble the rest of the review will find.
Limit your first Part 5 attempt to the ten targets in check 5.1. Teams that attempt comprehensive correlation abandon it around the fourth division and conclude the exercise does not work.
Schedule the constructability walkthrough as a meeting with an area list and an agenda, and let the superintendent run it. Ask the trades one question repeatedly: how would your crew actually install this?
Enforce Part 8 without exception, especially check 8.8. One preference comment in a log of ninety is enough to have the entire submission read as opinion rather than as findings.
Report the resolution rate at backcheck at every milestone. It is the only number that measures whether the review changed the documents, as opposed to measuring how much reading happened.
Prune the list annually from closeout data. Checks that never produce findings should come off, and every field-discovered defect should go on with a note about why it was missed.
Using This From Here
A checklist for drawing review is not a substitute for judgment. It is a way of making sure judgment gets applied to the right places, including the places a reviewer would not naturally look, which on a document set means anything outside their own discipline.
The two parts that separate strong review teams from average ones are specification correlation and constructability. Both get skipped for the same structural reason, which is that neither has an obvious owner. Correlation requires someone to read a project manual, constructability requires someone to leave the office, and neither is anyone’s job by default. Assign both explicitly and most of the value on this list follows.
Take it, cut the checks that do not apply to your work, assign the blocks by name, and run Part 1 on the next set that arrives. Then add whatever you find in the field to the bottom of it. Within three projects it will describe your market better than any list you could have bought.