What Is a Performance Measurement Baseline (PMB) in EVM?

<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-definition">The Definition</a></li><li><a href="#how-the-pmb-is-built">How the PMB Is Built</a></li><li><a href="#pmb-vs-total-project-budget">PMB vs Total Project Budget</a></li><li><a href="#worked-example-building-a-pmb">Worked Example: Building a PMB</a></li><li><a href="#the-pmb-on-nec4-contracts">The PMB on NEC4 Contracts</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 Performance Measurement Baseline (PMB) is the authorised, time-phased budget plan against which all <a href="/en/earned-value">earned value</a> performance is measured. Think of it as the total plan for how every pound will be spent, across every work package, across every month of the project. Without it, EVM is just arithmetic. With it, EVM becomes a diagnostic system. </p><p>Most people assume the PMB is just "the budget." It isn't. The PMB is the budget distributed across time and organised by control account. It excludes management reserve. That distinction matters, and I've watched it trip up commercial teams on projects worth tens of millions. </p><p>This term 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/formulas">earned value formulas page</a>. </p><h2 id="the-definition">The Definition</h2><p><strong>PMB = Sum of all control account budgets + Undistributed Budget (UB)</strong></p><p>Or, equivalently: </p><p><strong>Total Project Budget = PMB + Management Reserve (MR)</strong></p><p>The PMB includes every pound that's been assigned to specific work. Management reserve sits outside the PMB because it hasn't been allocated to any control account yet. It's the contingency held by the project manager for unknown unknowns. </p><p>When management reserve is drawn down to cover a problem, it moves into the PMB (allocated to a control account). The PMB grows, but the total project budget stays the same. </p><h2 id="how-the-pmb-is-built">How the PMB Is Built</h2><p>The PMB doesn't appear from nowhere. It's constructed bottom-up from the work breakdown structure, through control accounts, into a time-phased budget that creates the baseline S-curve. </p><pre class="ge-ascii-diagram ge-anim"> Building the PMB – From WBS to S-Curve WORK BREAKDOWN STRUCTURE ┌─────────────────────────────────────┐ │ Project (£28M total budget) │ │ ├── WBS 1: Foundations £4.2M │ │ ├── WBS 2: Structures £8.5M │ │ ├── WBS 3: M&amp;E £6.1M │ │ ├── WBS 4: Fit-out £5.8M │ │ └── WBS 5: Externals £1.9M │ └─────────────────────────────────────┘ │ ▼ CONTROL ACCOUNTS (8 accounts) ┌─────────────────────────────────────┐ │ CA-01: Piling £2.1M │ │ CA-02: Substructure £2.1M │ │ CA-03: Steel frame £4.8M │ │ CA-04: Concrete frame £3.7M │ │ CA-05: M&amp;E install £6.1M │ │ CA-06: Internal fit-out £5.8M │ │ CA-07: Externals £1.9M │ │ CA-08: Undistributed £0.5M (UB) │ │ ───── │ │ PMB Total: £27.0M │ │ + Management Reserve: £1.0M │ │ = Total Project Budget: £28.0M │ └─────────────────────────────────────┘ │ ▼ TIME-PHASED BUDGET (18 months) ┌─────────────────────────────────────┐ │ £K │ │ 2400│ xxxxxx │ │ 2000│ xxx xxx │ │ 1600│ xx xx │ │ 1200│ xx xx │ │ 800│ xx xx │ │ 400│ x x │ │ └──┬──┬──┬──┬──┬──┬──┬──┬──┬─ │ │ M1 M3 M5 M7 M9 M11 M13 M18│ │ │ │ Cumulative PMB = the S-curve │ │ (This is your PV baseline) │ └─────────────────────────────────────┘ </pre><p>The cumulative PMB plotted over time is your <a href="/en/earned-value/definitions/planned-value">Planned Value</a> curve. At any given month, the cumulative PV equals the sum of all budgeted work scheduled to that date from the PMB. </p><h2 id="pmb-vs-total-project-budget">PMB vs Total Project Budget</h2><p>This catches people out. The PMB is not the same as the total project budget. </p><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Component</th><th>Part of PMB?</th><th>Part of Total Budget?</th></tr></thead><tbody><tr><td>Control account budgets (all WBS elements)</td><td>Yes</td><td>Yes</td></tr><tr><td>Undistributed budget (UB)</td><td>Yes</td><td>Yes</td></tr><tr><td>Management reserve (MR)</td><td><strong>No</strong></td><td>Yes</td></tr></tbody></table></div><p><strong>Why does management reserve sit outside the PMB?</strong> Because MR is unallocated contingency. It hasn't been assigned to any work package or control account. Including it in the PMB would inflate your baseline and make performance look artificially good. When MR is drawn down, it enters the PMB through a formal baseline change. </p><p>On a £28M project with £1M of management reserve, the PMB is £27M. Every EVM calculation uses £27M as the baseline, not £28M. If you calculate <a href="/en/earned-value/definitions/cost-performance-index">CPI</a> or <a href="/en/earned-value/definitions/schedule-performance-index">SPI</a> against £28M, you're measuring performance against a budget that includes money you haven't planned to spend yet. Your metrics will look better than reality. </p><h2 id="worked-example-building-a-pmb">Worked Example: Building a PMB</h2><span class="ge-worked-label">Worked Example</span><div class="ge-callout ge-anim"><p><strong>Scenario:</strong> A £28M NEC4 Option C commercial fit-out project in Birmingham. 18-month programme from April 2025 to September 2026. The project controls team builds the PMB during mobilisation.</p><br><p><strong>Step 1: Establish BAC and MR</strong></p><p>- Target total of the Prices: £28,000,000</p><p>- Management reserve (agreed with sponsor): £1,000,000 (3.6%)</p><p>- <strong><a href="/en/earned-value/definitions/budget-at-completion">BAC</a> for PMB purposes: £27,000,000</strong></p><br><p><strong>Step 2: Allocate to control accounts</strong></p><br><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Control Account</th><th>CAM</th><th>Budget</th><th>% of PMB</th></tr></thead><tbody><tr><td>CA-01: Piling and foundations</td><td>Sarah Mitchell</td><td>£2,100,000</td><td>7.8%</td></tr><tr><td>CA-02: Substructure</td><td>Sarah Mitchell</td><td>£2,100,000</td><td>7.8%</td></tr><tr><td>CA-03: Steel frame</td><td>Dave Thornton</td><td>£4,800,000</td><td>17.8%</td></tr><tr><td>CA-04: Concrete works</td><td>Dave Thornton</td><td>£3,700,000</td><td>13.7%</td></tr><tr><td>CA-05: M&amp;E installation</td><td>Raj Patel</td><td>£6,100,000</td><td>22.6%</td></tr><tr><td>CA-06: Internal fit-out</td><td>Claire Adams</td><td>£5,800,000</td><td>21.5%</td></tr><tr><td>CA-07: External works</td><td>Claire Adams</td><td>£1,900,000</td><td>7.0%</td></tr><tr><td>CA-08: Undistributed budget</td><td>PM hold</td><td>£500,000</td><td>1.8%</td></tr><tr><td><strong>PMB Total</strong></td><td></td><td><strong>£27,000,000</strong></td><td><strong>100%</strong></td></tr></tbody></table></div><br><p><strong>Step 3: Time-phase each control account</strong></p><br><p>Each control account manager (CAM) distributes their budget across the programme months based on the Accepted Programme. For example, CA-03 (steel frame) spans months 4-9:</p><br><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Month</th><th>M4</th><th>M5</th><th>M6</th><th>M7</th><th>M8</th><th>M9</th></tr></thead><tbody><tr><td>Monthly spend (£K)</td><td>480</td><td>960</td><td>1,200</td><td>1,080</td><td>720</td><td>360</td></tr><tr><td>Cumulative (£K)</td><td>480</td><td>1,440</td><td>2,640</td><td>3,720</td><td>4,440</td><td>4,800</td></tr></tbody></table></div><br><p><strong>Step 4: Stack all control accounts to create the PMB S-curve</strong></p><br><p>The cumulative total across all CAs creates the baseline S-curve. At month 9, cumulative PMB = £16,200,000. This means PV at month 9 is £16.2M.</p><br><p>If <a href="/en/earned-value/definitions/earned-value">EV</a> at month 9 comes in at £14.8M, SPI = 14.8 / 16.2 = 0.914. The project is delivering progress at 91.4% of the planned rate.</p></div><h2 id="the-pmb-on-nec4-contracts">The PMB on NEC4 Contracts</h2><p>On NEC4 Option C, the PMB maps to the cost-loaded Accepted Programme against the target total of the Prices. That's a mouthful, but here's what it means in practice: </p><p><strong>The Accepted Programme is your time-phasing mechanism.</strong> Every activity on the Accepted Programme should have a Defined Cost allocation. The cumulative cost to any date is <a href="/en/earned-value/definitions/planned-value">PV</a>. </p><p><strong>The target total is your BAC (minus MR).</strong> If you've set aside management reserve, subtract it from the target to get the PMB. Most NEC4 projects don't explicitly separate MR from the target, which is a problem. Without a clear MR allocation, there's no budget buffer that sits outside the PMB. </p><p><strong>Compensation events change the PMB.</strong> When a CE is implemented under clause 65, the target adjusts. The PMB should be updated to reflect the new scope and its time-phased budget. This is a formal baseline change, not a casual adjustment. </p><p>I've worked on projects where the PMB was set at contract award and never touched again despite twelve compensation events totalling £2.3M. The EVM data was measuring performance against a baseline that was £2.3M short of reality. Every metric was wrong. The fix took the project controls team a week of rework. </p><h2 id="common-mistakes">Common Mistakes</h2><ol><li><strong>Including management reserve in the PMB.</strong> The most fundamental error. If MR is in your PMB, your baseline is inflated and your CPI looks better than it is. MR sits outside until it's formally allocated to a control account through a baseline change request.</li><li><strong>Not time-phasing the budget.</strong> A PMB that says "CA-03: £4.8M" without distributing it across months isn't a PMB. It's a budget allocation. Without time-phasing, you can't derive PV, which means you can't calculate SPI or SV. The PMB must be time-phased or it's useless for EVM.</li><li><strong>Setting the PMB once and never updating it.</strong> The PMB isn't a museum piece. It changes when scope changes are formally approved (CEs on NEC4, variations on JCT). Keep it current or accept that your EVM is measuring against a fiction.</li><li><strong>No undistributed budget.</strong> On complex projects, not all scope is fully defined at contract award. Some budget should sit as undistributed (within the PMB but not yet allocated to a specific control account) until the scope clarifies. This is where <a href="/en/earned-value/definitions/planning-package">planning packages</a> come in.</li><li><strong>Confusing PMB with the S-curve.</strong> The S-curve is a visualisation of the PMB. The PMB is the underlying data: control account budgets, time-phased, summing to BAC minus MR. The S-curve is what it looks like when you plot the cumulative total over time.</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>What's the difference between PMB and <a href="/en/earned-value/definitions/budget-at-completion">BAC</a>?</h3><p>On most construction projects, they're very close. BAC is the total approved project budget. PMB = BAC minus management reserve. If there's no formal MR, PMB equals BAC. In practice, many UK construction projects don't explicitly define MR, so the PMB and BAC are treated as the same number. That works until you need a contingency drawdown and suddenly there's no mechanism for a formal baseline change. </p><h3>How often should the PMB be updated?</h3><p>Only when there's a formal baseline change: an approved compensation event, a scope variation, or a re-baseline triggered by a major programme revision. Monthly updates to "smooth out" the PMB are a red flag. They usually mean someone is adjusting the baseline to hide poor performance. The PMB should be stable between formal changes. </p><h3>Can the PMB decrease?</h3><p>Yes, if a scope reduction is formally implemented. On NEC4, a CE that reduces the target (rare but possible) would reduce the PMB. In practice, PMBs almost always grow because scope changes typically add work, not remove it. </p><h3>What happens when management reserve is exhausted?</h3><p>If MR is fully consumed, the only remaining budget flexibility comes from requesting additional funding (a new budget from the sponsor) or accepting that the project will overrun the total budget. Exhausting MR is an escalation trigger. It means all identified contingency has been used and the project is exposed to any further scope changes or risks. </p></article></div>