Scope
Describe the specific systems, components, or drawings being deferred. Include reference to contract drawings and specifications, expected deliverables for the deferred items, and any affected project phases or interfaces.
Use a Project Proposal Deferred Submittal to document agreed deferrals, maintain schedule momentum, and create a clear record of responsibilities and review expectations. It reduces ambiguity for owners and design professionals and helps manage contractual risk while preserving project continuity.
Typical users include general contractors, specialty subcontractors, design consultants, and owners' representatives involved in phased or design-assist projects.
Accurate identification of who uses this submittal helps assign review duties and avoids delays or rework.
The contractor's project manager submits the deferred submittal, coordinates affected trades, documents schedule impacts, and tracks approvals. They are responsible for ensuring proposed interim controls meet contract performance standards and for providing revised drawings or submittals by the agreed follow-up dates.
The architect or engineer reviews deferred materials for compliance with design intent, verifies performance criteria, and issues acceptances or clarifications. Their review timeline and conditions should be documented in the submittal to prevent scope ambiguity and to support later inspections or approvals.
Describe the specific systems, components, or drawings being deferred. Include reference to contract drawings and specifications, expected deliverables for the deferred items, and any affected project phases or interfaces.
Explain reasons for deferral, such as long lead procurement, pending manufacturer data, or phased engineering. Provide alternatives considered and rationale why immediate completion is impractical or unnecessary.
State target dates for each deferred deliverable, milestones for review and resubmission, and expected impact on critical path activities. Tie dates to contract deadlines and propose reasonable review windows.
Define measurable acceptance tests, performance parameters, applicable codes or standards, and required supporting documentation. Specify who will verify compliance and what constitutes conditional acceptance versus final approval.
Identify submitting party, reviewers, and approvers with contact details. State review turnaround times, escalation paths for disputes, and responsibility for corrective actions if deferred items do not meet requirements.
List temporary measures, field mock-ups, or hold points that preserve safety and function until final materials are approved. Include inspection requirements and who authorizes use of interim solutions.
| Field | Configuration |
|---|---|
| Routing | Sequential reviewers, role-based assignments, and escalation paths. |
| Authentication | Email link, SMS code, or stronger methods as required. |
| Notifications | Automated reminders at set intervals and on status change. |
| Versioning | Retain version history and attach timestamps to each resubmission. |
Use secure eSubmission channels supporting audit trails, role-based access, and version control to meet contractual and regulatory expectations.
As contract specifies; often tied to shop drawing schedule.
Standard 7–14 calendar days unless contract stipulates otherwise.
Owner or construction manager typically responds within contract timeline.
Resubmit addressed comments promptly; propose realistic dates.
Document final acceptance, including as-built references and retained records.
Compile package, obtain signatures, and submit through specified channel.
Design team evaluates deferred items and records comments.
Use interim controls or mock-ups pending final materials.
Receive signed approval and incorporate approved items into project records.
A general contractor deferred shop drawings for façade panels to maintain erection schedule while awaiting custom finish confirmation.
A hospital renovation deferred selection of HVAC units pending updated infection-control specifications from clinical leadership.
Attach supporting drawings, vendor data sheets, product submittals, test reports, and shop-drawing excerpts. Clearly label each file and include version numbers to streamline reviewer cross-referencing and reduce resubmission cycles.
Provide signed documents as searchable PDF/A for archival and a standard PDF for reviewers. Include the audit trail or certificate of completion embedded or bundled with the exported files.
Include revision numbers, submission date in MM/DD/YYYY, submitting party, and reviewer status. Embedded metadata aids retrieval and satisfies audit and procurement requests.
Retain one signed master in an access-controlled repository and distribute copies to owner, architect, and prime contractor. Keep exportable audit logs and reviewer comments with each copy.