Deferred submittals and delegated design: tracking the engineered items that arrive later
The warehouse schedule shows the mezzanine package arriving shortly before installation. The coordinator then discovers that its defined design and review route has several steps. Those steps need to be confirmed and planned before the purchase or installation date becomes the only date anyone watches.
List the actual items that need later design or later submission, and confirm who prepares, reviews and authorizes each stage. Delegated design concerns a defined design responsibility; deferred submission concerns timing. They may overlap on an item, but do not assume every supplier drawing is delegated design or every engineered package follows the same authority review route.
Map the review chain before scheduling it
- Find the project's named obligations. Review the relevant contract documents, specifications and permit requirements with the responsible project team. Record the item, defined scope and requirement source. Ask the responsible professional about an ambiguous design interface instead of assigning an engineering responsibility through a coordinator's spreadsheet. Identify later information that the project expressly requires.
- Confirm the professional roles. Record the party providing the defined design and the professional responsible for integrating or reviewing it where applicable. Establish how design assumptions, loads or interfaces are to be communicated by the qualified parties. The register follows that exchange; it does not provide a technical design, expand a professional's scope or decide that an unexplained seal settles every requirement.
- Confirm any authority step. Ask the responsible professional and permitting authority which information, approvals or assurances apply to this project and when. Distinguish an internal professional assurance from a required authority submission. In British Columbia, the cited supporting-professional guidance expressly separates its recommended S-B and S-C forms from Code-mandated Letters of Assurance; those supporting forms are not intended as authority submissions.
- Plan preparation, review and release. Work back from the date the information is needed using confirmed preparation, coordination and applicable authority steps. Mark unconfirmed durations as assumptions requiring an answer. Track returned comments and resubmissions as well as first receipt, and identify the evidence needed before the affected ordering or work is authorized. Update the dates when a dependency changes.
British Columbia's public Letters of Assurance guidance identifies different professional responsibilities and explains where those letters apply. Use that jurisdictional example to ask better questions, not to copy its forms onto another jurisdiction's project. The applicable permit, qualified professionals and current project requirements determine your item's actual route.
Common mistakes
- Using delegated and deferred as interchangeable labels.
- Treating every professional assurance as a permit-authority submission.
- Scheduling installation from first receipt without allowing the confirmed review steps.
Checklist
Check one later design package
- Item and requirement source.
- Defined design responsibility and interfaces.
- Professional review and coordination roles.
- Applicable authority step.
- Confirmed durations and visible assumptions.
- Evidence required for the affected release.
Check your understanding
A sealed package has arrived. Is it ready for installation?
