What Is Discrete Effort 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="#the-three-types-of-effort">The Three Types of Effort</a></li><li><a href="#why-discrete-effort-produces-better-data">Why Discrete Effort Produces Better Data</a></li><li><a href="#the-80-20-rule">The 80/20 Rule</a></li><li><a href="#worked-example-structural-steelwork-package">Worked Example: Structural Steelwork Package</a></li><li><a href="#common-mistakes">Common Mistakes</a></li><li><a href="#converting-loe-to-discrete-practical-tips">Converting LOE to Discrete: Practical Tips</a></li><li><a href="#frequently-asked-questions">Frequently Asked Questions</a></li></ul></nav><article class="ge-article-body"><p>Discrete effort is work that produces a specific, measurable output, something you can point at and say "that's done" or "that's not done." In <a href="/en/earned-value">earned value management</a>, discrete effort is the gold standard for measuring progress because it's objective. You either erected the steel or you didn't. You either poured the concrete or you didn't. There's no judgement call.</p><p>Compare that with <a href="/en/earned-value/definitions/level-of-effort">Level of Effort</a> (LOE), where progress is measured by time spent rather than output delivered. The site manager has been on site for 6 months, so we'll say that work package is 50% complete. That's not measurement. That's assumption wearing a spreadsheet.</p><p>If you want your EVM data to mean anything, maximise the proportion of discrete effort in your work breakdown structure. The industry rule of thumb is 80/20: at least 80% discrete effort, no more than 20% LOE. Most construction projects can achieve this. Most don't bother.</p><p>This page is part of the <a href="/en/earned-value/definitions">earned value definitions glossary</a>. For the full formula reference, see the <a href="/en/earned-value/definitions">earned value formulas page</a>.</p><h2 id="the-three-types-of-effort">The Three Types of Effort</h2><p>EVM recognises three types of effort, each with a different method for earning value:</p><pre class="ge-ascii-diagram ge-anim"> ┌─────────────────────────────────────────────────────────────┐ │ THREE TYPES OF EFFORT IN EVM │ │ │ │ DISCRETE EFFORT LOE APPORTIONED │ │ (Measurable output) (Time-based) (Derived) │ │ │ │ EV based on: EV based on: EV based on: │ │ Physical completion Time elapsed Another WP's │ │ progress │ │ │ │ 100│ ╱────── 100│ ╱────── 100│ ╱──── │ │ │ ╱ │ ╱ │ ╱ │ │ % │ ╱ % │ ╱ % │ ╱ │ │ │ ╱ Steps │ ╱ Linear │ ╱ Mirrors │ │ │ ╱ (milestones) │╱ (automatic) │ ╱ parent │ │ 0 │╱────────────── 0 │────────────── 0 │╱────────── │ │ └───── Time ──── └──── Time ──── └──── Time ──── │ │ │ │ EXAMPLES: EXAMPLES: EXAMPLES: │ │ - Steelwork erection - Site management - QA inspection │ │ - Concrete pours - Security - Health &amp; safety│ │ - Piling - General prelims for a specific │ │ - Road surfacing - Design team work package │ │ - Cable pulling - Welfare │ │ - Drainage runs │ │ │ │ RELIABILITY: HIGH RELIABILITY: LOW RELIABILITY: MED│ │ (Objective) (Assumed) (Inherited) │ └─────────────────────────────────────────────────────────────┘ </pre><p><strong>Discrete effort</strong> earns value based on measurable physical completion. 200 of 400 piles installed = 50% complete. No ambiguity.</p><p><strong>Level of Effort (LOE)</strong> earns value based on time elapsed. If the site management work package is budgeted for 12 months and you're at month 6, EV = 50% of the budget. Regardless of whether the site manager has been brilliant or useless.</p><p><strong><a href="/en/earned-value/definitions/apportioned-effort">Apportioned effort</a></strong> earns value based on another work package's progress. The QA inspection for the steelwork package earns at the same rate as the steelwork itself. It's a derived measurement. Not ideal, but better than LOE.</p><h2 id="why-discrete-effort-produces-better-data">Why Discrete Effort Produces Better Data</h2><p>This isn't just theory. It changes the numbers you report to the board.</p><p>LOE work packages always show a <a href="/en/earned-value/definitions/cost-performance-index">CPI</a> of approximately 1.0 and an <a href="/en/earned-value/definitions/schedule-performance-index">SPI</a> of exactly 1.0. They have to. EV equals PV by definition (since progress is measured by time, not output). So LOE work packages mathematically cannot show schedule variance. They're invisible to the warning system.</p><p>That's dangerous. If 40% of your <a href="/en/earned-value/definitions/budget-at-completion">BAC</a> is in LOE work packages, 40% of your project is running on autopilot with no early warning capability. Your aggregate SPI could be 0.98 (looks fine) while the discrete portion is actually at 0.88 (not fine at all). The LOE is masking the problem.</p><p>I've seen this exact scenario on a £30M highways project. The programme reported SPI of 0.96, "minor slippage, nothing to worry about." When we stripped out the LOE, the discrete SPI was 0.82. The project was 18% behind on actual productive work. But the site management, security, traffic management, and welfare packages (all LOE) were pulling the average up because they always show SPI = 1.0.</p><p>That project finished 4 months late. The warning signs were there at month 5, but the LOE contamination hid them.</p><h2 id="the-80-20-rule">The 80/20 Rule</h2><p>Aim for at least 80% of your <a href="/en/earned-value/definitions/budget-at-completion">BAC</a> in discrete effort work packages. Cap LOE at 20%.</p><p>On construction projects, this is achievable. Most physical works are inherently discrete:</p><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Work Type</th><th>Effort Type</th><th>Measurement Method</th></tr></thead><tbody><tr><td>Piling (600mm CFA piles)</td><td>Discrete</td><td>Number installed / total required</td></tr><tr><td>Structural steelwork</td><td>Discrete</td><td>Tonnes erected / total tonnes</td></tr><tr><td>Concrete pours</td><td>Discrete</td><td>m3 poured / total m3</td></tr><tr><td>Road surfacing</td><td>Discrete</td><td>m2 laid / total m2</td></tr><tr><td>Cable installation</td><td>Discrete</td><td>Linear metres pulled / total LM</td></tr><tr><td>Drainage</td><td>Discrete</td><td>Metres laid / total metres</td></tr><tr><td>M&amp;E first fix</td><td>Discrete</td><td>Rooms completed / total rooms</td></tr><tr><td>Commissioning</td><td>Discrete</td><td>Systems commissioned / total systems</td></tr><tr><td>Site management</td><td>LOE</td><td>Time elapsed</td></tr><tr><td>Security</td><td>LOE</td><td>Time elapsed</td></tr><tr><td>General preliminaries</td><td>LOE</td><td>Time elapsed (or apportion to discrete packages)</td></tr><tr><td>Design team</td><td>LOE</td><td>Time elapsed (unless milestone-based)</td></tr></tbody></table></div><p>The trick is converting things that look like LOE into discrete effort. Site management feels like LOE, but you can apportion it across the discrete packages it supports. Design feels like LOE, but you can measure it against milestones (outline design issued, detailed design approved, construction drawings released). With a bit of creativity, you can push your discrete ratio above 85%.</p><h2 id="worked-example-structural-steelwork-package">Worked Example: Structural Steelwork Package</h2><span class="ge-worked-label">Worked Example</span><div class="ge-callout ge-anim"><p><strong>Scenario:</strong> A £4.2M structural steelwork package on a £32M NEC4 Option A distribution centre in Northampton. The package involves fabrication and erection of 1,850 tonnes of steel across three phases.</p><p><strong>Measurement method:</strong> Discrete, tonnes erected (verified by site survey each fortnight).</p><p><strong>At the month 4 review (30 June 2025):</strong></p><ul><li>Total tonnes in contract: 1,850t</li><li>Tonnes erected to date: 680t</li><li>Budget (BAC) for this package: £4,200,000</li><li>Budget rate: £4,200,000 / 1,850t = £2,270/tonne</li></ul><p><strong>EV calculation:</strong></p><ul><li>Physical % complete: 680 / 1,850 = <strong>36.8%</strong></li><li>EV = £4,200,000 x 0.368 = <strong>£1,545,600</strong></li><li><a href="/en/earned-value/definitions/planned-value">PV</a> at month 4 (from baseline programme): £1,720,000 (the programme shows 760t should be erected by now)</li><li><a href="/en/earned-value/definitions/actual-cost">AC</a> (Defined Cost for steelwork to date): £1,610,000</li></ul><p><strong>Performance indices:</strong></p><ul><li><a href="/en/earned-value/definitions/schedule-performance-index">SPI</a> = £1,545,600 / £1,720,000 = <strong>0.90</strong> (behind programme, 80t less than planned)</li><li><a href="/en/earned-value/definitions/cost-performance-index">CPI</a> = £1,545,600 / £1,610,000 = <strong>0.96</strong> (slight cost overrun, spending £2,368/tonne vs budget of £2,270/tonne)</li></ul><p><strong>Why this works:</strong> The measurement is objective. 680 tonnes is 680 tonnes, verified by survey, not estimated by a project manager with a spreadsheet. The SPI of 0.90 is a real signal that the steelwork is behind programme. If this were an LOE package, SPI would automatically be 1.0 and nobody would know there's a problem until the crane goes home early.</p></div><h2 id="common-mistakes">Common Mistakes</h2><ol><li><strong>Classifying physical works as LOE.</strong> I've seen earthworks packages measured as LOE because "it's hard to measure volume on site." It's not. You have GPS surveys, drone topography, and wagon counts. If you can measure it, measure it. Don't default to LOE because discrete measurement takes effort.</li></ol><ol><li><strong>Not reporting discrete and LOE performance separately.</strong> Your aggregate SPI includes LOE, which always equals 1.0. Report discrete SPI alongside aggregate SPI so decision-makers can see actual productive performance. On any project where LOE exceeds 15% of BAC, the aggregate SPI is misleading.</li></ol><ol><li><strong>Using percentage complete estimates as "discrete" measurement.</strong> A project manager saying "I think we're about 60% done" is not discrete measurement. That's subjective LOE wearing a percentage. Discrete effort requires an objective physical measure: tonnes, metres, units, m3, number of piles, number of rooms. If you can't count it, it's not discrete.</li></ol><ol><li><strong>Ignoring the 80/20 rule.</strong> Most construction EVM implementations I've reviewed have 50% to 60% discrete effort. That means 40% to 50% of the project is on autopilot with no schedule early warning. Push for 80%. The effort to convert LOE packages into discrete or apportioned packages pays for itself in data quality.</li></ol><h2 id="converting-loe-to-discrete-practical-tips">Converting LOE to Discrete: Practical Tips</h2><p>Not everything can be discrete. But more can be than most people think.</p><p><strong>Design work:</strong> Instead of measuring by time spent, measure by deliverable milestones. Outline design issued (20%), detailed design complete (50%), construction drawings issued (80%), design for construction approved (100%). That's discrete milestone measurement, and it's far more meaningful than "the design team has been working for 3 months."</p><p><strong>Commissioning:</strong> Measure by systems commissioned. 12 HVAC zones, each zone is a discrete unit. 8 of 12 commissioned = 67%. Not "we've been commissioning for 4 weeks out of 6."</p><p><strong>Preliminaries:</strong> Apportion to the discrete packages they support, weighted by value. If steelwork is 30% of the project by value, allocate 30% of the prelims budget to the steelwork package. Now the prelims earn at the same rate as the productive work.</p><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 <a href="/en/earned-value/definitions/earned-value">earned value</a> 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>What's the difference between discrete effort and Level of Effort?</h3><p>Discrete effort earns value based on measurable physical output (tonnes erected, metres laid, units installed). LOE earns value based on time elapsed, regardless of what was actually accomplished. Discrete effort produces reliable <a href="/en/earned-value/definitions/schedule-performance-index">SPI</a> and <a href="/en/earned-value/definitions/cost-performance-index">CPI</a> data. LOE always shows SPI of 1.0, making it useless for schedule performance measurement.</p><h3>Why does LOE contaminate EVM data?</h3><p>Because LOE work packages earn value automatically based on time, not output. Their SPI is always 1.0 by definition. When aggregated with discrete packages, they pull the overall SPI towards 1.0, masking real schedule slippage on the productive work. If 30% of your <a href="/en/earned-value/definitions/budget-at-completion">BAC</a> is LOE, your aggregate SPI is 30% fiction.</p><h3>What's the ideal ratio of discrete to LOE?</h3><p>The industry standard is 80% discrete, 20% maximum LOE. In construction, where most work is physical and measurable, you should aim for 85%+. The remaining 15% covers genuinely time-based activities like site management and security that can't reasonably be measured by output.</p><h3>Can apportioned effort replace discrete effort?</h3><p>No, discrete is always preferred. But apportioned effort is significantly better than LOE because it inherits the schedule performance of the parent discrete package. If the steelwork package (discrete) is behind programme, the QA inspection package (apportioned) will also show as behind programme. LOE would show it on track regardless.</p></article></div>