Every construction cost report is only as useful as the structure underneath it. If the budget is organized one way, the contractor's billing another and the schedule a third, the owner ends up reconciling spreadsheets every month instead of managing the project. And when the board asks what the mechanical systems cost per square foot across the last five projects, nobody can answer, because each project was coded differently.
This guide explains the work breakdown structure, the cost breakdown structure and cost codes in plain terms, how UniFormat and MasterFormat differ, why owners and contractors code costs differently, and how to set up a structure that rolls up cleanly from a single trade package to a whole capital program.
Three terms that get mixed up
Work breakdown structure (WBS). A hierarchy of the work and deliverables, from the whole project down to manageable pieces. The U.S. Government Accountability Office's Cost Estimating and Assessment Guide describes a good WBS as product-oriented, with child elements that add up to their parent, at least three levels deep, and supported by a dictionary defining what each element contains.
Cost breakdown structure (CBS). The way costs are categorized and summarized. In practice it's the budget's structure: hard costs, soft costs, owner items, contingency, and the elements or trades beneath them.
Cost codes. The actual codes used in the accounting and project control systems so each invoice, commitment and change order lands in the right bucket. Cost codes are how the CBS gets enforced.
On a well-run project these line up. The WBS defines the work, the schedule activities carry WBS codes, the budget follows the same structure, and cost codes map to it. GAO's guide specifically calls for the cost WBS to be consistent with the schedule's WBS and, where earned value is used, with the earned value structure.
UniFormat and MasterFormat: two ways to slice a building
Two classification systems from the Construction Specifications Institute dominate North American construction, and they answer different questions.
UniFormat organizes a building by its physical elements and their function, regardless of how they're built. The NIST report on UNIFORMAT II, by Robert Charette and Harold Marshall, sets out six major groups: A Substructure, B Shell, C Interiors, D Services, E Equipment and Furnishings, and F Special Construction and Demolition, with building sitework as G. Beneath them are elements such as B20 Exterior Enclosure or D30 HVAC.
MasterFormat organizes by work results, the trades and products that create those elements. It's the system behind most specifications and trade contracts. The current structure, revised by CSI in 2004, uses numbered divisions such as 03 Concrete, 08 Openings, 09 Finishes, 23 HVAC and 26 Electrical.
The exterior wall is a good example of the difference. In UniFormat, it's one element, B20 Exterior Enclosure, covering cladding, windows and exterior doors together. In MasterFormat, the same wall is split by work result across divisions such as 04 Masonry, 07 Thermal and Moisture Protection and 08 Openings, depending on what it's made of and how it's packaged.
View the data
| UniFormat element | Typical MasterFormat divisions |
|---|---|
| A10 Foundations | 03 Concrete |
| B10 Superstructure | 03 Concrete, 05 Metals |
| B20 Exterior Enclosure | 04 Masonry, 07 Thermal & Moisture, 08 Openings |
| C30 Interior Finishes | 09 Finishes |
| D30 HVAC | 23 HVAC |
| D50 Electrical | 26 Electrical |
Neither system is better. They're built for different jobs. The Construction Specifier notes that UniFormat suits early design, cost organization and facility management, while MasterFormat suits project manuals and detailed cost information. Both feed the broader OmniClass classification.
In Canada, quantity surveyors have their own elemental tradition. The NIST report notes that the Canadian Institute of Quantity Surveyors published a standard classification of building elements in 1972, revised in 1990 and later adopted by the Royal Architectural Institute of Canada. Many Canadian cost consultants report elemental estimates in a format descended from that work.
Why owners and contractors code differently
The coding conflict is built into the way projects are delivered.
Contractors think in trades. They buy the job in trade packages, so their schedule of values, subcontracts and cost reports follow MasterFormat divisions or their own trade codes. That's how they manage buyout and subcontractor billing.
Owners need elements. Owners compare projects, benchmark costs per square metre, track the cost of design decisions and plan capital replacement. That's elemental thinking. The NIST report argues that early-stage estimates based on an elemental classification provide the cost information needed for economic decisions, and that elements help keep evaluations consistent over time.
Owners also need the full picture. A contractor's coding stops at the contract. The owner's budget includes design fees, permits, project management, furniture, IT, moving, financing and contingency. Those need their own codes, at the same level as the construction cost.
The answer isn't to force the contractor to bill elementally. It's to have a mapping: each trade line in the schedule of values is tagged to the owner's element and WBS code. The contractor bills the way it buys. The owner reports the way it decides.
Building an owner's cost structure
A practical owner structure usually combines three dimensions:
- Where: program, project or site, building, and sometimes phase or floor.
- What: cost category (hard cost, soft cost, owner items, contingency) and, for hard costs, the element.
- How bought: the contract or trade package, so commitments and invoices can be traced to a contract.
A cost code then strings these together. For example, a code might read program, site, category, element: P1-S03-HC-B20 for hard cost, exterior enclosure, at site 03 of program 1. The exact format matters less than applying it the same way everywhere.
View the data
| Level | Example | Code segment |
|---|---|---|
| Program | Program P1 | P1 |
| Site | Site S03 | S03 |
| Category | Hard cost | HC |
| Element | B20 Exterior Enclosure | B20 |
Keep the code list short at the top and let detail grow only where it's useful. A dozen elements is usually enough at schematic design. By construction documents, the hard cost elements may split one level further, for example B20 into walls, windows and doors, where the design team needs to track trade-offs. GAO's guide also recommends updating the WBS as the project becomes better defined and as changes occur, so plan for the structure to grow during design.
Aligning the WBS with the schedule and budget
The biggest payoff from a consistent structure is that the schedule and the budget can talk to each other. If schedule activities carry the same WBS codes as the budget, the project team can:
- Cost-load the schedule and produce a reliable cash flow forecast.
- Calculate earned value by element or by site, not just for the project as a whole. Our guide to earned value management explains why that matters.
- See which part of the project is driving a cost or schedule variance, rather than just knowing that one exists.
- Price change orders against the right budget line, so contingency drawdown is visible by element. Our guide to managing change orders covers the process.
Without that alignment, owners end up with a schedule that says the envelope is 60% complete and a cost report that can't say what the envelope has cost.
Roll-up across a program
For owners running several projects, the structure has to roll up. That means the same categories and element codes on every project, even if the trade packages differ. A store renovation, a new-build branch and a distribution centre won't share every element, but where they do, the codes should match.
On programs we've supported, the single most valuable step for multi-site owners was agreeing a standard code list before the first project started, then holding every consultant and contractor to it. It made benchmarking possible after a handful of sites, and it made program-level reports a matter of summing columns instead of reconciling spreadsheets. Our guide to building a master schedule for a multi-site program covers the schedule side of the same problem.
Common mistakes
- Adopting the contractor's codes as the owner's budget. It works for one project and fails for the next, when a different contractor uses different codes.
- Too much detail too early. Hundreds of codes at schematic design invite miscoding and make reports unreadable.
- No dictionary. If nobody has written down whether site lighting is a site cost or an electrical cost, it will be coded both ways.
- Soft costs lumped into one line. Design, permits, management and furniture need separate codes, or the total project cost can't be controlled.
What owners should do
- Set an owner cost structure before design starts, covering hard costs, soft costs, owner items and contingency, with an elemental breakdown for hard costs.
- Write a short WBS dictionary that says what belongs in each code, especially for items that could fall in two places.
- Require consultants and contractors to map to it. Estimates in the owner's elemental format; schedules of values tagged with owner codes; schedule activities carrying WBS codes.
- Use the same structure on every project in the program, so costs roll up and can be benchmarked.
- Review the mapping at each design stage and add detail only where it supports a decision.
The bottom line
A cost breakdown structure isn't glamorous, but it decides whether an owner's cost reports explain anything. Organize the budget by elements the owner cares about, let contractors bill by trade with a clear mapping, tie the schedule to the same WBS, and keep the codes consistent across every project. The reward is a cost history you can actually use.
Want help setting up a cost structure for your next project or capital program? Book a 30-minute call with Benjamin R. Consulting.
Sources: U.S. GAO, Cost Estimating and Assessment Guide: Survey of Step 4 (Work Breakdown Structure); Charette, R.P. and Marshall, H.E., UNIFORMAT II: a classification of building elements and related sitework, NIST (1999); WBDG SpecsIntact, CSI MasterFormat; The Construction Specifier, Using CSI formats effectively (2013). The coding examples are illustrative. This article is general information, not legal advice.