Construction Documents Checklist For Architects

CDs don't have to be a nightmare if you actually organize them

I still remember the project that made me build my first real checklist. It was a mid-rise mixed-use building somewhere in New Jersey, and the plan review came back with comments that made it look like I'd never drawn a door before. Missing hardware schedules, no fire-rated wall details, a structural connection detail that was just a placeholder saying "see architect." The consultant coordination had completely fallen through the cracks because nobody had a single place to verify that all the pieces were accounted for. That project cost me three weeks of rework and a lot of bad relationships. I built a spreadsheet after that. It eventually became this. A construction documents checklist is simply a systematic verification tool that ensures every required drawing, specification section, schedule, and note exists before you stamp and issue. It's not a philosophical concept. It's a practical quality gate. Without one, you're relying on memory, which fails. With one, you're relying on a system that catches the things you miss.

What goes into a Construction Documents Checklist For Architects

Here's how I actually run through this on a project. The list I use covers roughly 200 to 400 line items depending on project size. For a small commercial job it's maybe two hundred. For a hospital or a university project it easily climbs past four hundred. The breakdown usually looks like this: The title page and cover sheet section checks for project name, address, owner contact information, drawing index, general notes, symbol legends, and the seal block. You'd be surprised how often the seal block is missing or has the wrong project number. The zoning and site planning set verifies setback calculations, parking stall counts, accessibility routes, landscape requirements, stormwater management notes, utility connections, and grading plans. This is where I catch things most often because the landscape architect and civil engineer sometimes deliver their work independently and something gets lost in the handoff.

The architectural drawings themselves are the big chunk. Floor plans, reflected ceiling plans, interior and exterior elevations, building sections, and wall sections. Each of these needs to cross-reference the others. If a ceiling height shown on the reflected ceiling plan doesn't match the building section, that's a red flag. I check the door and window schedules against the floor plans to make sure every opening is accounted for. A single unchecked door that appears on a plan but not on the schedule is a classic gap that shows up during construction and costs real money to fix. Specifier and specification sections get their own review pass. Every spec section should have a corresponding G-codes or CSI MasterFormat number, a title, a scope statement, and products and methods sections. Missing product substitutions clauses is another common problem. I've had spec sections that specified exact manufacturers without allowing equivalent products, which means the contractor has no way to value-engineer and the whole project stalls when that product goes obsolete. Structural coordination is where independent structural drawings intersect with architectural intent. Column locations on the structural plan must align with what's shown on the architectural floor plan. Beam depths affect ceiling heights. Fire-rated assemblies need both architectural and structural verification. I once had a structural engineer specify a steel beam that was deeper than the architectural ceiling detail allowed. The MEP coordinator caught it during shop drawing review, but it should have been caught at the CD stage. The workaround I used was a simple overlay check. I superimposed the structural framing plan over the architectural ceiling plan at the same scale and walked through every beam location against every ceiling zone. Took about twenty minutes and caught six conflicts.

MEP coordination is perhaps the most painful part of this process. Mechanical, electrical, and plumbing drawings need to be checked against the architectural spaces. Are there enough light switches for the circuit layout? Is there clearance around the HVAC equipment shown on the mechanical plan? Are the electrical panels accessible? Are the plumbing stacks aligned with the fixture layouts? I run a specific check where I print the floor plan at 1/4 inch scale and trace over it with colored markers for each discipline. Mechanical in blue, electrical in red, plumbing in green. The overlaps reveal conflicts immediately. It's an old trick and it still works because it's visual. Sustainability and energy compliance documentation is now a required part of this on most projects. LEED certification paths, ENERGY STAR compliance, local energy code verifications. These need to be explicitly noted on the drawings. I've seen projects where the energy model was done but no one put the results on the plan set. The contractor built to code but the owner couldn't get the certification because the documentation wasn't tied to the construction drawings. Accessibility compliance is non-negotiable and it's where most people get sloppy. I check every accessible route against the floor plan, every restroom layout against the ADA checklist, every sign height and placement requirement. The trick here is to verify not just what's drawn but what's implied by the drawing. A hallway might look wide enough on paper but the door swings could reduce the clear width below the required twenty-four inches. That's the kind of thing that shows up during the accessibility review and causes change orders.

How to actually implement this without it becoming useless paperwork

The biggest problem I see with construction documents checklists is that people create them and then never update them. A static checklist dies within a year. My version has been updated on roughly every other project for the past twelve years. Each project adds items I discover are necessary. I keep a running log of plan review comments and submittal returns. Every comment that says "detail missing" or "schedule incomplete" gets added to the checklist as a permanent item. That's how it stays useful. Another practical issue is who owns the checklist. On my projects, I assign it to the project architect of record but also require each discipline lead to mark off their own sections. It's not enough for one person to go through the entire thing. The structural engineer needs to verify the structural section. The MEP engineer needs to verify their coordination. I send the checklist to each consultant as a separate file with only their relevant section highlighted. It usually takes them about fifteen to thirty minutes to complete, depending on project complexity. The timeline matters. I recommend completing the checklist at the 60 percent design review milestone, not at the final CD stage. At 60 percent, changes are still cheap. Catching a missing detail at 60 percent means adding a drawing. Catching it at 90 percent means redoing three other sheets because the missing detail affects something else. This is the single most important timing decision for this whole process. If you only do the checklist at the end, you're not really doing a checklist. You're doing a last-minute panic audit.

There's also a digital component now that I wish I had known about earlier. Using BIM-based clash detection tools like Navisworks or even just coordinated Revit models can automate a significant portion of this checklist. The software can generate conflict reports between disciplines. But here's the reality check: automated tools miss things that a human eyeball catches. The software won't tell you that a door swing violates an egress path. It won't notice that the fire rating on a wall assembly is inconsistent between the floor plan and the section. Use the digital tools for volume work but never skip the manual review. The manual review is where you catch the semantic errors, not the geometric ones. Another thing nobody talks about is the difference between a checklist and a quality control process. A checklist is a list. Quality control is a process. The list is just one tool in that process. The process includes: design development review with all disciplines present, peer review by someone who wasn't involved in the design, client review with written sign-off, and the final checklist verification. Skipping any of those steps increases the chance of errors going undetected. The checklist catches omissions. The other steps catch mistakes.

Where this approach breaks down and what to do instead

A construction documents checklist For Architects has clear limitations. It cannot catch errors that require domain expertise in another discipline. If your structural engineer has designed a beam that's undersized, your checklist won't flag that. That requires a separate structural review, usually by the structural engineer or an independent reviewer depending on jurisdiction. The checklist catches missing items and coordination gaps, not design adequacy. It also becomes less effective on fast-track projects. When the schedule is compressed and design and construction documents overlap significantly, there's no time to run a full checklist at 60 percent because there may not be a 60 percent milestone. In those cases, the practical workaround is to break the checklist into phases. Run a partial checklist at schematic design to lock the big items: square footage, room names, access routes, fire ratings. Run another partial at design development to lock the medium items: door and window schedules, material selections, fixture types. Run the full checklist at the final stage for everything else. This is less elegant but it's the reality of fast-track delivery. Small firms sometimes skip checklists entirely because they think it's overhead that only large firms need. This is wrong. Small firms actually benefit more because they have fewer staff to catch each other's mistakes. A checklist is literally a second pair of eyes that you always have available, regardless of how many people are on the project. For a ten-person firm, a well-maintained checklist probably saves more time than it costs.

As for a download link, I'm not going to host one directly here. What I can tell you is that most professional organizations like the AIA and NCARB provide sample document checklists in their practice guides. The AIA's practice management resources have a solid starting template. From there, you adapt it to your office's project types and your jurisdiction's specific requirements. The checklist I referenced earlier in this post is proprietary to my practice and I don't share it publicly, but the structure is what I've described above. It's not complicated to build from scratch. It took me about a week of project work to assemble the first version. Subsequent versions take about an hour per project to update with new items from lessons learned. The bottom line is that this is a baseline tool, not a substitute for competent design. It won't prevent every error. It will prevent the errors that come from forgetfulness, poor coordination, and unclear scope boundaries. Those three categories account for roughly sixty to seventy percent of plan review comments I've seen over the years. The remaining thirty to forty percent are design adequacy issues that require different solutions entirely.