Coordinating Subcontractor Demolition Work Schedules Effectively

The Complexity of Multi-Contractor Demolition

Large demolition projects frequently involve multiple subcontractors, each with their own equipment, crews, and timelines. Coordinating these teams so that one contractor's work doesn't compromise the structural safety assumptions of another is one of the project manager's most challenging responsibilities.

Structural engineers typically design the demolition sequence assuming a controlled, predictable progression. But in reality, contractors operate independently, often trying to complete their work faster than scheduled, and sometimes deviating from the specified sequence without authorization.

Common Coordination Failures

Scenario 1: The facade contractor accelerates work and removes north exterior walls before interior bracing is fully installed. The engineer's load calculations assumed exterior walls would provide lateral stability during interior floor removal. Unintended loading conditions result.

Scenario 2: The mechanical contractor removes interior ductwork in a sequence different from the engineer's specification because it was more efficient for their crew. However, the ductwork braced a floor system the engineer needed in place during the next demolition phase. The floor system deflects more than anticipated.

Scenario 3: Two contractors work on different floors of the same building. The upper-floor contractor finishes ahead of schedule and removes their temporary bracing before the lower-floor contractor's phase is complete. The lower structure loses expected lateral support and experiences unintended forces.

Each of these scenarios represents a breakdown in schedule coordination and communication.

Engineering-to-Contractor Communication Chain

The information flow from structural engineer to field contractor typically goes: Engineer → Project Manager → Contractor → Crew Lead.

At each step, detail is lost. The engineer specifies "Remove second floor after west bracing is installed." By the time this reaches the crew lead, it might become "Remove the second floor when you can."

Dependency Management Systems

Effective coordination requires explicit dependency documentation:

Hard Dependencies: Element A cannot begin removal until Element B is complete.

• Example: Interior temporary bracing cannot be removed until upper-floor demolition is complete

Soft Dependencies: Element A should begin only after Element B is complete, but brief overlap is acceptable.

• Example: Facade removal can begin when upper floors are cleared, but brief overlap is acceptable if loads are managed

Conditional Dependencies: Element A's timing depends on conditions verified during Element B.

• Example: "Ground floor removal can begin only after settlement monitoring shows less than 1mm movement in adjacent structures"

A coordination system that maps these dependencies prevents contractors from starting work that violates the engineer's sequencing assumptions.

Scheduling Best Practices

Explicit Phase Gates: Define clear gates between demolition phases.

• Phase 1 Complete gate: "All Phase 1 removals complete, all Phase 1 temporary supports in place and verified"
• Phase 2 Start gate: "Phase 1 gate satisfied, engineer has approved Phase 2 beginning"

Contractor Notification Requirements: Specify when the engineer must be notified before work proceeds.

• "Contractor will notify engineer 48 hours before beginning Phase 3 floor removals"
• "Engineer will verify bracing before floor slab removal begins"

Contingency Protocols: Define what happens if one contractor falls behind.

• "If Phase 2 bracing installation lags more than two days, notify engineer immediately—Phase 3 timing may require adjustment"
• "Do not start Phase 3 without written engineer approval even if behind schedule"

Temporary Support Coordination

Temporary bracing is especially critical to coordinate:

• Installation sequence: Some bracing must go in before removals begin; some must follow demolition
• Inspection requirements: When does the engineer verify bracing before the contractor can proceed?
• Removal sequence: Which bracing can be removed first, and under what conditions?
• Contractor responsibilities: Who installs bracing—the demolition contractor or a separate bracing contractor?

If two contractors both think the other is responsible for installing bracing, you have a safety failure waiting to happen.

Documentation for Coordination

Effective schedules include:

Sequence Diagrams

• Visual representation showing which contractor's work overlaps with which other contractor's work
• Critical path indicating dependencies between contractors

Phase Breakdown by Contractor

• Which contractor does Phase 1A, 1B, 1C
• What triggers the start of each contractor's work
• Verification steps before each contractor proceeds

Communication Schedule

• When contractor meetings occur
• When engineer visits for verification
• When the project manager reviews progress against the sequencing specification

Risk Identification

• Which coordination points are most critical?
• What contractor conflicts could disrupt the sequence?
• What early warning signs indicate a contractor is deviating from the plan?

Real-World Coordination Example

Consider a building with three main demolition contractors:

Contractor A (Envelope): Remove exterior facade and spandrels Contractor B (Structure): Remove floors and interior columns Contractor C (Utilities): Disconnect and remove mechanical, electrical, plumbing systems

The engineer's sequence specifies:

• Contractors A and C proceed simultaneously on top floors (no structural loads to redistribute)
• Contractor B begins only after A and C clear upper floors
• Contractor C must avoid removing braces that Contractor B needs
• Contractor A cannot proceed to lower floors until Contractor B stabilizes the structure

A coordination failure occurs when Contractor A removes lower facade before Contractor B has finished upper-floor work and installed lower-level bracing. Now the structure has lower lateral support than the engineer assumed during load calculations.

Prevention: The project manager maintains a master schedule showing exactly which days each contractor can work on which areas, with verification gates between phases.

Technology for Coordination

Traditional tools—paper schedules and status meetings—struggle to communicate dependencies clearly. Better systems visualize:

• Which contractor controls the critical path
• When dependencies are satisfied
• What contractor is behind and how that affects others

Visual coordination systems make it obvious when one contractor's work affects another's, preventing the schedule deviations that compromise structural safety.

Implementation Steps

To improve subcontractor coordination on your next project:

1. Map all dependencies explicitly—don't assume contractors will infer sequencing
2. Assign responsibility for each phase—who does this work, and who verifies it?
3. Define gates clearly—what conditions must be met before the next contractor proceeds?
4. Schedule verification visits—when does the engineer confirm work is correct before the next phase begins?
5. Plan for contingencies—if one contractor falls behind, how does that affect the others?

Conclusion

Large demolition projects succeed or fail based on whether the spatial and temporal sequence engineers design actually gets executed in the field. Clear coordination systems, explicit dependency documentation, and visual representation of schedules help ensure that contractors follow the engineer's intent rather than their own assumptions.

Improve your project coordination today. Join our waitlist to be first to access coordination tools that help structural engineers manage complex multi-contractor demolition schedules with confidence.