1.9 Cost Breakdown Structure and Cost Estimate Development

1.9 Cost Breakdown Structure and Cost Estimate Development

A Cost Breakdown Structure (CBS) organizes money for estimating, budgeting, commitments, actual-cost collection, and forecasting. A Work Breakdown Structure (WBS) organizes deliverable scope. They should relate through a code of accounts, but they need not have identical hierarchies.

CBS purposes

A CBS may classify:

• direct labor, material, equipment, and subcontracts;
• indirect field costs;
• engineering, procurement, construction, and commissioning;
• organizational responsibility;
• asset, system, area, or contract package; and
• contingency, escalation, taxes, and owner costs under defined policy.

The design must support decisions. An accounting chart that collects payroll by department may be insufficient for project control unless costs can also map to project work.

Develop the estimate

Estimate development is an iterative process:

1. confirm scope and maturity;
2. select estimate methods appropriate to the available definition;
3. quantify work and identify resources;
4. apply production rates and unit costs;
5. estimate indirects and time-dependent costs;
6. address escalation, currency, location, and market conditions;
7. quantify risk and contingency under policy;
8. reconcile exclusions, allowances, and owner costs; and
9. document the basis of estimate.

Detailed quantities may support unit-rate estimates, while early concepts may require analogous or parametric methods. Precision should not imply maturity that the scope does not possess.

Basis of estimate

The basis records:

• scope documents and estimate date;
• methods and data sources;
• quantities, rates, productivity, and crews;
• pricing basis and escalation;
• calendars and schedule assumptions;
• inclusions, exclusions, allowances, and contingency;
• risks and opportunities; and
• reconciliation to previous estimates.

This allows the schedule team to use the same production and resource assumptions instead of inventing separate duration logic.

Integrate cost and schedule

The WBS/OBS intersection can create control accounts where scope, budget, schedule, and responsibility meet. Work packages below them can map to activities and cost accounts at a practical level.

Avoid two extremes:

• Too coarse: one cost line for the entire project cannot explain variance.
• Too granular: every invoice or general-ledger line becomes a schedule activity, making the network unmanageable.

Choose a control level where performance can be measured and managed.

Time-phasing

Once activities have credible logic, durations, and calendars, costs or resources can be distributed over time. The result supports cash flow, funding, procurement, and earned-value planning. Time-phasing a defective schedule produces a precise-looking but unreliable forecast.

Cost loading should follow the earning rule. A major equipment purchase may earn value at defined design, fabrication, delivery, and acceptance milestones rather than entirely at invoice payment. Actual cost and earned value answer different questions and must be reconciled without being equated.

Change and forecast

When scope or execution changes, update the estimate and schedule consistently. A changed crew assumption affects duration and labor cost; a later finish can extend time-dependent indirect costs; an accelerated sequence can create premium-time cost or congestion. The integrated forecast should explain both effects.

Example

A piping package contains 10,000 linear feet. The estimate assumes a crew output of 100 feet per day and a defined crew cost. The schedule duration, resource load, and labor budget should reconcile to that basis. If field output falls to 75 feet per day, the update should forecast remaining duration and cost from the new evidence rather than retaining incompatible assumptions.

The CBS is useful when it connects financial data to controllable scope and time without distorting either model.

Applied review: reconcile cost and schedule structures

The cost breakdown structure organizes authorized cost for estimating, budgeting, commitment, accumulation, and control. It may align closely with the work breakdown structure, but the two need not be identical: the WBS is deliverable-oriented, while cost accounts may reflect accounting, contract, or organizational needs. A coding crosswalk lets users summarize schedule work to the appropriate control account without forcing one structure to perform every purpose.

Estimate development supplies more than a total budget. The scheduler needs quantities, production rates, crew assumptions, procurement quotations, indirect support, escalation basis, calendars, and estimate exclusions. A duration derived from quantity divided by daily production is only as credible as the quantity, production basis, crew availability, and work-face conditions. Procurement estimates should distinguish fabrication, transport, inspection, and delivery rather than burying lead time in one date.

Reconcile estimate and schedule scope before baselining. Confirm that every significant estimate package has planned work and that scheduled scope has an authorized cost basis or an identified exception. Time-phased cost loading should follow the expected timing of work or expenditure, not an arbitrary straight-line spread selected to make a curve look smooth. In an exam problem, a mismatch is a prompt to investigate scope, coding, timing, and assumptions—not automatically proof that either the estimate or schedule is wrong.