What Is Resource Loading in Construction Scheduling?

<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="#the-conversion-chain">The Conversion Chain</a></li><li><a href="#why-resource-loading-is-where-evm-succeeds-or-fails">Why Resource Loading Is Where EVM Succeeds or Fails</a></li><li><a href="#worked-example-earthworks-package-6-activities">Worked Example: Earthworks Package, 6 Activities</a></li><li><a href="#loading-methods">Loading Methods</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>Resource loading is the process of assigning labour, plant, and materials to every activity in your construction programme. It's the step that transforms a bar chart into a cost-loaded schedule, and without it, you can't generate a <a href="/en/earned-value/definitions/planned-value">Planned Value</a> (PV) curve. No PV curve, no <a href="/en/earned-value">earned value management</a>. The whole system depends on this one exercise. </p><p>Resource loading 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>Resource loading = assigning specific resources (labour hours, plant days, material quantities and costs) to each scheduled activity, then pricing those resources to create a time-phased cost baseline</strong></p><p>The output is a cost-loaded programme where every activity has a budget and a duration. When you spread those budgets across the project timeline, you get the PV curve, the S-curve that tells you how much work should be done at any point in time. </p><p>On NEC4 Option A, the Activity Schedule provides the budget per activity. Resource loading adds the time dimension: which month does each activity's cost fall in? </p><h2 id="the-conversion-chain">The Conversion Chain</h2><p>Every EVM system starts here. This is the chain from raw programme to usable PV data. </p><pre class="ge-ascii-diagram ge-anim"> FROM PROGRAMME TO PLANNED VALUE ================================ Step 1: ACTIVITY Step 2: RESOURCES Step 3: COST (what needs doing) (what's needed) (what it costs) ┌───────────────┐ ┌─────────────────────────┐ ┌──────────────────┐ │ Earthworks │───▶│ 2x excavators (8 weeks) │───▶│ Plant: £96,000 │ │ Wk 4 - Wk 12 │ │ 1x dozer (6 weeks) │ │ Plant: £36,000 │ │ │ │ 6x labourers (8 weeks) │ │ Labour: £57,600 │ │ │ │ Disposal: 12,000m3 │ │ Materials: £180K │ └───────────────┘ └─────────────────────────┘ └──────────────────┘ │ ▼ Total: £369,600 Step 4: TIME-PHASE Step 5: AGGREGATE (spread across weeks) (sum all activities per period) Wk 4: £46,200 Month 1: £185,400 ─┐ Wk 5: £46,200 Month 2: £462,000 │ Wk 6: £46,200 Month 3: £389,200 │ = PV Curve Wk 7: £46,200 Month 4: £280,600 │ (S-curve) .. │ Wk 12: £46,200 Month 18: £210,000 ─┘ The PV curve IS the planned spending profile. EV is measured against it. SPI depends on it. </pre><h2 id="why-resource-loading-is-where-evm-succeeds-or-fails">Why Resource Loading Is Where EVM Succeeds or Fails</h2><p>I'll be blunt. Most EVM failures I've seen don't trace back to bad formulas or wrong definitions. They trace back to sloppy resource loading. </p><p>If your resource loading is inaccurate, if you've assigned costs evenly across durations instead of reflecting how the work actually happens, your PV curve is fiction. And every metric that depends on PV (<a href="/en/earned-value/definitions/schedule-performance-index">SPI</a>, <a href="/en/earned-value/cost-schedule-variance">SV</a>, schedule forecasts) is fiction too. </p><p>On one highways programme I worked on, the planning team had resource-loaded the entire programme by dividing each activity's budget by its duration and spreading it evenly. Earthworks at £46K per week, every week, for 8 weeks. In reality, the first 2 weeks were mobilisation and topsoil strip (low cost), weeks 3-6 were bulk dig (high cost), and weeks 7-8 were trimming and proof rolling (medium cost). The even spread meant the PV was overstated in weeks 1-2 and understated in weeks 3-6. SPI oscillated wildly. Nobody trusted the EVM reports. By month 4, the project controls team had abandoned EVM altogether. </p><p>All because of lazy resource loading. </p><h2 id="worked-example-earthworks-package-6-activities">Worked Example: Earthworks Package, 6 Activities</h2><span class="ge-worked-label">Worked Example</span><div class="ge-callout ge-anim"><p><strong>Scenario:</strong> A £3.2M earthworks package on a £22M NEC4 Option C highway scheme near Bristol. The planning engineer needs to resource-load the six main activities for the EVM baseline.</p><br><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>#</th><th>Activity</th><th>Duration</th><th>Key Resources</th><th>Budget</th></tr></thead><tbody><tr><td>1</td><td>Site clearance</td><td>2 weeks</td><td>1x excavator, 4x labourers, grab lorry</td><td>£48,000</td></tr><tr><td>2</td><td>Topsoil strip &amp; storage</td><td>3 weeks</td><td>2x excavators, 2x dumpers, 4x labourers</td><td>£86,000</td></tr><tr><td>3</td><td>Bulk excavation</td><td>6 weeks</td><td>3x excavators, 4x dumpers, 1x dozer, 8x labourers, disposal</td><td>£1,420,000</td></tr><tr><td>4</td><td>Fill importation</td><td>4 weeks</td><td>6x tippers (external), 2x excavators, 1x roller, 6x labourers</td><td>£980,000</td></tr><tr><td>5</td><td>Proof rolling &amp; testing</td><td>2 weeks</td><td>1x roller, testing rig, 2x labourers</td><td>£126,000</td></tr><tr><td>6</td><td>Topsoil reinstatement</td><td>3 weeks</td><td>1x excavator, 2x dumpers, 4x labourers</td><td>£540,000</td></tr><tr><td></td><td><strong>Total</strong></td><td></td><td></td><td><strong>£3,200,000</strong></td></tr></tbody></table></div><br><p><strong>Resource loading detail for Activity 3 (Bulk Excavation):</strong></p><br><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Resource</th><th>Rate</th><th>Quantity</th><th>Weekly Cost</th></tr></thead><tbody><tr><td>Excavator (3 units)</td><td>£1,500/week each</td><td>6 weeks</td><td>£4,500/wk</td></tr><tr><td>Dumper (4 units)</td><td>£800/week each</td><td>6 weeks</td><td>£3,200/wk</td></tr><tr><td>Dozer (1 unit)</td><td>£1,800/week</td><td>6 weeks</td><td>£1,800/wk</td></tr><tr><td>Labourers (8 people)</td><td>£600/week each</td><td>6 weeks</td><td>£4,800/wk</td></tr><tr><td>Disposal (12,000m3)</td><td>£65/m3</td><td>2,000m3/week</td><td>£130,000/wk</td></tr><tr><td>Fuel &amp; consumables</td><td>lump sum</td><td>6 weeks</td><td>£2,500/wk</td></tr></tbody></table></div><br><p><strong>But it's not a flat profile.</strong> Weeks 1-2 ramp up (60% of peak output). Weeks 3-5 are full production. Week 6 ramps down (40% of peak).</p><br><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Week</th><th>Profile Factor</th><th>Weekly Cost</th></tr></thead><tbody><tr><td>Week 1</td><td>60%</td><td>£142,080</td></tr><tr><td>Week 2</td><td>60%</td><td>£142,080</td></tr><tr><td>Week 3</td><td>100%</td><td>£236,800</td></tr><tr><td>Week 4</td><td>100%</td><td>£236,800</td></tr><tr><td>Week 5</td><td>100%</td><td>£236,800</td></tr><tr><td>Week 6</td><td>40%</td><td>£94,720</td></tr><tr><td><strong>Total</strong></td><td></td><td><strong>£1,089,280</strong></td></tr></tbody></table></div><br><p><em>(Remaining £330,720 of the £1,420,000 budget covers disposal costs, which are loaded against actual volumes removed per week.)</em></p><br><p>When you aggregate all six activities across the programme timeline, you get the earthworks PV curve, the baseline against which you'll measure <a href="/en/earned-value/definitions/earned-value">EV</a> every month.</p></div><h2 id="loading-methods">Loading Methods</h2><p>Three main approaches. Which you use depends on the data you have and the accuracy you need. </p><p><strong>1. Bottom-up (resource-based).</strong> Assign individual resources to each activity, price them, and sum up. Most accurate. Most time-consuming. Use for high-value packages and the first 6 months of any project. </p><p><strong>2. Top-down (cost-based).</strong> Start with the activity budget and spread it across the duration using a profile (linear, front-loaded, back-loaded, or bell curve). Less accurate but faster. Acceptable for preliminary estimates and low-value packages. </p><p><strong>3. Hybrid.</strong> Bottom-up for the top 20% of activities by value (which typically account for 80% of the cost). Top-down for the rest. This is what I'd recommend for most construction projects. You get the accuracy where it matters without spending weeks loading resources for minor activities. </p><h2 id="common-mistakes">Common Mistakes</h2><p><strong>Even-spread loading.</strong> Dividing the budget equally across every week of an activity's duration. Real construction doesn't work like that. Earthworks ramp up and down. Concrete pours are lumpy. M&amp;E installation accelerates once the building envelope is closed. Use profiles that reflect reality, not arithmetic convenience. </p><p><strong>Forgetting preliminaries.</strong> Site establishment, welfare, supervision, temporary works, these are real costs that consume budget over time. If they're not resource-loaded, your PV curve understates the early months and overstates the later months. Load them as a continuous resource across the full programme duration. </p><p><strong>Not updating resource loading after re-programming.</strong> When the programme changes, the resource loading must change with it. If Activity 3 moves from weeks 6-12 to weeks 8-14, the costs move too. I've seen teams update the bar chart but not the cost loading. The PV curve is then disconnected from the programme, and SPI becomes meaningless. </p><p><strong>Over-precision on minor activities.</strong> Bottom-up loading every activity down to individual bolt quantities is a waste of time. Focus precision on the big-ticket items. Broad-brush the rest. An 80/20 approach gets you 95% of the accuracy for 30% of the effort. </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 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>How long does resource loading take on a typical construction project?</h3><p>For a competent planning engineer, allow 2-3 weeks for a £20-40M project. That's for proper bottom-up loading of major packages and top-down loading of minor ones. Rushing it to "just get something into Primavera" produces a baseline that needs reworking by month 3 anyway. </p><h3>Does NEC4 require resource loading?</h3><p>NEC4 doesn't explicitly require resource-loaded programmes. But clause 31.2 requires the Contractor to show on each programme "the order and timing of the operations" and "provisions for float and time risk allowances." A resource-loaded programme is the most effective way to demonstrate compliance and to support <a href="/en/earned-value/definitions/accepted-programme">Accepted Programme</a> submissions. </p><h3>Can I resource-load in P6 / MS Project / Asta?</h3><p>All major scheduling tools support resource loading. Primavera P6 and Asta Powerproject are the most common in UK construction. Both allow you to assign resource dictionaries to activities and generate cost-loaded curves. MS Project works too but struggles with the complexity of large programmes. Whichever tool you use, the output should be exportable as a time-phased budget. That's your PV curve. </p><h3>What's the relationship between resource loading and the <a href="/en/earned-value/s-curve-tracking">S-curve</a>?</h3><p>The S-curve IS the visual output of resource loading. When you aggregate all resource-loaded costs across the programme timeline and plot them cumulatively, you get the characteristic S-shape: slow start (mobilisation), steep middle (peak production), slow finish (snagging and handover). The S-curve is your PV baseline plotted over time. </p></article></div>