JobsHVAC
Schedule & spec reconciliation
Equipment schedules checked against the plans, and the plans against Division 23, so mismatches surface before bid day instead of on site.
- Works with
- Estimators, project engineers and design-assist teams
- Starts from
- Plans, equipment schedules and the project specifications
- Delivers
- A list of conflicts, each linked to both sources
01
Summary
Drawings and specifications are produced by different people at different times, and they drift apart. A unit is scheduled at one capacity and tagged differently on the plan; a spec section calls for a product the schedule no longer lists; an addendum updates one document and not the other. Each mismatch is a pricing risk if it is missed and an RFI if it is caught.
Operon reads the schedules as tables and the plans as drawings, connects every tag across them, and checks each scheduled item against what the plans show and what the specs require. What comes back is a short list of conflicts, each with both sources side by side.
02
Inputs and outputs
What goes in
- Equipment, fan, pump and air device schedules
- Mechanical plans and details
- Division 23 specification sections
- Addenda and bulletins
What comes out
- Items drawn but not scheduled, and scheduled but not drawn
- Tag, capacity and model conflicts between schedule and plan
- Schedule entries that conflict with the specs
- Draft RFIs with both references attached
03
How it runs
Step
Operon
Your team
01
Read the schedules as data
Operon
Extracts every schedule row, column and note into structured records.
Your team
Points out project-specific schedules or legends.
02
Connect tags across sources
Operon
Matches each tag on the plans to its schedule row and the spec section that governs it.
Your team
Confirms the tagging conventions the design team used.
03
Compare
Operon
Lists every conflict: missing items, duplicate tags, capacities or models that disagree.
Your team
Reviews the list and sets aside expected differences.
04
Raise
Operon
Drafts RFIs or clarifications with both sources cited.
Your team
Edits and sends the ones that matter.
04
What changes
Today
With Operon
When mismatches surface
Today
During construction, as change orders
With Operon
Before bid day, as RFIs
Evidence
Today
Screenshots pasted into an email
With Operon
Both sources linked in the finding
After an addendum
Today
Re-checked from memory
With Operon
The comparison re-run on the new revision
05
Checks built in
Two sources per finding
Every conflict cites the schedule row and the plan or spec location it disagrees with.
Nothing is corrected silently
Operon reports conflicts. Your team decides which document is right.
06
Getting started
Pick a recent project where schedule and plan conflicts cost you money. We run the comparison on that set first, so you can judge the findings against what actually happened.
First results within a week. Live in three weeks.
- Plans, schedules and Division 23 for one project
- Any RFIs or change orders that came from mismatches
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.