JobsHVAC · Construction
Submittal review
Product data compared against the governing spec section, with deviations and missing information drafted into review comments for the engineer to approve.
- Works with
- Project engineers, project managers and engineers of record
- Starts from
- Submittal packages and the project specifications
- Delivers
- A draft review with every deviation cited
01
Summary
A single mechanical submittal can run to hundreds of pages of cut sheets, performance data and certifications, and every page has to be checked against the spec section that governs it. It is careful, slow work, and it piles up exactly when the schedule is tightest.
Operon reads the submittal and the spec side by side. It pulls the requirements out of the spec section (capacities, materials, ratings, accessories, certifications), finds the matching data in the product literature, and drafts a review: what complies, what deviates and what is missing. The engineer reads the draft, not the whole stack.
02
Inputs and outputs
What goes in
- Submittal packages: cut sheets, performance data and shop drawings
- The governing specification sections
- Equipment schedules and the relevant plan sheets
- Your review stamp and comment conventions
What comes out
- A requirement-by-requirement compliance table
- Deviations and missing data, each cited to its page
- Draft review comments in your format
- A record of who approved what, and when
03
How it runs
Step
Operon
Your team
01
Extract the requirements
Operon
Turns the spec section into a checklist of requirements.
Your team
Adds project-specific requirements or exceptions.
02
Find the evidence
Operon
Locates each requirement's answer in the product data, page by page.
Your team
Flags manufacturer data that needs a closer look.
03
Draft the review
Operon
Marks each requirement as met, deviating or missing, with citations, and drafts the comments.
Your team
Reads the draft and edits the comments.
04
Sign and track
Operon
Logs the decision and keeps the reviewed submittal linked to the spec and the schedule.
Your team
Stamps and returns the submittal.
04
What changes
Today
With Operon
First pass
Today
Every page read against the spec
With Operon
A draft with every deviation cited
Consistency
Today
Depends on who reviews
With Operon
The same checklist on every submittal
Record
Today
Comments in a PDF markup
With Operon
Each decision linked to its requirement
05
Checks built in
The engineer signs
Operon drafts. Approval, rejection and the stamp stay with your engineer.
Cited, not summarised
Each finding points to the spec clause and the page of product data.
06
Getting started
Send two or three submittals your team has already reviewed, with their spec sections. Compare our draft with your final review.
First results within a week. Live in three weeks.
- Two or three reviewed submittal packages
- The governing spec sections
- Your returned reviews, for comparison
Related jobs
Further reading
Start with the work that costs you the most.
Tell us where your team loses the most hours. Three weeks later, an AI employee built for your company is doing that work.