Scope Gap Scanner

Paste plan notes or spec sections. Get a structured list of flagged gaps, commonly missed items for the trade, and code requirements that are not called out.

Good at:
Catching what you missed the first two reads — scope not assigned, coordination not addressed, code items buried in the notes.
Not for:
Replacing a full plan review or confirming code compliance.

Flags items based on text provided. Does not read drawings. Verify all flagged code requirements with the AHJ before bid submission.

Helps calibrate commonly missed items. e.g. electrical, framing, mechanical, concrete

Paste spec sections, scope notes, Division 01 requirements, or any plan text you want reviewed.

PDF, Word, image. Up to 3 files, 10 MB each.

Flagged gaps, commonly missed items, and code requirements will appear here once the tool runs.

Get this result as a PDF

Run the tool above first — then we can email you a PDF of the result.

Questions people ask first

What does the Scope Gap Scanner do?

Reads plan notes or spec sections and flags what's missing — scope not assigned to a trade, coordination handoffs not addressed, code items buried in the spec that nobody assigned. The output is a structured list of gaps and commonly-missed items for the trade you're bidding.

Is this a substitute for a full plan review?

No. The Scanner reads the specific notes you paste — it doesn't have the plans, the other spec sections, or the drawings. It catches what you missed in the section you're staring at; the comprehensive plan review is still your job.

What text should I paste?

The plan notes, the spec section, the scope-of-work text, the room finish schedule — whatever has the words that describe what's expected. The Scanner reads the language. Drawings, schedules, and details that are only in PDF graphics won't help it.

Will it tell me whether the scope is constructible?

No. Constructibility is a different problem — sequence, conflict, means-and-methods. The Scanner catches what's missing from the words; the question of whether the words describe something buildable is on you.

Will it confirm code compliance?

No. The Scanner flags code items that aren't called out in the scope (e.g. “the spec doesn't mention fire-stopping at penetrations but the assembly described requires it”). It doesn't certify that the code references it flags are current for your AHJ. Treat code flags as “go look at this,” not “this is the rule.”