Submittal Register Management: The 300-Item Tracking Problem Every Commercial Project Has
Every commercial construction project has a submittal register — the list of all required submissions to the design team for review and approval before the corresponding work can be procured and installed. Shop drawings for structural steel, product data for mechanical equipment, samples for finish materials, test reports for assemblies, mock-ups for curtain wall details. A medium-sized project typically has 200-500 submittal items, each with its own timing requirements and consequences for delay.
When submittals are managed well, they flow through review smoothly and don't constrain the project. When they're managed badly, they become a constant source of schedule pressure: long-lead items not submitted early enough, resubmittals stacking up, design team review lagging, and field work held up waiting for approvals that should have happened weeks earlier. Good submittal management is unglamorous but essential.
The register includes several submittal types:
Common submittal types
- Shop drawings — detailed fabrication drawings for structural steel, precast, curtain wall, custom millwork
- Product data — manufacturer literature for specified products
- Samples — physical samples of finish materials for verification
- Mock-ups — full-scale assemblies built for approval before full installation
- Test reports — results from specified testing (concrete strength, weld qualifications, etc.)
- Certificates — manufacturer certifications (quality, compliance, welder qualifications)
- Schedules — fabrication or delivery schedules for long-lead items
- Closeout documents — as-builts, O&M manuals, warranties
Each type has its own review process. Shop drawings typically need the most engineering review. Product data is often straightforward comparison to specifications. Samples require physical handling. Mock-ups require site visits. The register needs to reflect these differences in expected timing.
The submittal register captures specific information per item:
Register fields per submittal
- Submittal number (unique identifier)
- Spec section reference
- Submittal type (shop drawing, product data, etc.)
- Description
- Submitting party (prime contractor, specific subcontractor)
- Designer reviewer (architect, specific engineer)
- Required submission date (calculated from need-by date and review duration)
- Actual submission date
- Required return date
- Actual return date
- Status (pending, under review, returned, approved)
- Review comments / action (approved, approved as noted, revise and resubmit, rejected)
- Resubmittal number if applicable
The register becomes a project management tool when it's used actively — not just populated at project start and forgotten. Status updates, deadline tracking, and escalation on overdue items make the register operational rather than decorative.
When submittals need to go in depends on procurement lead time and installation timing:
Submission timing calculation
- Installation date (from schedule)
- Minus: material delivery lead time (from approved submittal to site)
- Minus: review duration (typically 10-15 business days for prime review + designer review)
- Minus: buffer for potential resubmittal cycles (add 10 business days for first resubmittal)
- = Target submission date
A structural steel submittal with 20-week fabrication lead time needs to be in review 20+ weeks before erection. Missing that submission window by two weeks means either fabrication can't start (delaying erection) or fabrication starts on unapproved design (risk of rework).
Submittals flow through a review sequence:
Typical submittal review sequence
- Submitter (subcontractor) creates and submits to GC
- GC reviews for completeness, conformance to drawings, and constructability
- GC routes to appropriate designer reviewer (architect or specific engineer)
- Designer reviews and marks up
- Designer returns with action (approved, approved as noted, revise and resubmit, rejected)
- GC distributes return to submitter
- Submitter revises if needed and resubmits
- Cycle continues until approved
Each step has its own duration. Review routing that's tight and automated minimizes dead time; routing that relies on email and manual handoffs introduces delays at each step.
Review duration is often specified in the general conditions. Enforcing it requires tracking:
Review SLA tracking
- Contract-specified review duration — typically 10-15 business days
- Day 0 = submittal logged in by designer
- Day count tracked automatically
- Warnings at 70% of SLA approaching (day 7-10 of 15)
- Escalation at SLA breach — GC communicates delay impact
- Schedule impact documented — delayed submittal reviews become delay claims if critical path
Design teams sometimes let reviews slip. A submittal register that tracks SLAs and enables escalation creates the accountability that moves stalled reviews. Without tracking, delays accumulate quietly.
Submittal review time is one of the most common sources of constructive delay claims. A design team consistently taking 25 days for 15-day reviews creates recoverable delay that contractors document through the submittal register. The register becomes evidence in any dispute.
First-round approval doesn't always happen. Resubmittals add delay:
Resubmittal handling
- Revision required — submitter revises and resubmits, clock restarts
- Revision marked up — specific issues flagged for correction
- Partial approval — some items approved, others need revision
- Multiple resubmittal cycles track separately
- Root cause of resubmittal captured — subcontractor error, design ambiguity, change in requirements
A submittal that takes three revision cycles takes roughly three times the base review duration. Planning without buffer for resubmittals sets up for schedule slippage. Tracking resubmittal frequency by submitter identifies subs needing better submittal preparation.
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
Long-Lead Item Management
Long-lead items need special attention:
Long-lead item management
- Identified in procurement plan at project start
- Submittals expedited to start procurement as soon as possible
- Early procurement sometimes happens on partial approval with risk acceptance
- Alternate options investigated during review — backup plan if primary approval fails
- Schedule float for these items should be minimal — track carefully
- Buyer-furnished equipment logistics planned
Switchgear, chillers, specialty steel, curtain wall, and certain architectural finishes can have 30-40+ week lead times. These items need submittal and procurement processes started at project mobilization, sometimes before.
Mock-ups and samples have physical logistics:
Mock-up and sample coordination
- Mock-up location planned — accessible for review, protected from construction damage
- Mock-up build scheduled to allow review and revision before full installation begins
- Sample submission includes multiple samples if variation possible
- Sample storage maintained for reference throughout project
- Design team mock-up review visits scheduled
- Client/owner review of key mock-ups included
Mock-ups are expensive and time-consuming. When they work well, they prevent expensive building-scale issues. When they're treated as afterthoughts, they either don't happen or don't produce the decisions they should.
Submittal management has moved from email-based to dedicated platforms:
Digital platform advantages
- Central repository — all submittals in one place, findable
- Automated routing — submitted items flow to correct reviewers
- Version control — clear current version, history preserved
- Status visibility — everyone sees current status without asking
- SLA tracking automated — overdue items flagged
- Audit trail — who did what when
- Integration with project schedule — submittal dates linked to construction dates
Common platforms include Procore, Autodesk Build (formerly BIM 360), Submittal Exchange, Newforma, and others. Whichever platform is used, the key is everyone actually using it consistently. A platform that some trades use and others bypass via email undermines the coordination.
Submittals at project closeout are their own category:
Closeout submittal management
- As-built drawings — accurate record of installed conditions
- Operations and maintenance manuals — organized by system
- Warranty certificates — from manufacturers and contractors
- Training documentation — who was trained on what systems
- Commissioning reports — system performance verification
- Spare parts inventories — specified replacement items delivered
Closeout submittals drive substantial completion certification and final payment. Projects that finish substantial completion but can't produce closeout submittals delay their own final payment. Tracking closeout submittal progress throughout the project — not just at the end — prevents the closeout scramble.
Submittal register management is where project scheduling meets design coordination. A disciplined process — structured register, timely submissions sized against procurement lead times, routed reviews with tracked SLAs, managed resubmittals, long-lead item focus, coordinated mock-ups and samples, digital platform adoption, and closeout tracking throughout the project — prevents submittals from becoming project bottlenecks. Projects with strong submittal management see few submittal-driven delays and fewer resubmittal cycles. Projects without it see constant pressure as long-lead items slip and design reviews lag. The submittal register is one of those project management tools that returns meaningful schedule certainty when actively managed and becomes a source of chronic delay when treated as documentation rather than operations.
Written by
Marcus Reyes
Construction Industry Lead
Spent twelve years running AP at a $120M general contractor before joining Covinly. Lives in the world of AIA G702/G703, retainage schedules, and lien waiver deadlines. Writes about the construction-specific workflows that generic AP tools get wrong.
View all posts