FIDIC, EPC, Lump Sum, BOT and PPP Contracts: Why Cost Control Must Go Deeper Than the BoQ

The type of construction contract determines far more than how a contractor gets paid.

 

It defines who carries the design risk, who carries the cost risk, how changes are managed, how progress is certified and, ultimately, how exposed the contractor is to cost overruns.

 

This becomes particularly important in large EPC, Lump Sum, Turnkey, BOT and PPP projects, where the commercial structure provided by the client may not contain enough detail to manage the actual cost of construction.

 

The key principle is simple:

 

 

For enterprise contractors, the contractual Bill of Quantities (BoQ) is therefore only one dimension of project control.

 

True construction cost control requires connecting the BoQ, Work Breakdown Structure (WBS), Cost Codes and actual site execution.

 

And this is where a construction-specific ERP becomes critical.

 

First, FIDIC, EPC, Lump Sum, BOT and PPP Are Not the Same Thing

 

These terms are often used together, but they describe different aspects of project delivery.

 

• FIDIC provides standardized forms of construction and engineering contracts.
• EPC — Engineering, Procurement and Construction describes a project delivery model in which the contractor assumes responsibility for engineering, procurement and construction.
• Lump Sum (LS) primarily describes a pricing arrangement where the contractor agrees to deliver a defined scope for an agreed price, subject to the contract’s provisions for variations and other adjustments.
• BOT — Build-Operate-Transfer combines construction with a concession period during which the private party operates the asset before transferring it.
• PPP — Public-Private Partnership is broader still, typically involving a long-term contractual relationship between the public and private sectors covering combinations of design, construction, financing, operation and maintenance.

 

These structures can overlap.

 

An EPC project, for example, can be delivered as a Lump Sum Turnkey contract using the FIDIC Silver Book.

 

What matters from a cost-control perspective is the amount of commercial, design, construction and performance risk transferred to the contractor.

 

 

FIDIC Red, Yellow and Silver: Different Allocations of Risk

 

Under the FIDIC Red Book, the Employer traditionally provides most of the design, while the contractor executes the construction works.

 

This generally creates a relatively direct relationship between design, quantities, measurement, progress and payment.

 

• The FIDIC Yellow Book shifts more design responsibility toward the contractor. The contractor must increasingly manage engineering, procurement, construction, time and cost as interconnected processes.
• The FIDIC Silver Book, commonly associated with EPC/Turnkey delivery, transfers substantially greater responsibility to the contractor.

 

The Employer is effectively purchasing an outcome:

 

Deliver the required facility, plant or infrastructure asset according to the agreed requirements, price and completion obligations.

 

For the contractor, however, delivering that outcome may involve tens of thousands of activities, resources, purchase orders, material movements, labor transactions, machinery hours and subcontractor operations.

 

That creates a major cost-control problem.

 

The EPC Paradox: A Simple Commercial Price Can Hide Enormous Construction Complexity

 

Consider a simplified EPC BoQ containing a line such as:

 

Structural Works — $12 million

 

From the client’s commercial perspective, that may be perfectly adequate.

 

From the contractor’s cost-control perspective, it is almost meaningless.

 

That $12 million could contain:

 

excavation, dewatering, reinforcement, concrete, formwork, structural steel, labor, cranes, pumps, temporary works, consumables, logistics, material wastage, specialist subcontractors and indirect resources.

 

If the original BoQ does not provide this level of engineering analysis, the contractor cannot simply accept the lack of detail.

 

The contractor has to manufacture that granularity internally.

 

This is where Cost Codes become strategically important.

 

Cost Codes Can Become the First-Level Rough-Cut Budget

 

ProjectVIEW ERP approaches construction cost control through three interconnected project dimensions:

 

 

• The BoQ represents the commercial dimension: what the client is buying and what the contractor is ultimately selling.
• The WBS represents the execution and time dimension: where, when and in what sequence the work must be performed.
• The Cost Code (Cost Control Accounts) represents the internal cost-control dimension: how the contractor classifies and monitors expenditure.

 

ProjectVIEW supports assigning Cost Codes to the BoQ budget and establishing relationships between the BoQ budget and project scheduling structures.

 

When the EPC BoQ lacks sufficient engineering detail, Cost Codes can therefore provide the first internal rough-cut decomposition of the project budget.

 

A high-level BoQ item such as Structural Works can internally be distributed across cost categories for earthworks, concrete, reinforcement, formwork, structural steel, labor, machinery and subcontractors.

 

The contractor is no longer dependent on the client’s commercial structure to determine how the project should be controlled internally.

 

The WBS Adds the Dimension the BoQ Does Not Have: Time

 

Cost Codes answer:

 

What type of cost are we incurring?

 

The WBS answers:

 

Where and when are we performing the work?

 

ProjectVIEW’s tendering and budgeting methodology allows resources, productivity assumptions and timeframes to be associated with BoQ structures and project planning.

 

This creates three different but interconnected views of the same project:

 

BoQ = Commercial

 

WBS = Time and execution

 

Cost Codes = Cost classification

 

Connecting these three dimensions establishes the project’s initial cost-control framework.

 

But the real intelligence begins when construction starts.

 

Site Execution Creates the Missing Engineering Detail

 

A budget is an assumption.

 

Construction is reality.

 

Every day, the construction site generates information that can progressively enrich the original budget.

 

How much work was completed?

 

How many labor hours were required?

 

How much material was consumed?

 

How many hours was a crane, excavator or other piece of equipment utilized?

 

How much subcontracted work was executed and certified?

 

What should that amount of physical progress have cost?

 

And what did it actually cost?

 

ProjectVIEW’s cost-control methodology captures daily transactions including project progress, employee transactions and machinery transactions and uses them to build the actual project cost picture.

 

Its wider construction-management model connects materials, subcontractor certifications, labor productivity and machinery utilization with BoQ–WBS–Cost Code relationships.

 

This is where a relatively rough EPC budget starts becoming a detailed engineering cost model.

 

From Rough-Cut Budget to Child-Level Cost Analysis

 

At tender stage, the contractor may begin with:

 

BoQ → Cost Code

 

During project planning this becomes:

 

BoQ → Cost Code → WBS

 

During construction it develops further:

 

BoQ → Cost Code → WBS → Resources → Daily Transactions

 

The original high-level budget progressively acquires child-level operational detail.

 

A structural works budget can eventually be analyzed down to a specific WBS activity, cost category, crew, material consumption, machinery utilization, subcontractor certificate and physical progress transaction.

 

Instead of simply knowing that structural works are over budget, management can begin asking:

 

Which activity?

 

Which Cost Code?

 

Which resource?

 

Which crew?

 

Which subcontractor?

 

Which material?

 

Which machine?

 

Which day?

 

That is a fundamentally different level of cost control.

 

Daily Work Orders: The Surgical Dissection of Construction Cost

 

Projects are not actually built through monthly financial reports.

 

They are built through daily work.

 

The ultimate level of construction cost control is therefore the ability to associate operational transactions with the project’s commercial, scheduling and cost structures.

 

A daily work transaction should answer:

 

What are we building? — BoQ

 

Where are we building it? — WBS

 

What category of expenditure is involved? — Cost Code

 

Who performed the work? — Labor or subcontractor

 

What did they consume? — Materials

 

What equipment was required? — Machinery

 

What progress was achieved? — Physical progress

 

What should that progress have cost? — Budget

 

What did it actually cost? — Actual Cost

 

This is what we mean by the surgical dissection of a construction project.

 

ProjectVIEW extends the same logic into procurement. Materials procurement and warehouse processes can be associated with BoQs, WBS and Cost Codes, allowing expenditure to remain connected with its project purpose from requisition through purchasing and site consumption.

 

Subcontractor contracts and certifications can also carry Cost Codes, bringing subcontracted work into the same cost-control structure.

 

The BoQ Should Become a Living Cost Structure

 

The BoQ received during tendering should not remain a static Excel document disconnected from execution.

 

ProjectVIEW can import an Excel BoQ and transform it into a hierarchical structure of BoQ code lines. Materials, labor, plant and subcontractors can then be associated with those lines during estimating.

 

Once construction starts, reality begins enriching the original model.

 

The digital evolution becomes:

 

Tender BoQ

 

→ Cost-Coded Budget

 

→ WBS-Linked Project Baseline

 

→ Resource Budget

 
 

→ Daily Site Transactions

 

→ Actual vs Budgeted Cost

 

→ Productivity and Resource Variances

 

→ Management Action

 

This closes one of construction’s most persistent information gaps:

 

the gap between estimating what construction should cost and understanding what construction is actually costing.

 

Why This Matters Even More in EPC and Lump Sum Projects

 

The financial consequences become particularly significant under EPC and Lump Sum contracts.

 

Imagine a contractor has:

 

Contract revenue: $500 million

 

Budgeted cost: $450 million

 

Expected margin: $50 million

 

If execution ultimately costs $485 million, the additional $35 million does not disappear because the client’s BoQ lacked sufficient detail.

 

It comes directly from the contractor’s margin.

 

The objective of construction cost control therefore cannot simply be to report the overrun afterward.

 

The objective must be to identify deviations while management still has time to intervene.

 

That means continuously comparing:

 

Budgeted vs actual labor productivity

 

Budgeted vs actual material consumption

 

Planned vs actual machinery utilization

 

Budgeted vs certified subcontractor costs

 

Planned vs actual physical progress

 

Budgeted vs actual project cost

 

ProjectVIEW’s cost-control model captures site transactions and compares execution against the project baseline rather than waiting for accounting to become the first indication that something has gone wrong.

 

From Traditional Cost Reporting to “Quantum” Cost Control

 

Traditional financial ERP is very good at answering:

 

What did we spend?

 

Construction cost engineering needs to go considerably further:

 

 

By connecting:

 

BoQ ↔ WBS ↔ Cost Codes

 

and continuously feeding that structure with:

 

Labor ↔ Materials ↔ Machinery ↔ Subcontractors ↔ Progress

 

ProjectVIEW ERP progressively breaks project performance into smaller measurable units.

 

This creates what we call “quantum” Cost Control: the continuous decomposition of project cost and performance into increasingly granular operational elements, allowing deviations to be identified closer to where and when they originate.

 

Instead of discovering at month-end that concrete works are over budget, management should be able to drill toward the underlying operational cause.

 

That is the difference between reporting a cost overrun and controlling one.

 

The Real Digital Thread: From Tendering to Construction

 

Many enterprise contractors still operate through disconnected technology layers.

 

One system handles estimation.

 

Primavera handles scheduling.

 

Another platform manages site activities.

 

Procurement operates through corporate ERP.

 

Subcontractor information sits elsewhere.

 

Accounting records financial transactions.

 

Excel attempts to reconcile everything.

 

The result is not digital transformation.

 

It is digital fragmentation.

 

ProjectVIEW ERP takes a different approach by creating an integrated construction-specific backbone connecting:

 

Tendering → Budgeting → Planning → Procurement → Site Execution → Subcontractors → Cost Control

 

The client’s BoQ becomes the commercial starting point.

 

Cost Codes provide the contractor’s internal cost structure.

 

The WBS adds schedule and execution.

 

Procurement consumes the budget.

 

Site transactions record reality.

 

Subcontractor certifications record external production.

 

Progress measures what was actually built.

 

And the resulting information continuously feeds project cost control.

 

ProjectVIEW’s architecture is specifically designed to connect estimation, procurement, subcontractors, site operations and cost control around the common dimensions of BoQ, WBS and Cost Codes.

 

The objective is not another dashboard.

 

It is a digital cost-control backbone for construction.

 

In EPC, the Contract Price Is Only the Beginning

 

FIDIC, EPC, Lump Sum, BOT and PPP arrangements allocate responsibilities and risks differently.

 

But one principle becomes increasingly important as more risk moves toward the contractor:

 

 

An EPC contractor may receive a relatively high-level contractual BoQ.

 

That does not make granular cost control impossible.

 

It makes granular cost control more important.

 

ProjectVIEW ERP addresses this by using Cost Codes as first-level rough-cut budgeting elements, connecting them with contractual BoQ items and time-based WBS activities, and then progressively enriching this structure with real construction data:

 

Labor productivity.

 

Materials exploitation.

 

Machinery utilization.

 

Procurement.

 

Subcontractor certifications.

 

Physical progress.

 

Daily site transactions.

 

The project can progressively evolve from:

 

Contract → BoQ → Cost Code → WBS → Resources → Daily Execution → Actual Cost

 

And this is where a construction-specific ERP becomes fundamentally different from a generic financial ERP.

 

Accounting tells you where the money went.

 

Construction cost engineering must tell you why it went there—and early enough to do something about it.

 

For EPC and Lump Sum contractors carrying significant execution risk, that difference can ultimately determine whether they protect their project margin or explain why it disappeared.