Labour Cost Tracking on Construction Sites: Why Your Timesheets Need to Drive More Than Payroll

Most construction companies treat timesheets as a payroll input. Workers clock in, supervisors sign off, HR processes salaries. End of story.

Meanwhile, labour costs — which make up 25–40% of total project cost on most GCC construction sites — disappear into a single aggregate line in the cost report. No project-level breakdown. No WBS allocation. No productivity signal. By the time a cost overrun surfaces, the project has been overspending on labour for weeks.

The Payroll Trap: When Timesheets Stop at HR

Labour is processed for payroll but not for project controls. That one disconnect creates three problems that compound across a project's life:

No committed cost visibility. When you approve a work package, you are committing a certain number of manhours. If those hours are not tracked against the right WBS codes in real time, you have no idea whether you are within budget until the end-of-month payroll run hits the books.

No productivity signal. Knowing you spent SAR 180,000 on labour in Week 14 tells you nothing. Knowing that your steel-fixers spent 4.2 manhours per tonne of rebar on Levels 4–8, against a budget rate of 3.1 manhours, tells you exactly where the problem is — and gives you four weeks to fix it before it compounds.

No project-level P&L. If labour is allocated to payroll cost centres rather than project codes, your management accounts show company-level gross margins that blend profitable and loss-making projects. A CFO running a SAR 600M portfolio with seven active projects cannot see which two are destroying margin if labour never reaches the project cost report.

Labour Cost as a Share of Total Project Cost

The exact percentage depends on project type and procurement strategy:

• Building construction (structural, architectural): 30–40% of direct cost
• Infrastructure (roads, earthworks): 20–30%
• MEP and finishing works: 35–45%
• Civil works under supply-and-fix subcontracts: lower for the GC, but the subcontractor's labour is still your production risk

At SAR 200M project level, a 2% labour cost overrun is SAR 4M. Across a portfolio of five concurrent projects, that is exposure that matters.

What Proper Labour Cost Tracking Actually Requires

Linking Every Timesheet Hour to a WBS Code

Every worker's hours need to be allocated to a specific work package — not just a project, and not just a trade. "Rebar — Level 3 Structure" not "civil works." This is where most companies fail: the timesheet form is too simple (one cost centre for the whole project) or too complex (workers do not know which code to select, so supervisors batch-assign at month-end, destroying accuracy).

The right approach is a two-level structure: the worker selects their trade and location, the system resolves the WBS code. Supervisors confirm daily, not monthly. Mobile collection — QR-based or a simple phone form — eliminates paper timesheets that sit in a supervisor's van for three weeks.

Productivity Benchmarking: Manhours per Unit of Output

Labour cost only becomes a management tool when paired with quantity output. The metric is manhours per unit (MH/unit):

• Concrete pours: MH per m³ placed
• Rebar: MH per tonne fixed
• Formwork: MH per m² erected and struck
• Blockwork: MH per m² laid
• Cable pulling: MH per metre

If your budgeted rate is 3.1 MH/tonne for rebar and your site is running at 4.2 MH/tonne, the productivity index is 0.74. At 50 tonnes per week, that is 55 extra manhours per week — roughly SAR 4,500 per week in avoidable cost, compounding across the duration of the structure.

Overtime Management and GCC Labour Regulations

Saudi labour law caps standard working hours at eight per day, 48 per week. Overtime is paid at 150% of the base rate. In GCC construction — with summer heat restrictions, Ramadan working hour adjustments, and peak-season site pressures — overtime often runs at 15–25% of total hours worked.

That premium needs to appear in cost reports, not just in the payroll ledger. A project budgeted on standard hours that runs 20% overtime across a six-month structural phase absorbs an unplanned SAR 800K–1.2M labour cost inflation with no visibility in the cost report until the payroll bill arrives.

Timesheet systems that capture day-type, shift, and overtime flags automatically separate standard and premium labour cost in the cost report — and allow project managers to see the overtime rate by work package before it becomes a budget line.

Labour Analytics That Change Project Decisions

Once timesheets flow to WBS codes and carry quantity outputs, three analytics become available that change what project managers actually do:

Productivity trend. Week-over-week MH/unit by trade and location. Declining productivity is one of the earliest signals of scope creep, poor sequencing, tool shortages, or workforce management problems — all fixable when caught in Week 6, not Week 16.

Labour cost versus budget by WBS. Not the company's total payroll, but this project, this work package, this week's budget versus actual. A structural engineer running reinforced concrete frames needs to know whether concrete labour is within budget at Levels 4–6 before moving falsework to Levels 7–9.

Earned value integration. When timesheet hours drive the actual cost input into an EVM model — alongside PO commitments and work confirmations — the cost performance index becomes accurate. Projects that feed EVM with end-of-month payroll data are always looking backward. Projects that feed it with daily timesheets are managing in the present.

GOSI, Musaned, and Saudi Regulatory Compliance

In Saudi Arabia, labour data is not only a project management tool — it is a regulatory requirement.

GOSI contributions are calculated on actual salaries including overtime. A timesheet system that captures overtime separately makes GOSI calculations audit-ready without manual reconciliation.

Musaned requires accurate workforce rosters. Real-time timesheet data keeps the workforce register current — critical when NEOM, Aramco, or ROSHN conduct compliance checks on workforce documentation.

Ministry of Human Resources site inspections check that workers are not on site outside permitted hours, particularly during summer heat restrictions (prohibited outdoor work 12:00–15:00, June through September in Saudi Arabia). Automated shift-type flags in the timesheet system create the documentation trail for these checks.

Five Steps to Start Tracking Labour Costs Properly This Week

1. Define your WBS codes before work starts. Labour allocated to undefined codes gets batched to a general "other" category and is unrecoverable for cost control. Build the WBS structure before mobilisation and make it the field supervisor's reference.

2. Move to daily timesheet collection. Weekly or monthly collection means you are always three weeks behind actual site conditions. Daily collection via mobile — even a supervisor-level log covering 15–20 workers — takes 10 minutes and provides current data.

3. Capture quantity outputs alongside hours. Add a single quantity field to the daily log: tonnes of rebar fixed, m³ of concrete placed, m² of formwork. Hours without quantities are a cost record. Hours with quantities are a productivity record.

4. Separate standard and overtime hours from day one. Do not blend them into a single figure. The moment standard and premium hours are separate in the timesheet, the cost report shows true labour cost without manual extraction from payroll.

5. Run a weekly productivity review by trade. Not a monthly report — a weekly 20-minute review comparing current MH/unit against budget by trade. The project quantity surveyor and site supervisor together. Corrective actions taken in Week 4 cost a fraction of what they cost in Week 14.

Takeaways

Labour cost is not a finance department problem. It is the most immediate controllable cost on your site, and it is currently invisible in most GCC construction cost reports.

The practical shift is not a technology project — it is a data discipline change. Daily timesheet collection at supervisor level, WBS code assignment at time of capture, quantity output alongside hours. When that data flows into your cost management system in real time, a 25–40% share of your project cost becomes manageable rather than a monthly surprise.