Plan Check vs Plan Review

These two terms mostly describe the same activity, and the honest answer is that the difference is more about regional habit and context than a strict technical distinction.

Where the Terms Overlap

Both refer to the process of checking a set of construction drawings and specifications against applicable building codes and, often, against internal design standards, before or during construction. Whether someone calls it a "plan check" or a "plan review" usually depends more on where they're located and who they work for than on any real difference in what's happening.

Where a Loose Distinction Sometimes Applies

In practice, "plan check" is more commonly used by jurisdictions and building departments, especially on the West Coast, to describe the formal process a submitted drawing set goes through before a permit is issued. "Plan review" tends to show up more often in a design team's internal process, describing a check that happens before drawings are ever submitted to a jurisdiction, or a third-party review commissioned separately from the permitting process.

That's a loose pattern, not a rule. Plenty of jurisdictions use "plan review" for their own permitting process, and plenty of firms use "plan check" internally. If someone uses one term instead of the other, it's rarely worth reading much into it without more context.

Why the Distinction Matters Less Than Who's Doing It

What actually changes the nature of the review is who's performing it and at what stage, not which word they use. A jurisdictional plan check by a building department reviewer is checking for code compliance specifically, with the authority to require corrections before permit issuance. An internal design team review, whatever it's called, is usually broader, checking for code compliance but also coordination, constructability, and adherence to the firm's own standards. A third-party review commissioned by an owner is different again, often independent of both the design team and the jurisdiction.

Where AI-Assisted Review Fits

Structured AI's QA/QC Compliance Checks are typically used as a pre-submittal step, whichever term a firm prefers for it, checking a drawing set against code and compliance requirements before it goes to the jurisdiction. The goal is the same regardless of terminology: catch the issues a jurisdictional reviewer would flag, before they generate a formal comment and a correction cycle.

FAQ

Do building departments use "plan check" and "plan review" interchangeably? Many do, though there's a mild regional pattern toward "plan check" in parts of the West Coast and "plan review" being more common elsewhere. It's not a strict rule.

Does using the wrong term matter when talking to a jurisdiction? Generally no. Building department staff are used to both terms and will understand what's being asked either way.

Is a pre-submittal AI check the same as a jurisdictional plan check? No. A pre-submittal AI check is meant to catch likely issues before formal submittal. It doesn't replace the jurisdiction's own plan check or review process, which still has to happen for a permit to be issued.