Your reviewer starts with a list of likely problems, not a blank page
SubmittalCheck reads each submittal against the spec and flags likely deviations before review. Every flag points at the page and the spec clause behind it. Your reviewer decides every one.
A submittal that misses the spec costs a review cycle
The first read of a submittal is careful, line-by-line work. When it misses something, the cost shows up later.
The first read is slow
Checking every submitted value against the spec section, the equipment schedule and the current addendum takes a reviewer who knows all three.
Misses come back around
A wrong rating condition or a missing attachment caught late means another round trip with the subcontractor and another review cycle.
Substitutions slip through
An unlisted manufacturer without a substitution request, or a tag that isn't on the schedule, is easy to miss in a thick package.
The same checks on every submittal
SubmittalCheck pulls each submitted value with its page number, then checks it against the spec by fixed rules. Same extracted values, same result. Each flag is sorted as non-compliant, substitution, missing information or check, and cites the page and the spec clause.
From documents to transmittal
Documents in
The submittal, the spec section it is filed under, the equipment schedules and the current addendum.
Read, compare, flag
Each value is checked against the spec, and each flag cites the page and the clause.
Your reviewer decides
Accept, edit or reject each flag. A rejection needs a reason. Nothing is decided for you.
Transmittal
Your reviewer picks the stamp. Only accepted items go on the transmittal, as comments to the subcontractor.
What SubmittalCheck is, and what it isn't
Two stops are built in: a transmittal cannot be issued while any flag is undecided, and the stamp cannot be lighter than the accepted flags support.
- A first read that checks values against what the spec states
- Cited: open the source page and read it yourself before you decide
- Logged: who decided, what they decided and the reason, in an audit trail
- Signed off by a person on every item: your people decide, the tool drafts and checks
- A stamp. Your reviewer chooses Approved, Approved as noted, Revise and resubmit, or Rejected
- A judge of whether a deviation is acceptable. That is a call for your PM and the A/E of record
- A code authority. Code questions are advisory and go to the A/E or are dismissed with a reason
- Validated software. It is offered as a paid pilot
Common questions about SubmittalCheck
No. It drafts and checks. A named reviewer on your team accepts, edits or rejects every flag and chooses the stamp: Approved, Approved as noted, Revise and resubmit, or Rejected. A transmittal cannot be issued while any flag is undecided, and the stamp cannot be lighter than the accepted flags support.
Every submitted value against the spec's numeric limits, units and rating conditions; that every value and attachment the spec asks for is there; that the material or type is one the spec allows; that an unlisted manufacturer comes with a substitution request; that values match the equipment schedule tag by tag; and that the submittal is made against the current spec revision.
No. It checks values against what the spec states. Whether a deviation is acceptable on your job is a call for your PM and the A/E of record. Code questions are advisory only: they are listed separately, and your reviewer sends each one to the A/E or dismisses it with a reason.
No, and we don't call it that. It is offered as a paid pilot. Every flag cites the page and spec clause behind it so your reviewer can read the source before deciding, and every decision is logged with who made it and why.
Data handling is agreed in writing before any document is shared: where files are stored, who can see them, and a commitment that they are never used to train AI models.
It depends on the project and the volume of submittals. We scope that on a 30-minute call and give you a fixed number before anything starts.