A quantum schedule is the part of a disputed account that carries the money, and it is frequently built for the party producing it rather than for the party who has to assess it. Those are different documents. Building the second kind is part of a final account dispute review.
The test is simple: can somebody who was not on the project take any single line and establish whether it is right, without asking a question. Most schedules fail it.
One line, one claim
Each line should correspond to one identifiable item with its own basis, its own evidence and its own value.
Items grouped by period, by trade or by convenience cannot be assessed individually, which means they tend to be assessed collectively and reduced.
Where an item has several components, those belong as sub lines rather than folded into a single figure.
The columns that matter
Reference, description, contractual basis, quantity, rate, value claimed, value assessed where known, and difference.
A column stating the evidence reference for each line is worth more than any amount of narrative, because it answers the assessor’s first question before it is asked.
Keep it to one page width where possible. Schedules that sprawl across printed pages are read less carefully.
Grouping by head of claim
Variations, remeasurement, loss and expense, prolongation, deductions. Each group has a different basis and a different kind of evidence.
Grouping that way lets an assessor deal with a whole category where they accept the approach, which is far quicker than working through a mixed list.
It also makes double counting visible, which is the fastest way to lose credibility on an otherwise sound account.
Showing the basis
Each line should state what it rests on: a contract rate, an adjusted rate, a fair valuation, a compensation event assessment, a contractual provision.
Where the basis is contested, that is a different kind of disagreement from a measurement difference and should be visible as such.
A schedule where every line says claim is not stating a basis, and it invites a response that every line is refused.
Evidence referenced rather than attached
Precise references: document number, date, page where relevant. A reference to the project records is not a reference.
The supporting material should be available on request and organised to match the schedule, so that a request for item forty two produces item forty two.
Attaching everything to the schedule makes it unusable; attaching nothing makes it unverifiable. References bridge the two.
Marking status honestly
Agreed, agreed in principle, disputed on value, disputed on entitlement. Those four states cover most items and each leads somewhere different.
Marking items agreed as they are agreed, with a date, prevents the same ground being covered by the next person to pick up the file.
It also focuses attention. An account showing eighty per cent agreed is read quite differently from the same account presented as wholly in dispute.
Totals that reconcile
The schedule should reconcile to the account, and the account to the contract sum. Where it does not, that discrepancy will be found and it will undermine everything.
Rounding, duplicated lines and items moved between categories are the usual causes, and all of them are avoidable with a check before submission.
A schedule that reconciles cleanly buys credibility that no amount of argument produces.
Keeping it alive
A schedule is a working document rather than a submission. It should be updated as items are agreed, evidence is produced and positions move.
Version control matters, because two parties working from different versions of the same schedule produce confusion rather than progress.
Dating each version and circulating it after each meeting is enough.
What the assessor does with it
Works through it looking for reasons to reduce, because that is the job. A schedule that makes reductions easy to justify will produce them.
The counter is not to obscure the detail but to make the well supported items unanswerable, so that the reductions concentrate where they belong.
An account where the strong items are clearly strong tends to settle closer to the claimed figure than one where everything is presented with the same confidence.
The same schedule in a narrower dispute
Where only part of the account is in dispute, the same structure works at smaller scale: one payment cycle, one package, one head of claim.
That is frequently the better route, because a narrow dispute resolved quickly releases the rest of the account.
Each of the claims and dispute services produces a schedule of this kind for its own subject, which is what makes them assessable rather than arguable.
What to do with the assessed column
Where the other side has assessed the account, their figures belong in the schedule alongside yours rather than in a separate document.
That single step converts two competing claims into one analysis, and it is usually the point at which the real differences become visible.
It also demonstrates that the claim has engaged with the response, which changes how the whole document is received by whoever reads it next.
Ignoring the assessment and resubmitting the original figures achieves the opposite, and it is a common reason an account stops moving entirely.
Where it fits
The schedule is the backbone of a disputed account and of whatever follows it, so building it well is never wasted.
Maintained through the project it is largely a matter of collation rather than preparation, which is commercial management work.
Built at the end from scattered records it is the bulk of the effort, and it is still the first thing worth doing before anything else is attempted.
Final account stopped moving?
A final account dispute review reconciles the account, sets the disputed items out on a schedule with their basis and evidence, and gives a view on where the gap can realistically be closed.