Why a checklist, and when to run it
Most drawing errors that turn into RFIs and change orders are not engineering mistakes. They are consistency mistakes: a schedule that no longer matches the plan, a background that moved after the ductwork was drawn, a breaker size that was right two revisions ago. Nobody misses them because they are hard. They get missed because they sit between sheets, between disciplines, or between revisions, where no single reviewer is looking.
A checklist makes that in-between space someone's job. Run it before every issue that leaves the office: permit, bid, and issued for construction at minimum, and before any revision that touches more than one discipline. The order below matters. It starts with the set as a whole, moves to the places disciplines meet, and only then goes discipline by discipline, because a coordination error found late is the most expensive kind to fix.
Download the one-page checklist (PDF) Every check below on a single printable sheet, with space for your project and your jurisdiction.
1. The sheet set and title blocks
Start with the envelope before the contents. These take minutes and they are the first thing a plan examiner or contractor notices.
- Sheet index matches the set. Every sheet in the index exists, every sheet in the set is in the index, and titles match word for word.
- Revision information is consistent. The revision number and date in each title block match the revision schedule, and every change in this issue is clouded and tagged.
- Old clouds are cleared. Clouds from a previous issue left in place tell the contractor something changed when it did not.
- Scales are right and stated. The stated scale matches the drawing, and enlarged plans say which area they enlarge.
- North arrows and key plans agree. Every plan sheet orients the same way as the architectural plans, and the key plan highlights the right area.
- Seal and signature blocks are present where required, for the right discipline, on the sheets your jurisdiction requires.
2. Where disciplines meet
This is where most expensive errors live, so give it the most time.
- Backgrounds are current. Confirm the architectural and structural backgrounds under every MEP plan are the latest issue. A moved wall or a new column invalidates everything drawn over the old one.
- Ceiling space works. Compare duct depths, pipe mains and light fixtures against the ceiling heights on the reflected ceiling plan and the structure above. Check the tightest corridor, not the typical one.
- Equipment fits its room. Mechanical and electrical rooms show the equipment, its service clearances and a path to get it in and out.
- Penetrations are coordinated. Openings through structure, shafts and rated assemblies appear on the structural and architectural drawings, not only on yours.
- Rated walls carry the right protection. Where ducts cross fire-rated walls and floors shown on the life safety plan, fire and smoke dampers are shown and scheduled.
- Roof equipment is supported. Rooftop units, fans and condensers appear on the structural roof framing plan with their weights.
- Electrical data matches mechanical data. Every piece of mechanical and plumbing equipment has a circuit, and the voltage, phase, MCA and MOCP on the electrical drawings match the equipment schedules exactly.
3. Mechanical
- Schedules match plans. Every tagged unit on the plans is in the schedule, and every scheduled unit appears on a plan. Tags are unique.
- Airflow adds up. The air devices served by each unit sum to roughly the unit's scheduled airflow, and duct sizes are reasonable for the airflow they carry.
- Outdoor air intakes are separated from exhausts. Check intake locations against exhaust outlets, plumbing vents and flues, using the separation distances in your adopted mechanical code (in the International Mechanical Code, the intake location requirements are in Section 401.4).
- Condensate has somewhere to go. Every cooling coil shows a drain route to an approved receptor.
- Controls and sequences exist for every system that needs them, and the points list matches the equipment actually shown.
- Access is shown for filters, dampers, valves and equipment above hard ceilings, with access panels coordinated with the architect.
4. Electrical
- Panel schedules, one-line and plans agree. Every circuit on a plan is in a panel schedule; every panel on the one-line has a schedule; feeder sizes match between the one-line and the schedules.
- Working space is shown. Panels, switchboards and disconnects show the required working clearances in front of them (NEC Section 110.26), and nothing else is drawn in that space.
- Home runs are labelled with panel and circuit, and circuit counts per panel leave the spare capacity your standard calls for.
- Emergency and normal power stay separate where the code requires it, and life safety loads are on the right source.
- Devices sit where the architecture allows. Receptacles, switches and fire alarm devices are not drawn on glazing, inside door swings or behind casework.
- Lighting controls match the energy code approach declared in the general notes.
5. Plumbing
- Fixture counts match the architecture. Every fixture on the architectural plans is on the plumbing plans, and the reverse.
- Risers match plans. Pipe sizes, fixture connections and floor-to-floor routing on the riser diagrams agree with the floor plans.
- Vents terminate in the right places, clear of air intakes, operable windows and doors per your adopted plumbing code.
- Cleanouts are shown and accessible, not buried under finishes or in inaccessible ceilings.
- Relief and overflow have a route. Water heater relief valves discharge to an approved location, and roof drainage includes the secondary or overflow system your code requires.
- Equipment is scheduled and powered. Pumps, water heaters and booster systems appear in schedules and carry electrical data that matches the electrical drawings.
6. Fire protection
- Coverage follows the ceilings. Sprinkler layouts match the current reflected ceiling plan, including soffits, clouds and changes in ceiling height.
- Obstructions are checked. Wide ducts, light fixtures and beams under sprinklers are checked against the obstruction rules in NFPA 13 for the sprinkler type used.
- Standpipes and connections are coordinated. Standpipe locations match the stairs on the architectural plans, and the fire department connection appears on the civil or site plan.
- Fire alarm interfaces are shown where the sprinkler system, dampers and air handlers must report to or be shut down by the fire alarm system.
7. Notes, details and specifications
- Every callout resolves. Each detail and section reference points to a detail that exists, on the sheet it names.
- Boilerplate is current. General notes do not reference a code edition, product or project that no longer applies.
- Notes and specs do not contradict each other. Where the drawings and the specification both describe a material or method, they say the same thing.
- Abbreviations are defined and the legend covers every symbol actually used.
8. Making it repeatable
A checklist only helps if it runs the same way every time. Three habits make the difference.
- Record every finding with a sheet, a location and a severity, so the person fixing it does not have to rediscover it, and so you can see which kinds of error keep coming back.
- Close every finding explicitly. Fixed, not an issue, or deferred with a reason. An open list at issue time is a decision someone should make on purpose.
- Have someone other than the author run it. The person who drew the set sees what they meant to draw.
9. Example: New York City, where the filing layer is thick
The checklist above is written against the model codes. Every jurisdiction amends them and adds its own filing rules, so the list needs a local layer. New York City is a useful example because its layer is thick. Swap in your own jurisdiction's equivalents as you read.
- Use the city's codes, not the model codes. New York City enforces its own Construction Codes, including the NYC Building, Mechanical, Plumbing and Fuel Gas Codes, plus the NYC Electrical Code and the NYC Energy Conservation Code. They are based on the model codes but amended, so check every section reference in your general notes points to the NYC code and the edition the project is filed under.
- Expect a plan examiner's objections, and pre-empt them. Drawings filed through DOB NOW are reviewed by a plan examiner, who issues objections that must be resolved before approval. Most objections are the same consistency problems in this checklist: sheets that disagree, missing information, and code references that do not match the filing. Every one you catch first is a review cycle you do not wait for.
- Professional certification raises the stakes of your own QA. NYC lets a registered architect or professional engineer professionally certify that an application complies, which can skip the full plan examination. Those filings are subject to audit, so under self-certification your checklist is the plan review.
- Show energy code compliance on the drawings. NYC requires energy code compliance to be documented as part of the filing. Check the energy analysis agrees with the equipment actually scheduled: efficiencies, capacities and lighting power in the analysis should match the MEP schedules sheet for sheet.
- Coordinate with FDNY as well as DOB. Sprinkler, standpipe and fire alarm work involves the Fire Department as well as the Buildings Department. Make sure fire protection and fire alarm drawings agree with each other and with the mechanical drawings where dampers and air handlers tie into the fire alarm system.
- Tight existing buildings make coordination the main risk. Much of the city's work is alteration inside existing structures, where shafts, ceiling space and roof area are fixed. The "where disciplines meet" checks deserve even more time here than on a new building.
10. Example: Miami, where wind and water drive the design
Miami shows a different kind of local layer. The filing rules matter less than two physical facts: hurricane-force wind and a hot, humid, coastal climate. Both reach straight into the MEP drawings.
- Use the Florida Building Code and its HVHZ provisions. Florida enforces a statewide code, the Florida Building Code, with its own building, mechanical, plumbing, fuel gas and energy volumes. Miami-Dade and Broward counties sit in the High-Velocity Hurricane Zone (HVHZ), which carries stricter provisions than the rest of the state. Check your general notes cite the Florida code and the HVHZ requirements, not the model codes.
- Every rooftop and exterior item needs a wind anchorage design. Rooftop units, condensers, exhaust fans, curbs, louvers and exterior conduit and piping must be attached to resist the design wind load. Check that each one has an anchorage detail or calculation and that it matches the equipment actually scheduled. A unit substitution without a new anchorage check is a common gap.
- Exposed products need product approval. In the HVHZ, exterior products such as louvers and some rooftop equipment generally need Miami-Dade product approval (a Notice of Acceptance) or Florida product approval. Check each exposed product on the drawings has an approval that covers how it is installed.
- Roof penetrations are a roofing problem too. HVHZ roofing requirements are strict. Coordinate every curb, penetration and equipment support with the roofing details so the roof system and the equipment attachment agree.
- Design for humidity, not only temperature. Miami is a hot-humid climate, so latent load and dehumidification drive the HVAC design. Check that outdoor air is conditioned before it reaches occupied spaces, that the building is not drawn to run at negative pressure and pull in humid air, and that condensate drains, auxiliary pans and overflow protection are shown for every cooling coil. They carry far more water here than in a northern climate.
- Specify for salt air. Near the coast, outdoor equipment, coils, fasteners and supports corrode quickly. Check that coil coatings and corrosion-resistant materials are specified for exposed equipment and that the specification and the schedules say the same thing.
- Check the flood zone before placing equipment. Much of the area is in a mapped flood zone. Electrical gear, generators, pumps and mechanical equipment should be at or above the required flood elevation, or protected as the code allows. Confirm the design flood elevation on the architectural or civil drawings and check every piece of ground-floor and below-grade equipment against it.
- Know who reviews the plans. Permits go through the building department of the municipality or county where the project sits, and Florida law also lets an owner use a private provider for plan review and inspection. Like NYC's professional certification, a private provider route puts more weight on the quality of the set you submit.
Applying this to your own jurisdiction
New York City and Miami adapt the same checklist in different directions. In New York the local layer is mostly procedural: which codes, which agencies, which review path. In Miami it is mostly physical: what the wind and the water do to equipment on the roof and at grade. Most jurisdictions have some of both. Before your next issue, write down four things for yours: the codes and local amendments in force, the problems your plan reviewer most often rejects, whether any review path puts the full review on you, and the climate or hazard conditions that change how equipment is selected, placed and attached.
Want to see the checklist run on your own drawings? Start a 14-day free trial and upload a set. Redline flags findings for you to accept or reject, and the stamp stays yours.
Questions
How long should a QA review of an MEP set take?
It depends on the size of the set and how many disciplines changed since the last issue. The sheet set and title block checks take minutes. The coordination checks take the most time and should get it, because that is where the expensive errors are.
Who should run the QA check?
Someone other than the person who drew the set. The author sees what they meant to draw. A second reviewer sees what is actually on the sheet.
Should the checklist change by project type?
Keep one core list and add project-type sections, for example lab exhaust, healthcare, or kitchen hoods. A single core list is what makes findings comparable from one project to the next.
Can software run this checklist?
Parts of it. Consistency checks, such as schedules against plans or electrical data against equipment schedules, are well suited to an automated first pass. The judgment calls, and the decision to issue, stay with the engineer.