Planning & documentation
Steel Building Shell Scope Gaps at Trade Boundaries
Identify who supplies, installs, seals, inspects, and maintains steel building shell interfaces that commonly cross contract boundaries.

Define the condition and its scope
A scope gap is often a missing transition rather than a missing major component.
A steel building proposal is a boundary between several businesses: the building-system supplier, concrete contractor, erector, enclosure installer, and trades that complete the occupied space. Cold-formed components may be included in one package and field-installed under another. Comparing the headline amount alone hides these handoffs. Start with the issued scope and give every bidder the same drawings, revision list, delivery assumptions, and request for written exclusions. Keep owner decisions visible beside contractor commitments so that an unresolved preference does not become an assumed inclusion.
References: Project Planning Guide · Commissioning documents: process, contents, and acceptance
Gather the inputs before deciding
Walk the shell boundary in sections: foundation to wall, wall to opening, wall to roof, and roof to equipment. At each crossing, list every required operation, including preparation, supply, installation, continuity checks, temporary protection, and final review. Compare that list with the accepted exclusions of both neighboring contractors. The missing item is often the work between packages, such as connecting a membrane behind trim or completing a sill transition. A broad statement that a contractor provides a complete system needs clarification when the adjoining package contains a specific exclusion.
- Perimeter base transition
- Door surround completion
- Eave closure responsibility
- Temporary weather protection
References: Project Planning Guide · Commissioning documents: process, contents, and acceptance
Set observable handoff deliverables
Separate panel and door packages can leave the opening perimeter assigned to neither installer.
| Input | Evidence to keep with it | Review status |
|---|---|---|
| Perimeter base transition | Coordinated slab-to-wall detail | Identify reviewer and written decision |
| Door surround completion | Door perimeter scope acknowledgment | Identify reviewer and written decision |
| Eave closure responsibility | Accepted closure and flashing sequence | Identify reviewer and written decision |
Sequence review and release
Begin with one representative interface and invite the contractors who touch it. Mark the proposed handoff directly on the coordinated detail, identifying material ownership and the point at which each installer leaves its work. Ask the responsible reviewer to resolve continuity or compatibility questions. Incorporate the accepted allocation into both scopes and into the installation sequence. Then repeat the check at differing conditions; a personnel-door resolution does not automatically cover an overhead door, louver, or roof curb. Track any unassigned operation as an open purchasing constraint.
- Locate perimeter base transition in the current record.
- Compare door surround completion with the table's evidence.
- Document the decision: Assign each transition to a contractor and its review authority.
Worked project coordination example
A contractor receives wall panels and sectional doors under separate orders. Both vendors exclude perimeter air sealing. A marked opening detail becomes the basis for an added scope assignment before installers mobilize.
Apply the stated release decision to the case: Assign each transition to a contractor and its review authority. The responsible team determines acceptance for the actual project and records any condition that still requires resolution.
Keep a closeout record another team can use
An interface is resolved when the detail, contractor allocation, sequence, and observation responsibility agree. Save acknowledgments from both neighboring packages and identify the drawing revision used. At installation, compare the first completed interface with the accepted record before the condition is repeated. Record concealed work while accessible and note who protects it until final closure. The owner handoff should retain the interface allocation for maintenance: later repair crews need to know the assembly and transition materials, not merely which company supplied the largest panel package.
For this issue, include accepted closure and flashing sequence in the handoff. If review remains pending, identify the dependent work and its owner; do not present the record as a completed technical acceptance.
Common questions
Does a complete material list prove complete scope?
No. Installation, transitions, testing, and temporary protection need explicit allocation.
How should perimeter base transition be documented?
Assign each transition to a contractor and its review authority. Retain coordinated slab-to-wall detail and check that the decision reached the team performing the dependent work.
Sources & further reading
Use the current documentation for the exact product and project. Source links do not imply a partnership or endorsement.
- Project Planning Guide U.S. General Services Administration / WBDG
- Commissioning documents: process, contents, and acceptance Whole Building Design Guide
Prepared with AI assistance. Linked references require current project-specific review. How these guides are prepared.
Prepare a supply inquiry
- Record the project drawing or detail and the specified product, profile, or system.
- List the complete configuration, physical units, quantities, and cuts per piece.
- Request current manufacturer documents; confirm compatibility, price, and availability before ordering.
- Obtain the responsible professional's review for loads, code requirements, or installation.