Subcontractor agreement: Payment And Contract Terms

Every row is a verbatim sentence read from the named source's own page through our fetch service on the date shown, hash-pinned to the stored read (the sha of the page's visible text; the raw page is mirrored to R2).

7 of the 18 named sources that could be read published a usable figure; 11 published none and are recorded as not published, never filled in; 5 could not be read (blocked, dead or unreachable) and count nowhere.

The headline figures (median, minimum, maximum, quartiles) are over ONE figure per source in day (a source's median where its page yielded several accepted sentences), so N counts sources, never sentences; 59 candidate sentence(s) were refused by a reviewer with the reason recorded.

The fuller derivation this dataset is chartered to grow into (not yet what the figures above are; they are each source's own published figure as read): one row per jurisdiction per term: the retainage cap and its release trigger, the days from invoice to payment for public and private work, the pay-when-paid position, the notice a contractor must give before suspending, and the instrument each is set by.

The comparison across five regimes is the figure nobody publishes: the spread of retainage caps, the fastest and slowest statutory payment clock, and which jurisdictions void pay-when-paid outright.

Beside it, one row per contract document (subcontract, schedule of values, application for payment, quote, estimate, proposal, invoice) with the fields its publisher says it must carry and whether it is binding on acceptance.

Changed-since carries the reforms, which are frequent.

59 candidate sentences on these pages were refused by a reviewer; each refusal and its reason is recorded in the review ledger.