MasonMason vs Pre-Check Tools
Pre-check tools confirm a permit set is complete. Mason reviews it against the code. They solve different problems on the same desk.
Where the difference shows up.
Pre-check tools answer "is the submission complete." Mason answers "does it meet the code." Here is the line between the two.
Mason
Pre-Check Tools
Mason
Pre-Check Tools
Mason
Pre-Check Tools
Mason
Pre-Check Tools
Mason
Pre-Check Tools
Mason
Pre-Check Tools
Three things Mason does that pre-check tools do not.
Both tools have a place. These are the lines where Mason picks up where a pre-check tool stops.
Reads What Is on the Page
Pre-check tools confirm a sheet is present. Mason reads the dimensions, callouts, and notes on that sheet and runs them against the applicable code.
Drafts the Letter Language
Pre-check tools produce a checklist. Mason produces a draft comment letter with cited code references, ready for the reviewer to refine.
Stays Current With Code Cycles
Pre-check rules are static configurations. Mason updates as the CRC, CPC, CEC, CWUIC, and Energy Code change. Your reviews never run on a stale rule set.
What this looks like in your day.
How the two tools sit next to each other in a typical plan review workflow.
Intake stays clean.
Use a pre-check tool to filter incomplete submissions before they reach a reviewer. That gate still has its place.
Substance gets reviewed.
Once the set is complete, Mason runs the code check. Your reviewer reads the draft, verifies the citations, and signs off.
Two tools, one outcome.
A complete permit set that meets the code, delivered faster than either tool can produce alone.
The fastest way to understand the gap is to run both on the same permit set.
Bring a plan your team has already reviewed. Watch Mason draft the comment letter while the pre-check tool flags page numbering. Compare side by side.