Sixty-one percent of what.

Why this isn't the single-contract problem

Reporting Week 25 dealt with progress and valuation disagreeing, and the resolution there was a meeting: two functions inside one organisation, sharing a cut-off calendar, reconciling to an agreed outcome.

Two things change when the figures come from separate companies.

The first is that each figure is also a commercial position. A contractor's progress figure supports their application for payment. The Engineer's assessment supports the employer's cash position. Neither party is being dishonest and neither is disinterested, and there is no meeting at which the two become one number.

The second is that nobody owns the aggregate. Each contractor is accountable for their own figure and none of them for the sum. It is assembled by whoever produces the monthly report, from five inputs prepared to five definitions, and its accuracy is nobody's obligation.

The gap that isn't a disagreement

A useful distinction gets lost when everything is treated as a dispute.

Some of the difference between a contractor's figure and a certified valuation is work that has been done and can't yet be evidenced — installed but not inspected, complete but not surveyed, delivered but not signed for. That isn't disputed work. It is work in a queue, and it will be certified next month.

The rest is genuine disagreement about what was built or what it is worth, and that is a much smaller number than the headline gap suggests.

Splitting the two changes the conversation. A gap that is eighty percent evidence lag and twenty percent dispute is a records problem with a small commercial tail. Reported as one figure, it looks like a large commercial dispute and gets escalated as one.

Making the aggregate mean something

The aggregate can be made defensible, and the requirement goes in at award rather than being negotiated later.

Every package reports physical progress on a stated method, and where a contractor uses something else internally, they convert. Weighting is by contract value, stated once, so a large package can't be diluted by a small one moving quickly.

And the denominator is fixed the way Reporting Week 7 fixed it within one contract: progress is measured against a current approved quantity, and when scope changes the denominator changes visibly rather than quietly.

None of that is difficult. It is simply a decision that has to exist before five contractors have each built a reporting system around their own habits.

On a project already running

Where the packages are let and the methods are established, imposing one method isn't available and pretending otherwise wastes a year.

What is available is disclosure. State on the report which method each package uses, next to its figure. The aggregate stays where it is; what changes is that a reader can see it is a composite, and the number stops being quoted as though it were a measurement.

That sounds like a small thing and it is the difference between a figure that misleads and one that informs. It also has an effect nobody expects: once the methods are printed side by side, the question of why they differ tends to get asked by somebody senior enough to settle it.

What to do with the number you have

Two habits make an unreliable aggregate survivable.

Report movement rather than level. A composite figure is unreliable as an absolute and considerably more reliable as a trend, because the method errors are roughly constant month to month and largely cancel in the difference.

And keep the packages visible underneath. Five separate percentages, each defensible in its own terms, carry more information than one number that is defensible in none. The single figure exists because somebody wants one line; the five exist because that is what is actually known.

System design

The first row costs nothing and is the one most reports omit. Printing the method beside the figure is the difference between a composite that informs and one that misleads.

Record	Produced by	Required quality	Verified against	Feeds
Measurement method per package	Each contractor	Stated once and printed beside the figure	Their own procedure	Whether the aggregate can be read
Weighting basis	Project controls	By contract value, fixed, not recalculated monthly	The contracts	The aggregate figure
Denominator per package	Project controls	Current approved quantity, restated visibly on scope change	The change register	Every percentage reported
Valuation gap split	Project controls with commercial	Evidence lag separated from genuine dispute	Inspection and survey records	Escalation · cash forecast

The last row is the one that changes how a gap is treated. Escalating an evidence lag as a commercial dispute consumes senior attention on a problem that resolves itself, and it makes the genuine disagreement underneath harder to see.

Practical insight

Find out which method each package on your project uses to produce the percentage you receive. Ask the question directly, package by package.

You will get three or four different answers and at least one person who isn't certain. That uncertainty is worth finding, because their figure is going into your aggregate every month.

Then take your last report and add one column beside each package: the method. Nothing else changes and your headline stays the same. The next person who quotes your project percentage in a meeting will see what it is made of, which is the whole of what you can do about it this month.

Key takeaways

• Five packages measuring five legitimate ways produce an aggregate that is a percentage of nothing.
• Each contractor is measuring correctly by their own rules, and the sum is still meaningless.
• Across companies, every figure is also an opening commercial position. There is no meeting where two become one.
• Nobody owns the aggregate. Each party owns their own figure and none of them the sum.
• Part of the gap to a certified valuation is evidence lag, not dispute, and it can be the larger part.
• Reported as one number it looks like a commercial dispute and gets escalated as one.
• Fix the method, the weighting and the denominator at award. Afterwards it can't be imposed.
• On a running project, disclose the method beside each figure and report movement rather than level.

Records born here. The measurement method stated per package · the weighting basis for the aggregate · the split of the valuation gap into evidence lag and dispute.

What is coming next

Progress is one number arriving from several organisations. Cost is another, and it arrives from books kept by companies with their own accounting periods and their own reasons for what goes in them.

Next week: the cost that arrives from another company's ledger.