The Subcontractor Valuation Is In. What Work Was Actually Done?
A subcontractor application should be tested against what is measured, accepted and contractually payable. Otherwise the valuation can outrun the work actually earned.
The short answer
A subcontractor application should be tested against what is measured, accepted and contractually payable. Otherwise the valuation can outrun the work actually earned.
Why subcontractor valuation can become misleading
In many construction businesses, claimed progress can differ from measured, accepted and contractually payable work. Each team may have a reasonable local record, but the project-level answer becomes weak when dates, definitions and coding structures do not line up. A programme update may be current to Friday, a valuation may use a different cut-off, procurement may still be converting instructions into orders, and finance may be working from posted transactions. The resulting meeting spends time reconciling versions before it can discuss decisions.
Build one evidence chain
Good subcontractor valuation therefore starts with a common project identity and a small set of governed definitions. A status should mean the same thing to site, commercial, procurement and finance. Where professional judgement is required, the assumption should be visible, dated and attributable rather than buried inside an overwritten spreadsheet cell.
Coding discipline matters as much as workflow. If site progress is measured by location, procurement by supplier, commercial records by contract package and finance by a different account structure, teams will keep rebuilding the relationship manually. The useful design is not to force every function into one screen; it is to preserve enough shared structure that evidence can travel from the workface to the commercial and financial view without losing context.
Separate the states behind the headline number
The strongest control is an evidence chain. It connects the management number to the event that created it, the document or transaction that records it, the person responsible for the next step, and the date on which the status last changed. That chain is more useful than a dashboard that simply repeats totals because it lets a reviewer move from an exception to the reason behind it.
Make the review about movement, not reconciliation
A second principle is to separate states that are often collapsed into one label. Construction work can be instructed but not agreed, ordered but not fully committed, delivered but not installed, installed but not accepted, applied but not certified, certified but not paid, or substantially complete but not commercially closed. When one broad status hides those differences, the forecast appears more certain than the evidence supports.
Use one project structure across functions
Management review should focus on movements and exceptions. A figure that changes for a documented reason is normally healthier than a figure that stays perfectly flat while the project changes around it. The review should ask what moved, why it moved, whether the reason is supported, who owns the next action, and whether the forecast has absorbed the consequence.
The most effective implementation approach is narrow. Choose one live project and one recurring management question, connect only the evidence needed to answer it, and compare the result with the existing review process. The gaps reveal where definitions, coding, approvals or handoffs need attention. Once the first flow is trusted by site, commercial and finance, it can be extended without turning the exercise into a large data-cleaning programme.
Match update frequency to the decision
Coding discipline matters as much as workflow. If site progress is measured by location, procurement by supplier, commercial records by contract package and finance by a different account structure, teams will keep rebuilding the relationship manually. The useful design is not to force every function into one screen; it is to preserve enough shared structure that evidence can travel from the workface to the commercial and financial view without losing context.
Give every exception an owner
Timing should match the decision. Not every field needs real-time capture, but each status needs a known freshness rule. A constraint that can stop tomorrow's work may need immediate attention. A package forecast may be refreshed weekly. Formal reporting may still close monthly. What matters is that the reader knows whether the number is current enough for the decision being made.
Start with one live project
Controls also need ownership. Someone must be responsible for confirming the evidence, someone for agreeing commercial treatment, and someone for updating the forecast or cash expectation. Shared access without clear ownership can produce a well-populated system that still leaves exceptions unresolved.
In many construction businesses, claimed progress can differ from measured, accepted and contractually payable work. Each team may have a reasonable local record, but the project-level answer becomes weak when dates, definitions and coding structures do not line up. A programme update may be current to Friday, a valuation may use a different cut-off, procurement may still be converting instructions into orders, and finance may be working from posted transactions. The resulting meeting spends time reconciling versions before it can discuss decisions.
What management should measure
The most effective implementation approach is narrow. Choose one live project and one recurring management question, connect only the evidence needed to answer it, and compare the result with the existing review process. The gaps reveal where definitions, coding, approvals or handoffs need attention. Once the first flow is trusted by site, commercial and finance, it can be extended without turning the exercise into a large data-cleaning programme.
A practical control checklist
- Measured Work — define the source, owner, cut-off date and next commercial consequence before treating the status as trusted.
- Accepted Progress — define the source, owner, cut-off date and next commercial consequence before treating the status as trusted.
- Materials On Site — define the source, owner, cut-off date and next commercial consequence before treating the status as trusted.
- Approved Change — define the source, owner, cut-off date and next commercial consequence before treating the status as trusted.
- Rework And Defects — define the source, owner, cut-off date and next commercial consequence before treating the status as trusted.
- Contra Charges — define the source, owner, cut-off date and next commercial consequence before treating the status as trusted.
- Previous Certification — define the source, owner, cut-off date and next commercial consequence before treating the status as trusted.
A subcontractor application should be tested against what is measured, accepted and contractually payable. Otherwise the valuation can outrun the work actually earned. The practical objective is not to create another report; it is to make the commercial meaning of the project visible early enough for someone to act.
How this connects to the wider commercial position
This issue sits inside the wider framework in The Project Is Progressing. Is the Commercial Position Keeping Up?. The pillar connects site evidence, change, commitments, valuations, applications, cash and forecast so that one local status does not become a misleading project conclusion.
When useful, compare this control with Payment applications because the two records often move together.
Connected project control
A connected construction ERP such as Saturn can help keep project, site, procurement, commercial and financial information within one governed project flow. The purpose is not to replace professional judgement; it is to make the evidence behind that judgement easier to trace, review and update when conditions change.
A management test for subcontractor valuation
A useful test is to ask whether a new project manager could understand the current position without interviewing five different people. They should be able to see the latest evidence, the commercial interpretation, the outstanding decision and the effect on forecast or cash. If the answer requires offline explanations, the control is depending on personal memory rather than a durable project record.
The same test can be applied at package level. Pick one material, subcontract or change package and trace it from the original scope through current site status, commitment, valuation and forecast. Any point where the reference changes, the cut-off date becomes unclear or the ownership disappears is a likely source of future reconciliation. Fixing those joins often produces more value than adding another summary dashboard.
Frequently asked questions
Why is a spreadsheet not enough?
Spreadsheets remain useful for analysis, but they rarely preserve workflow, source transactions, approvals and ownership across several teams. The control becomes stronger when the governed record is maintained in a shared project structure and spreadsheets are used as an analysis layer rather than the only source of truth.
Does connected control remove professional judgement?
No. Construction commercial management depends on judgement about entitlement, productivity, remaining work, risk and timing. The system should make those assumptions visible and attributable so that other people can understand and challenge them.
How often should this information be updated?
Use a frequency that matches the decision. Urgent site or access issues may need same-day action; package forecasts may be weekly; formal financial reporting may be monthly. The important point is that freshness expectations are explicit.
Where should a contractor start?
Choose one live project and one recurring question that currently requires manual reconciliation. Connect the minimum evidence needed to answer it, agree definitions with the relevant teams, then extend the approach after the first flow is trusted.