Construction submittal management with review codes, spec sections, and lead time tracking
Track shop drawings, product data, and samples from draft through approved - with revisions, CSI divisions, required-by dates, and reviewer routing so coordinators keep steel and MEP on schedule.
Construction Software
Construction submittal management
This is a shop drawing, product data, and sample management tool. It tracks review codes (A/B/C/D), revisions, CSI spec sections, lead times, and ball-in-court routing - giving general contractors, design teams, and trade partners a structured path from submission to field release with audit-ready history.
WorkHub
Part of WorkHub
- Review codes (Approved, Approved as Noted, Revise and Resubmit, Rejected) aligned to industry practice
- Revision tracking with current, superseded, and void states
- CSI spec section tags and required-by dates for procurement lookahead
- Ball-in-court reviewer routing and linked RFIs and files
The problem
Submittal logs in email are where schedule goes to die
When reviewers lose track of revision cycles, steel and MEP miss their windows. When lead times are not visible until procurement chases the PM, crews wait and margin bleeds. A clear register with ball-in-court and review codes on every package keeps approvals ahead of fabrication deadlines - before they become schedule claims.
From sub to field release - with approval clarity
A structured path for shop drawings and product data that respects the coordination cadence.
- 01
Submit the package
Sub uploads shop drawings or product data with spec section, trade, and required-by date - structured for GC review.
- 02
Route for review
Coordinator assigns architect or engineer reviewer with due date. Ball-in-court becomes visible to the team.
- 03
Respond with review code
Reviewer returns A/B/C/D decision with comments and attachments. Revise-and-resubmit cycles stay on the same record.
- 04
Release to field
Approved packages are findable by supers without calling the PM. Lead time and procurement path remain attached.
Submittal workflow built for GCs and subs
Review codes
Approved, approved as noted, revise and resubmit, rejected - standard A/B/C/D style responses aligned to AIA and industry practice.
Revision tracking
Current revision, resubmittal history, and void handling without spreadsheet sidecars or guessing which PDF is latest.
Spec sections
Tie packages to CSI divisions so architects filter what matters to their review queue and coordinators group by trade.
Lead times
Required-by dates and procurement lead time fields for lookahead planning - visibility before the deadline becomes a crisis.
Reviewer routing
Assign architect or consultant reviewers with ball-in-court visibility - so "waiting on design" is specific, not vague.
Linked RFIs & files
Attachments and cross-references stay on the submittal record for closeout - no duplicate uploads or orphaned context.
Deep dive
Register your coordinators rely on
Sortable table with status, trade, spec section, and overdue response dates - the same view coordinators open for OAC reviews and procurement updates.
- SUB-012 numbering aligned to contract specs
- Submit and respond workflows with ball-in-court
- Activity log on every status change and revision
Tasks · My work
T-067Punch - Level 4 waterproofing
MEP · Due Fri
T-068Close corridor firestop
You · Today
T-069Verify handrail torque
Done
Deep dive
From sub to field release
Approved packages are findable by supers without calling the PM. Status and review notes stay on the record for installation and verification.
- Drawer detail with review codes and comments
- Filter by under review or approved for field views
- Export-ready log for closeout binders
Tasks · Board
Open
Install door hardware
Paint touch-up L3
In progress
Punch package A
Done
Firestop corridor
Deep dive
Revision cycles without spreadsheet archaeology
Resubmittals increment on the same record. Void and superseded states keep history queryable without cluttering active queues.
- Revision labels (Rev A, Rev B) with upload timestamps
- Superseded packages hidden by default, available for audit
- Comment threads that span revisions
A-401 · Floor plan
2 open pins on this sheet
Rev C“We used to chase submittals across email and Dropbox. Review codes, revisions, and lead times now live in one register - approval cycles that used to take weeks now close in days.”
Built for everyone in the submittal loop
General contractors & coordinators
Own the register, route packages, and track review cycles with ball-in-court and overdue visibility - without spreadsheet maintenance.
Design & consultants
Receive clear submittal requests with spec sections and due dates. Respond with review codes and attachments that stay on the record.
Trade partners & fabricators
Submit shop drawings and product data with required-by context. See review status and decisions without email ping-pong.
FAQ
Submittal management FAQ
How shop drawings, product data, and approvals stay on track.
A construction submittal is a shop drawing, product data sheet, sample, or other documentation submitted by a trade or fabricator for review and approval before procurement or installation. Submittals ensure the proposed work matches contract specs and design intent.
Standard review codes are Approved (A), Approved as Noted (B), Revise and Resubmit (C), and Rejected (D) - aligned to AIA practice. These codes clarify whether the sub can proceed, needs minor fixes, or must resubmit.
Resubmittals increment on the same record with revision labels (Rev A, Rev B). Superseded packages stay queryable for audit without cluttering active queues, and comment threads span revisions for full context.
Yes. Packages link to CSI divisions so architects filter their review queue by relevant sections and coordinators group by trade and spec number.
Yes. Lead time and required-by fields help coordinators plan procurement and flag packages at risk of missing fabrication deadlines - before the schedule slips.
Yes. Subs with project access can create submittals, attach documents, and see review status - reducing email coordination and keeping the log centralized.
Related
Explore connected modules
Build on the Construction OS
Join the waitlist for Aroclad - field and office collaboration inside a platform built for the full construction lifecycle.