Engine · Field · BETA

Spec versus submittal. Deviations flagged.

The Submittal Reviewer is the Trueleveler engine that compares the vendor's submittal text against the controlling spec section and produces a numbered findings list. Each finding has a severity tag (Critical / Major / Minor / Info), a category (substitution, omitted requirement, conflicting standard, etc.), a recommended action and, where the documents have the words, a side-by-side quote pair (spec text vs submittal text). Every quote is checked against the document it came from, and a quote that cannot be found there is removed. Composes an overall review_result — Approved, Approved as Noted, Revise and Resubmit, or Rejected — and persists the findings onto submittal_revisions so the tracker shows the decision history.

Try it now

A stored sample review of a made-up curtain wall package is on this page, with nothing to upload and nothing to sign up for. Running your own spec section and submittal needs a free account (no card); the no-signup demo only levels bids.

Numbered
findings list
4 levels
severity classification
Checked
quoted passages found in the source text
Pro
plan tier

See it run

A screen recording of Submittal Reviewer on sample project data, with a voice-over and subtitles.

Transcript

Each finding points to its page.

Add the spec and submittal.

Submittal Reviewer compares the two.

Click a cited page, and the spec opens right there.

Sample review · nothing to sign up for

See a sample review of a curtain wall submittal.

A made-up curtain wall package: a specification section, a subcontractor's submittal summary, and a stored review of the two, in the format the Submittal Reviewer returns. Nothing is uploaded and no review is run.

Sample project: made-up documents, not a real submittal

Finding 1 of 8 · Critical · material · Spec 08 44 13 §2.2.C

The entrance sidelites are heat-strengthened glass. The specification requires fully tempered safety glazing there.

SpecificationSafety glazing: provide fully tempered glass, ASTM C1048, Kind FT, complying with 16 CFR 1201, at the entrance sidelites and at every lite within 24 inches (610 mm) of a door.
SubmittalEntrance sidelites: 1 inch (25 mm) insulating units with 1/4 inch (6 mm) heat-strengthened outboard and inboard lites.

Recommended actionChange the entrance sidelites, and every lite within 24 inches (610 mm) of a door, to fully tempered glass to ASTM C1048 Kind FT, and show the change on the glass schedule.

Limits. v1 is text-only — pasted text or PDF extract. There is no OCR on this path, so a scan comes through empty and the run is refused rather than answered from nothing. v2 (post-PDF sidecar) adds drawing-bbox pin overlays on shop drawings.

01 · What it catches

The deviations that show up at install, not review.

Submittals fail in predictable ways. A sub proposes a manufacturer not on the approved-equal list. The data sheet shows a smaller motor than the spec'd horsepower. A finish color is two shades off from the spec'd RAL number. Most of these slip past reviewers because a single sub may submit 40 pages and the reviewer has 30 other submittals waiting. Submittal Reviewer reads the whole package, compares it line-by-line to the controlling spec, and produces a numbered list of the deviations it finds.

CRITICAL · Spec violation

Submitted motor 5HP. Spec calls for 7.5HP minimum.

Hard violation of a numeric spec requirement. The sub must revise the submittal or formally request a substitution per spec 01 25 00. Engine output: severity Critical, recommended action "Revise and Resubmit."

MAJOR · Substitution

Manufacturer not on approved-equal list

Sub proposes Carrier 50TC where spec basis-of-design is Trane and approved equals are York / Daikin. Substitution may be acceptable on equipment match, but the request requires architect approval per spec 01 25 00. Engine output: severity Major, recommended action "Approve as Noted — submit substitution form 1.5."

MINOR · Wattage tolerance

Light fixture submitted 14.8W. Spec calls for 15W ±5%.

Inside the spec'd tolerance band but worth flagging for the PM to confirm photometric performance still meets the LDRA targets. Engine output: severity Minor, recommended action "Approve as Noted — verify photometric report."

INFO · Missing data

Cut sheet lacks the warranty term

Manufacturer's data sheet doesn't state warranty period. Spec 23 09 00 requires 5-year compressor warranty. Not a violation — possibly an omission on the sub's part. Engine output: severity Info, recommended action "Approve as Noted — submittal must include warranty letter."

02 · When to run it

Every submittal. Before it hits the architect's desk.

The reviewer is meant to run before the formal submittal review — it pre-flights the package, surfaces the deviations the sub should fix, and lets the GC kick obvious problems back to the sub instead of consuming the architect's review window.

  • Every new submittal — sub uploads the package, engine runs, findings are ready. GC PM sees the issues before the architect ever sees the document.
  • Owner-side QA — owner-rep PMs use the same engine to verify the GC's submittal review actually caught the deviations the spec requires.
  • Before a long-lead order — run the review before you release the order, and link the run to the tracked submittal so its findings show on that submittal in the Submittal Tracker. When you then issue a PO, or release the item to fabrication, while the submittal is still open and its review has Critical findings, Procurement lists them first. It is a warning only: you can continue, so the decision is yours.
03 · What you upload

Spec section. Submittal text. Nothing else is required.

v1 is text-only — pasted text or PDF extract. v2 (post-PDF sidecar) adds drawing-bbox pin overlays on shop drawings.

Required

Spec section text

The controlling spec section (CSI MasterFormat). PDF extracted to text or pasted directly. Multi-section comparison is supported — e.g., 23 09 00 + 23 09 23.3 for a controls submittal.

Required

Submittal text

Shop drawing notes, product data, manufacturer cut sheets, sample descriptions. PDF text extract or paste. The engine handles equipment schedules and tabular data in the cut sheets.

04 · What you get back

Numbered findings. Side-by-side quotes. One recommendation.

Sample review for a packaged rooftop unit submittal against spec 23 73 13:

SUBREVIEWSubmittal 23-73-13.A · Rev 1 · ABC Mechanical · Packaged Rooftop Unit RTU-1 · Submitted 5/12/2026 · 18 pages parsed against spec 23 73 13 (12 pages). As-submitted
F1CRITICALCooling capacity short · Substitution · Spec 23 73 13 §2.3.A: "Cooling capacity: 30 tons nominal at 95°F DB / 78°F WB." Submitted: Trane YHC275 rated 23 tons. Action: Revise — substitute capacity-matched unit (YHC360 = 30 tons). FLAG
F2MAJORManufacturer not on approved-equal list · Spec 23 73 13 §2.1: "Basis-of-Design: Carrier 48TC. Approved equals: Trane YHC, Lennox LCH." Submitted: Daikin DDS series — not on list. Action: Submit substitution request per spec 01 25 00 form. WARN
F3MAJORFilter MERV rating mismatch · Spec §2.5.B: "MERV-13 minimum." Submitted cut sheet: Standard MERV-8 filter, MERV-13 listed as upgrade ($420 add). Action: Revise to include MERV-13 as base. WARN
F4MINORSEER rating exceeds spec · Spec §2.3.D: "SEER 14 minimum." Submitted: SEER 16.1. Action: Note — compliance with margin, no action required. OK
F5INFOWarranty term not listed on cut sheet · Spec §1.6: "Compressor warranty: 5 years." Submitted: Warranty letter not included. Action: Note — require manufacturer warranty letter at resubmittal. Verify
F6INFOVibration isolation type not specified · Spec §2.7: "Curb-mounted with spring isolators." Submitted: Mounting curb shown; isolator details on separate drawing. Action: Confirm vibration package included. Verify
ΣRESULTRecommended review_result: Revise and Resubmit · 1 Critical + 2 Major findings must be resolved · 1 Minor + 2 Info findings can be noted at next revision. Notes-to-sub auto-drafted. PM stamp ready
The recommended review_result

One of four standard stamps composed by the engine based on the finding mix. Approved = no findings above Minor. Approved as Noted = no Critical, ≤3 Major needing acknowledgment. Revise and Resubmit = ≥1 Critical or >3 Major. Rejected = irreconcilable substitution or wholesale spec violation. The PM stamps the actual decision — the engine just suggests the starting point with the math behind it.

05 · How it chains

One review. Three places it can go next.

Submittal Reviewer sits in the field-phase chain. Its result can be saved on the submittal in the tracker. From a finding you can go on to the RFI Drafter or to CO Review; the finding is not carried across for you, so paste the text in.

  • Submittal Tracker — link the run to a tracked submittal that has a revision and the review_result and the findings are saved on that revision. You set the submittal's status yourself.
  • RFI Drafter — if a deviation needs architect clarification (e.g., substitution acceptability), open the RFI Drafter and paste the finding into its manual question. The review does not fill the RFI in for you.
  • CO Review — if the substitution lands as a cost add (or credit), run it through CO Review. The review result is not carried across; upload the change order and its contract or PO there.
  • Procurement — a submittal can be pushed into the Procurement Tracker from the Submittal Tracker. When a PO is issued, or the item is released to fabrication, Procurement looks at the submittal it came from: if that submittal is still open and its latest review has Critical findings, it lists them first. It is a warning only, so you can continue, and nothing there stops a PO; the findings stay on the submittal.
06 · FAQ

Things everyone asks first.

What submittal formats are supported?

v1 is text-based. Native PDFs with extractable text parse cleanly. Scanned PDFs do not — there is no OCR on this path, so a scan comes through empty and the run is refused rather than answered from nothing. Equipment schedules and tabular cut sheets are recognized as tables. Pasted text from email or a spec viewer works the same way. v2 (shipping when the PDF sidecar lands) adds drawing-bbox pin overlays that point to the exact spot on a shop drawing where a finding lives.

What if the spec is ambiguous about a requirement?

Ambiguity is itself a finding. If the spec is silent on a parameter the submittal addresses (e.g., refrigerant type isn't specified, sub picks R-32), the engine surfaces this as an Info finding noting the spec gap. The PM decides whether to accept the sub's choice or RFI the architect for clarification — either way, the gap is captured in the audit trail.

How does it handle a 200-page submittal with 4 spec sections?

The full package parses against each controlling spec section. Each section's findings get their own numbered series (F1–F5 for spec 23 09 00, then F1–F3 for 23 09 23.3, etc.). The overall review_result is composed from the worst severity across all sections.

Can subcontractors run the same review pre-submission?

Yes — the engine works the same for subs reviewing their own submittal before sending to the GC. Pro plan covers both roles. Subs can use it to catch their own deviations before formal submission.

Does it generate the notes-to-subcontractor text?

Yes. For every Critical or Major finding, the engine drafts a one-sentence note in PM voice: "Provide cooling capacity of 30 tons nominal at 95/78 design conditions per spec 23 73 13 §2.3.A." The PM edits or approves; the notes auto-attach to the submittal's return stamp. The sub gets a single document with every issue listed. The notes are written by the engine from the findings; read them before you send them.

Drop a submittal. See the deviations.

Bring one real submittal and the spec section it's against to a 15-minute call. We'll run the review on screen, walk the findings, and you keep the output with the recommended notes to sub.

Try Free for 14 Days →