Read the subcontract register

Commitments read against what they have already cost, with insurance currency and unit-price run rates.

Spending is visible: an invoice arrives and a number moves. A commitment is invisible until it is too late to change it. Signing more sitework than a cost code holds is a decision somebody makes on a Tuesday and a problem the ledger only shows months later, when the invoices catch up.

This register is the number that would have said so on the Tuesday. Every subcontract is listed against the cost code it commits, beside what has actually been billed against it.

The contract sum this register uses

A subcontract has two sums and they are not interchangeable. The one here is the current sum: the stated contract amount plus every executed change order. That is what a cost code has been committed to, so it is what the committed column and the budget read.

The other is the total of the schedule of values, which is what pay applications bill against. The two agree only while the schedule has been kept up to date. The pay applications page shows both and names the gap when there is one. Neither figure is corrected from the other: a change order that has not reached the schedule is something to go and do, not a discrepancy to absorb quietly.

Insurance currency

A certificate is shown by its real failure date rather than by the policy's own expiry. The date that matters is the day the carrier's cancellation notice would already be due, because a certificate stops being good on the day you should have heard something, not at midnight on the last day of the policy.

Unit-price commitments

Where a subcontract is priced by the unit rather than by the lump sum, the register carries the run rate against the plan revision it was quoted on, and flags a commitment that has drifted far enough to be worth requoting. It surfaces the reading. It does not act on it.