---
ref_id: PR34
ref_type: Process
ref_name: "Control Schedule"
version: "1.0.0"
status: Active
pmbok8_source: "PMBOK8 Guide §2.1"
companion_ref_shortcode: PG-APG
related_skills:
  - SKL-05-04
related_artifacts:
  - A15
  - A17
file_path: "reference/processes/PR34-control-schedule.md"
---
# PR34 — Control Schedule

## Process Identity
| Field | Value |
|---|---|
| **Process ID** | PR34 |
| **Process Name** | Control Schedule |
| **Process Group** | Monitoring and Controlling |
| **Knowledge Area** | Schedule Management |
| **PMBOK Source** | Process Groups: A Practice Guide §7.5; PMBOK 8 §2.3.2.3 |

---

## Purpose
Monitor the status of the project to update the project schedule and manage changes to the schedule baseline. Maintains the schedule baseline throughout the project.

---

## Inputs
| Input | Description |
|---|---|
| Project management plan | Schedule management plan, schedule baseline, scope baseline, performance measurement baseline |
| Project documents | Lessons learned register, project calendars, project schedule, resource calendars, schedule data |
| Work performance data | Actual start/finish dates, percent complete |
| Organizational process assets | Schedule control tools and templates |

---

## Tools and Techniques
| Tool / Technique | Notes |
|---|---|
| Data analysis | Earned value analysis, iteration burndown chart, performance reviews, trend analysis, variance analysis, what-if scenario analysis |
| Critical path method | Identify schedule float and critical path |
| Project management information system | Scheduling software tools |
| Resource optimization | Resource leveling and smoothing |
| Leads and lags | Adjust activity relationships |
| Schedule compression | Crashing, fast-tracking |

---

## Outputs
| Output | Description |
|---|---|
| Work performance information | Schedule variance (SV), schedule performance index (SPI) |
| Schedule forecasts | ETC, EAC for schedule |
| Change requests | Corrective/preventive actions; schedule baseline changes |
| Project management plan updates | Schedule baseline, cost baseline, performance measurement baseline |
| Project documents updates | Assumption log, basis of estimates, lessons learned register, project schedule, resource calendars, risk register, schedule data |

---

## Key Concepts
- Any change to the schedule baseline requires approval through Perform Integrated Change Control (PR31).
- For **agile** projects: focuses on burndown/burnup, velocity, and retrospectives.
- For **predictive** projects: focuses on critical path, variance analysis, and SPI.
- Contractor and supplier schedule updates must be monitored when work is contracted.

---

## PMBOK 8 Alignment
- Maps to **Monitor and Control Schedule** in PMBOK 8 §2.3.2.3.
- Schedule performance domain (§2.3) governs all scheduling activities.

---

## Related Processes
- Feeds into: PR31 (Perform Integrated Change Control)
- Cross-links: PR35 (Control Costs), PR38 (Control Resources)

---

## Cross-References

| Related Item | Type | Relationship |
|---|---|---|
| A15 | Artifact | Primary artifact produced or updated by this process |
| A17 | Artifact | Primary artifact produced or updated by this process |
| SKL-05-04 | Skill | Skill that executes this process |

## Practitioner Notes

Practitioners executing this process should seek answers to the following questions:
1. Is schedule variance (SV) and SPI calculated and reported regularly?
2. Are schedule compression options evaluated before corrective action is taken?
3. Are forecast dates (EF) communicated to stakeholders?
4. Are resource reallocation decisions documented and approved?
5. Is the schedule baseline updated only through formal change control?

## Change Log

| Version | Date | Description | Author |
|---|---|---|---|
| 1.0.1 | 2026-06-03 | Added Cross-References, Practitioner Notes, and Change Log sections (F-12 Batch 4) | PMO Director |
