Variance thresholds and escalation paths in project governance
A variance threshold is the size of deviation that must be reported upward with an explanation. GAO says stakeholders should agree it and write it into a governing document, and review it periodically. When a variance passes it, the project manager reports it to management with the cause and recommended corrective actions.
Where thresholds come from
Task 1 of the PMP content outline's Business Environment domain, 'Define and establish project governance', includes outlining governance escalation paths and thresholds, alongside defining success metrics and setting up structure, rules, reporting and policies through organizational process assets.
GAO's schedule guide says the threshold for reporting schedule variances varies by program size, complexity and risk. All stakeholders should agree on it, and it should be formally defined in a governing document that considers how many days an activity is late and how much float it has. A template's default value is a starting point at most.
What happens at the threshold
If a variance exceeds the threshold, GAO says it is reported to management with a detailed description that includes the cause and recommended corrective actions. Below it, the project manager handles it within the authority governance gives.
Example: the governance plan lets the project manager absorb cost variances up to 5 percent. A supplier price rise is forecast to take the project to 8 percent over. The project manager raises it with the sponsor, the next level on the escalation path, as soon as the forecast shows the breach, and brings the cause, options and a recommendation.
Keeping thresholds useful
GAO's cost guide says variance analysis thresholds decide which variances need analysis and a narrative explanation in the contract performance report. Thresholds should be periodically reviewed and adjusted so they keep giving management the view it needs of current and potential problems. Freezing them for the life of the project to keep reports comparable works against that.
Where the exam catches people
Believing the template's default threshold is enough: GAO says stakeholders agree the threshold and define it in a governing document.
Believing thresholds should never change so reports stay comparable: GAO says to review and adjust them periodically.
Believing a forecast breach can wait until it happens: once the forecast shows the tolerance will be exceeded, it goes to the next level.
Believing every variance goes to senior management: only those beyond the agreed threshold are reported upward with cause and corrective action.