Purpose
The purpose of this policy is to establish clear rules for identifying, managing, and reporting schedule variances in Memorres projects, and to define how forecasting must be performed once variances are detected. For lean PM teams (1–3 members), this policy provides discipline and clarity, ensuring that deviations from the baseline timeline are consistently measured and addressed without guesswork or informal adjustments.
Projects frequently deviate from plans due to resource changes, scope adjustments, or unforeseen risks. Without defined variance thresholds and forecasting rules, such deviations can be ignored, underestimated, or overreacted to, leading to missed deadlines, client dissatisfaction, or unnecessary escalation. This policy standardizes how variances are classified, which thresholds trigger action, and how forward-looking forecasts must be created and reported.
By applying this policy, Project Managers safeguard delivery commitments, enable sponsors to make informed decisions, and ensure stakeholders are aware of risks early. For Memorres, where multiple projects run concurrently with lean resources, consistent variance and forecasting practices strengthen governance and credibility.
Scope
This policy applies to all projects managed by the Memorres Project Management Department and is mandatory during Execution & Control phases once a baseline schedule has been approved. It governs both variance management and schedule forecasting.
The scope of this policy includes:
- Defining variance thresholds by category (minor, moderate, critical).
- Assigning escalation rules based on thresholds.
- Specifying forecasting methods (rolling wave, EAC—Estimate at Completion).
- Mandating evidence and reporting cadence in MIC.
The policy excludes scope or cost variance management, which are addressed in related policies. Responsibility for compliance lies with the Project Manager. The PMO monitors adherence, and Sponsors must approve corrective actions when thresholds are breached.
Main Section
Table 1: Policy Areas & Compliance Rules
| Policy Area | Rule | Compliance Expectation | Evidence/Example |
| Variance Measurement | All activities must be measured against baseline start and finish dates. | PM updates actual vs. baseline weekly. | Gantt baseline vs. actual log. |
| Threshold Categories | Minor (<5% slippage), Moderate (5–15%), Critical (>15%). | Categorize variance and apply response rules. | Task slipped 2 days on 40-day plan → 5% (Moderate). |
| Escalation Rules | Minor → log only; Moderate → inform stakeholders; Critical → escalate to Sponsor. | PM must follow escalation within 48h of detection. | Sponsor notified of >15% delay. |
| Forecasting | Forecast revised EAC dates using updated assumptions. | PM recalculates remaining durations monthly or after major slippage. | EAC shows delivery 10 days late. |
| Reporting | Variance and forecast must be reflected in weekly status reports. | Update MIC log and status reports within SLA. | Weekly report includes variance table. |
Table 2: Variance Thresholds & Escalation
| Variance Level | % Slippage vs. Baseline | Action Required | Escalation Timeline | Example |
| Minor | <5% | Document in MIC; monitor. | No escalation. | Task slipped 1 day on 30-day schedule. |
| Moderate | 5–15% | Inform stakeholders; adjust forecast. | Within 48h. | Module delayed 5 days on 40-day plan. |
| Critical | >15% | Escalate to Sponsor/PMO; propose corrective action. | Within 24h. | Go-live milestone delayed 10 days on 50-day schedule. |
Table 3: Forecasting Methods
| Method | Description | Application Guidance | Example |
| Rolling Wave Forecasting | Update near-term tasks in detail, keep distant tasks high-level. | Use when uncertainty is high or project is long-term. | Next 2 sprints planned in detail; later phases high-level. |
| Estimate at Completion (EAC) | Recalculate expected end date based on current performance. | Use when moderate/critical variance is detected. | Baseline: 100 days, current performance → 110 days EAC. |
| Scenario Forecasting | Model alternative corrective actions (fast-tracking, resource reallocation). | Use when sponsor requests options. | Adding 1 resource reduces delay from 10 → 5 days. |
Closing Note & Cross-References
The Variance Thresholds & Forecasting Rules Policy ensures Memorres projects do not drift from their schedules unnoticed. It provides lean PM teams with clear thresholds, escalation rules, and forecasting methods to maintain governance. Once variances exceed thresholds, corrective actions must be recorded, approved, and monitored in MIC.