Approve the workbefore it ships.
Track submittals through review with the ball-in-court clear and long-lead items flagged against the schedule.
A late submittal is a late delivery is a late job. ErectOS runs the submittal log as a schedule-aware pipeline — every package tracked through review, every long-lead item flagged against the date it has to ship — so approvals never become the reason the building slips.
Ball-in-court, clear
See exactly who holds each submittal and how long it has been there — architect, engineer, or sub.
Long-lead flagged
Submittals tie to procurement dates, so the ones that gate a delivery surface before they are late.
Spec-linked
Each package maps to its spec section and the detail it satisfies — review with the requirement in hand.
Move it through review, without the chase.
Log the package, route it to the reviewer, and track every cycle — with the spec section and required-on-site date attached from the start.
1.0 Route
SUB-052 returned approved-as-noted.
Curtain wall cleared to fabricate — ships Wk 26.
Protect the date the delivery depends on.
Tie each submittal to its procurement and install dates, so the ones that gate a long-lead delivery are flagged the moment they fall behind.
2.0 Protect
2 long-lead submittals threaten Wk 28 delivery.
Wired to the whole build
Submittals reads from and writes to every module it touches — your data is entered once and trusted everywhere.
An approved submittal releases the long-lead order automatically.
At-risk approvals flag the deliveries and milestones they gate.
Each package links to the detail and spec it satisfies.
Spec clarifications flow straight to the affected submittal.
Approvals never become the reason the building slips.
Submittals → SchedulesThe long-lead item is flagged before it is late.
Submittals → ProcurementNothing ships until it is approved against the spec.
Submittals ↔ Specs