Skip to main content

Automated Submittal Review

Nomic reviews a contractor submittal against the project specifications and drawings, and returns a structured review report with an approval recommendation for A/E confirmation.

Attach the three documents to a conversation and ask for the review — no workflow required:

  • The submittal — the contractor document under review.
  • The project manual or specifications — the requirements that govern it.
  • The drawing set — for sheets, details, and schedules the submittal has to match.

Assistant reads the submittal end to end, searches the specs for the governing sections, cross-references the relevant sheets and schedules, and verifies conflicts against the drawings before recording them. It will ask for the specs or drawings if they are missing rather than guess at requirements.

Nomic reviews what the contractor actually submitted. It does not fill in gaps on the contractor's behalf — missing warranties, test reports, or samples are reported as outstanding items, not inferred.

Automated Submittal Review

What you get back

A Results document with five sections:

SectionContents
1. Submittal identificationName, product or system, manufacturer and model, discipline, submittal type — each linked to where it appears
2. ReferencesThe governing spec sections and paragraph numbers, plus the sheet and detail numbers that apply
3. AnalysisKey compliance notes, coordination notes, and missing information or outstanding items
4. Narrative summaryA paragraph explaining the determination, with conditions of approval and required contractor actions
5. Approval determinationApproved / No Exceptions Taken, Approved as Noted, Revise and Resubmit, Rejected, or Reviewed for Record Only

The narrative summary is written for copy-paste under your review stamp in Bluebeam Revu, using standard A/E comment phrasing ("Verify dimensions in field prior to fabrication", "Provide warranty information meeting the requirements of Spec Section …").

Every compliance claim cites the spec paragraph, drawing detail, or submittal page it came from, so a reviewer can check the determination against the source rather than take it on trust.

Run it as a workflow

Use the Submittal Review workflow (Workflows → Nomic) when submittals arrive on a steady cadence and you want every reviewer to produce the same report. The workflow requests the three documents as named file slots, seeds the Results artifact, and runs in Background Agent mode so a long review finishes without supervision. It can also be launched from the Agent API if you want to hang it off an existing submittal intake process.

Supported Context