21.1 Cost and Resource Loading Summaries from the Project Schedule
Key Takeaways
- Support/Inform the Scheduling Process is only 5% of the CCP exam (6 of 119 questions), covering cost and resource loading, review of loaded schedules, and periodic cost-resource updates — the CCP is not the PSP.
- Resource loading assigns quantities and derives cost from rates, which allows rate, productivity, and quantity variances to be separated directly from the schedule; direct cost loading does not.
- Loaded value must reconcile exactly to the control account budget; any residual represents activities added without budget, scope without an activity, or double-loaded level-of-effort work.
- Linear loading is an assumption that fails on mobilization-heavy or commissioning-heavy activities, manufacturing a first-period schedule variance that no one can perform away.
- The monthly update re-estimates remaining resources rather than halving them, re-phases the forecast profile onto new dates, and never re-phases the baseline — moving PV to match progress forces schedule variance toward zero.
21.1 Cost and Resource Loading Summaries from the Project Schedule
Domain 5 of the CCP blueprint — Support/Inform the Scheduling Process — is 5% of the exam, 6 questions. It is small, and its size is itself examinable information: the CCP is not the PSP. What Domain 5 asks is narrow and specific. This section covers 5.A support the development of cost/resource loading summaries based on project schedules, 5.B review baseline/detailed project schedules with respect to cost resources/loading, and 5.D support the scheduling process (e.g., forecast, update cost resources).
1. What Cost Loading Is
Cost loading assigns budget to schedule activities so that the schedule can generate a time-phased cost profile. Resource loading assigns labour, equipment, and material quantities to activities, from which cost is then derived through rates.
| Approach | How it works | Best for |
|---|---|---|
| Direct cost loading | A dollar value is assigned to each activity | Simple contracts; payment-application schedules |
| Resource loading | Quantities of labour, equipment, and material are assigned; cost derives from rates | Labour-intensive work where productivity is the driver |
| Hybrid | Resource-load the direct labour; cost-load the subcontract and material | Most large capital projects |
Resource loading is more work but far more useful, because it lets you separate a rate change from a productivity change from a quantity change — the decomposition of Section 18.3 — directly from the schedule.
2. Prerequisites for a Usable Loaded Schedule
| Prerequisite | Why |
|---|---|
| Common WBS between estimate and schedule | Without it, budget cannot be mapped to activities |
| Activity granularity matched to control need | Activities spanning several control accounts cannot be loaded cleanly |
| Complete network logic | Open ends and dangling activities produce a distorted time phasing |
| Realistic calendars | Loading against an unrealistic calendar time-phases cost into periods when no work will occur |
| Agreed progress rule per activity | Loading defines what money is at stake; the rule defines when it is earned |
| Reconciliation to the total budget | Loaded value must sum to the control account budget, with no orphan or double-counted money |
[!IMPORTANT] Loaded value must reconcile to the budget exactly. Reconciliation failures are common and corrosive: activities added during scheduling but not in the estimate, scope in the estimate with no activity to carry it, and level-of-effort activities loaded twice. Any residual after reconciliation is an error, not a rounding difference.
3. Producing the Cost Loading Summary
The output of cost loading is the time-phased budget — the planned value curve that becomes the performance measurement baseline.
Worked example. A control account has a budget of $4,800,000 across four activities:
| Activity | Budget | Duration | Start | Loading pattern |
|---|---|---|---|---|
| Foundations | $1,200,000 | 3 months | M1 | Linear |
| Structural steel | $2,000,000 | 4 months | M3 | Linear |
| Mechanical install | $1,200,000 | 3 months | M5 | Linear |
| Commissioning | $400,000 | 2 months | M7 | Linear |
Time-phased planned value by month:
| Month | Foundations | Steel | Mechanical | Commissioning | Period PV | Cumulative PV |
|---|---|---|---|---|---|---|
| 1 | $400,000 | — | — | — | $400,000 | $400,000 |
| 2 | $400,000 | — | — | — | $400,000 | $800,000 |
| 3 | $400,000 | $500,000 | — | — | $900,000 | $1,700,000 |
| 4 | — | $500,000 | — | — | $500,000 | $2,200,000 |
| 5 | — | $500,000 | $400,000 | — | $900,000 | $3,100,000 |
| 6 | — | $500,000 | $400,000 | — | $900,000 | $4,000,000 |
| 7 | — | — | $400,000 | $200,000 | $600,000 | $4,600,000 |
| 8 | — | — | — | $200,000 | $200,000 | $4,800,000 |
The cumulative column is the S-curve. Note that it is genuinely S-shaped here — slow in month 1–2, steep in months 3–6, flat at the end — purely from activity overlap, without any smoothing assumption. That shape is a schedule property, not a drawing convention.
[!TIP] Linear loading is an assumption, and it is often wrong. Activities with mobilization-heavy or commissioning-heavy cost profiles should be loaded to match reality. Loading a six-month erection activity linearly when half its cost is crane mobilization in month one produces a planned value curve that no one can perform to, and manufactures a schedule variance in the first period.
4. Reviewing a Schedule for Cost Loading (Task 5.B)
Reviewing a contractor's cost-loaded schedule is a distinct commercial exercise, because the loaded schedule is often also the payment mechanism.
| Review test | What it detects |
|---|---|
| Total reconciliation | Loaded value versus contract value |
| Front-end loading | Early activities carrying disproportionate value (Section 19.3) |
| Value against duration | Very high value on very short early activities |
| Level-of-effort proportion | Excessive value in activities with no measurable output |
| Milestone value | Large payments at milestones with weak completion definitions |
| Retention interaction | Whether the profile leaves adequate value to secure completion |
| Resource realism | Whether the implied manning curve is achievable locally |
5. Updating Cost Resources and Forecasting (Task 5.D)
Each period the loaded schedule must be refreshed, and the refresh has a required sequence:
- Status the activities — actual start, actual finish, remaining duration.
- Update remaining resource requirements, not just remaining duration. An activity 50% complete that has consumed 70% of its hours needs its remaining hours re-estimated, not simply halved.
- Recalculate the network and identify the current critical path.
- Re-phase the remaining budget onto the updated dates, producing a revised forecast profile.
- Reconcile against the cost forecast produced independently in the cost system. Where the two diverge, find out why — divergence is information, not an inconvenience.
- Update the funding requirement for the changed cash timing (Section 17.3).
[!WARNING] Do not re-phase the baseline. Updating the forecast profile onto new dates is routine. Moving the baseline planned value onto new dates destroys schedule variance, because SV is defined as EV minus PV and re-phasing PV to match progress forces SV toward zero. The baseline moves only through approved change.
A six-month structural erection activity carries $3,000,000 of budget, of which $1,400,000 is crane mobilization and heavy lift setup incurred in the first month. The scheduler loads the activity linearly at $500,000 per month. What is the consequence?
At the monthly update an activity is 50% complete by physical measure but has consumed 70% of its budgeted labour hours. The planner halves the original hours to set the remaining requirement. What is wrong with this?
A project is running behind, and the planning lead proposes re-phasing the baseline planned value curve onto the current forecast dates so that reporting 'reflects reality.' What is the objection?