Definition The BoQ-WBS-Cost Code relationship refers to the structural integration of three foundational project control frameworks: the Bill of Quantities (BoQ), which defines contractual scope through measured quantities and unit rates; the Work Breakdown Structure (WBS), which organises project work into a hierarchy for planning and execution; and cost codes, which provide company-wide classification for cost accumulation, analysis, and benchmarking. These three structures serve distinct but complementary purposes: BoQ answers: What is the contractual scope, and how will it be measured and paid? WBS answers: How is work organised for planning, assignment, and control? Cost codes answer: How are costs classified for analysis, comparison, and enterprise learning? The relationship between them is not optional integration—it is the architectural foundation upon which project control systems and construction ERPs should be built. A change in BoQ quantities must flow to WBS work packages and cost code budgets. Progress measured against WBS activities must reconcile to BoQ valuations and cost code actuals. Variances identified in cost code reports must trace to specific BoQ items and WBS elements. When these structures operate in isolation—maintained in separate systems, managed by separate teams, reconciled manually or not at all—project control degrades into fragmented reporting that detects problems after they become irreversible. When they are integrated, the organisation gains the visibility and traceability required for proactive project management. Context in Project-Based Industries The BoQ-WBS-Cost Code triad (trilateral connectivity) is universal across project-based industries, though terminology and emphasis may vary by sector. In construction, the relationship is most explicit. Quantity surveyors prepare BoQs that define commercial scope. Planners develop WBS structures that organise execution. Cost controllers maintain cost code structures that enable analysis. The challenge—and the opportunity—lies in connecting these traditionally separate functions into an integrated control framework. In marine and offshore, the BoQ equivalent may be called a priced scope of work or work package breakdown. The WBS reflects the phased nature of offshore campaigns: engineering, procurement, fabrication, transportation, installation, hook-up, commissioning. Cost codes must accommodate both onshore fabrication and offshore installation activities. Integration is complicated by multiple execution locations, subcontractors, and interfaces. In shipbuilding, the BoQ manifests in priced specifications and contract schedules. The WBS follows vessel construction methodology: blocks, zones, systems. Cost codes track fabrication, outfitting, and trials costs. The relationship enables comparison across vessels and provides the foundation for production cost management. In mining, BoQs govern the civil, structural, mechanical, and E&I packages that comprise a mining development project. The WBS organises work by area, discipline, and system. Cost codes enable comparison across geographically dispersed sites and projects. Integration is essential for managing the multi-disciplinary complexity of mining capital projects. In project-based manufacturing, the BoQ equivalent is the priced bill of materials and labour schedule for engineered-to-order production. The WBS organises production stages from engineering through fabrication to delivery. Cost codes classify production costs for analysis and benchmarking. Integration connects customer-specific orders to company-wide performance measurement. The Common Challenge Across all these industries, organisations face a common challenge: the three structures are often developed and maintained by different functions using different systems with different objectives. Commercial teams own the BoQ, focused on contract administration, valuations, and claims Planning teams own the WBS, focused on scheduling, resource allocation, and progress tracking Finance/controls teams own cost codes, focused on cost accumulation, reporting, and forecasting Without deliberate integration, these structures drift apart. The BoQ reflects contract amendments that are not captured in the WBS. The WBS is restructured for scheduling convenience without updating cost code mappings. Cost code actuals cannot be reconciled to BoQ valuations because the linkages were never established or have not been maintained. The result is a control environment where no single version of the truth exists—where commercial position, schedule status, and cost performance cannot be reconciled into a coherent picture of project health. Why This Concept Exists The BoQ-WBS-Cost Code relationship exists because effective project control requires integration across commercial, operational, and financial dimensions. No single structure provides complete visibility; only their integration delivers comprehensive control. Scope must be controlled from multiple perspectives. The BoQ defines scope contractually—what the contractor is obligated to deliver and what the owner is obligated to pay. The WBS defines scope operationally—how work is organised for execution. These perspectives must align: every BoQ item must map to WBS elements where the work is planned and performed. When they diverge, contractual scope and operational scope become disconnected. Cost must be traceable to scope. Costs do not arise in isolation—they are generated by performing work. Cost codes classify costs for analysis, but understanding cost performance requires tracing costs back to the scope that generated them. A concrete cost variance is meaningless without knowing which BoQ items and which WBS work packages are affected. The triad provides this traceability. Progress must be measurable consistently. Progress can be measured in multiple ways: quantities installed (BoQ), work packages completed (WBS), or earned value achieved (cost codes). These measures must reconcile. If the BoQ shows 60% of concrete quantities installed, the WBS shows 55% of concrete work packages complete, and cost codes show 70% of concrete budget spent—something is wrong. Integration enables reconciliation; fragmentation hides inconsistencies. Change must propagate through all structures. When scope changes—through variation, design development, or unforeseen conditions—the change affects BoQ (new or modified items), WBS (new or modified work packages), and cost codes (budget adjustments). If change is captured in one structure but not others, the structures diverge. Integrated change management ensures that a single change event updates all three structures consistently. Enterprise learning requires project-to-enterprise linkage. Individual projects generate data; enterprise learning requires consolidation. Cost codes provide the company-wide classification that enables consolidation. But cost code data is meaningful only when it can be traced to the BoQ items and WBS elements that generated it. The triad connects project-specific execution to enterprise-wide intelligence. The BoQ-WBS-Cost Code relationship exists because project control is inherently multi-dimensional. Controlling only the commercial dimension (BoQ), only the operational dimension (WBS), or only the financial dimension (cost codes) provides incomplete visibility. Integration delivers the comprehensive control that project-based businesses require. How It Works Conceptually The BoQ-WBS-Cost Code relationship operates through defined mappings and data flows that connect the three structures into an integrated control framework. The Three Structures Each structure has a distinct architecture and purpose: Bill of Quantities (BoQ) Section 1: Substructure 1.1 Excavation 1.1.1 Bulk excavation to reduce levels - 2,500 m³ @ $12.00 = $30,000 1.1.2 Trench excavation for foundations - 800 m³ @ $18.00 = $14,400 1.2 Concrete 1.2.1 Blinding concrete - 120 m³ @ $180.00 = $21,600 1.2.2 Reinforced concrete to foundations - 450 m³ @ $320.00 = $144,000 The BoQ is contract-specific, quantity-based, and commercially focused. It defines what will be paid for and how payment is calculated. Work Breakdown Structure (WBS) 1.0 Project 1.1 Foundations 1.1.1 Foundation Zone A 1.1.1.1 Excavation - Zone A 1.1.1.2 Formwork - Zone A 1.1.1.3 Reinforcement - Zone A 1.1.1.4 Concrete - Zone A 1.1.2 Foundation Zone B 1.1.2.1 Excavation - Zone B 1.1.2.2 Formwork - Zone B 1.1.2.3 Reinforcement - Zone B 1.1.2.4 Concrete - Zone B The WBS is project-specific, execution-focused, and organised for planning and control. It defines how work is assigned and managed. Cost Codes 03 CONCRETE 03.10 Formwork 03.10.10 Foundation Formwork 03.10.20 Wall Formwork 03.10.30 Slab Formwork 03.20 Reinforcement 03.20.10 Foundation Reinforcement 03.20.20 Wall Reinforcement 03.30 Concrete Placement 03.30.10 Foundation Concrete 03.30.20 Structural Concrete Cost codes are company-wide, analysis-focused, and organised for cost accumulation and benchmarking. They define how costs are classified across all projects. The Mapping Relationships Integration requires explicit mappings between structures: BoQ to WBS Mapping Each BoQ item maps to one or more WBS work packages where the work is performed: BoQ Item WBS Work Package(s) 1.2.2 RC to foundations – 450 m³ 1.1.1.4 Concrete – Zone A (250 m³) 1.1.2.4 Concrete – Zone B (200 m³) This mapping enables: Allocation of BoQ quantities to WBS elements for planning Roll-up of WBS progress to BoQ for valuation Tracing of BoQ variances to specific work locations BoQ to Cost Code Mapping Each BoQ item maps to one or more cost codes for cost classification: BoQ Item Cost Code(s) 1.2.2 RC to foundations – 450 m³ 03.30.10 Foundation Concrete (concrete) 03.20.10 Foundation Reinforcement (rebar) 03.10.10 Foundation Formwork (formwork) This mapping enables: Classification of BoQ item costs into company-wide categories Benchmarking of BoQ items against historical cost code performance Consolidation of project data into enterprise cost intelligence WBS to Cost Code Mapping Each WBS work package maps to cost codes for cost accumulation: WBS Work Package Cost Code(s) 1.1.1.4 Concrete – Zone A 03.30.10 Foundation Concrete 03.20.10 Foundation Reinforcement 03.10.10 Foundation Formwork This mapping enables: Accumulation of actual costs by work package and cost code Earned value calculation linking WBS progress to cost code budgets Variance analysis at the work package level with cost code detail Data Flows With mappings established, data flows through the integrated structure: Budget Flow BoQ values are loaded as the commercial baseline BoQ values are allocated to WBS work packages based on BoQ-WBS mapping Work package budgets are classified by cost code based on WBS-Cost Code mapping Cost code budgets aggregate for enterprise-level analysis Actual Cost Flow Transactions are coded to cost codes at point of entry (timesheets, invoices, commitments) Cost code actuals are linked to WBS work packages Work package actuals roll up for schedule-based reporting Work package actuals reconcile to BoQ items for commercial reporting Progress Flow Quantities installed are measured against BoQ items BoQ progress translates to WBS work package completion percentages Work package completion drives earned value calculation Earned value is analysed by cost code for performance measurement Variance Analysis Flow Cost code variance is identified (actual vs. budget) Variance is traced to affected WBS work packages Work packages are linked to BoQ items Root cause is diagnosed: quantity variance, rate variance, or productivity variance Change Management Flow Scope change is identified and documented BoQ is updated (new items, modified quantities, revised rates) WBS is updated (new work packages, modified scope) Cost code budgets are adjusted Baseline is versioned; variance reporting reflects change impact Why Generic Approaches Fail Generic enterprise systems and fragmented toolsets consistently fail to deliver integrated BoQ-WBS-Cost Code control because they do not understand or support the relationships between these structures. Separate systems for separate structures. Many organisations use different systems for each structure: estimating software for BoQ, scheduling software for WBS, accounting software for cost codes. These systems were not designed to integrate, and the effort required to maintain manual linkages exceeds organisational capacity. The structures diverge. No native BoQ capability. Generic ERP systems—designed for manufacturing or service businesses—have no concept of a Bill of Quantities. They may have bills of materials (BOMs) for production, but BOMs assume repeatable products with stable component lists. BoQs are project-specific, quantity-driven, and subject to remeasurement and variation. Without native BoQ support, commercial scope control operates outside the enterprise system. WBS as scheduling taxonomy only. Many scheduling tools treat the WBS as an activity classification scheme rather than a scope decomposition structure. The WBS becomes whatever structure makes scheduling convenient, disconnected from commercial scope (BoQ) and cost classification (cost codes). When the schedule is restructured, the link to commercial and financial data breaks. Cost codes as chart of accounts. Generic accounting systems use cost codes—or their equivalent—as extensions of the general ledger chart of accounts. This creates a financial classification, but not a project control classification. The cost codes serve period-based financial reporting rather than project-based cost control. Integration with BoQ and WBS is not supported. No mapping infrastructure. Even when organisations recognise the need for BoQ-WBS-Cost Code integration, generic systems provide no infrastructure for establishing and maintaining mappings. Relationships must be documented externally and reconciled manually—a process that breaks down under the volume and pace of project transactions. Change management breaks integration. Integrated structures are most valuable—and most vulnerable—when scope changes. A variation that adds BoQ items, creates new WBS work packages, and adjusts cost code budgets tests whether integration is real or theoretical. Generic systems that cannot propagate change through all three structures will diverge at the first significant variation. No earned value integration. Earned value management requires linking cost budgets (from cost codes), work completion (from WBS), and scope quantities (from BoQ). Generic systems that do not integrate these structures cannot calculate earned value correctly—or at all. The BoQ-WBS-Cost Code relationship requires systems purpose-built for project-based enterprises—systems where the triad is not an afterthought but the architectural foundation. Where It Applies General Contracting. Integration of BoQ-based commercial management with WBS-based planning and cost code-based analysis—enabling reconciliation of valuations, schedule progress, and cost performance. EPC Projects. Integration across engineering deliverables, procurement packages, and construction work packages—with cost codes enabling analysis of performance by discipline and project phase. Marine and Offshore. Integration of priced work packages (BoQ equivalent) with campaign-based WBS and cost codes that span onshore and offshore activities—enabling control across complex execution sequences. Shipbuilding. Integration of contract specifications (BoQ equivalent) with block-based WBS and production cost codes—enabling vessel cost control and cross-vessel benchmarking. Mining Development. Integration of package-based BoQs with area/discipline WBS structures and mining-specific cost codes—enabling control across multi-year, multi-discipline capital projects. Infrastructure Programmes. Integration of contract BoQs with programme-level WBS and standardised cost codes—enabling portfolio-level visibility while maintaining project-level control. The Triad in Practice: An Integrated Example Consider a concrete foundation scope item and how it flows through the integrated triad: BoQ Definition Item 1.2.2: Reinforced concrete Grade C40 to pile caps Quantity: 450 m³ Unit Rate: $320/m³ Total Value: $144,000 WBS Allocation Work Package 1.1.1.4: Concrete - Zone A - Allocated quantity: 250 m³ - Allocated budget: $80,000 Work Package 1.1.2.4: Concrete - Zone B - Allocated quantity: 200 m³ - Allocated budget: $64,000 Cost Code Classification Cost Code 03.30.10: Foundation Concrete - Budget from WP 1.1.1.4: $50,000 (concrete material and placement) - Budget from WP 1.1.2.4: $40,000 Cost Code 03.20.10: Foundation Reinforcement - Budget from WP 1.1.1.4: $20,000 (rebar material and fixing) - Budget from WP 1.1.2.4: $16,000 Cost Code 03.10.10: Foundation Formwork - Budget from WP 1.1.1.4: $10,000 (formwork material and labour) - Budget from WP 1.1.2.4: $8,000 Progress Measurement (at month end) BoQ Progress: - Item 1.2.2: 280 m³ installed (62% complete) - Value: $89,600 WBS Progress: - WP 1.1.1.4: 250 m³ complete (100%) - WP 1.1.2.4: 30 m³ complete (15%) Cost Code Actuals: - 03.30.10: $58,000 spent - 03.20.10: $24,000 spent - 03.10.10: $12,000 spent - Total: $94,000 Integrated Analysis Earned Value (based on BoQ progress): - BCWP = 62% × $144,000 = $89,280 Cost Performance: - ACWP = $94,000 - Cost Variance = $89,280 - $94,000 = -$4,720 (over budget) - CPI = 0.95 Diagnostic (by cost code): - 03.30.10 Concrete: On budget - 03.20.10 Reinforcement: 20% over budget (rate increase) - 03.10.10 Formwork: 15% over budget (productivity issue in Zone B) Commercial Position: - Certified value: $89,600 (BoQ valuation) - Cost incurred: $94,000 - Margin at risk: $4,400 This integrated analysis is possible only because the BoQ, WBS, and cost codes are connected. The BoQ provides commercial scope and valuation. The WBS provides operational status by location. Cost codes provide diagnostic detail by cost type. Together, they reveal not just that the project is over budget, but why—and where corrective action is needed. Common Misconceptions Misconception: The BoQ, WBS, and cost codes are three ways of describing the same thing. Reality: Each structure serves a distinct purpose. The BoQ is commercial (what we are contracted to deliver and paid for). The WBS is operational (how we organise work for execution). Cost codes are analytical (how we classify costs for understanding and benchmarking). They describe the project from different perspectives that must be integrated, not substituted for one another. Misconception: Integration means using the same structure for all three purposes. Reality: Using a single structure—making the BoQ serve as both WBS and cost code—sacrifices the benefits of each. The BoQ is organised for commercial management; forcing it to serve planning purposes compromises execution organisation. The WBS is organised for operations; forcing it to serve cost analysis purposes compromises benchmarking. Integration connects distinct structures; it does not collapse them into one. Misconception: Mapping can be done once at project setup and then left alone. Reality: Mappings must be maintained throughout project execution. Scope changes introduce new BoQ items that require WBS and cost code mapping. WBS restructuring (for planning optimisation) requires remapping to BoQ and cost codes. Cost code structure refinement requires updating project mappings. Integration is ongoing work, not initial configuration. Misconception: Integration is a technology problem. Reality: Integration is fundamentally an organisational and process problem that technology enables. If commercial, planning, and cost control functions operate in silos with different objectives and incentives, no technology will achieve integration. Effective integration requires organisational alignment on the importance of the triad, defined processes for establishing and maintaining mappings, and accountability for data integrity. Misconception: Small projects do not need this level of integration. Reality: The overhead of integration should be proportionate to project size and complexity. Small projects may use simplified structures with more direct mappings. But the principle remains: commercial scope, operational planning, and cost classification must connect. A small project with disconnected structures will experience the same control failures as a large project—just at smaller scale. Misconception: This is only relevant for re-measurement contracts. Reality: While the BoQ is most explicit in re-measurement contracts, the principle applies to all contract types. Lump-sum contracts still have scope that must be organised for execution (WBS) and cost that must be classified for analysis (cost codes). Design-build and EPC contracts still require integration of commercial, operational, and financial control. The structures may be called different names, but the triad remains. Related Topics What Is a Project-Based Business? — The economic model that requires integrated BoQ-WBS-Cost Code control. What Is a Capital Project? — The discrete engagement for which the triad provides control. What Is a Project-Based Operating Model? — The operational framework within which the triad operates. What Is a Bill of Quantities (BoQ)? — The commercial scope definition component of the triad. What Is a Work Breakdown Structure (WBS)? — The operational planning component of the triad. What Are Cost Codes in Construction? — The cost classification component of the triad. What Is Project Cost Control? — The discipline that depends on integrated BoQ-WBS-Cost Code data. What Is Earned Value Management? — The performance measurement methodology built on the triad. RELATED ASSETS Related Industries Construction Project-based Manufacturing Marine and Offshore Construction Mining and Quarrying Shipbuilding and Repairs RELATED ASSETS Related Stakeholders Owner/Developer E&P Owners Mine & Quarry Owner Consultants General Contractors Marine Contractor Shipbuilders Mining Contractor RELATED ASSETS Related Roles C-level Executives Project Manager Bidding Manager Cost Estimator Cost Controller Go to Previous Topic Previous Topic Return to What is? Go to Hub Go to Next Topic Next Topic