What Is a Deferred Submittal in Construction?

A deferred submittal is a piece of the construction documents that isn't fully designed when the building permit is issued and gets reviewed separately once the main permit set is approved. Fire sprinklers, curtain wall, precast connections, and elevators are the usual candidates, mostly because a specialty contractor needs a confirmed structural and architectural backdrop before they can finish their own design.

Every GC and plan reviewer has run into deferred submittals before. The definition is easy. The hard part is tracking which items are deferred, confirming the deferred design actually fits the approved structure, and making sure nobody treats "deferred" as "somebody else's problem until it shows up on site." Deferred items are one category inside the broader submittal types a project tracks, and they carry the highest coordination risk of any of them because the design isn't finished until well after the rest of the set is approved.

What typically gets deferred on a permit set?

Not every incomplete design element qualifies for deferral. Building officials generally approve it for scope that depends on a specialty contractor's own engineering, a fabricator's shop process, or an owner decision that hasn't been finalized, and it should be listed the same way any other submittal type is tracked in the project's submittal log. The most common categories:

How does deferred-submittal approval work?

Two approvals happen at different times. First, the building official has to agree to the deferral itself, usually at the time the permit set is submitted, and the architect or engineer of record lists every deferred item directly on the approved drawings so the scope is visible from day one instead of surfacing later. Second, once the deferred design is actually complete, it goes back through plan review as its own package, sealed by the deferred submittal's design professional, and reviewed by both the building department and the architect or engineer of record for the base project.

That second review matters more than teams often expect. The building department checks the deferred item against code. The architect or engineer of record checks it against the structure and systems that were already approved, since a curtain wall shop drawing that assumes an anchor point the structural engineer never confirmed is a coordination failure, not a code violation, and the building department isn't the one positioned to catch it.

Where do deferred submittals go wrong?

The most common failure is a coordination gap between the deferred design and everything around it, not a missed deadline. Fire sprinkler layouts get built against a reflected ceiling plan that changed after the permit set was issued. A curtain wall anchor detail lands on a beam that was resized in a later structural revision the fabricator never saw. None of that shows up in the deferred submittal's own plan review, because the reviewer is checking the deferred package against code, not cross-referencing it sheet by sheet against every discipline that touched the space since permit issuance.

This is exactly the kind of cross-discipline check that gets skipped under deadline pressure, because it means someone has to hold the current approved structural and architectural sheets next to the incoming deferred package and look for conflicts by eye. Helonic reads the full drawing set, including deferred submittal packages once they arrive, and flags where a deferred item's layout conflicts with structure, MEP, or life safety drawings that were revised after the base permit, the same cross-check a coordination meeting is supposed to catch, done automatically instead of by memory.

How should you track deferred items through the project?

Track deferred items on a register that names the responsible engineer, permit status, and the date the item must return to the set.

• List every deferred item on the approved drawings, not just in a separate memo, so the scope is visible to every trade working near it. See how to organize submittals for a numbering system that scales to deferred packages too.
• Track deferred submittals in the same log as regular submittals, using the same fields described in the submittal log guide, so nothing falls through a separate, informal process.
• Confirm the deferred design against the current drawing set, not the drawings as they existed at permit issuance, since revisions issued after permit are exactly what gets missed.
• Bundle related deferred scope into one submission where possible. All fire protection items in a single package usually reviews faster and cheaper than several small submittals.
• Close the loop before the trade mobilizes. A deferred submittal approval that arrives after the specialty contractor is already on site turns a paperwork delay into a schedule delay, the same kind of downstream cost tracked in RFI vs. ASI vs. bulletin vs. change order.