Resource loading in Primavera P6 means assigning the labour, equipment, materials and costs needed to deliver each activity, with a budgeted quantity and a price for each. It turns a programme of dates into a time-phased plan of hours and money, which is what you need for budget checks, cash flow, S-curves and earned value management (EVM).
Owners, lenders and project controls teams ask for a resource loaded or cost loaded schedule because it ties the programme to the budget. Without loading, the schedule says when work happens. With it, the schedule also says how much effort and money that work needs, and when.
What is resource loading and why do owners ask for it?
Resource loading is the act of creating resource assignments on activities: each assignment names a resource from the P6 resource dictionary, sets its budgeted units (or units per time), and picks up the resource's price per unit to calculate budgeted cost. Owners and project controls teams ask for it for four main reasons:
- Budget validation: the total loaded cost can be reconciled against the approved project budget.
- Cash flow forecasting: loaded costs spread over activity durations produce the planned spend curve (the S-curve).
- Progress measurement: EVM needs budgets on the activities that do the work, so value can be earned as they progress.
- Resource planning: loaded units show peaks, shortages and over-allocation, which can then be resolved by adjusting the plan or by levelling.
What is a cost-loaded schedule?
A cost-loaded schedule is a schedule in which the project budget is distributed across the activities, so every activity carries a budgeted cost and the sum of those costs equals the budget (or a defined part of it). In P6 the cost normally comes from resource assignments (units multiplied by price per unit) and from project expenses for lump-sum items.
A resource-loaded schedule carries quantities such as labour hours or equipment days. A cost-loaded schedule carries money. Most owner specifications want both: resources with prices, so the hours and the cost come from the same assignments. A schedule can be resource loaded in units only and still be useful for labour planning, but it cannot support cost reporting until prices are added.
Many contracts use the cost-loaded schedule as the basis for monthly payment applications and for the performance measurement baseline. That is why the loaded total must reconcile to the contract sum or control budget, with no cost parked on milestones, level-of-effort activities or a single "budget" activity.
What resource types does Primavera P6 use?
P6 has three resource types: Labor, Nonlabor (typically equipment) and Material. Lump-sum costs that are not driven by units, such as permits or travel, are usually entered as project expenses against the activity. Each behaves differently when loaded:
| What you are loading | Example | How it is loaded in P6 | How cost is calculated |
|---|---|---|---|
| Labour (Labor resource) | Carpenter, engineer | Units per time, for example 8 h/day, over the activity duration | Budgeted units multiplied by price per unit |
| Equipment (Nonlabor resource) | Crane, excavator | Units per time, for example 1 day/day or 8 h/day | Budgeted units multiplied by rental or hourly rate |
| Material (Material resource) | Concrete, rebar | Total quantity, for example 50 m³, with a unit of measure | Quantity multiplied by unit cost |
| Lump-sum cost (project expense) | Travel, permits, subcontract sum | A fixed amount on the activity, in the Expenses tab | The entered amount |
Labour and equipment are usually duration-driven: total units equal units per time multiplied by duration, so a longer activity uses more hours. Material is usually quantity-driven: the total quantity is fixed by the scope, whatever the duration. Expenses are independent of duration and units.
Before loading, set each resource's calendar and price per unit in the resource dictionary, and a default cost account if you use one. Then assign the resource to each activity and enter the budgeted units or units per time. P6 calculates budgeted cost from the price.
How does resource loading feed EVM and the S-curve?
Once the schedule is loaded and baselined, P6 can report earned value and draw S-curves. The chain works like this:
- Planned Value (PV): the budgeted cost of work scheduled. It is the time-phased baseline budget for work that should have been done by the data date.
- Earned Value (EV): the budgeted cost of work performed. It is each activity's budget multiplied by its performance percent complete.
- Actual Cost (AC): the cost actually incurred for the work performed, entered as actual units and costs on the assignments or brought in from the cost system.
The S-curve plots cumulative PV over time. Once work starts, cumulative EV and AC are plotted against it, and the gaps show the variances:
- Schedule Variance (SV) = EV − PV. Negative means less work has been done than planned.
- Cost Variance (CV) = EV − AC. Negative means the work done has cost more than its budget.
- SPI = EV / PV and CPI = EV / AC. Below 1.0 means behind schedule or over budget.
Without accurate loading, PV, EV and AC cannot be attributed to the activities that generate them, and the EVM figures mean very little. This is why owners and lenders often make resource and cost loading a contract requirement. For how loaded schedules are set up and reported in practice, see our project controls and EVM services.
What are the common resource-loading mistakes?
These are the errors that most often make a loaded schedule fail review, and how to avoid them.
1. Loading resources without cost accounts
Cost accounts map loaded costs to the project's cost breakdown structure, so P6 costs can be reconciled with the cost system and reported by cost code. Without them the totals may be right but cannot be reported against the budget lines. Set a default cost account on each resource in the dictionary, and check it on each assignment and expense.
2. Using the wrong duration type
P6 has four duration types. They control which of duration, units and units per time is recalculated when you change one of the others:
- Fixed Duration and Units/Time (the P6 default): changing duration recalculates total units. Suits labour and equipment working a set rate per day.
- Fixed Duration and Units: changing duration keeps total units and recalculates units per time. Suits a fixed quantity or budget that must be spread over whatever duration the activity takes.
- Fixed Units/Time: changing duration recalculates total units, and changing total units recalculates duration. Suits a fixed crew size where more work means a longer activity.
- Fixed Units: changing duration recalculates units per time, and changing units per time recalculates duration. Suits effort-driven work where total hours are fixed and adding resource shortens the activity.
The wrong type makes quantities and costs change unexpectedly when durations are edited during updates.
3. Overlooking resource calendars
Resource-dependent activities are scheduled on the resource's calendar, not the activity calendar. If a resource calendar differs from the project calendar, for example a 4-day week or a different holiday list, dates and units per day will not match what you expect. Align resource calendars with the days the resource actually works.
4. Putting cost where it cannot be earned
Cost loaded onto a single summary activity, a milestone, or a level-of-effort activity, or kept in a spreadsheet outside P6, cannot be earned as the real work progresses, so EV and the S-curve are distorted. Load cost on the activities that do the work, through resource assignments with prices or through expenses.
5. Ignoring resource curves
By default P6 spreads units evenly across the activity duration. Real effort often ramps up or tails off. Where it matters, assign a resource curve (for example front-loaded, back-loaded or bell-shaped) so the planned spend profile and the S-curve are realistic.
6. Not reviewing resource usage
After loading, review the Resource Usage Profile and Resource Usage Spreadsheet for over-allocation against each resource's maximum units. Use resource levelling with care: it delays activities within their float and priorities, and can push the finish date out. Often it is better to resolve conflicts by adjusting assignments, durations or sequence, then confirm the logic still holds.
What is the difference between resource loading and resource levelling?
Resource loading assigns resources to activities. Resource levelling then resolves over-allocation by delaying activities (within float where possible) so demand does not exceed each resource's available units. Loading comes first and is usually a requirement. Levelling is optional, and its results should be reviewed because it can move dates and consume float that the logic alone would not.
How do you check a resource-loaded schedule?
Check 10 of the DCMA 14-point assessment looks for activities with a duration of one day or more that carry no resources or cost. It has no pass mark, but on a schedule that is meant to be loaded every such activity needs a reason. Then reconcile the loaded total to the budget by cost account, confirm prices against the rate build-up, and look at the S-curve for spikes that point to cost dumped on one activity. An independent reviewer (Project Assure) does these checks as part of a schedule review; our DCMA 14-point assessment explainer covers the other thirteen checks.
Resource loading is the foundation of credible project controls, not a box to tick for the owner. Load labour, equipment, materials and expenses correctly, avoid the mistakes above, and the same schedule supports EVM, cash flow forecasting and realistic progress measurement.
