| name | schedule-management-cpm |
| description | CPM schedule management guidance for construction PMs—understanding critical path, developing lookaheads, documenting delays, writing schedule narratives, and protecting float entitlement. |
Schedule Management (CPM) Skill
Purpose
Help construction project managers effectively use, communicate, and manage CPM schedules. Focus on practical application—understanding critical path, coordinating with field teams, documenting delays, and writing schedule narratives—not building schedules from scratch.
When to Use This Skill
Activate when users ask about:
- Critical path method (CPM) concepts or terminology
- Reading and interpreting P6 or MS Project schedules
- Float types, float ownership, or float consumption
- Lookahead schedule development (3-week, 6-week)
- Pull planning or Last Planner System
- Schedule updates, data dates, or statusing
- Delay documentation or delay analysis methods
- Recovery schedules or acceleration
- Schedule narratives for owner reports
- Weather day tracking and documentation
- Logic relationships (FS, SS, FF, SF)
- Constraints and their impact
- Early completion schedules and entitlement
- Fragnets for changes or delays
Key Principles
PM Role in Scheduling
Project managers don't typically build schedules, but they must:
- Understand and communicate critical path to field teams
- Develop actionable lookahead schedules
- Document delays in real-time (not after the fact)
- Review and approve schedule updates
- Write schedule narratives for owner reports
- Protect the company's schedule entitlement
- Recognize when recovery action is needed
The Schedule is a Communication Tool
A schedule serves three purposes:
- Planning: Sequencing work and allocating resources
- Communication: Aligning field, office, and owner expectations
- Documentation: Recording what was planned vs. what happened
Document Delays as They Occur
The schedule tells the delay story. If delays aren't documented contemporaneously:
- Float consumption goes untracked
- Causation becomes disputed
- Entitlement to time extensions is weakened
- Recovery options are limited
Quick Reference
Critical Path Basics
The critical path is the longest sequence of activities that determines project duration. Any delay to a critical activity delays the project.
| Term | Definition |
|---|
| Critical Path | Longest path through the network; determines completion date |
| Total Float | Time an activity can slip without delaying project completion |
| Free Float | Time an activity can slip without delaying any successor |
| Critical Activity | Activity with zero (or near-zero) total float |
| Near-Critical | Activity with 1-10 days total float (threshold varies) |
Logic Relationships
| Relationship | Meaning | Example |
|---|
| FS (Finish-to-Start) | B can't start until A finishes | Forms stripped → Backfill |
| SS (Start-to-Start) | B can't start until A starts | Excavate → Haul (with lag) |
| FF (Finish-to-Finish) | B can't finish until A finishes | Inspections → Punch list |
| SF (Start-to-Finish) | B can't finish until A starts | Rare; avoid if possible |
Float Ownership Quick Guide
| Contract Language | Float Belongs To |
|---|
| "Float is a shared resource" | First user (race for float) |
| "Float belongs to the project" | Neither party exclusively |
| "Contractor-owned float" | Contractor (rare) |
| Silent on float | Typically shared/project |
Delay Analysis Methods
| Method | When to Use | Complexity |
|---|
| As-Planned vs As-Built | Simple, clear delays | Low |
| Time Impact Analysis (TIA) | Prospective analysis during project | Medium |
| Windows Analysis | Multiple delays, complex project | High |
| Collapsed As-Built | After-the-fact, causation disputes | High |
Schedule Status Types
| Status | Definition |
|---|
| Baseline | Original approved schedule; locked for comparison |
| Current/Updated | Latest schedule reflecting actual progress |
| As-Planned | What was planned to happen |
| As-Built | What actually happened |
| Recovery | Plan to regain lost time |
Reference Files
- Critical path explained for field teams
- Float types and practical implications
- Logic relationships with examples
- Constraints and why they matter
- Reading P6/MS Project schedules
- Resource loading basics
- Delay analysis methods overview
- Documentation requirements
- Concurrent delay concepts
- Excusable vs compensable delays
- When to involve a claims consultant
- Fragnet development
- 3-week and 6-week lookahead procedures
- Pull planning and Last Planner System
- Field coordination meetings
- Constraint identification and removal
- Lookahead templates and formats
- Monthly report schedule sections
- Owner update templates
- Milestone tracking and reporting
- Variance explanation language
- Progress photography correlation
- When recovery is needed
- Acceleration vs compression
- Recovery schedule development
- Cost implications
- Contractor vs owner responsibility
- Contract provisions analysis
- Tracking float consumption
- Protecting entitlement
- Early completion schedules
- Pacing and absorption
- Documentation requirements
- Weather day definitions
- Averaging methods
- Claiming weather days
- Abnormal vs expected weather
- Data date management
- Statusing activities correctly
- Maintaining logic integrity
- Out-of-sequence progress
- Update submission requirements
Common PM Questions
"How do I explain critical path to my super?"
See CPM Fundamentals. Simple explanation:
"The critical path is the longest chain of activities. If any of those activities slips, the project finish slips the same amount. Other activities have 'float'—room to slip without affecting the end date. We need to protect critical activities."
"When do I need a recovery schedule?"
See Recovery Schedules. Triggers:
- Project forecast shows completion past contract date
- Critical path delay exceeds available float
- Owner formally requests recovery plan
- Liquidated damages exposure becomes significant
"How do I document a delay?"
See Delay Analysis Basics. Minimum documentation:
- Daily log entry describing the delay event
- Photos showing the impacted work
- Correspondence notifying owner (per contract notice requirements)
- Schedule update showing impact to critical path
- Fragnet if impact is significant
"Who owns the float?"
See Float Ownership. Check contract first:
- Most contracts: Float is a shared project resource
- Some federal contracts: Government-owned float
- Contractor-owned float is rare and must be explicit
"What's the difference between TIA and windows analysis?"
See Delay Analysis Basics.
- TIA: Inserts delay event into schedule to measure prospective impact
- Windows Analysis: Divides project into time periods, analyzes each window
- TIA is better during the project; Windows is better after completion
Integration Notes
Not Covered Here (See Other Skills)
- Procore Schedule Module: Uploading, viewing, linking schedules (see procore-project-management)
- 4D Scheduling/TimeLiner: BIM-schedule integration (see vdc-bim-coordination)
- P6 Software Operation: Button clicks, filters, layouts (this skill is concepts, not software)
Handoffs
- Schedule updated → Upload PDF to Procore → Write narrative (this skill)
- Delay identified → Document per this skill → Notify owner via correspondence (procore skill)
- 4D needed → Export from P6 → Link in NavisWorks (vdc skill)
Schedule Narrative Template
SCHEDULE STATUS – [Month Year]
Current Status:
The project is currently [X days ahead of / behind / on] the baseline
schedule. The Data Date for this update is [date]. Contract Substantial
Completion is [date]; current forecast Substantial Completion is [date].
Critical Path:
The current critical path runs through [describe path: e.g., "Building A
structural steel → metal deck → MEP rough-in → inspections → drywall"].
Critical activities this period include [list 3-5 activities].
Progress This Period:
[Describe major activities completed, percentage complete on key items,
any milestones achieved]
Delays/Impacts:
[Describe any delays, their causes, duration, and impact to critical path.
If none: "No critical path delays occurred this period."]
Lookahead (Next 30 Days):
Key activities planned include:
- [Activity 1]
- [Activity 2]
- [Activity 3]
Concerns/Risks:
[Describe any emerging schedule risks, constraint issues, or coordination
challenges that may affect upcoming work]
Lookahead Meeting Agenda
3-WEEK LOOKAHEAD MEETING AGENDA
1. Review Last Week's Commitments (10 min)
- What was promised vs completed?
- Reasons for any misses (not blame—learning)
- PPC (Percent Plan Complete) calculation
2. Constraint Review (10 min)
- What's blocking work in the 3-week window?
- RFIs, submittals, inspections, materials, access
- Who is responsible to remove each constraint?
3. Make Ready (15 min)
- What work CAN be done next week?
- All constraints removed?
- Labor, equipment, materials confirmed?
4. Weekly Work Plan (15 min)
- Each foreman commits to specific tasks
- Commitments are reliable promises, not hopes
- Handoffs coordinated between trades
5. 6-Week Lookahead Review (10 min)
- Upcoming milestones
- Long-lead items
- Major coordination issues
Action Items: [List with owners and dates]
