Why Your Team Can't Build the Future With Yesterday's Tools
You can tell yourself that your way of working is fine. The spreadsheets work. The email chains work. The site guys know how to handle things on the fly. And it’s all true, right up until it isn’t.
Most Australian construction businesses are running dual-track projects without realising it. One exists in the software: schedules, cost codes, risk registers, forecasts, all sensible and organised. The other exists in reality: site changes that haven’t made it back into the system, costs running hot that haven’t updated the forecast, decisions getting made on information that’s two weeks old because that’s how long it takes to collate the snapshot everyone needs.
Nobody’s sitting around waiting for things to go wrong. It’s just that the industry has always run this way, and the margin erosion is too quiet to notice until it’s already happened.
The numbers that shouldn't be this high
A longitudinal study tracking rework across 346 Australian projects found that rework reduced contractor profit by an average of 28% over a single year.
Australian construction is bleeding margin to poor execution visibility. A longitudinal study tracking rework across 346 Australian projects found that rework reduced contractor profit by an average of 28% over a single year. That’s not on one bad job. That’s the aggregate across everything in the book.
And rework isn’t cheap to begin with. Separate Australian research puts the direct cost of rework at an average of 6.4% of contract value. On a $50M project, that’s roughly $3.2 million in direct rework costs alone, before variations, delays, or disputes get added.
Time gets lost in the same places. The PlanGrid/FMI survey of 80 construction leaders across Australia and New Zealand found the industry bleeds 33% of all working hours to unproductive activities: 4.9 hours per worker per week hunting for information, 3.4 hours on conflict resolution, 3.2 hours fixing mistakes that shouldn’t have happened. Poor data and communication alone were projected to drive $8.4 billion in rework across Australia and New Zealand in a single year.
Or put another way, you’re giving away money every week to problems that are solvable. Nobody looks at it that way because it doesn’t show up as a single line item. It shows up as delay. As rework. As disputes. As margin that’s just gone.
The gap isn't about having a system. It's about people believing it.
Ask a group of construction leaders why projects slip into rework and cost overruns, and the answers cluster around two things: poor communication between stakeholders, and a lack of confidence in the accuracy of project data. Not a lack of systems. Not insufficient oversight. A confidence problem.
A PM knows the schedule probably isn’t up to date. The cost system might not reflect what’s actually happening on site. The site manager’s reality and what the office thinks is happening are two different stories. So when a decision needs making, you make it the way humans always have — you call someone, ask around, get a few opinions, and hope you’ve got enough of the picture to make the call.
That works up to a point. But that point moved a long time ago.
Digital skills aren't IT skills. They're survival skills.
Here’s where most construction thinking breaks down: the assumption that “going digital” is an IT problem, solved by throwing software at it. Get the right platform, migrate the data, run a training course, done.
It doesn’t work that way. Digital confidence, the ability of your team to use connected information to make faster, better decisions, is a culture problem masquerading as a software problem. You can’t train your way out of it if the leadership doesn’t actually believe the system works. You can’t mandate it if project managers still build their real forecasts in a separate spreadsheet because they don’t trust the platform. You can’t automate around it because the gaps are behavioural, not technical.
The disconnect usually starts at the top. A director who still prefers a phone call. A PM who doesn’t use the collaboration platform because they never quite got comfortable with it. A team lead who took one training course two years ago and has only used 10% of the system ever since. That trickles down, and suddenly you’ve got software that cost real money running at maybe half its value, with teams doing workarounds instead of using the actual features.
The best-performing construction companies, the ones protecting margin, delivering on time, building repeat client relationships, don’t necessarily have fancier software than everyone else. They have leadership that uses it. They have an expectation that decisions get made on current data, not hunches. They have the willingness to change how a job works because the system flagged a problem earlier than usual. That’s a cultural choice, not a technical one.
What changes once the team actually trusts the system
- A few things shift once your people collectively believe in the data and the platform:
Cost forecasts stay accurate. Not because the software is smarter, but because when someone’s variance pops up in the system, it gets investigated and corrected in real time instead of discovered in reconciliation. You catch the trend before it compounds. - Problems surface before they become disputes. A trade running two hours over every day becomes a conversation with the planner before it becomes an invoice dispute three months later. You’ve got time to adjust, not just react.
- Decisions land faster. The PM doesn’t spend three hours collecting emails and status updates before they can answer a simple question about where a task stands. They know.
- People stay with their skills instead of leaving their knowledge. When everything’s in the system and not in one person’s head, teams don’t evaporate when someone leaves. The project carries the history.
- Commercial risk stays visible. Not hidden in late-surfacing reports or surprises in reconciliation, but available to leadership every week. You can steer instead of just tracking.
Where to actually start
The companies getting this right don’t rip everything out and start over. They pick one critical workflow, usually something touching cost, schedule, or site communication where the pain is very real, and commit to running it digitally, front to back, with everyone involved. Not as an experiment. As the actual way of working.
That might be “Site changes go through digital documentation. No email version. No site office email chain. One source.” It seems simple, and it is. But it breaks the workaround habit. It builds the muscle of using the system. And it works often enough that people start to actually trust it.
From there you build. Connect the next piece. The next. Each time getting faster because the team’s already bought in and knows where to look.
But none of it works unless the leadership team actually uses the system themselves. That’s the non-negotiable part. You can’t ask your team to trust data they can see you not trusting. Doesn’t work.
The question isn't whether you need to change. It's whether you can afford to wait.
Margins in construction get squeezed every cycle. Rework costs stay high. Communication problems never really go away. But the operators protecting margin through this cycle aren’t doing it by being tougher negotiators or hiring smarter people. They’re doing it by using systems that let them see problems earlier than their competitors and move faster.
If your current way of working is fine, it’s fine right now. Ask yourself what it’ll look like in three years when competitors in your space have their teams actually believing in their data, making decisions faster, and catching issues before they cost money.
That gap compounds.