CPM Schedule Guidelines What CPM Can Legitimately Do With the Owner
Purpose:
This document defines the legitimate uses of the Critical Path Method (CPM) schedule on our projects. CPM remains a reasonable Owner-facing administrative, reporting, and forecasting tool. It is not the system that drives field production. Each use below stays inside that boundary and does not violate the practices identified in CPM Schedule Guidelines: What We Will Not Do.
- Demand work-in-progress (WIP) that exceeds the capacity of people and resources available. Releasing more work than the available crews, materials, supervision, and space can absorb causes overload, dropped quality, and safety risk. WIP must be aligned to real capacity, with a buffer.
- Trade stack. Trade stacking is forcing multiple trades to work in the same area at the same time. It creates congestion, safety hazards, interference between crews, and lost productivity — the equivalent of squeezing five people into a one-person space.
- Trade burden. Trade burdening is asking a single trade or crew to cover more areas or tasks simultaneously than is reasonable. It stretches teams thin, drives travel time, increases variability and defects, and produces burnout. Scope must be matched to capacity, not to the calendar.
- Release work without a full kit. Activities will not start before drawings, materials, tools, labor, information, and access are confirmed in place. Starting without a full kit guarantees mid-task stoppages and cascading downstream delays.
- Crash activities to recover the schedule. Crashing means accelerating critical-path activities by piling on labor, equipment, or overtime. It typically increases cost, reduces quality, raises safety exposure, and triggers a downward productivity spiral. We recover through planning, not through bodies.
- Strip out buffers or treat float as expendable. Variation is inevitable. Removing buffers makes the schedule brittle and turns ordinary issues into crises. Protective buffers will be maintained and used deliberately, not erased to fabricate a tighter critical path.
- Build the schedule in a silo. Schedules created without input from the superintendents, foremen, and trades who will execute the work produce plans the field cannot follow. The people who build the project will participate in planning the project.
- Use the schedule as a weapon. The CPM schedule will not be wielded to pressure, blame, threaten, or accuse contractors and trades. It is a coordination tool, not a legal cudgel.
- Open more work fronts than the team can supervise. Sprawl across too many active areas spreads supervision thin, fragments focus (focus drops to ~60% with three areas, ~25% with five), and prevents work from being finished cleanly.
- Force constant multitasking and context switching. Pulling crews from area to area destroys momentum and costs 15–45 minutes per switch per worker. Sequences will be planned for one-process flow, not parallel chaos.
- Lock the baseline and refuse to adapt. A baseline that cannot be updated as field conditions change becomes a liability rather than a guide. The plan will be updated when reality requires it; rigidity is not the same as discipline.
- Default to “add more labor” as the first response to slippage. Adding crew without planning, training, onboarding, and capacity analysis usually slows the project further. Capacity will be increased intentionally and proactively — never as a reflex.
- Push materials onsite ahead of need. Bringing materials too early creates excess inventory, drives motion and transportation waste, damages stored product, and starts a downward productivity spiral. Materials will be pulled to align with installation.
- Blame people for system failures. When projects struggle under CPM, the root cause is usually structural, not individual. The system will be investigated before people are reassigned, replaced, or disciplined.