Cost aggregation

Cost aggregation is the technique of summing estimated costs of activities or work packages to higher WBS levels and control accounts to build the project budget. It time-phases the totals to create the cost baseline and determine funding needs.

Definition

Refer to the definition above.

Key Points

  • Bottom-up technique that rolls up costs from activities and work packages to WBS levels and control accounts.
  • Results are time-phased to form the cost baseline and an S-curve for performance tracking.
  • Includes direct, indirect, and procurement costs and contingency reserves; management reserve is not part of the baseline.
  • Relies on an approved WBS, schedule, resource rates, and risk responses that affect costs.
  • Supports funding limit reconciliation and cash flow planning with sponsors and finance.
  • Iterative: update as scope, schedule, or rates change, keeping traceability to estimates of record.

Purpose of Analysis

  • Translate detailed cost estimates into a consolidated, time-phased project budget.
  • Enable baseline establishment for Earned Value Management and cost control.
  • Determine periodic funding needs and align them with organizational constraints.
  • Provide visibility of costs by control account, phase, or deliverable for accountability.

Method Steps

  • Organize cost estimates by WBS element and assign each to a control account or cost center.
  • Sum costs within each WBS level and roll them up to the overall project total.
  • Allocate sums across the schedule to create a time-phased budget (monthly or weekly buckets).
  • Incorporate approved contingency reserves tied to identified risks.
  • Apply agreed indirect rates and include contracted costs per payment schedules.
  • Validate totals and timing with finance and reconcile to any funding limits.
  • Document assumptions and create the cost baseline and cash flow (S-curve).

Inputs Needed

  • Work Breakdown Structure (WBS) and WBS dictionary.
  • Activity and work package cost estimates with bases of estimate.
  • Project schedule and resource loading.
  • Resource and labor rate tables; vendor quotations and contracts.
  • Risk register and agreed contingency strategies.
  • Indirect cost rates and organizational accounting policies.
  • Cost management plan and funding constraints from the business case or sponsor.

Outputs Produced

  • Time-phased cost baseline by WBS and control account.
  • Control account budgets and summarized project budget.
  • Funding requirements and cash flow profile (e.g., S-curve).
  • Updated cost estimates and bases of estimate with aggregation assumptions.
  • Cost aggregation worksheets or reports for governance reviews.

Interpretation Tips

  • Ensure the baseline excludes management reserve but includes approved contingency.
  • Check that time-phasing aligns with scheduled work; avoid front-loading or back-loading without cause.
  • Differentiate from bottom-up estimating: estimating creates package-level numbers; aggregation rolls them up and time-phases them.
  • Use control accounts to assign ownership and enable performance measurement.
  • If funding limits are breached in any period, coordinate funding limit reconciliation and adjust timing or scope as needed.

Example

A control account has three work packages estimated at 40k, 60k, and 50k. The schedule spreads them over three months. The project manager aggregates the costs by month (e.g., 30k, 70k, 50k), applies indirect rates, adds 10% contingency based on risk analysis, and produces a time-phased baseline for that control account. These roll up to the project-level baseline and S-curve.

Pitfalls

  • Including management reserve in the baseline and overstating planned value.
  • Ignoring timing, resulting in an un-phased lump-sum budget that is not useful for control.
  • Double-counting indirect costs or contingency across multiple WBS elements.
  • Using outdated labor rates or vendor quotes, leading to inaccurate totals.
  • Failing to capture procurement payment schedules, causing cash flow mismatches.
  • Poor traceability to work packages, making variance analysis difficult.

PMP Example Question

While finalizing the budget, a project manager groups work package estimates under control accounts and spreads the totals across months to create the cost baseline. Which technique is being used?

  1. Cost aggregation
  2. Parametric estimating
  3. Reserve analysis
  4. Funding limit reconciliation

Correct Answer: A — Cost aggregation.

Explanation: Cost aggregation rolls up estimates to higher WBS levels and time-phases them into a cost baseline. Funding limit reconciliation adjusts the timing to fit limits but is not the aggregation itself.

AI for Project Managers — Build Plans Faster, Lead Better

Turn messy inputs into structured project plans in minutes. If you are a project manager tired of spending hours on documentation, this course shows you how to use AI to work faster while staying fully in control.

This is not a generic AI course. You will learn how to use AI as a practical co-pilot to build real project artifacts—charters, WBS, schedules, risk registers, and executive reports—using structured, reliable prompt frameworks.

You will also learn how to keep your project aligned across scope, schedule, cost, and risk, and how to interpret performance data like Earned Value Management to support better decisions and communication.

Everything is designed for immediate use. You get ready-to-use prompt templates and workflows you can apply right away in your projects. Watch the video to see how it works and start building your first AI-supported project plan.

Explore the Course


Stop Managing Admin. Start Leading the Future!

HK School of Management helps you learn AI prompt engineering for project work. Move beyond status reports and risk logs with practical prompt frameworks for everyday tasks. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Enroll Now