Why NI construction firms can't answer basic questions about their own projects | Somvilla
Labour costs, material waste, and project margin are rarely visible in real time for NI contractors. Here's what that's actually costing you.
Ask a contracts manager how a project is going and you’ll get an answer. Ask them what the current margin is against tender, what the committed labour cost is to date, or whether the groundworks package is running over — and most of them have to go away and find out.
That gap between “it’s going fine” and actual numbers is where profit disappears.
How most NI contractors track project costs
The typical setup at a contractor running three to fifteen projects simultaneously looks like this: Sage handles payroll, supplier invoices, and the accounts. Each project has a folder, physical or digital, with the tender breakdown, subcontractor orders, and delivery dockets. The contracts manager or QS maintains a cost spreadsheet that gets updated when they have time, which is not often enough.
Subcontractor valuations get agreed on site and processed through accounts. Variations get logged somewhere. Materials get delivered and signed for, and the delivery notes eventually make their way back to the office. By the time all of this is reconciled into a picture of where the project actually stands, weeks have passed.
There is no malice in this. It’s how the industry works. The problem is that the construction business runs on margin, and margin is a lagging indicator when you’re tracking it this way.
When you find out a project is loss-making
The moment most contractors discover a project has gone wrong is practical completion, when the final account is settled and the numbers are totalled. By that point the concrete has been poured, the subcontractors have been paid, and the only question left is how bad it is.
If you’d known at 40% build that the groundworks were running 18% over budget, you would have had options. Challenge the subcontractor. Cut scope elsewhere. Have a commercial conversation with the client about a variation. Go into the next phase with your eyes open rather than your fingers crossed.
None of those conversations are possible when the cost data arrives after the fact. The information existed — it was on dockets, in Sage, on subcontractor invoices — it just wasn’t assembled into a usable picture at the time when it would have changed something.
What live project margin reporting looks like
A project dashboard for a construction business doesn’t need to be complicated. It needs to answer four questions in real time:
- What have we committed to spend on each trade package, and what does the budget say we should have spent at this stage?
- How many labour hours have we used versus the programme allowance?
- What materials have been delivered and booked against this project?
- What is the current forecast final margin, given what we know today?
The last one is the important one. Forecast final margin at 40% build is a number that changes decisions. Final account margin tells you what happened.
Getting to this requires connecting two things that currently don’t connect: the cost data in Sage and the site-level information that lives in spreadsheets, paper dockets, and the contracts manager’s head.
The Sage problem
Sage 50 and Sage 200 are used by the majority of NI contractors for a reason — they’re solid accounting software. But they were built for accounts, not project cost reporting. You can run a nominal ledger by cost code. You cannot easily get a live view of committed cost versus budget by trade package across six active projects, with a forecast final margin for each.
This isn’t a criticism of Sage. It’s a description of what it was designed to do. Project cost reporting is a different layer, and most contractors either don’t have it or have it in the form of a spreadsheet that one person maintains and everyone else treats as approximate.
What building a project dashboard involves
The data for a project cost dashboard already exists in Sage. The work is in getting it out in the right shape and combining it with site-level inputs.
A typical build involves three parts. First, a read-only connection to Sage that pulls posted costs, committed orders, and subcontractor valuations by project and cost code. Second, a simple web form — accessible from a phone on site — where the contracts manager or site foreman logs labour hours, material receipts, and any known variations at the end of each day or week. Third, a dashboard that combines both, calculates committed cost versus budget, and shows the forecast final margin for each active project.
The site input form takes five minutes to fill in. The dashboard updates automatically when costs are posted in Sage. The contracts manager doesn’t need to build a spreadsheet. The director can see the current margin position across all active projects in thirty seconds.
The return on one project saved
A 2% margin swing on a £500,000 contract is £10,000. A 5% swing is £25,000. The cost of building and running this reporting layer is a fraction of either.
The more accurate framing is: one project that would have finished loss-making, where you instead had the visibility to intervene at 40% build, pays for this infrastructure many times over. Every project after that is where it compounds.
DataPulse Report covers the Sage connection and reporting dashboard — from £1,800, delivered in 5–7 days. If the site input and Sage also need to feed into a connected system, SyncBridge handles the integration layer from £2,400.
Start a brief → — no call, fixed price, quoted within two business days.