---
reference_type: Focus Area
reference_id: FA04
name: Monitoring and Controlling
version: "1.0.0"
status: Active
pmbok8_source: "Process Groups Practice Guide — Monitoring and Controlling"
authority: PMI-derived
---

# FA04 — Monitoring and Controlling
**Type:** Focus Area
**PMBOK8 Source:** Process Groups Practice Guide — Monitoring and Controlling
**Version:** 1.0.0

## Definition
Monitoring and Controlling is the focus area that tracks, reviews, and regulates the progress and performance of the project against the approved baselines. It identifies any areas in which changes to the plan are required and initiates the corresponding corrective, preventive, or change-control actions. Unlike the other focus areas, Monitoring and Controlling does not occur at a single point in the lifecycle — it runs concurrently with all other focus areas from project initiation through closure. This continuous nature makes it the feedback and governance engine of the project, ensuring that deviations are detected early, decisions are made with current data, and the project remains aligned with authorized scope, schedule, cost, and quality targets.

## Entry Conditions
- Project execution (FA03) has begun and work is producing measurable outputs
- Performance baselines (scope, schedule, financial) are approved and established
- Performance reporting cadence and thresholds are defined in the Integrated PMP (A14)
- A change control process and Change Log (A12) are in place
- Risk monitoring responsibilities are assigned

## Primary Activities
- Monitor and control project work by collecting performance data, analyzing variances, and reporting status against all baselines
- Perform integrated change control by reviewing all change requests, assessing impacts, and approving or rejecting changes through the change control board or designated authority
- Control scope by comparing delivered scope against the scope baseline and managing scope creep
- Control schedule by analyzing schedule performance indices, identifying critical path impacts, and initiating corrective actions
- Control costs by analyzing cost performance indices, earned value metrics, and financial forecast variances
- Control quality by inspecting deliverables against acceptance criteria, performing testing, and managing defect resolution
- Monitor stakeholder engagement by assessing whether stakeholder satisfaction and engagement levels remain aligned with the communications plan
- Monitor risks by reviewing the Risk Management Record, tracking risk triggers, implementing contingency plans, and identifying new risks
- Control procurements by reviewing vendor performance against contract terms, managing claims, and overseeing contract changes

## Primary Outputs / Artifacts Produced
| Artifact | Purpose |
|---|---|
| A17 — Performance Reporting Record (updated each cycle) | Records current performance status, variance analysis, and forecasts; the primary communication vehicle for project health |
| A12 — Change Log (change decisions recorded) | Documents all change requests, impact assessments, approval/rejection decisions, and implementation status |
| A18 — Issue Log (updated) | Tracks open issues identified through monitoring, their resolution actions, owners, and closure status |
| A19 — Risk Management Record (risk response tracking) | Updated with risk status, trigger observations, response execution records, and newly identified risks |
| A20 — Quantitative Risk Reserve Decision Record (reserve drawdowns) | Records decisions to draw down contingency or management reserves and the justification for each drawdown |

## Artifacts Consumed (Inputs)
| Artifact | Source |
|---|---|
| A14 — Integrated Project Management Plan | FA02 Planning; defines the baselines and thresholds against which performance is measured |
| A15 — Schedule Baseline | FA02 Planning; the authorized schedule against which actual progress and EV calculations are made |
| A16 — Financial Baseline | FA02 Planning; the authorized cost plan against which actual spend and EAC forecasts are compared |
| A13 — Requirements Traceability Matrix | FA02 Planning; used in scope and quality control to verify all requirements are being addressed |
| A09 — Quality Management Plan | FA02 Planning; defines acceptance criteria and quality thresholds used in quality control activities |

## Skills Active in This Focus Area
| Skill ID | Skill Name |
|---|---|
| SKL-05-01 | Monitor and Control Project Work |
| SKL-05-02 | Perform Integrated Change Control |
| SKL-05-03 | Validate Scope |
| SKL-05-04 | Control Scope |
| SKL-05-05 | Control Schedule |
| SKL-05-06 | Control Costs |
| SKL-05-07 | Control Quality |
| SKL-05-08 | Monitor Stakeholder Engagement |
| SKL-05-09 | Monitor Risks |

## Relationship to Performance Domains
Monitoring and Controlling serves as the governance overlay that connects and monitors progress across all 7 performance domains:

- **PD8-01 — Governance:** Regulates project performance, conducts change control, and manages knowledge audits.
- **PD8-02 — Scope:** Inspects deliverables against quality requirements and controls scope creep (Control Scope and Validate Scope processes).
- **PD8-03 — Schedule:** Monitors activity progress and critical path deviations against the schedule baseline.
- **PD8-04 — Finance:** Tracks expenditures, calculates earned value indices (CV, SV, CPI, SPI), and forecasts financial completion.
- **PD8-05 — Stakeholders:** Assesses stakeholder engagement levels and monitors communications performance.
- **PD8-06 — Resources:** Monitors team performance, resource usage, and supplier/procurement contract compliance.
- **PD8-07 — Risk:** Monitors risk triggers, implements contingency responses, and updates the risk register.

## Exit Criteria / Quality Gate
- All planned deliverables are formally accepted by the sponsor or designated acceptance authority
- All performance variances are within approved tolerance bands or have approved corrective action plans
- No open critical issues remain in the Issue Log (A18)
- All change requests are resolved (approved, rejected, or deferred) with documented decisions in the Change Log (A12)
- Risk posture is documented as acceptable; all critical risks are closed or have active response plans
- Final performance reports are current and complete
- Closure is formally authorized by the sponsor; transition to FA05 Closing is approved

*Authority: Process Groups Practice Guide — Monitoring and Controlling · Source type: PMI-derived*
*Repository: https://github.com/fakhruldeen/PMOSkills*
