Management by Exception in Project Controls Explained

<div class="ge-article-wrapper"><nav class="ge-toc" aria-label="Table of contents"><p class="ge-toc-label">In this article</p><ul class="ge-toc-list"><li><a href="#what-it-actually-means">What It Actually Means</a></li><li><a href="#the-variance-funnel">The Variance Funnel</a></li><li><a href="#setting-the-right-thresholds">Setting the Right Thresholds</a></li><li><a href="#worked-example-monthly-exception-report-on-a-40m-programme">Worked Example: Monthly Exception Report on a £40M Programme</a></li><li><a href="#why-it-matters-in-construction">Why It Matters in Construction</a></li><li><a href="#common-mistakes">Common Mistakes</a></li><li><a href="#frequently-asked-questions">Frequently Asked Questions</a></li></ul></nav><article class="ge-article-body"><p>Management by exception is the governance principle that says you don't review everything, you only review what's going wrong. In earned value terms, it means setting variance thresholds on your <a href="/en/earned-value/definitions/cost-performance-index">CPI</a> and <a href="/en/earned-value/definitions/schedule-performance-index">SPI</a> metrics and only escalating control accounts that breach those thresholds. Without it, your monthly project review becomes a three-hour crawl through 30 control accounts where 25 of them are fine. </p><p>This term is part of the <a href="/en/earned-value/definitions">earned value definitions glossary</a>. For the core metrics that feed exception reporting, see the <a href="/en/earned-value/cpi-spi">CPI and SPI formula page</a>. </p><h2 id="what-it-actually-means">What It Actually Means</h2><p>Management by exception is not ignoring problems. It's the opposite. It's building a system that forces problems to the surface faster by filtering out the noise. The principle is simple: define what "normal" looks like, define what "abnormal" looks like, and only spend senior leadership time on the abnormal. </p><p>In <a href="/en/earned-value">earned value management</a>, "normal" means a control account running within acceptable variance bands. "Abnormal" means a control account that's breached a threshold you set in advance. </p><p>Think of it as a funnel. </p><h2 id="the-variance-funnel">The Variance Funnel</h2><pre class="ge-ascii-diagram ge-anim"> ALL CONTROL ACCOUNTS (e.g., 15 on a £40M programme) ==================================================== ┌─────────────────────────────────────────────────┐ │ │ │ GREEN ZONE: CV &lt; 3% AND SV &lt; 3% │ │ Action: CAM monitors. No escalation. │ │ "Carry on. You're fine." │ │ │ │ Typical: 9-10 of 15 control accounts │ │ │ ├─────────────────────────────────────────────────┤ │ │ │ AMBER ZONE: CV 3-5% OR SV 3-5% │ │ OR |CV| &gt; £50K OR |SV| &gt; 2 weeks │ │ Action: CAM writes variance narrative. │ │ PM reviews. Corrective action plan due. │ │ "Explain yourself. Fix it." │ │ │ │ Typical: 3-4 of 15 control accounts │ │ │ ├─────────────────────────────────────────────────┤ │ │ │ RED ZONE: CV &gt; 5% OR SV &gt; 5% │ │ OR |CV| &gt; £100K OR |SV| &gt; 4 weeks │ │ OR CPI &lt; 0.90 OR SPI &lt; 0.90 │ │ Action: Escalate to project director. │ │ Recovery plan within 5 working days. │ │ "This is a problem. Senior attention now." │ │ │ │ Typical: 1-3 of 15 control accounts │ │ │ └─────────────────────────────────────────────────┘ Result: Instead of reviewing 15 packages, the project director focuses on 1-3 that matter. </pre><p>The thresholds aren't arbitrary. They're set during baseline and agreed with the client or sponsor. On NEC4 contracts, I've seen them written into the project execution plan as part of the reporting requirements in the Works Information. </p><h2 id="setting-the-right-thresholds">Setting the Right Thresholds</h2><p>This is where most teams get it wrong. They either set thresholds so tight that everything triggers an exception (defeating the purpose), or so loose that genuine problems slip through until they're unrecoverable. </p><p>Here's what I've found works on UK construction programmes: </p><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Threshold Type</th><th>Green</th><th>Amber</th><th>Red</th></tr></thead><tbody><tr><td>Cost Variance (%)</td><td>< 3%</td><td>3% to 5%</td><td>> 5%</td></tr><tr><td>Cost Variance (£)</td><td>< £50K</td><td>£50K to £100K</td><td>> £100K</td></tr><tr><td>Schedule Variance (%)</td><td>< 3%</td><td>3% to 5%</td><td>> 5%</td></tr><tr><td>Schedule Variance (time)</td><td>< 2 weeks</td><td>2 to 4 weeks</td><td>> 4 weeks</td></tr><tr><td><a href="/en/earned-value/definitions/cost-performance-index">CPI</a></td><td>> 0.95</td><td>0.90 to 0.95</td><td>< 0.90</td></tr><tr><td><a href="/en/earned-value/definitions/schedule-performance-index">SPI</a></td><td>> 0.95</td><td>0.90 to 0.95</td><td>< 0.90</td></tr><tr><td><a href="/en/earned-value/definitions/to-complete-performance-index">TCPI</a></td><td>< 1.05</td><td>1.05 to 1.10</td><td>> 1.10</td></tr></tbody></table></div><p>On smaller contracts (under £10M), the £ thresholds drop. I'd use £25K and £50K for amber and red. On a £200M programme, you might go as high as £250K and £500K. The percentages tend to stay the same regardless of contract size. </p><p>One thing I'd add: use both percentage AND absolute thresholds. A 6% variance on a £200K control account is £12K, annoying but manageable. A 3% variance on a £15M control account is £450K. That's a different conversation entirely. </p><h2 id="worked-example-monthly-exception-report-on-a-40m-programme">Worked Example: Monthly Exception Report on a £40M Programme</h2><span class="ge-worked-label">Worked Example</span><div class="ge-callout ge-anim"><p><strong>Scenario:</strong> A £40M NEC4 Option C highways improvement programme in Yorkshire, 10 months into a 24-month contract. The programme has 15 control accounts managed by 6 CAMs. The commercial lead runs the monthly EVM cycle and produces an exception report for the project director.</p><br><p><strong>Thresholds agreed at baseline:</strong></p><p>- Green: CV < 3% and SV < 3%</p><p>- Amber: CV 3-5% or SV 3-5% or |CV| > £75K</p><p>- Red: CV > 5% or SV > 5% or |CV| > £150K or CPI < 0.90</p><br><p><strong>Month 10 results:</strong></p><br><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>#</th><th>Control Account</th><th><a href="/en/earned-value/definitions/budget-at-completion">BAC</a></th><th>CPI</th><th>SPI</th><th>CV</th><th>Status</th></tr></thead><tbody><tr><td>1</td><td>Earthworks</td><td>£6.2M</td><td>0.97</td><td>1.02</td><td>-£48K</td><td>GREEN</td></tr><tr><td>2</td><td>Drainage</td><td>£3.8M</td><td>0.94</td><td>0.96</td><td>-£62K</td><td>GREEN</td></tr><tr><td>3</td><td>Pavement</td><td>£8.1M</td><td>0.99</td><td>0.98</td><td>-£24K</td><td>GREEN</td></tr><tr><td>4</td><td>Structures (Bridge A)</td><td>£5.4M</td><td>0.86</td><td>0.82</td><td>-£218K</td><td>RED</td></tr><tr><td>5</td><td>Structures (Bridge B)</td><td>£4.1M</td><td>0.93</td><td>0.91</td><td>-£88K</td><td>AMBER</td></tr><tr><td>6</td><td>Utilities</td><td>£2.9M</td><td>0.88</td><td>0.95</td><td>-£104K</td><td>RED</td></tr><tr><td>7</td><td>Signage &amp; Road Markings</td><td>£1.2M</td><td>1.04</td><td>1.01</td><td>+£18K</td><td>GREEN</td></tr><tr><td>8</td><td>Landscaping</td><td>£0.8M</td><td>0.96</td><td>0.94</td><td>-£11K</td><td>GREEN</td></tr><tr><td>9</td><td>Traffic Management</td><td>£2.4M</td><td>0.95</td><td>0.97</td><td>-£38K</td><td>GREEN</td></tr><tr><td>10</td><td>Prelims &amp; Site Establishment</td><td>£3.1M</td><td>0.91</td><td>1.00</td><td>-£82K</td><td>AMBER</td></tr><tr><td>11-15</td><td>(5 remaining accounts)</td><td>£2.0M</td><td>Various</td><td>Various</td><td>Various</td><td>GREEN</td></tr></tbody></table></div><br><p><strong>Exception report summary:</strong></p><p>- <strong>RED (2):</strong> Bridge A (CPI 0.86, CV -£218K) and Utilities (CPI 0.88, CV -£104K)</p><p>- <strong>AMBER (2):</strong> Bridge B (CPI 0.93, CV -£88K) and Prelims (CPI 0.91, CV -£82K)</p><p>- <strong>GREEN (11):</strong> No escalation required</p><br><p>The project director's meeting focuses entirely on Bridge A and Utilities. That's 2 control accounts, not 15. The meeting takes 45 minutes instead of 3 hours. The Bridge A <a href="/en/earned-value/definitions/control-account-manager">CAM</a> explains that unexpected rock encountered during piling has driven a compensation event notification, and the team discusses whether to notify an early warning or go straight to a CE notification under clause 61.3.</p><br><p>Without management by exception, the project director would have spent equal time on the landscaping package (which is £11K under budget and doesn't need anyone's attention).</p></div><h2 id="why-it-matters-in-construction">Why It Matters in Construction</h2><p>Construction projects generate enormous volumes of data. A £100M programme might have 40 control accounts, each reporting monthly on cost, schedule, risk, and quality. That's 160 data points before you even start on subcontract packages and variations. </p><p>No project director can meaningfully process all of that. They need a filter. </p><p>Management by exception is that filter. It tells senior leaders: "Here are the 3 things that need your attention this month. Everything else is on track." It prevents two failure modes: </p><p><strong>Micro-management:</strong> Where the project director reviews every line item and the CAMs stop taking ownership because decisions get made above them. I've watched this kill morale on a £65M education programme. The PD insisted on reviewing every control account personally. By month 6, the CAMs had stopped writing variance narratives because "what's the point, he'll just override whatever we recommend." </p><p><strong>Negligence:</strong> Where nobody reviews anything until the final account reveals a £3M hole. The opposite extreme, and just as damaging. </p><p>Management by exception sits in the middle. Trust the CAMs on the green accounts. Challenge them on the amber ones. Fix the red ones together. </p><h2 id="common-mistakes">Common Mistakes</h2><ol><li><strong>Setting thresholds after problems appear</strong>: Thresholds must be agreed during baseline, not invented during the first bad month. If you set them reactively, they're not thresholds; they're excuses.</li><li><strong>Using percentages without absolute values</strong>: A 4% variance on a £500K account is £20K. A 4% variance on a £10M account is £400K. Both are "amber" on percentage alone. Only one of them should keep the PD up at night. Always use both percentage and absolute triggers.</li><li><strong>Never updating thresholds</strong>: On a 3-year programme, the thresholds you set at month 1 might not make sense at month 24. As packages complete and remaining work concentrates in fewer accounts, the thresholds may need tightening.</li><li><strong>Treating amber as green</strong>: Amber means "write a variance narrative and present a corrective action plan." It does not mean "it's fine, don't worry about it." I've seen too many amber accounts drift quietly into red because nobody took the amber trigger seriously.</li><li><strong>No consequence for red status</strong>: If a control account hits red and nothing changes, the system is performative. Red must trigger a specific response: recovery plan, resource reallocation, scope review, or <a href="/en/earned-value/definitions/estimate-at-completion">EAC</a> revision. Otherwise, you're just colouring cells in a spreadsheet.</li></ol><div class="ge-product-note ge-anim"><p><strong>How Gather helps.</strong> Gather's AI reads your site diaries daily and maps progress against your cost-loaded programme, giving you accurate earned value data without manual spreadsheet updates. <a href="https://gatherinsights.com/contact">Book a demo</a> to see it working on a live NEC4 project.</p></div><h2 id="frequently-asked-questions">Frequently Asked Questions</h2><h3>Who sets the variance thresholds?</h3><p>The project controls lead typically proposes them during baseline, but they need sign-off from the project director and (on NEC4 contracts) agreement with the Project Manager if they form part of the reporting requirements. On client-side EVM, the client's commercial team often dictates thresholds. </p><h3>Can different control accounts have different thresholds?</h3><p>Yes, and they often should. A high-risk account like piling or tunnelling might warrant tighter thresholds (2% amber, 4% red) than a straightforward account like fencing (5% amber, 8% red). The principle is that higher-risk work gets more scrutiny. Just document it clearly so nobody argues about which threshold applies. </p><h3>How does management by exception relate to NEC4 early warnings?</h3><p>They're complementary systems. Management by exception is an internal governance tool. It determines which control accounts get senior attention. NEC4 early warnings (clause 15) are a contractual mechanism requiring notification of events that could increase cost, cause delay, or impair performance. An amber or red exception report often triggers an early warning review. But they're not the same thing. You can have an early warning that doesn't affect any current control account variance, and you can have an amber variance that doesn't warrant a contractual early warning. </p><h3>What's the difference between management by exception and management by objectives?</h3><p>Management by objectives (MBO) is about setting performance targets and measuring against them. Management by exception is about filtering which performance data reaches which level of management. They work together: MBO defines what success looks like for each control account, and management by exception determines who gets involved when things deviate from that definition. In EVM terms, the <a href="/en/earned-value/definitions/budget-at-completion">BAC</a> and schedule baseline are the objectives. The variance thresholds are the exception triggers. </p></article></div>