Operating Intelligence for Construction Companies: The Complete Guide

Construction is the largest industry in the world by output and one of the least efficient by data. A company managing 15 active projects across three states might have project data in Procore, labor costs in a payroll system, subcontractor billings in Sage 300 Construction, equipment locations tracked in a spreadsheet, and change orders living in someone's email inbox. None of these systems are connected. None of them agree.

The result: a project manager finds out a job is trending 18% over budget at month-end closeout — six weeks after the cost variance first appeared in the field. At that point, margin recovery requires either renegotiating with the owner (unlikely) or absorbing the loss (expensive). The data was always there. The visibility was not.

Operating intelligence changes that equation. This guide covers the construction-specific operating metrics framework, the data integration challenges that make construction uniquely hard, and the operating system that high-performing construction companies use to catch margin leaks at the job site level — before they compound into project losses.

Why Construction Data Fails Operators

McKinsey's research on the construction industry is sobering: roughly 80% of large construction projects finish over budget, and the average cost overrun is approximately 20% of the original contract value. Schedule overruns are even more consistent — 77% of projects are delivered late, with an average delay of 20 months for major infrastructure work.

These numbers do not reflect an execution problem. Construction workers, project managers, and site superintendents are not incompetent. They reflect a data problem.

The Four Failure Points in Construction Data

Most construction companies experience some combination of these four breakdowns:

1. Fragmented job site data. Daily labor hours, material deliveries, equipment usage, and subcontractor productivity are tracked locally by site supervisors — often in paper logs or individual spreadsheets. This data rarely flows into ERP automatically, and when it does, it arrives in batch form that obscures real-time trends.
2. Subcontractor billing gaps. Subcontractor pay applications (Schedule of Values billings) arrive on their own timeline, often with change orders that were verbally approved on site but never formally documented. This creates systematic underbilling or overbilling on the prime contract side that does not surface until a formal WIP analysis.
3. Change order lag. According to industry surveys, the average commercial construction project generates 35–40 change orders. Each one represents a cost and revenue adjustment that affects the cost-to-complete calculation. When change orders sit unexecuted for weeks, cost-to-complete projections are structurally inaccurate.
4. ERP and project management disconnect. Procore is where project managers live. Sage 300 Construction or Viewpoint Vista is where accountants live. Data flows between them manually — via CSV export, re-keyed cost entries, or monthly reconciliation sessions. The two systems are rarely in real-time sync, which means neither party has an accurate picture of true job cost at any given moment.

What Operating Intelligence Means for Construction

Operating intelligence is not a new ERP system. It is not a replacement for Procore, Sage, or Viewpoint. It is the layer that connects those systems and surfaces the decisions that their individual data cannot surface alone.

In SaaS or ecommerce, operating intelligence connects CRM, billing, and ad spend to answer: "Where are we making money, and where are we leaking it?" In construction, the question is the same — but the data sources are different.

Data Source	What It Contains	What It Cannot Tell You Alone
Procore	RFIs, submittals, daily logs, schedule, drawings	True job cost, billing status, earned value
Sage 300 / Viewpoint	Job cost ledger, AP, AR, payroll, subcontracts	Real-time field progress, schedule risk
Subcontractor billing	Pay applications, lien waivers, retainage	Completion percentage, remaining scope
Equipment telematics	GPS location, engine hours, idle time	Allocated cost per job, utilization vs. budget
Bid / CRM pipeline	Proposals, win rates, backlog	Capacity against active project portfolio

An operating intelligence system connects these sources, normalizes the data into a consistent cost and schedule framework, and surfaces specific actions: which projects are trending to a loss, which subcontractors are behind their billing schedule, which equipment is sitting idle at a cost of $800 per day.

The Construction Operating Metrics Framework

Construction companies track hundreds of metrics. Most of them are project-specific. For operating intelligence — the kind that informs decisions at the company level — the framework collapses to three tiers: financial health, project execution, and resource efficiency.

Tier 1: Financial Health Metrics

Metric	Formula	Target / Warning Threshold
Gross margin %	(Contract Revenue − Job Costs) ÷ Contract Revenue	Target: 15–25% for GC; Warning: <10%
Underbilling ratio	Costs in Excess of Billings ÷ Total Contract Value	Warning: >5% signals cash flow risk
Overbilling ratio	Billings in Excess of Costs ÷ Total Contract Value	Warning: >10% signals deferred revenue risk
Backlog coverage	Contracted Backlog ÷ Monthly Revenue Run Rate	Target: 6–12 months; Warning: <4 months
Project-level EBITDA	Project Revenue − (Labor + Materials + Subcontractors + Equipment + OH)	Positive with >8% margin target

Tier 2: Project Execution Metrics

Metric	Formula	Why It Matters
Cost-to-complete variance	Revised ETC − Original ETC	Early indicator of job loss before closeout
Schedule performance index	Earned Value ÷ Planned Value	<0.9 signals schedule risk; <0.8 requires intervention
Cost performance index	Earned Value ÷ Actual Cost	<0.9 signals cost overrun in progress
Change order realization rate	Approved Change Orders ÷ Submitted Change Orders	Low rate (<60%) signals scope absorption risk
Subcontractor payment lag	Avg Days from Pay App Submission to Payment	>45 days creates downstream cash flow and lien risk

Tier 3: Resource Efficiency Metrics

Metric	Formula	Target
Equipment utilization rate	Billable Hours ÷ Available Hours	Target: 70–85%; Warning: <60%
Labor productivity ratio	Earned Labor Hours ÷ Actual Labor Hours	Target: ≥1.0; Warning: <0.85
Overhead absorption rate	Total Overhead ÷ Total Direct Job Cost	Track vs. bid overhead rate; variance >15% needs review

WIP Reporting: The Financial Heartbeat of Construction

The Work in Progress (WIP) schedule is the single most important financial document in a construction company. It is required by bonding companies, reviewed by lenders, and serves as the primary basis for recognizing revenue under percentage-of-completion accounting (ASC 606 for most contractors).

A WIP schedule calculates, for every active contract: how much revenue has been earned to date, how much has been billed, and what the gap between those two numbers means for cash and margin.

Why Most WIP Schedules Are Wrong

In practice, most construction companies produce their WIP schedule once per month, using cost data that is 2–4 weeks old at the time of preparation. The percentage-complete calculation relies on a project manager's estimate of remaining cost — a figure that is often optimistic and rarely updated in between accounting cycles.

The result: a WIP schedule that looks clean on paper but masks 3–4 projects trending toward losses that will only surface at closeout — sometimes months later. Bonding companies and lenders have learned to read the signals (sudden drops in estimated gross profit, sharp increases in underbilling) but by the time they ask questions, the margin is already gone.

An operating intelligence system that integrates with both Procore (for real-time cost and schedule data) and Sage or Viewpoint (for accounting actuals) can generate a WIP schedule at any point in the month — not just at month-end. That cadence shift alone changes the conversation from "we found a problem at closeout" to "we caught a trend three weeks ago and adjusted."

Cost-to-Complete: The Metric That Predicts Losses Before They Happen

Cost-to-complete (CTC) is the estimated cost required to finish the remaining scope of a project. It is the most actionable forward-looking metric in construction finance, and it is almost universally underused.

The formula is straightforward: CTC = Total Revised Estimate at Completion − Costs Incurred to Date.

But the power of CTC is not in its calculation — it is in comparing it against the remaining contract value (RCV): the portion of the contract price that has not yet been billed.

• If CTC < RCV: the project is on track to finish in profit.
• If CTC = RCV: the project will break even at completion — no margin recovery.
• If CTC > RCV: the project has a forecasted loss that should be recognized immediately under GAAP. The loss does not get smaller by finishing faster; it must be recorded now.

How CTC Variance Signals Project Health

The most useful CTC metric is not the absolute number — it is the variance from the original estimate. A CTC that has grown 15% from the original estimate in the first 30% of a project's duration is a warning sign of systematic underestimation, scope creep, or subcontractor performance issues.

Construction companies that track CTC variance at the cost-code level (not just the project level) can identify exactly where margin is eroding: concrete work running 22% over, electrical subcontractor falling behind, steel delivery delays adding crane rental days. That specificity enables targeted intervention.

Without CTC tracking integrated across the project portfolio, operators are essentially navigating by the rearview mirror — seeing where margin went after it left, not before.

Equipment Utilization: The Silent Margin Leak

For a contractor that owns heavy equipment — cranes, excavators, concrete pumps, compaction equipment — the fleet is one of the largest balance sheet items and one of the most persistently underanalyzed cost drivers.

Equipment ownership cost accrues whether the equipment is running or not. A tower crane costing $18,000 per month in ownership expense (depreciation, financing, insurance, maintenance reserve) that sits idle between projects for three weeks generates $13,500 in unrecovered fixed cost. Multiply that across 15 assets and you have a company that is systematically underpricing jobs or quietly burning margin in overhead.

What Good Equipment Utilization Looks Like

Industry benchmarks for owned equipment utilization in commercial construction typically target 70–85% of available hours in billable production. Below 60%, the cost per productive hour rises sharply and begins to distort job cost budgets — equipment looks cheap at bid time because ownership cost is buried in overhead, but it is not free.

An operating intelligence layer that connects equipment telematics (GPS hours, engine hours from Caterpillar Product Link, Trimble, or similar) with job cost allocation data can produce a utilization dashboard that answers:

• Which assets are below 60% utilization this month and costing overhead without revenue offset?
• Which jobs are running higher equipment hours than budgeted and should trigger a change order review?
• Is it cheaper to rent a specific piece of equipment for the next 60 days than to continue holding it idle?

These are not questions that require a new system. They require connecting the data that already exists across telematics platforms and the ERP job cost ledger.

Data Integration Challenges in Construction

Construction is one of the hardest industries to integrate data across, for reasons that go beyond the volume of systems involved. Here are the specific challenges that most generic BI or analytics platforms fail to address:

1. The Cost Code Problem

Every construction project uses a cost code structure to allocate expenses: concrete, steel, labor by trade, equipment, subcontractors, general conditions. These cost codes are set up per-project in Procore and per-job in Sage, but the naming conventions differ by PM, by project type, and by legacy configuration. Integrating cost data across projects means normalizing cost codes that were never designed to be normalized.

An operating intelligence layer must apply a master cost code taxonomy that maps project-level codes to company-level categories — so a CFO can see, across all active projects, what percentage of total field labor is running over budget without opening 15 separate Sage job cost reports.

2. The Change Order Timing Problem

A change order approved verbally on site in week 2 might not be executed in the contract until week 8. During those six weeks, the additional scope is being built, the cost is being incurred, and the revenue is not yet recognized because the contract amendment is not signed. This creates a systematic underbilling condition that inflates cash flow risk in the WIP schedule.

Procore tracks change events and potential change orders in real time. Sage tracks executed change orders when they are entered by accounting. The gap between these two systems — potential versus executed — is one of the most significant sources of WIP inaccuracy in construction finance. Connecting the two systems and flagging the delta closes this gap.

3. The Subcontractor Management Problem

A general contractor managing 12 active projects might have 80–120 active subcontracts at any given time. Each subcontractor submits pay applications on their own schedule, at their own percentage of completion, with their own interpretation of what has been installed. Reconciling these billings against the prime contract schedule of values — and against actual progress in the field — requires a data layer that most construction companies simply do not have.

Subcontractor overbilling (billing ahead of actual progress) is one of the leading causes of cash flow crises on construction projects. A subcontractor that has billed 70% complete but is only 50% done has effectively borrowed working capital from the general contractor — and if they fail to complete, the GC is exposed.

4. The Labor Cost Lag Problem

Field labor is typically the largest direct cost on a construction project, often 30–40% of total job cost. But payroll data — even when payroll is processed weekly — typically does not flow into the job cost ledger in real time. Hours are collected on daily time sheets (often paper), entered into payroll, processed at week-end, and allocated to jobs in the ERP on a one-to-two-week lag.

This means that for any given week, the job cost ledger is missing the most recent week or two of labor actuals. A cost-to-complete calculation that does not account for these unbilled labor costs will systematically understate actual costs and overstate remaining margin.

5. The ERP Configuration Problem

Sage 300 Construction, Viewpoint Vista, and Spectrum (among others) are powerful but heavily configurable systems. Two companies running the same ERP version might have completely different job cost structures, billing module configurations, and chart of accounts. This makes off-the-shelf integrations fragile — what works for one Sage installation often breaks on another.

Operating intelligence for construction requires an integration architecture that adapts to the specific ERP configuration rather than assuming a standard schema.

The Weekly Project Health Review

The most impactful change a construction company can make is not installing new software — it is running a structured weekly project health review anchored on live operating data. Here is what that cadence looks like for a mid-size general contractor.

The Weekly Review Structure

Review Layer	Attendees	Key Metrics Reviewed	Output
Portfolio pulse (Monday, 30 min)	COO, CFO, VPs of Operations	CTC variance by project, WIP underbilling flags, equipment utilization, backlog coverage	Projects requiring escalation this week
Project deep-dives (Tuesday–Wednesday)	PM + Superintendent + PM Accounting	Cost code variance, subcontractor billing status, change order pipeline, schedule CPI/SPI	Revised ETC updates, change order submissions, subcontractor directives
Resource allocation (Thursday)	Operations Manager, Equipment Manager	Equipment deployment schedule, labor allocation by trade, subcontractor capacity	Equipment redeployment decisions, hire/subcontract decisions for upcoming projects
Financial closeout (Friday)	CFO, Controller	Cash position, billings submitted vs. received, lien waiver status, pay app approvals	AR follow-ups, banking covenant compliance check

This structure only works if the underlying data is fresh. If the portfolio pulse on Monday is running on cost data that is three weeks old, the discussion is historical rather than operational. Operating intelligence — specifically, the integration of Procore daily cost data with the ERP job cost ledger — is what makes this cadence actionable rather than archival.

How Fairview Handles Construction Operating Intelligence

Fairview connects the data systems that construction companies already use and surfaces the metrics that matter most across the project portfolio — without requiring a data team to build and maintain the integrations.

The core workflow for a construction company using Fairview:

1. Connect Procore and ERP. Fairview pulls project cost data, schedule progress, subcontractor billing status, and change order pipeline from Procore. It pulls job cost actuals, pay applications, and contract values from Sage 300 Construction or Viewpoint.
2. Normalize cost codes. Fairview maps project-level cost codes to a company-level taxonomy, so portfolio-level views reflect apples-to-apples comparisons across projects with different cost code structures.
3. Calculate WIP in real time. Rather than waiting for month-end, Fairview generates a live WIP schedule that updates as costs are entered and billings are processed. Overbilling and underbilling flags surface automatically.
4. Track cost-to-complete variance. Fairview monitors CTC against the original estimate at the cost-code level and flags any project where CTC variance exceeds a defined threshold — typically 10% — so the project manager and controller can investigate before the variance compounds.
5. Surface equipment utilization. For companies with telematics integration, Fairview allocates equipment hours to jobs and calculates utilization against available hours, surfacing idle assets weekly.
6. Weekly operating report. Every Monday, operators receive a portfolio-level digest: which projects are trending to loss, which subcontractors are behind billing schedule, which equipment is underutilized, and what requires an owner's attention this week.

The output is not a dashboard. It is a prioritized action list — the specific decisions that the COO or operations leader needs to make in the next five business days to protect margins across the portfolio.