Weighted Milestones in Earned Value: EV Measurement Guide

<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="#how-it-works">How It Works</a></li><li><a href="#why-its-the-best-method-for-construction">Why It's the Best Method for Construction</a></li><li><a href="#setting-the-right-milestones">Setting the Right Milestones</a></li><li><a href="#worked-example-4m-structural-package-on-a-mixed-use-scheme">Worked Example: £4M Structural Package on a Mixed-Use Scheme</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>The weighted milestone method is an <a href="/en/earned-value/definitions/earned-value">earned value</a> measurement technique where you assign a budget weight to each milestone and only claim <a href="/en/earned-value/definitions/earned-value">EV</a> credit when that milestone is fully complete. No partial credit. No 90% done. Either the milestone is achieved and you book the value, or it isn't and you book nothing. It's the most honest EVM technique for construction because it eliminates the subjectivity that plagues percent-complete estimates.</p><p>This term is part of the <a href="/en/earned-value/definitions">earned value definitions glossary</a>. For understanding how different measurement techniques compare, see the <a href="/en/earned-value/definitions/progress-measurement">progress measurement</a> page.</p><h2 id="how-it-works">How It Works</h2><p>You break a <a href="/en/earned-value/definitions/work-package">work package</a> into discrete milestones, assign each a budget weight (usually based on the cost or effort proportion), and measure progress by counting completed milestones. The cumulative EV at any point is the sum of budget weights for all achieved milestones.</p><p>It's binary. Done or not done. That's what makes it powerful.</p><pre class="ge-ascii-diagram ge-anim"> WEIGHTED MILESTONES – HOW EV ACCUMULATES ============================================= Work Package: Structural Frame – BAC = £4,000,000 Milestone Weight Cum. EV Status ──────────────────────────────────────────────────── M1 Excavation complete 10% £400,000 DONE ✓ M2 Foundations poured 15% £1,000,000 DONE ✓ M3 Columns to level 2 20% £1,800,000 DONE ✓ M4 Slab level 2 cast 20% £2,600,000 IN PROGRESS M5 Columns to roof 20% £3,400,000 NOT STARTED M6 Frame complete 15% £4,000,000 NOT STARTED ──────────────────────────────────────────────────── Current EV = M1 + M2 + M3 = £400K + £600K + £800K = £1,800,000 (M4 is 70% done but gets ZERO credit until 100% complete) EV (£M) | 4.0 ┤ ────── M6 ✓ | ╱ 3.4 ┤ ──── M5 ✓ | ╱ 2.6 ┤ ──── M4 ✓ | ╱ 1.8 ┤ ──── M3 ✓ ← WE ARE HERE (EV = £1.8M) | ╱ 1.0 ┤ ── M2 ✓ | ╱ 0.4 ┤ M1 ✓ |╱ 0.0 ┼────────────────────────────────────── Time Jan Feb Mar Apr May Jun Staircase pattern = earned value only jumps at milestones Flat sections = work in progress, no EV credit yet</pre><p>The staircase pattern is the hallmark of weighted milestones. Between milestones, EV is flat. When a milestone completes, EV jumps. This creates a lumpy <a href="/en/earned-value/definitions/s-curve">S-curve</a> rather than the smooth curve you'd get from percent-complete measurement, but it's a more truthful representation of progress.</p><h2 id="why-its-the-best-method-for-construction">Why It's the Best Method for Construction</h2><p>I've used three EVM techniques on construction projects: percent complete, fixed formula (0/100 or 50/50), and weighted milestones. Weighted milestones wins. Here's why.</p><p>Percent complete is subjective. Ask three people how complete the M&amp;E rough-in is and you'll get three answers. The site foreman says 75% (based on what's installed). The QS says 60% (based on cost). The planner says 65% (based on programme). Who's right? Nobody knows, and the disagreement burns an hour of every progress meeting.</p><p>The <a href="/en/earned-value/definitions/fixed-formula-method">fixed formula method</a> (50/50 or 0/100) is too crude for packages longer than a few weeks. A 6-month M&amp;E package using 0/100 would show zero EV for 5.5 months then full credit at completion. That's useless for monthly reporting.</p><p>Weighted milestones hit the sweet spot. They're objective (the milestone is either done or it isn't), granular enough for monthly reporting (assuming you've set 4-8 milestones per package), and they force the team to define what "done" actually means before the work starts.</p><h2 id="setting-the-right-milestones">Setting the Right Milestones</h2><p>The quality of weighted milestone measurement depends entirely on how you define the milestones. Too few and you get the same problem as 0/100, long flat periods with no EV movement. Too many and you're basically doing percent complete with extra steps.</p><p><strong>The rules I follow:</strong></p><ul><li><strong>4 to 8 milestones per work package.</strong> Fewer than 4 creates reporting gaps. More than 8 starts to feel like micromanagement.</li><li><strong>Each milestone should represent a physical deliverable.</strong> "Foundations poured" is a milestone. "Design 50% complete" is not. That's just percent complete wearing a disguise.</li><li><strong>Milestone weights should reflect cost proportion.</strong> If excavation is 10% of the work package budget, the excavation milestone gets a 10% weight. Don't assign equal weights unless the milestones genuinely represent equal effort.</li><li><strong>Milestones must be objectively verifiable.</strong> Can someone walk on site and confirm it's done without a subjective judgement? If yes, it's a good milestone. If it requires a committee discussion, it's not.</li></ul><h2 id="worked-example-4m-structural-package-on-a-mixed-use-scheme">Worked Example: £4M Structural Package on a Mixed-Use Scheme</h2><span class="ge-worked-label">Worked Example</span><div class="ge-callout ge-anim"><p><strong>Scenario:</strong> A £4M structural frame package on a £30M NEC4 Option C mixed-use development in Bristol. The package has a 6-month duration from January to June 2026. The <a href="/en/earned-value/definitions/control-account-manager">CAM</a> sets up weighted milestones for EV measurement.</p><p><strong>Milestone definition:</strong></p><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>#</th><th>Milestone</th><th>Weight</th><th>Budget Value</th><th>Planned Completion</th></tr></thead><tbody><tr><td>M1</td><td>Excavation complete</td><td>10%</td><td>£400,000</td><td>31 Jan 2026</td></tr><tr><td>M2</td><td>Foundations poured and cured</td><td>15%</td><td>£600,000</td><td>28 Feb 2026</td></tr><tr><td>M3</td><td>Columns to level 2 complete</td><td>20%</td><td>£800,000</td><td>21 Mar 2026</td></tr><tr><td>M4</td><td>Level 2 slab cast and struck</td><td>20%</td><td>£800,000</td><td>18 Apr 2026</td></tr><tr><td>M5</td><td>Columns to roof level complete</td><td>20%</td><td>£800,000</td><td>16 May 2026</td></tr><tr><td>M6</td><td>Frame complete (roof slab cast)</td><td>15%</td><td>£600,000</td><td>13 Jun 2026</td></tr><tr><td></td><td><strong>Total</strong></td><td><strong>100%</strong></td><td><strong>£4,000,000</strong></td><td></td></tr></tbody></table></div><p><strong>Monthly progress report (end of March 2026):</strong></p><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Milestone</th><th>Status</th><th>EV Claimed</th></tr></thead><tbody><tr><td>M1 Excavation</td><td>Complete (27 Jan)</td><td>£400,000</td></tr><tr><td>M2 Foundations</td><td>Complete (3 Mar, 3 days late)</td><td>£600,000</td></tr><tr><td>M3 Columns to L2</td><td>Complete (20 Mar, 1 day early)</td><td>£800,000</td></tr><tr><td>M4 Level 2 slab</td><td>In progress (formwork 70% done)</td><td>£0</td></tr><tr><td>M5 Columns to roof</td><td>Not started</td><td>£0</td></tr><tr><td>M6 Frame complete</td><td>Not started</td><td>£0</td></tr></tbody></table></div><p><strong>EV at end of March = £400K + £600K + £800K = £1,800,000</strong></p><p>Note: M4 is 70% through formwork, but the weighted milestone method gives zero credit until the slab is cast and struck. This is conservative, but honest. The <a href="/en/earned-value/definitions/planned-value">PV</a> at end of March (per the baseline) includes M4 as scheduled for 18 April, so PV at end of March = £1,800,000.</p><p><strong>SV = £1,800,000 - £1,800,000 = £0. Exactly on programme.</strong></p><p>But here's the nuance: M2 was 3 days late. That 3-day slip was absorbed by completing M3 one day early and starting M4 formwork before the planned date. The milestones show on-programme, and the daily recovery effort is invisible in the numbers, which is exactly how it should work. The <a href="/en/earned-value/definitions/control-account-manager">CAM</a> managed the slippage within the package without escalation.</p></div><h2 id="common-mistakes">Common Mistakes</h2><ol><li><strong>Defining milestones that aren't binary.</strong> "Steel erection 50% complete" is not a milestone. It's a subjective progress estimate dressed up as a milestone. Real milestones are binary: "Steel erection to level 3 complete" can be verified by standing on site and looking up. Either the steel is there or it isn't.</li><li><strong>Weights that don't match cost.</strong> Assigning equal 20% weight to five milestones when the first one represents 5% of cost and the last represents 40% distorts the EV curve. Weight each milestone according to its proportion of the work package <a href="/en/earned-value/definitions/budget-at-completion">BAC</a>.</li><li><strong>Too few milestones on long packages.</strong> A 9-month M&amp;E package with only 2 milestones (rough-in complete, commissioning complete) means you'll have months of zero EV movement. Split it into 6-8 milestones covering first fix, second fix, testing, and commissioning stages.</li><li><strong>Changing milestone definitions mid-package.</strong> Once the baseline is set, the milestones are locked. If you redefine "foundations complete" halfway through to include backfill (which wasn't originally included), you've corrupted the baseline comparison. Any changes must go through the formal <a href="/en/earned-value/definitions/re-baselining">re-baselining</a> process.</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>When should I use weighted milestones instead of percent complete?</h3><p>Use weighted milestones whenever you can define clear physical deliverables, which is most construction work. Percent complete is better suited to continuous activities where there's no natural milestone, like site management or design coordination. For discrete packages (structural, M&amp;E, externals), weighted milestones are almost always the better choice.</p><h3>What happens to EV reporting during long gaps between milestones?</h3><p>EV stays flat. That's by design. If there's a 6-week gap between milestones, the <a href="/en/earned-value/definitions/s-curve">S-curve</a> will show a plateau. This can make progress look stalled in dashboard reports. The solution isn't to abandon weighted milestones. It's to break the package into more milestones so the gaps are shorter. Aim for monthly milestone completions at minimum.</p><h3>Can weighted milestones be combined with other EVTs on the same project?</h3><p>Absolutely. Most projects use a mix. Weighted milestones for construction packages, <a href="/en/earned-value/definitions/apportioned-effort">level of effort</a> for site management and prelims, and percent complete for design activities. Each <a href="/en/earned-value/definitions/work-package">work package</a> gets the technique that best fits the nature of the work. The <a href="/en/earned-value/implementation-guide">EVM implementation guide</a> covers how to select the right technique for each package type.</p></article></div>