Think about what your project controls team actually does every week:
Chase teams for status updates. Ping site managers: “Is WP-02 really complete?” Email designers: “Can you confirm those deliverables are in the CDE?” Wait for responses. Update the spreadsheet. Send it around. Realize someone updated their copy offline. Merge the versions. Find the conflicts. Start over.
Then do it all again next week.
This isn’t project management. This is data administration.
Here’s what nobody quantifies: the time cost of manual tracking.
A typical project controls team spends 8-12 hours per week managing spreadsheet trackers. That’s one full-time person’s week, just maintaining status data. And that’s before they actually analyze anything.
Multiply that across a £10M programme: 500+ hours per year on data entry and chasing. That’s £30K-50K in pure overhead. And it doesn’t even get you real data—it gets you last week’s answers.
But that’s not the worst part. The worst part is what you’re not doing while you’re updating spreadsheets.
You’re not catching compliance gaps early. You’re not coordinating across teams in real-time. You’re not enabling progressive assurance. You’re managing status instead of managing delivery.
Progressive assurance means verifying compliance continuously, in real-time. But if your tracker is a spreadsheet:
That’s not progressive assurance. That’s delayed reporting pretending to be assurance.
Real progressive assurance requires real-time visibility. And real-time visibility requires automation, not manual data collection.
Imagine your project tracker updated itself.
Deliverable uploaded to CDE? Status updates automatically. Inspection completed? Verification recorded automatically. Assurance check passed? Status flows through automatically. Issue logged? Relevant teams notified automatically.
Your team doesn’t chase status. Status flows to them.
The time savings alone are staggering. Those 10 hours per week your team spends managing spreadsheets? They’re now available for actual project management: analyzing trends, catching risks early, solving problems, coordinating teams.
But the real value isn’t time saved. It’s capability gained.
With automation, you can finally do progressive assurance. Real-time verification. Continuous compliance checking. Early gap detection. The kind of oversight that actually prevents rework.
Manual tracking (spreadsheet): - Weekly status updates (if someone remembers) - Chasing teams for data - Gaps discovered at handover - No real-time verification - Compliance audit at the end
Automated tracking: - Real-time status (connected to actual deliverables) - No chasing required (data flows automatically) - Gaps discovered during delivery - Continuous verification - Compliance verified throughout
One is administrative overhead. The other is project governance.
Here’s what this really signals: manual, spreadsheet-based project management is becoming obsolete.
Not because spreadsheets are bad tools (they’re fine for what they do). But because projects have become too complex, data requirements too sophisticated, and compliance expectations too strict for manual systems to work.
Progressive assurance isn’t a nice-to-have. It’s table stakes. And progressive assurance requires real-time data, which requires automation.
The projects winning right now aren’t the ones with better spreadsheets. They’re the ones that automated away the spreadsheet problem entirely.
Imagine your project trackers working like this:
Work happens → Data flows automatically → Tracker updates in real-time → Teams see actual status → Compliance is verified continuously → No chasing. No manual updates. No data lag.
Your team moves from “managing data” to “managing delivery.”
And compliance goes from “verified at the end” to “verified throughout.”
That’s not just better tracking. That’s a different way of running projects.
Your team shouldn’t be spending 10 hours a week updating spreadsheets. They should be managing actual delivery.
If they are, something needs to change.