A UK Project Director we spoke to last month sat through his Monday morning progress meeting hearing "we are 47 percent complete" against a programme showing 51 percent planned. His QS was building the interim valuation off the same number. Everyone in the room knew the 47 percent came from a spreadsheet a site manager updated on Friday evening from a mix of walk-round observation and gut feel.
That is the site progress conversation on most UK construction projects in 2026. The spreadsheet number is wrong by 5 to 15 percent. Everyone knows it. Interim valuations get built off it anyway.
This article is a candid buyer's guide for project directors, construction directors, and commercial directors wanting genuinely reliable site progress data. What the software has to do. The configurable progress matrix.
The 2026 UK vendor landscape. Real cost bands. And how progress data connects to interim valuation without creating downstream commercial exposure.
What Site Progress Software Actually Has to Do
Six capabilities that separate real progress tracking from a shared spreadsheet.
Configurable progress matrix. Break work into measurable units per work package. Foundations, superstructure, envelope, internals, MEP first fix, MEP second fix, finishes, external works. Each with defined measurement units and methodology.
Mobile capture on site with photo evidence. Site managers, foremen, and QSs capture progress at the workface, with photos linked to specific activities and locations. Not desktop entry from a Friday walk-round.
Defined percentage-complete methodology per activity. Physical measurement (how much floor area, how many blocks laid, how many linear metres of pipe installed). Earned value calculation. Milestone-based completion for indivisible work. The methodology chosen per activity type, not a single method forced on everything.
Cross-site rollup for portfolio views. Project Director sees weekly progress across all live sites. Programme Director sees the full portfolio. Aggregation is comparable because methodology is standardised.
Programme integration for planned-vs-actual. Import from Primavera P6, Asta Powerproject, or MS Project. Show actual completion against planned. Variance analysis. Forecast to completion.
Interim valuation and application for payment feed. Progress data flows to the QS for monthly interim valuations. Wrong data means over-application (client rejection, cashflow problem) or under-application (money left on the table).
Generic project management platforms handle two or three of these. That is why the progress tracking category exists as separate software or as a specialist module within construction PM platforms.
The Configurable Progress Matrix
The single most important design element for reliable progress tracking. Not a technology choice, a discipline choice.
Break work into measurable units. Concrete floor slab: measured in square metres poured. Blockwork: measured in square metres laid. First fix electrical: measured in circuits complete. External cladding: measured in panels installed. Every activity gets a unit that a site foreman can physically count or measure.
Define what percentage complete means. For each activity, decide the measurement methodology. Physical measurement for tangible work. Earned time for design or admin. Milestone-based for indivisible activities. Do this at project kickoff, not month six when everyone is arguing about numbers.
Standardise across sites. Portfolio developers with 5+ concurrent sites need comparable progress. That requires the same measurement methodology across projects. Standardisation feels bureaucratic on day one and pays back on month twelve when the board asks portfolio-level questions.
Adjust for scope changes. Variations and change orders alter the baseline. The progress matrix updates with each accepted change. Failure to do this means percentage-complete numbers drift meaningless against a stale scope.
The CIOB research and policy hub publishes guidance on progress measurement discipline; the pattern is consistent that measurement methodology matters more than the software choice.
The 2026 UK Vendor Landscape
LetsBuild. Belgian/EU platform with strong UK footprint. Focused on site coordination and progress tracking. Mobile-first design. £30 to £70 per user per month. Best for mid-market contractors wanting focused progress and coordination.
PlanRadar. Austrian SaaS with strong UK presence. Excellent on defects and inspections. Progress capability lighter than LetsBuild. £30 to £90 per user per month. Best for defect-heavy contracts with progress as secondary requirement.
Fieldwire (Hilti-owned). US mid-market with strong foreman-level task and progress management. £30 to £75 per user per month. Best for medium contractors with site-focused workflow.
Procore. Enterprise-tier construction PM with progress bundled into broader platform. £180 to £350 per project per month equivalent for main contractor tier. Best for large contractors already committed to Procore.
Custom builds. Defensible for portfolio developers with cross-project reporting requirements, contractors above £100m turnover with unusual progress workflow, or where progress integrates with a custom commercial or valuation platform.
For most UK contractors between £30m and £100m turnover with standard workflow, LetsBuild or Fieldwire cover the essential needs. Custom becomes defensible above £100m or with portfolio complexity. See our earlier post on construction project management software UK for the broader construction PM platform picture.
How Progress Data Feeds Interim Valuations
Progress and valuation are commercially linked but methodologically distinct.
Progress measurement. Physical work done on site. Foreman-observed and QS-verified. The truth of what has been built.
Interim valuation. Monthly application for payment against the contract. Combines progress against measured work, retention held, materials on site, preliminaries, and any variations agreed. Signed by client's QS or contract admin.
The connection point. Progress data feeds the measured work portion of interim valuation. If progress is wrong, interim application is wrong. Over-application gets rejected by client, causing cashflow problem. Under-application leaves money on the table until next month or beyond.
Software that connects these cleanly:
Progress captured per work package with defined measurement methodology
QS review workflow before application
Interim valuation calculation with materials, retention, and variations
Application generation with supporting evidence trail
Certified payment tracking against application
Programmes that keep these separate (progress software + separate valuation spreadsheet) reintroduce the errors the platform was supposed to fix. The GOV.UK construction statistics show cashflow disputes as a leading cause of UK construction insolvency; interim application accuracy directly affects this.
Real 2026 Cost Bands
Off-the-shelf annual cost (fully-loaded for typical mid-market UK contractor):
LetsBuild: £15k to £45k
PlanRadar: £15k to £60k (broader than progress-only)
Fieldwire: £15k to £45k
Procore: £30k to £180k (bundled progress within broader platform)
Custom build:
Proof of concept: £30k to £60k over 8 weeks (one work package type, mobile capture, progress matrix)
Pilot: £70k to £150k over 3 to 4 months (full progress matrix, cross-site rollup, one integration)
Production: £180k to £400k over 6 to 10 months (multi-site, programme integration, interim valuation feed, portfolio dashboards)
Add £15k to £60k per year in ongoing platform run cost. Add £30k to £100k per year if you keep in-house engineering.
Break-even for custom against off-the-shelf typically lands at year two for portfolio developers or contractors above £100m turnover with unusual reporting workflow.
What We Learned Building a UK Property Platform
We built a multi-site management platform for a UK property developer with 30-plus concurrent sites. Progress tracking was central. Two lessons transfer directly.
Measurement methodology matters more than software features. Our earliest version had beautiful progress capture UI but inconsistent methodology across sites. Percentages were not comparable. Portfolio rollup produced numbers nobody trusted. We rebuilt with standardised measurement discipline per activity type. Same UI, comparable data. Portfolio Director could finally make decisions on the numbers.
Photo evidence linked to progress capture prevents disputes. Every progress increment above 10 percent required photo evidence. QS review became faster because photos supported the number. Client valuation reviews became easier because supporting evidence was one click away. Disputes over "did that really happen this week" evaporated.
You can see our shipped work at our portfolio. If you want a candid conversation about your specific progress tracking programme, book a progress tracking software call with WhiteStone.
Common Failure Modes
Three failure modes we see repeatedly.
Rolling out platform without progress methodology discipline. Beautiful software, inconsistent measurement, unreliable numbers. Sites capture but data is not comparable. Portfolio reporting stays in spreadsheet.
Progress data disconnected from valuation. Progress captured in platform, valuation built in Excel. Errors reintroduced at the interface. Cashflow surprises follow.
Desktop-only progress capture. Site manager types Friday walk-round observations into desktop system.
Same lag, same accuracy problem as spreadsheet era. Mobile capture at the workface is the operational difference.
Frequently Asked Questions
How do you measure real site progress vs planned?
Progress is physical work done on site, measured against a defined methodology per activity (physical measurement, earned value, milestone). Planned is what the programme (P6, Asta) said should be done by this date. Variance analysis compares the two. Reliable comparison requires consistent measurement discipline, not just software.
What is a configurable progress matrix?
A breakdown of project work into measurable units per work package, with defined measurement methodology per activity. Foundations measured in cubic metres of concrete. Blockwork in square metres. First fix electrical in circuits complete. Standardised across sites for portfolio reporting comparability.
How does progress data feed valuations?
Progress captured per work package with defined measurement methodology, reviewed by QS, combined with materials on site, retention, preliminaries, and variations. Result feeds monthly interim application for payment. Wrong progress data means wrong application, causing cashflow problems or leaving money on the table.
Buy or build for UK progress tracking software?
For most UK contractors under £100m turnover, LetsBuild or Fieldwire cover the essentials at £15k to £45k annually. Custom becomes defensible for portfolio developers with cross-project reporting, contractors above £100m with unusual workflow, or when progress integrates with a custom commercial platform.
How long does site progress software rollout take?
Off-the-shelf: 3 to 8 weeks contract to first live site, plus 3 to 6 months to embed measurement discipline. Custom: 6 to 10 months from kickoff to production, plus 3 to 6 months to standardise methodology across sites. Rollouts that skip methodology work fail regardless of software choice.
The One Thing to Remember
Site progress tracking software is only as reliable as the measurement discipline underneath it. Beautiful mobile capture on top of inconsistent methodology gives you a prettier version of the same wrong number. The programmes that succeed standardise measurement per activity type before rollout. The programmes that fail buy the platform first and hope the discipline follows.
If you want a candid conversation about your specific programme, browse our custom software development services or come to the call.
