Skip to content
Danaos

Construction Cost Recipes: How Labor, Materials, Machinery and Time Form a Unit Rate

A construction unit rate is not simply a price.

 

It is the result of a resource recipe.

 

Behind the cost of one cubic metre of concrete, one tonne of structural steel, one metre of pipeline or one square metre of formwork sits a combination of materials, labor, machinery, subcontracted work and productivity.

 

That is the principle behind Construction Cost Recipes in ProjectVIEW ERP.

 

And importantly, the underlying methodology is not a DANAOS invention. It is consistent with established cost-engineering principles documented by AACE International, RICS, USACE and the U.S. Government Accountability Office (GAO).

 

A realistic construction unit rate is created by understanding:

 

Materials + Labor + Machinery/Plant + Subcontracting + Productivity

 

Time then influences the quantity of labor and machinery required to produce each unit of work.

 

In ProjectVIEW ERP these assumptions can be stored as reusable Cost Recipes / Productivity Templates, associated with the Bill of Quantities (BoQ), connected to the Work Breakdown Structure (WBS) and Cost Codes, and ultimately challenged by actual project performance.

 

The objective is not merely to know what something cost last time.

 

It is to understand why it cost that amount.

 


 

What is a Construction Cost Recipe?

 

A Construction Cost Recipe is the structured combination of resources required to deliver one measurable unit of construction work.

 

For example, a reinforced-concrete BoQ item may require:

 

  • concrete and reinforcement;
  • formwork materials;
  • carpenters, steel fixers and concrete workers;
  • concrete pumps, cranes and vibrators;
  • specialist subcontractors;
  • and a defined level of productivity.

 

The Bill of Quantities (BoQ) is therefore more than a commercial schedule of prices. RICS NRM 2 provides standardized rules for measuring and describing construction works and specifically supports the development of bills of quantities and schedules of rates.

 

RICS NRM 2 — Detailed Measurement for Building Works

 

In ProjectVIEW ERP Estimation & Tendering those BoQ lines can be associated directly with materials, labor, machinery/plant and subcontractors.

 

That resource combination becomes the basis of the Cost Recipe.

 


 

How do resources actually form a unit rate?

 

A simplified direct construction unit cost can be expressed as:

 

Material Cost

 

  • Labor Cost
  • Machinery/Plant Cost
  • Subcontracted Direct Cost = Direct Unit Cost**

 

Preliminaries, indirect costs, overhead, risk and profit may then be applied according to the contractor’s estimating methodology to arrive at a tender or selling rate.

 

But the important issue is what sits underneath those numbers.

 

Materials

 

The material component is broadly:

 

Required Quantity × Current Material Price + Waste Allowance

 

The engineering quantity may remain relatively stable.

 

The market price does not.

 

This is why construction procurement —matters during estimation.

 

ProjectVIEW can maintain historical material prices and use procurement activity to refresh the cost database used during estimating and budgeting. Its current product documentation specifically includes storing historical prices and soliciting updated costs during estimation.

 

A Cost Recipe can therefore preserve how much material is required, while procurement updates what that material currently costs.

 


 

How does labor productivity affect the unit rate?

 

Labor is where productivity becomes critical.

 

A simplified relationship is:

 

Labor Unit Cost = Labor Workhours per Unit × Labor Cost per Hour

 

This principle is independently supported by AACE International Recommended Practice 73R-13: Establishing Labor Productivity Norms.

 

AACE defines a labor productivity norm in terms of the number of workhours required for an activity per unit of measurement.

 

AACE International — Labor Productivity Norms:

 

Consider a simple example.

 

A crew costs $2,000 per shift.

 

If it produces 100 units:

 

Labor contribution = $20/unit

 

If the same crew produces only 50 units:

 

Labor contribution = $40/unit

 

The wage did not double.

 

The work effort required per unit doubled.

 

This is why labor productivity is not merely an HR KPI.

 

It is a cost-engineering variable.

 


 

Is time itself part of the unit rate?

 

This requires an important distinction.

 

Time is not necessarily a separate direct-cost ingredient.

 

AACE specifically distinguishes workhours from duration.

 

But time influences how long labor, machinery, supervision and other resources remain committed to producing the work.

 

Therefore:

 

Productivity → Resource Hours → Cost

 

and:

 

Quantity ÷ Productivity → Required Work Effort

 

Crew size and work effort can then influence:

 

Project Duration → Schedule → Time-related Costs

 

This distinction matters because simply adding “time” as another line item can double-count costs already represented through labor and equipment hours.

 

The better concept is:

 

time connects productivity to resource consumption.

 


 

How does machinery form part of a Cost Recipe?

 

Construction machinery follows similar logic.

 

A simplified formula is:

 

Machinery Unit Cost = Equipment Hours per Unit × Equipment Hourly Cost

 

The U.S. Army Corps of Engineers (USACE) publishes detailed methodologies for calculating equipment ownership and operating costs, including depreciation, fuel, servicing, repairs and other operating components.

 

USACE Construction Equipment Ownership and Operating Expense Schedule

 

This reinforces an important point.

 

A crane, excavator or concrete pump should not simply be assigned a generic lump-sum cost.

 

Its cost contribution depends on its hourly cost and utilization.

 

In ProjectVIEW Machinery Management machinery can have hourly working and idle costs, utilization can be recorded against BoQ-related work, and plant transactions can feed project cost control.

 

If the machine requires twice as many hours to deliver the same quantity, the machinery contribution to the unit rate increases.

 


 

Why is a historical unit price not enough?

 

Suppose a contractor knows:

 

Concrete works on Project A = $145/m³

 

That is useful historical information.

 

But it does not explain the result.

 

Was concrete expensive?

 

Was waste excessive?

 

Were labor hours above the expected productivity?

 

Was machinery underutilized?

 

Was the crew composition inefficient?

 

Did logistics increase cycle times?

 

Was specialist subcontracting required?

 

A historical rate answers:

 

“What did we pay?”

 

A Cost Recipe attempts to answer:

 

“What resources produced that cost?”

 

That distinction is strategically important.

 

The GAO Cost Estimating and Assessment Guide emphasizes structured cost data, WBS development, scheduling, estimating methodologies and updating estimates when actual costs become available.

 

GAO Cost Estimating and Assessment Guide

 

The principle is clear:

 

actual project performance should improve future estimates.

 


 

How does ProjectVIEW connect the Cost Recipe with execution?

 

This is where the ProjectVIEW ERP cost-control model goes beyond maintaining a library of historical unit prices.

 

ProjectVIEW connects three project dimensions:

 

BoQ ↔ WBS ↔ Cost Codes

 

The BoQ defines what must be delivered.

 

The WBS defines how the work is planned and progresses through time.

 

The Cost Codes provide the internal financial and operational classification.

 

ProjectVIEW’s Estimation & Tendering methodology then associates direct resources with BoQ lines, including materials, labor, plant and subcontractors. Productivity templates can accelerate these allocations; labor rates can be related to specialties and HR productivity; plant can be related to machinery utilization; and productivity can help establish a more realistic timeframe for the BoQ and Primavera schedule.

 

Execution then provides the reality check.

 

ProjectVIEW can capture actual:

 

labor productivity, machinery utilization, material consumption, subcontractor performance, progress, and project cost.

 

Its published product architecture explicitly connects Estimation & Bidding, Cost Control, Procurement, Materials, Machinery, HRMS and site data capture.

 

The loop becomes:

 

Estimate → Budget → Execute → Capture Actuals → Compare → Learn → Update the Cost Recipe → Estimate Again

 


 

Why are Cost Recipes strategically important?

 

A contractor does not become better at estimating simply because it has completed more projects.

 

It becomes better when it retains and structures what those projects taught it.

 

Without this feedback loop, project knowledge remains scattered across spreadsheets, procurement records, planners, cost controllers, machinery departments and experienced employees.

 

With structured Construction Cost Recipes past project execution can become reusable estimating intelligence.

 

That is the real distinction.

 

A historical unit price tells you:

 

what the work cost.

 

A Cost Recipe helps explain:

 

what resources were required, at what productivity, for how much work effort, and at what cost.

 

And when the Cost Recipe is continuously tested against actual construction data, estimating stops being only a forecasting exercise.

 

It becomes a continuous organizational learning process.

 

That is the principle behind ProjectVIEW ERP: Do not only record the final price. Understand the recipe behind it.

 


 

About the Author

 

Christos Emmanouilidis is a Civil Engineer and Chief Customer and Commercial Officer at DANAOS Projects Software Solutions LLC

 

His work focuses on construction cost control, industry-specific ERP, project operations and digital transformation across project-based enterprises.

Calendar