NexusBuilding ComponentsYour supply list is empty.

Planning & documentation

Documenting the Steel Erection Readiness Handoff

Prepare a reviewable steel erection readiness handoff covering concrete notifications, anchor changes, site access, and unresolved constraints.

By Nexus Building Components3 min readRecorded content date
A steel erection readiness handoff showing accepted anchors, accessible supports, clear laydown, and current documents together.
AI-generated concept illustration — Provide required written notifications and resolve documented readiness constraints.

Define the condition and its scope

Erection readiness requires evidence of prerequisite conditions, not an optimistic calendar date.

A steel building schedule works when each milestone has observable prerequisites. A planned delivery date does not establish that access roads are ready, foundation information is accepted, lifting arrangements are complete, or enclosure materials can be protected. Separate purchasing release, fabrication release, shipment, unloading, erection, dry-in, inspections, and occupancy. Assign an owner to each prerequisite and record the evidence that permits the next activity. This approach applies to both a red iron shell and cold-formed work sequenced inside an existing building.

References: Steel erection: site layout and construction sequence · Commissioning documents: process, contents, and acceptance

Gather the inputs before deciding

Identify who issues and receives the required readiness communications under the applicable erection provisions. Collect concrete information, accepted anchor-change dispositions, access conditions, and remaining site constraints. Distinguish an observed completed foundation from the evidence authorizing erection. Ask the controlling contractor and erector to confirm the actual prerequisites and safety arrangements for this project; unrelated inspections should not be treated as equivalent notifications.

  • Concrete readiness notification
  • Anchor-change disposition
  • Site access condition
  • Unresolved erection constraints

References: Steel erection: site layout and construction sequence · Commissioning documents: process, contents, and acceptance

Set observable handoff deliverables

A completed pour does not by itself establish readiness for the erection loads.

Review record for this condition
InputEvidence to keep with itReview status
Concrete readiness notificationRequired written concrete notificationIdentify reviewer and written decision
Anchor-change dispositionReviewed anchor modification recordIdentify reviewer and written decision
Site access conditionDated site readiness walkthroughIdentify reviewer and written decision

Sequence review and release

Conduct the readiness review before the erector's dependent operations begin. Compare the notification package with the current foundation and anchor records. Route discrepancies or unaccepted modifications to the appropriate responsible professionals. Confirm maintained access, graded working areas, and preplanned operations with the contractor. Document the actual release and distribute it to the erector without substituting a verbal assurance for required written information.

  1. Locate concrete readiness notification in the current record.
  2. Compare anchor-change disposition with the table's evidence.
  3. Document the decision: Provide required written notifications and resolve documented readiness constraints.

Worked project coordination example

The slab appears complete but a foundation readiness notification is missing. The controlling contractor gathers the required documentation and anchor-change records before the erector treats mobilization as authorized.

Apply the stated release decision to the case: Provide required written notifications and resolve documented readiness constraints. 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

Keep written notifications, supporting references, review dispositions, and the dated site condition together. Identify limitations or areas still held so a partial readiness decision is not read as unrestricted authorization. Record later changes that affect the accepted conditions. The erection record should show what the erector received and when, while preserving separate responsibility for the contractor's project-specific methods and safety planning.

For this issue, include dated site readiness walkthrough 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 this checklist replace the erection plan?

No. Use the applicable regulations, qualified planning, and project-specific safety arrangements.

How should concrete readiness notification be documented?

Provide required written notifications and resolve documented readiness constraints. Retain required written concrete notification 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.

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.

Your supply list

0 items

Your list is empty

Add products to review prices and check out, or download a quote.