What Is a Planning Package in EVM? Future Work Budgets

<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-hierarchy-where-planning-packages-live">The Hierarchy: Where Planning Packages Live</a></li><li><a href="#worked-example-progressive-elaboration-on-a-20m-project">Worked Example: Progressive Elaboration on a £20M Project</a></li><li><a href="#when-to-convert-the-two-month-rule">When to Convert: The Two-Month Rule</a></li><li><a href="#planning-package-vs-undistributed-budget-vs-management-reserve">Planning Package vs Undistributed Budget vs Management Reserve</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>A planning package is a budget placeholder within a <a href="/en/earned-value/definitions/control-account">control account</a> for work that's been identified but not yet planned in enough detail to become a work package. You know it's coming. You know roughly what it'll cost. But you don't yet have the scope definition, schedule detail, or <a href="/en/earned-value/definitions/earned-value-technique">earned value technique</a> assignment needed to measure progress against it. So you park the budget in a planning package until you do. </p><p>It's not laziness. It's honesty. Pretending you can plan Phase 3 fit-out to work package detail while you're still pouring Phase 1 foundations is fiction. Planning packages acknowledge that construction projects are progressively elaborated. You plan in detail what you're doing now, and at a summary level what you're doing later. </p><p>This term is part of the <a href="/en/earned-value/definitions">earned value definitions glossary</a>. For how planning packages sit within the broader WBS, see the <a href="/en/earned-value/implementation-guide">earned value implementation guide</a>. </p><h2 id="the-hierarchy-where-planning-packages-live">The Hierarchy: Where Planning Packages Live</h2><pre class="ge-ascii-diagram ge-anim"> CONTROL ACCOUNT STRUCTURE – SHOWING PLANNING PACKAGES Control Account: CA-04 Internal Fit-Out Owner: S. Patel BAC: £5,200,000 Duration: Month 6 to Month 18 ┌──────────────────────────────────────────────────┐ │ CONTROL ACCOUNT: CA-04 │ │ Budget: £5,200,000 │ │ │ │ ┌─────────────────────────────────────────────┐ │ │ │ WORK PACKAGES (detailed) │ │ │ │ Budget: £3,300,000 │ │ │ │ │ │ │ │ WP-04.1: Drylining £1,200,000 Months 6-10 │ │ │ WP-04.2: Floor screed £480,000 Months 7-9 │ │ │ WP-04.3: Carpentry £620,000 Months 8-11 │ │ │ WP-04.4: Painting £540,000 Months 9-12 │ │ │ WP-04.5: Floor finish £460,000 Months 10-13 │ │ │ │ │ │ │ → Scope defined │ │ │ │ → Schedule detailed │ │ │ │ → EVTs assigned │ │ │ │ → Ready for EV measurement │ │ │ └─────────────────────────────────────────────┘ │ │ │ │ ┌─────────────────────────────────────────────┐ │ │ │ PLANNING PACKAGE (placeholder) │ │ │ │ Budget: £1,900,000 │ │ │ │ │ │ │ │ PP-04.A: Phase 2 Specialist Fit-Out │ │ │ │ £1,900,000 Months 12-18 │ │ │ │ │ │ │ │ → Scope identified but not detailed │ │ │ │ → Schedule: rough start/end only │ │ │ │ → No EVT assigned yet │ │ │ │ → CANNOT earn EV until converted │ │ │ │ → Will be converted to work packages │ │ │ │ by Month 10 (2 months before start) │ │ │ └─────────────────────────────────────────────┘ │ │ │ │ TOTAL: £3,300,000 + £1,900,000 = £5,200,000 │ │ All budget accounted for. No gaps. No double- │ │ counting. Planning package converted before │ │ the work begins. │ └──────────────────────────────────────────────────┘ </pre><p>The critical rule: <strong>planning packages cannot earn value.</strong> They hold budget, but until they're converted to work packages with defined scope, schedule, and an EVT, no <a href="/en/earned-value/definitions/earned-value">earned value</a> is claimed against them. This prevents teams from reporting progress on work that hasn't been properly planned. </p><h2 id="worked-example-progressive-elaboration-on-a-20m-project">Worked Example: Progressive Elaboration on a £20M Project</h2><span class="ge-worked-label">Worked Example</span><div class="ge-callout ge-anim"><p><strong>Scenario:</strong> £20M mixed-use development in Leeds. 22-month programme under NEC4 Option C. The project has three phases, but at contract award only Phase 1 has detailed work packages.</p><br><p><strong>At contract award (Month 0):</strong></p><br><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Control Account</th><th>Work Packages</th><th>Planning Packages</th><th>Total Budget</th></tr></thead><tbody><tr><td>CA-01 Substructure</td><td>4 WPs (detailed)</td><td>None</td><td>£3,100,000</td></tr><tr><td>CA-02 Frame</td><td>3 WPs (detailed)</td><td>1 PP (roof structure)</td><td>£4,800,000</td></tr><tr><td>CA-03 Envelope</td><td>2 WPs (detailed)</td><td>1 PP (curtain wall Phase 2)</td><td>£3,400,000</td></tr><tr><td>CA-04 M&amp;E</td><td>1 WP (risers only)</td><td>2 PPs (distribution, commissioning)</td><td>£4,200,000</td></tr><tr><td>CA-05 Fit-Out</td><td>None</td><td>1 PP (entire scope)</td><td>£2,800,000</td></tr><tr><td>CA-06 Externals</td><td>None</td><td>1 PP (entire scope)</td><td>£1,700,000</td></tr><tr><td><strong>Total</strong></td><td><strong>10 WPs</strong></td><td><strong>6 PPs</strong></td><td><strong>£20,000,000</strong></td></tr></tbody></table></div><br><p>Budget in work packages: £11,600,000 (58%)</p><p>Budget in planning packages: £8,400,000 (42%)</p><br><p>That 42% in planning packages is fine at Month 0 on a 22-month project. You can't plan fit-out details when you haven't finished the design.</p><br><p><strong>At Month 6 (Phase 1 nearing completion, Phase 2 starting):</strong></p><br><p>Conversions completed:</p><p>- PP in CA-02 → converted to WP-02.4 (roof structure, £1,100,000, weighted milestones)</p><p>- PP in CA-03 → converted to 2 WPs (curtain wall zones A and B, £1,800,000 total, units complete)</p><p>- PP-1 in CA-04 → converted to 3 WPs (distribution by floor, £1,900,000, percent complete by zone)</p><br><p>Budget in work packages: £16,400,000 (82%)</p><p>Budget in planning packages: £3,600,000 (18%)</p><br><p><strong>At Month 12 (Phase 2 well underway, Phase 3 imminent):</strong></p><br><p>All remaining planning packages converted:</p><p>- PP-2 in CA-04 → converted to WP-04.6 (commissioning, £400,000, milestones)</p><p>- PP in CA-05 → converted to 5 WPs (fit-out by zone, £2,800,000, mixed EVTs)</p><p>- PP in CA-06 → converted to 3 WPs (landscaping, car park, services, £1,700,000)</p><br><p>Budget in work packages: £20,000,000 (100%)</p><p>Budget in planning packages: £0 (0%)</p><br><p><strong>The conversion schedule was planned from Day 1.</strong> The project controls plan specified when each planning package would be converted, with a firm rule: conversion must happen at least 2 months before work starts.</p></div><h2 id="when-to-convert-the-two-month-rule">When to Convert: The Two-Month Rule</h2><p>There's no universal standard, but the practice I recommend (and the one that works) is to convert planning packages to work packages at least two reporting periods before the work begins. On a monthly reporting cycle, that's two months. </p><p>Why two months? Because conversion isn't just renaming a line item. You need to: </p><ol><li>Define the detailed scope (what's in, what's out)</li><li>Build the schedule (activities, durations, dependencies)</li><li>Spread the budget across activities (create the time-phased <a href="/en/earned-value/definitions/planned-value">planned value</a> curve)</li><li>Assign the earned value technique</li><li>Get the <a href="/en/earned-value/definitions/control-account">control account</a> manager to sign off</li></ol><p>Rush this and you end up with work packages that are planning packages in disguise, they have a name and a budget but no real schedule or EVT. That defeats the entire purpose. </p><h2 id="planning-package-vs-undistributed-budget-vs-management-reserve">Planning Package vs Undistributed Budget vs Management Reserve</h2><p>These three things look similar but serve completely different purposes. I've seen them confused on almost every project I've worked on. </p><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th></th><th>Planning Package</th><th><a href="/en/earned-value/definitions/undistributed-budget">Undistributed Budget</a></th><th><a href="/en/earned-value/definitions/management-reserve">Management Reserve</a></th></tr></thead><tbody><tr><td><strong>What is it?</strong></td><td>Budget for identified but undetailed work</td><td>Budget received (via change) but not yet allocated to a CA</td><td>Budget for unknown unknowns</td></tr><tr><td><strong>Where does it sit?</strong></td><td>Inside a control account</td><td>Outside control accounts, inside BAC</td><td>Outside BAC entirely</td></tr><tr><td><strong>Part of BAC?</strong></td><td>Yes</td><td>Yes</td><td>No</td></tr><tr><td><strong>Part of PMB?</strong></td><td>Yes (at summary level)</td><td>Temporarily no (until distributed)</td><td>No</td></tr><tr><td><strong>Can earn EV?</strong></td><td>No (until converted)</td><td>No (until distributed)</td><td>No</td></tr><tr><td><strong>Who manages it?</strong></td><td>Control account manager</td><td>Project controls lead</td><td>Programme director</td></tr></tbody></table></div><p>The key distinction: planning packages are inside a control account with an owner. Undistributed budget is floating between control accounts waiting to be allocated. Management reserve is outside the <a href="/en/earned-value/definitions/performance-measurement-baseline">performance measurement baseline</a> entirely. </p><h2 id="common-mistakes">Common Mistakes</h2><ol><li><strong>Leaving planning packages unconverted when work starts</strong>: If work begins on an unconverted planning package, you can't earn value against it. Some teams "solve" this by claiming EV anyway and promising to formalise the work package later. Don't. That's uncontrolled EV that will create reconciliation nightmares.</li><li><strong>Having too many planning packages too late in the project</strong>: At project start, 40% of BAC in planning packages is reasonable. At the halfway point, it should be under 10%. At 75% through, it should be zero. If you still have significant budget in planning packages past the halfway mark, your planning process has failed.</li><li><strong>Converting planning packages to a single mega-work package</strong>, The point of conversion is to add detail. Turning a £1.9M planning package into a single £1.9M work package with "percent complete, supervisor estimate" as the EVT adds no analytical value. Break it into 3 to 5 work packages with appropriate EVTs.</li><li><strong>Not adjusting the time-phased budget during conversion</strong>: Planning packages have a rough time profile (budget spread). When you convert to work packages, the time phasing needs to reflect the detailed schedule, not the original rough spread. Failing to update this creates <a href="/en/earned-value/definitions/planned-value">planned value</a> curves that don't match the actual work plan.</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>Can a planning package earn earned value?</h3><p>No. That's the defining characteristic. A planning package holds budget at the summary level but has no schedule detail or EVT assigned, so there's no basis for measuring progress. EV can only be earned against work packages. The planning package must be converted to one or more work packages before any value can be claimed. </p><h3>How many planning packages is too many?</h3><p>It depends on where you are in the project lifecycle. At contract award, having 30 to 50% of BAC in planning packages is normal for a complex construction project, you can't detail-plan work that's 18 months away. By the 25% completion mark, aim for under 20%. By 50% completion, under 5%. By 75% completion, zero. If you're still converting planning packages past the halfway point, your progressive elaboration process is too slow. </p><h3>What's the difference between a planning package and an unplanned work package?</h3><p>A planning package is an intentional, controlled placeholder within the EVM system. It has a budget, sits inside a defined control account, and has a planned conversion date. An "unplanned work package" is usually scope that was missed entirely during planning. It doesn't appear in the WBS at all. Planning packages are good practice. Unplanned scope is a planning failure. </p><h3>Who decides when to convert a planning package?</h3><p>The <a href="/en/earned-value/definitions/control-account-manager">control account manager</a> owns the conversion, but the timing should be governed by the project controls plan. Best practice is to have a conversion schedule agreed at project start, reviewed monthly, and enforced as a project controls milestone. The project controls lead should be tracking planning package percentages and escalating if conversions are falling behind. </p></article></div>