Pain/Gain Share in NEC4 Option C 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="#how-the-mechanism-works">How the Mechanism Works</a></li><li><a href="#worked-example-30m-option-c-with-banded-shares">Worked Example: £30M Option C With Banded Shares</a></li><li><a href="#how-evm-drives-the-pain-gain-outcome">How EVM Drives the Pain/Gain Outcome</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>Pain/gain share is the NEC4 mechanism that splits cost savings or overruns between the Client and Contractor on target cost contracts (Options C and D). If the final <a href="/en/earned-value/definitions/price-for-work-done-to-date">Price for Work Done to Date</a> comes in below the target, both parties share the gain. If it exceeds the target, both share the pain. The split ratios are defined in the Contract Data, and they're the single biggest commercial lever in any NEC4 Option C contract. </p><p>It's the mechanism that's supposed to align incentives. In theory, the Contractor is motivated to deliver efficiently because they keep a share of any saving. In practice? The maths gets complicated, the share ratios vary by band, and I've watched commercial teams misunderstand the calculation in ways that cost them six-figure sums. </p><p>This term is part of the <a href="/en/earned-value/definitions">earned value definitions glossary</a>. For how <a href="/en/earned-value">earned value management</a> connects to NEC4 target cost, see the <a href="/en/earned-value/nec4-target-cost">NEC4 target cost bridge page</a>. </p><h2 id="how-the-mechanism-works">How the Mechanism Works</h2><p>The calculation compares two numbers: </p><ol><li><strong>Total of the Prices</strong>: the target cost (adjusted for compensation events)</li><li><strong>Price for Work Done to Date (PWDD)</strong>: the actual <a href="/en/earned-value/definitions/defined-cost">Defined Cost</a> plus the Fee</li></ol><p>If PWDD < Total of the Prices, there's a gain. The Contractor keeps their share. If PWDD > Total of the Prices, there's pain. The Contractor absorbs their share. </p><pre class="ge-ascii-diagram ge-anim"> PAIN/GAIN SHARE MECHANISM – NEC4 OPTION C Target Cost (Total of the Prices): £30,000,000 GAIN ZONE PAIN ZONE (PWDD below target) (PWDD above target) │ Contractor Client │ Contractor Client keeps share keeps share │ absorbs absorbs │ ◄──────────────────────────────┼──────────────────────────────► £25M £27M £29M £30M │ £31M £33M £35M │ ────────────────────────────── │ ────────────────────────────── TYPICAL SHARE BANDS: │ │ Band 1: First 10% (£0-3M) │ Band 1: First 10% (£0-3M) Contractor: 50% │ Contractor: 50% Client: 50% │ Client: 50% │ Band 2: Beyond 10% (>£3M) │ Band 2: Beyond 10% (>£3M) Contractor: 25% │ Contractor: 80% Client: 75% │ Client: 20% │ INCENTIVE: Contractor keeps │ RISK: Contractor absorbs 50p of every £1 saved (first │ 50p of every £1 over target £3M), then 25p. │ (first £3M), then 80p. │ ════════════════════════════════════════════════════════════ NOTE: Share ratios are in Contract Data part 1. These are illustrative. Every contract is different. Common variants: 50/50 flat, 60/40, or banded as shown. </pre><p>The bands matter enormously. A flat 50/50 share means the Contractor carries half the pain to infinity. A banded structure (50/50 for the first tranche, then 80/20 beyond) means the Contractor's exposure accelerates as the overrun grows. The commercial team needs to understand exactly which structure they're working under. </p><h2 id="worked-example-30m-option-c-with-banded-shares">Worked Example: £30M Option C With Banded Shares</h2><span class="ge-worked-label">Worked Example</span><div class="ge-callout ge-anim"><p><strong>Scenario:</strong> £30M highways improvement, NEC4 Option C. 20-month programme. The Contract Data specifies the following pain/gain share:</p><br><p>- <strong>Gain:</strong> Contractor 50% / Client 50% (all savings)</p><p>- <strong>Pain:</strong> Contractor 50% / Client 50% (first 10% overrun), then Contractor 80% / Client 20% (beyond 10%)</p><br><p><strong>Target (Total of the Prices):</strong> £30,000,000 (adjusted for CEs throughout the project)</p><br><p><strong>Outcome 1: PWDD comes in at £27,600,000 (£2.4M under target)</strong></p><br><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Item</th><th>Calculation</th><th>Amount</th></tr></thead><tbody><tr><td>Saving</td><td>£30,000,000 - £27,600,000</td><td>£2,400,000</td></tr><tr><td>Contractor's gain share (50%)</td><td>£2,400,000 x 50%</td><td>£1,200,000</td></tr><tr><td>Client's gain share (50%)</td><td>£2,400,000 x 50%</td><td>£1,200,000</td></tr><tr><td><strong>Contractor receives</strong></td><td>PWDD + gain share</td><td><strong>£28,800,000</strong></td></tr></tbody></table></div><br><p>The Contractor delivered the work for £27.6M and takes home £28.8M. Good project. The gain share adds £1.2M to their bottom line.</p><br><p><strong>Outcome 2: PWDD comes in at £32,400,000 (£2.4M over target)</strong></p><br><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Item</th><th>Calculation</th><th>Amount</th></tr></thead><tbody><tr><td>Overrun</td><td>£32,400,000 - £30,000,000</td><td>£2,400,000</td></tr><tr><td>First 10% band (£3M cap), Contractor 50%</td><td>£2,400,000 x 50%</td><td>£1,200,000</td></tr><tr><td><strong>Contractor absorbs</strong></td><td></td><td><strong>£1,200,000</strong></td></tr><tr><td><strong>Contractor receives</strong></td><td>PWDD - pain share = £32,400,000 - £1,200,000</td><td><strong>£31,200,000</strong></td></tr></tbody></table></div><br><p>The Contractor spent £32.4M but only receives £31.2M. They've absorbed £1.2M of the £2.4M overrun.</p><br><p><strong>Outcome 3: PWDD comes in at £35,000,000 (£5M over target, bad project)</strong></p><br><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Item</th><th>Calculation</th><th>Amount</th></tr></thead><tbody><tr><td>Overrun</td><td>£35,000,000 - £30,000,000</td><td>£5,000,000</td></tr><tr><td>First 10% band (£3M), Contractor 50%</td><td>£3,000,000 x 50%</td><td>£1,500,000</td></tr><tr><td>Beyond 10% band (£2M), Contractor 80%</td><td>£2,000,000 x 80%</td><td>£1,600,000</td></tr><tr><td><strong>Total Contractor pain share</strong></td><td></td><td><strong>£3,100,000</strong></td></tr><tr><td><strong>Contractor receives</strong></td><td>£35,000,000 - £3,100,000</td><td><strong>£31,900,000</strong></td></tr></tbody></table></div><br><p>Now the banding bites. The Contractor spent £35M, receives £31.9M, and absorbs £3.1M of a £5M overrun. That's 62% of the overrun. If the Contractor's fee percentage was 8% on the original £30M target (£2.4M fee), they've just wiped out their entire fee and are losing £700K on the job.</p></div><h2 id="how-evm-drives-the-pain-gain-outcome">How EVM Drives the Pain/Gain Outcome</h2><p><a href="/en/earned-value/definitions/cost-performance-index">Cost Performance Index</a> is the leading indicator of where you'll land on the pain/gain scale. If cumulative CPI is below 1.0, you're trending towards pain. Above 1.0, you're trending towards gain. </p><p>The <a href="/en/earned-value/eac-etc-tcpi">EAC formula</a> (EAC = BAC / CPI) gives you the projected PWDD. Compare that to the target and you know your projected share position months before final account. </p><p>On the £30M highways project above, if CPI at month 12 is 0.93: </p><ul><li>Projected PWDD = £30,000,000 / 0.93 = £32,258,065</li><li>Projected overrun = £2,258,065</li><li>Projected Contractor pain share (at 50%) = £1,129,032</li></ul><p>That's a £1.13M hit to the Contractor's bottom line. And you can see it coming at month 12, with 8 months still to go. Eight months to investigate, intervene, recover CEs, and fight to get that CPI above 1.0. </p><h2 id="common-mistakes">Common Mistakes</h2><ol><li><strong>Not adjusting the target for compensation events</strong>: The target is not fixed at contract award. Every assessed compensation event adjusts the Total of the Prices. If the target isn't updated, the pain/gain calculation at final account will be wrong. I've seen disputes worth £800K that came down entirely to whether two CEs had been properly incorporated into the target.</li><li><strong>Confusing Defined Cost with PWDD</strong>: The pain/gain calculation uses PWDD, which is Defined Cost plus <a href="/en/earned-value/definitions/fee-percentage">Fee</a>. Not Defined Cost alone. The Fee is a percentage of Defined Cost. Getting this wrong understates the Contractor's costs and makes the gain look larger (or the pain smaller) than it really is.</li><li><strong>Ignoring disallowed cost</strong>: <a href="/en/earned-value/definitions/disallowed-cost">Disallowed Cost</a> is excluded from PWDD. If the Project Manager disallows £400K of cost, that comes straight off the Contractor's side. It doesn't reduce the pain; it increases it. The Contractor spent the money but can't include it in the calculation.</li><li><strong>Not modelling the share bands during tender</strong>: The pain/gain share structure should inform the tender price. If pain accelerates beyond 10% (Contractor takes 80%), you need to understand where that threshold sits relative to your risk exposure. Too many teams price the target without modelling the share mechanics.</li><li><strong>Treating pain/gain as a final account exercise</strong>: The share calculation happens at final account, but you should be projecting it monthly from month 3 onwards. Waiting until the end to discover you're in pain is inexcusable when the data exists to forecast it.</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>Does pain/gain share apply to all NEC4 contracts?</h3><p>No. Only Options C (target cost with activity schedule) and D (target cost with bill of quantities). Options A and B are lump sum, the Contractor carries all cost risk and reward. Option E is cost reimbursable with no target and no share mechanism. The pain/gain mechanism is specifically designed for target cost contracts where the Client wants some cost certainty while sharing the risk. </p><h3>Can the Contractor lose money on an NEC4 Option C contract?</h3><p>Yes. If the pain share exceeds the Contractor's fee (profit and overhead recovery), the project makes a loss. On a contract with an 8% fee on a £30M target (£2.4M), a Contractor pain share exceeding £2.4M means the project is loss-making. With aggressive banding (80% Contractor share beyond 10%), this can happen with overruns of 14% or more. It's not theoretical. It happens. </p><h3>What happens to pain/gain if compensation events increase the target significantly?</h3><p>Each assessed compensation event increases the Total of the Prices. If a £30M target grows to £34M through legitimate CEs, the pain/gain calculation uses £34M as the target. The Contractor isn't penalised for Client-risk events that increase cost. But, and this is important, the CE assessment must be correct. If a CE is under-assessed, the target increases by less than the actual cost impact, and the difference shows up as pain at final account. </p><h3>How does pain/gain share interact with earned value metrics?</h3><p>Your <a href="/en/earned-value/definitions/cost-performance-index">CPI</a> directly predicts your position. CPI > 1.0 = gain zone. CPI < 1.0 = pain zone. <a href="/en/earned-value/definitions/estimate-at-completion">EAC</a> predicts the final PWDD. Subtract the target from EAC and you've got the projected overrun or saving. Apply the share percentages and you know the projected financial outcome for both parties. Monthly EVM reporting makes this prediction available throughout the project, not just at final account. </p></article></div>