Building
Fit-out and superstructure packages, design responsibility matrices, and the Building Safety Regulator as a first-class read-only identity with a seat that costs nothing — a regulator holds an oversight relationship, not a customer one.
Product
One operating logic across every sector
Sector is an attribute of a project, not a product line. A tunnel and a fit-out differ in their work breakdown and their risk register — not in how a payment notice is reckoned or how evidence is chained.
Civil and infrastructure
Remeasurable works, statutory undertakers as a named delay cause, ground-condition risk carried explicitly, and NEC4 compensation events tracked against the notice clock rather than against a spreadsheet.
Specialised and operational
Short-cycle packages where the payment cycle bites hardest. The Construction Act engine computes the position — which notice established the notified sum, and what a missed one has already cost.
Sized from sole trader to sovereign programme
Thresholds are proportionate rather than fixed. A £40,000 domestic extension and a £2bn programme both have a "material variation", and it is not the same number. The platform decides the scale band from the contract value and applies the thresholds that follow from it, in one place, rather than scattering magic numbers through the engines.
Jurisdiction is data, not a fork
UK statutory periods, bank holiday calendars across the three jurisdictions including the weekend substitution rules, and the Scheme for Construction Contracts defaults where a contract is silent. Currency and tax presentation are held per jurisdiction for display — what a figure is labelled and what an invoice must say — not to compute a liability, which turns on registration and place of supply.
Your sector, your thresholds
Start with the scale you actually work at rather than the one a template assumes.