Systems
Project Scheduling & Dependencies
Critical path, handoffs, and field-ready schedules.
Definition
How we handle scheduling dependencies
Scheduling & Dependencies means mapping every trade handoff, defining readiness criteria, and resetting the critical path whenever scope or weather shifts.
Examples
- Framing start blocked until underground inspections are logged in the schedule.
- HVAC rough scheduled only after electrical homeruns are tagged and photographed.
- Exterior paint auto-shifts when rain forecast exceeds threshold, notifying subs and owners.
Critical path checklist
- Define long-lead items with order-by dates.
- Capture trade readiness for each milestone (photos + sign-offs).
- Log dependencies in the schedule tool with owners and backups.
- Hold weekly pull-plan to re-level dates and manpower.
Pitfalls
- Publishing schedules without readiness definitions.
- Ignoring small weather slips until they stack into delays.
- Letting subs resequence work without PM approval.
- Assuming long-leads will arrive on time without owner visibility.
FAQs
- How often should the schedule move?
- Weekly at minimum; daily for active phases with multiple subs onsite.
- Who approves resequencing?
- Project manager with superintendent input—never field-only decisions.
- Do we show clients every slip?
- Yes, but framed with mitigation steps and the updated critical path.
Dependency diagram
Backlog → Long-lead orders → Readiness checks → Trade handoffs → QA → Closeout. Each arrow represents a documented dependency that is reviewed weekly.