Definition A project-based operating model is the operational framework through which a project-based organization delivers capital projects. It defines how work is priced, planned, resourced, executed, controlled, and closed out—integrating commercial, technical, and operational functions into a coherent system aligned with the economics of project delivery. Unlike operating models designed for continuous production or service delivery, a project-based operating model must accommodate the unique characteristics of capital projects: discrete engagements with defined start and end points, scope defined by contract and subject to change, revenue earned through milestone achievement rather than volume, and margins determined by the gap between bid assumptions and execution reality. The operating model encompasses the processes, systems, data flows, decision rights, and performance measures that govern how projects move from opportunity identification through final account settlement. It is the connective tissue between strategy and execution—translating organizational capability into delivered projects. A project-based operating model is not a set of procedures documented in a quality manual. It is the lived reality of how an organization actually operates: how bids are assembled, how budgets are established, how progress is measured, how deviations are detected, how changes are managed, and how lessons are captured for future engagements. Context in Project-Based Industries The operating model is where organizational structure meets operational reality. A project-based organization may have the right structure—project authority, functional expertise, corporate governance—but without an effective operating model, that structure cannot translate into consistent project delivery. In construction, the operating model connects estimating departments to project teams to commercial functions. A bid prepared by estimators must translate into a project budget that site teams can execute against. Progress measured on site must flow into cost reports that inform commercial decisions. Variations identified in the field must connect to contractual claims that protect margin. When these connections break, projects drift into uncontrolled deviation. In marine and offshore, operating models must span onshore engineering, fabrication yards, and offshore installation campaigns. Design information flows from engineering to procurement to fabrication. Weight control, dimensional accuracy, and interface management require integrated data across organizational boundaries. The operating model defines how these handoffs occur and how deviations are caught before they compound. In shipbuilding, the operating model governs the flow from contract signature through steel cutting, block assembly, outfitting, and sea trials. Production planning, material procurement, and workforce allocation must align with the vessel delivery schedule. The operating model defines how the shipyard balances multiple vessels in various stages of construction while maintaining control over each individual project. In mining, operating models for capital project delivery must integrate feasibility studies, detailed engineering, procurement of long-lead equipment, civil works, mechanical installation, and commissioning. The transition from project delivery to steady-state operations requires careful handover processes embedded in the operating model. In project-based manufacturing, operating models connect customer specifications to engineering, production planning, fabrication, quality control, and delivery. Each order is a project with its own requirements, and the operating model must flex to accommodate variation while maintaining efficiency. Across all these industries, the operating model answers a fundamental question: how does work flow through the organization from opportunity to completion, and how is that flow controlled? Why This Concept Exists The project-based operating model exists because capital project delivery requires integration that functional processes and generic enterprise systems cannot provide. Estimation must connect to execution. A bid is a commercial commitment built on assumptions about quantities, productivity, resource costs, and risk. If those assumptions do not flow into project budgets, schedules, and resource plans, the project team inherits a target they cannot trace to its origins. When variances emerge, there is no baseline against which to measure deviation. The operating model must ensure that estimation outputs become execution inputs—with full traceability. Scope must anchor control. In capital projects, scope is defined through measurable quantities: the Bill of Quantities (BoQ) specifies what is to be delivered; the Work Breakdown Structure (WBS) organizes how it will be delivered; cost codes classify how costs are accumulated and reported. The operating model must integrate these structures so that a change in scope propagates to budget, schedule, and procurement simultaneously. Without this integration, control fragments across disconnected systems. Time, cost, and commercial position must align. A project may be on schedule but over budget. It may be under budget but exposed to unresolved variations. It may appear profitable until retention is trapped by disputed claims. The operating model must provide visibility across all dimensions—not siloed reports that obscure the true project position. Change must be captured and valued. Change is structural in capital projects, not exceptional. Design evolution, unforeseen conditions, owner instructions, and regulatory shifts generate variations that alter scope, cost, and time. The operating model must define how changes are identified, documented, quantified, and submitted for contractual resolution. Organizations without disciplined change management leave money on the table—or absorb costs they are entitled to recover. Learning must transfer across projects. Every completed project generates knowledge: actual productivity versus planned, supplier performance, risk events that materialised, estimates that proved accurate or optimistic. The operating model must capture this knowledge and feed it back into estimating, planning, and risk management for future engagements. Organizations that do not learn from their projects repeat the same mistakes and cannot improve their competitive position. The project-based operating model exists to create these connections—transforming fragmented activities into an integrated system capable of consistent, controlled project delivery. How It Works Conceptually A project-based operating model operates across the full project lifecycle, with processes and data flows connecting each phase to the next. Opportunity and Bid Management The operating model begins before the project exists—at the point where opportunities are identified, qualified, and pursued. Bid/no-bid decisions filter opportunities based on strategic fit, capability match, risk appetite, and resource availability. For opportunities pursued, the estimating process assembles the bid: Quantities are taken off from drawings and specifications Unit rates are developed from historical data, supplier quotations, and productivity assumptions Risk is assessed and priced through contingencies or contractual qualifications The bid is compiled, reviewed, and submitted The operating model defines who participates in bid development, what data sources are used, how assumptions are documented, and how the bid is approved. A disciplined bid process creates the foundation for project control; a chaotic one sets projects up for failure before they begin. Contract Award and Baseline Establishment Upon contract award, the bid transforms into a project baseline. This is a critical transition point where many organizations lose control. The operating model must define how: The bid estimate is converted into a project budget, with appropriate adjustments for contract negotiations The BoQ is loaded as the scope baseline, with quantities linked to budget and schedule The WBS is established, organizing scope into manageable work packages Cost codes are assigned, enabling cost accumulation against budget categories The schedule is developed, with activities linked to WBS elements and resource-loaded Procurement plans are established, identifying what must be bought, from whom, and when Risk registers are populated, with identified risks assigned owners and mitigation plans The baseline is the reference point against which all subsequent performance is measured. Without a properly established baseline, project control has no foundation. Execution and Control During execution, the operating model governs the continuous cycle of planning, doing, measuring, and adjusting. Planning establishes near-term targets: what work will be performed, what resources are required, what materials must be available, what milestones must be achieved. Execution mobilises resources and performs physical work. Site teams, fabrication crews, subcontractors, and suppliers convert plans into installed scope. Measurement captures actual performance: Quantities installed are measured against quantities planned Costs committed and incurred are recorded against budget Schedule progress is tracked against baseline milestones Quality is verified against specifications and standards Safety performance is monitored against targets Analysis compares actual to planned, identifies variances, diagnoses root causes, and forecasts outcomes. The critical questions are: Where are we versus where we planned to be? Why is there a variance? What will the project cost at completion? What must we do to recover or improve? Adjustment takes corrective action: re-sequencing work, reallocating resources, accelerating procurement, negotiating with subcontractors, or escalating issues that require management intervention. This cycle repeats continuously throughout execution—weekly, daily, or even hourly for critical activities. The operating model defines the cadence, the participants, the data requirements, and the decision authority at each stage. Change Management Change management is not a separate process but an integral part of the operating model. When scope changes—whether through owner instruction, design development, unforeseen conditions, or regulatory requirement—the operating model defines how: The change is identified and documented Impact on cost, time, and resources is assessed The change is submitted for approval or contractual claim The baseline is updated (or a variance is recorded against the original baseline) Downstream effects on procurement, schedule, and resource plans are propagated Effective change management protects margin by ensuring that legitimate additional costs are recovered through contractual mechanisms. Ineffective change management absorbs costs that should be compensated, eroding profitability invisibly. Commercial Management The operating model integrates commercial processes with project execution: Interim valuations measure progress and generate payment applications Cash flow management ensures that receipts from owners align with payments to suppliers and subcontractors Variation management tracks potential claims and manages them through to resolution Subcontractor management controls back-to-back obligations and ensures flow-down of contractual requirements Final account preparation reconciles all commercial matters for project closeout Commercial management is not a post-hoc administrative function. It is embedded in the operating model, running in parallel with technical execution and drawing on the same data. Closeout and Learning The operating model concludes with structured closeout: Final account is agreed with the owner Retention is released according to contractual terms Defect liability obligations are managed Project records are archived Lessons learned are captured and fed back into estimating, planning, and risk management Organizations that neglect closeout leave commercial value unrealised and fail to capture the learning that improves future performance. Why Generic Approaches Fail Generic operating models—designed for manufacturing, retail, or service businesses—fail in project-based environments because they assume conditions that do not exist. Standard ERP workflows assume repeatable transactions. Manufacturing ERPs process purchase orders, production orders, and sales orders in standardised flows optimised for volume and consistency. Project-based operations require flexibility to handle non-standard scope, variable quantities, and change-driven adjustments that standard workflows cannot accommodate. Period-based planning assumes continuous operations. Annual budgets divided into monthly periods work for businesses with stable, predictable activity. Capital projects have their own timelines, unrelated to fiscal calendars. A project budget must span from contract award to final account—which may cross multiple fiscal years—and must be controlled against project milestones, not accounting periods. Functional handoffs assume stable interfaces. In manufacturing, the handoff from engineering to production to shipping follows defined interfaces. In project-based operations, handoffs are context-dependent: each project has unique requirements, and the operating model must accommodate variation while maintaining control. Cost accumulation assumes standard costs. Product costing uses standard costs that vary within narrow bands. Project costing must accommodate actuals that may differ significantly from estimates due to productivity variation, scope change, and market conditions. An operating model that cannot handle variance analysis against project-specific baselines provides no diagnostic value. Performance measurement assumes stable metrics. Manufacturing measures throughput, yield, and unit cost. Project-based operations measure earned value, cost-to-complete, schedule variance, and commercial position. Generic dashboards do not provide the project-centric visibility that managers need. Generic operating models fail because they are designed for businesses where repetition enables optimisation. Project-based businesses require operating models designed for controlled adaptation to unique, changing, and uncertain conditions. Where It Applies General Contractors. Operating models that connect estimating, procurement, site operations, and commercial management across multiple concurrent projects. EPC Contractors. Integrated operating models spanning engineering, procurement, construction, and commissioning—often across multiple geographies and organisational entities. Shipyards. Production-oriented operating models that manage multiple vessels through fabrication, assembly, outfitting, and trials while controlling cost and schedule at the vessel level. Marine and Offshore Contractors. Campaign-based operating models that coordinate onshore preparation, vessel mobilisation, offshore execution, and demobilisation. Mining Development. Operating models that integrate feasibility, engineering, procurement, construction, and commissioning for capital projects that may span five to ten years. Specialty Contractors. Streamlined operating models focused on specific trade scopes—structural steel, mechanical, electrical, façade—operating as subcontractors within larger project structures. Project-Based Manufacturers. Operating models that connect customer order entry, engineering, production planning, fabrication, quality, and delivery for engineered-to-order products. Common Misconceptions Misconception: An operating model is the same as a set of procedures. Reality: Procedures document how specific tasks should be performed. An operating model defines how the entire organisation operates—how work flows, how decisions are made, how data moves, and how performance is measured. Procedures are components of an operating model, not substitutes for it. Misconception: Technology determines the operating model. Reality: Technology enables the operating model but does not define it. An organisation must first design how it wants to operate—then select and configure technology to support that design. Implementing an ERP system without defining the operating model simply automates dysfunction. Misconception: Operating models can be copied from other organisations. Reality: Operating models must fit organisational context: size, complexity, project types, geographic spread, and competitive positioning. Best practices can inform design, but effective operating models are tailored to the specific organisation and its strategic requirements. Misconception: The operating model is a one-time design exercise. Reality: Operating models must evolve as organisations grow, enter new markets, adopt new technologies, and respond to changing industry conditions. Continuous improvement is essential; static operating models become constraints rather than enablers. Misconception: Operating model design is an IT responsibility. Reality: Operating model design is a business responsibility with significant IT implications. Business leaders must define how the organisation should operate; IT enables that design through systems and data architecture. Delegating operating model design to IT produces technology-driven solutions disconnected from business reality. Related Topics What Is a Project-Based Business? — The economic model that the operating model is designed to execute. What Is a Project-Based Organization? — The structural framework within which the operating model operates. What Is a Capital Project? — The discrete engagement that the operating model is designed to deliver. What Is a Bill of Quantities (BoQ)? — The scope definition document that anchors the operating model’s control framework. What Is a Work Breakdown Structure (WBS)? — The hierarchical organisation of work that structures execution and control. What Are Cost Codes in Construction? — The classification system that enables cost accumulation and analysis within the operating model. What Is Project Cost Control? — The control discipline embedded within the operating model. What Is Project Lifecycle Continuity? — The integration of project phases that the operating model must enable. 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