From Submittal to Stamp: What Actually Happens During Plan Review

If you're not the one doing it, plan review can look like a black box. A set goes in, some amount of time passes, and a stamped set comes out the other side. For PMs coordinating a schedule, or clients waiting on a submittal, that gap is often the hardest part of a project to plan around. Here's what's actually happening in it.

The set arrives complete, in theory

A plan set ready for review is supposed to be internally finished: grading, drainage, utility, and detail sheets that all reflect the same design, cross-referenced correctly, with every callout pointing somewhere real. In practice, "complete" is aspirational. Design happens iteratively, changes get made on tight timelines, and the set that arrives for review usually still has small inconsistencies baked in from the process that produced it. That's not a flaw in the process. It's exactly what review exists to catch.

The first pass: does it hang together?

Before anyone asks whether the design decisions are right, review starts with a more basic question: is the set internally consistent? Does the grading plan match the drainage plan? Do the standards and code references hold up sheet by sheet? Are the drawings clear enough that a contractor in the field would read them the way they were intended? This pass is systematic and comprehensive, and it's the part of review most exposed to time pressure, because it's tedious and it doesn't require the reviewer's deepest expertise. It requires their attention, on every sheet, every time.

Findings get triaged, not just listed

A thorough first pass produces a list of issues, and not all of them carry the same weight. A missing dimension on a detail sheet is not the same as a drainage error that could send water onto a neighboring property. Part of what a good reviewer does is sort the list: what needs to be fixed before this set goes anywhere, what's worth a note for the next revision, and what's genuinely minor. That triage is itself a skill, and it's where a lot of the value in an experienced reviewer shows up.

The engineer of record's pass: judgment, not detection

By the time the engineer of record sits down with the findings, the systematic work should already be done. Their pass isn't about re-checking every sheet. It's about evaluating each finding in context: is this actually a problem given the site conditions, does the fix make sense given the budget and schedule, is there a tradeoff here that the finding doesn't capture. That's the judgment that can't be checklisted, and it's the reason the stamp means something.

Then it goes out the door

Once findings are resolved, the set gets finalized and stamped. The goal of everything before this point is that nothing about the submittal is a surprise, to the reviewing agency, the contractor, or the client. A plan review process that's working doesn't just produce a stamped set. It produces one that doesn't come back with problems nobody saw coming.

None of this is exotic. The firms that do it well aren't running a fundamentally different process than everyone else. They're just making sure every step actually happens, every time, instead of getting compressed when the schedule tightens.