Dallas, Texas · Project controls and construction IT since 2021 Projects fail in the forecast, not the field CareersPartnersProgram Rates512-908-5223Data date
Perspectives

When the schedule and the cost report disagree

Two systems, two answers, one board meeting. Why disconnected controls data is a forecasting problem, and what one source of truth actually takes.

April 7, 20265 min readBy Construction IT lead, EvrardBanes

It happens in a lot of board meetings. The schedule shows the project finishing three months late. The cost report shows it finishing on budget. Both were prepared by competent people, from systems that do not talk to each other. Leadership is asked to pick one. That is not a reporting problem. It is a forecasting failure caused by data.

How two answers happen

Schedules live in Primavera P6 or Microsoft Project. Costs live in an ERP or accounting system. Change orders live in a log, often a spreadsheet. Field progress lives in daily reports, photos and someone's notebook. Each system is accurate by its own rules. None of them is tied to the others by a shared structure. So a three-month delay shows up in the schedule without its cost of extended general conditions, escalation and idle equipment ever reaching the cost forecast.

What one source of truth actually takes

  • A shared work breakdown structure. Schedule activities, cost codes and change orders mapped to the same WBS, so every dollar and every day can be found in the same place.
  • A disciplined data date. Cost, schedule and progress cut off at the same moment each period. Data from three different weeks cannot be compared honestly.
  • Automated, checked pipelines. Data pulled from the source systems on a schedule, validated, and flagged when something does not reconcile. Not retyped by hand.
  • One reporting layer. A Power BI model that reads from the integrated data, so the board sees schedule and cost forecasts that were built from the same facts.

Why this is a controls job, not an IT job

Most integration projects fail because they are scoped as software projects. The hard questions are controls questions: what counts as progress, which cost belongs to which activity, when a change is in the forecast. You need people who understand both the database and the data date. That is why we run construction IT and project controls in the same firm.

See our work on construction data and integration and controls systems and P6 administration, or start with the executive reporting you wish you had.

Start a conversation

Put this to work on your project.

Send us the project, the schedule and the date that matters. A senior project controls lead replies within one business day.