Xalios
Get a Demo
Solutions/By industry/Construction and property

Variations and valuations,
read the day they land.

Payment applications checked against the contract and the last valuation, subcontractor certificates tracked before they expire, and contractual notices prepared with the dates counted.

The situation

Applications arrive monthly, each one a spreadsheet, a narrative and a bundle of supporting photographs. Somebody has to read them against the contract, the last valuation and the variations agreed since, inside a window measured in days.

At the same time, insurances and accreditations for every subcontractor on site expire on their own dates, and the one that lapsed is discovered when somebody asks for the certificate.

What arrives

Variation and change ordersRead
Payment applications and valuationsRead
Subcontractor certificates and insurancesRead
Site correspondence and noticesRead

Per project and per package. A role scoped to one project cannot see another’s commercial position.

Integrations →

Three roles teams start with

Reading an application against a contract is checkable work. Certifying it, and serving anything under the contract, is not.

LEVEL 1Certificate trackerReads every insurance, accreditation and qualification on file, records what expires when, and raises the ones approaching their date.
LEVEL 3Application checkerCompares the application against the contract sum, the agreed variations and the previous valuation, and lists every line that does not reconcile.
LEVEL 4Notice pack prepAssembles a contractual notice with the dates counted from the contract terms and the supporting record attached, unsent, for a quantity surveyor to review.
A floor, not a setting

Certification and notices stay with a person

Nothing is certified, and no notice under the contract is served, by an AI employee. Not at level 5, not with a configuration change. A payment notice or a payless notice served late or wrongly has consequences that cannot be withdrawn.

Instructions to site and anything affecting safety are outside its scope entirely. It reads the paperwork that follows the work; it does not direct the work.

The five levels and their floors →
It may

Check applications, reconcile variations, track expiring certificates, count contractual dates, prepare notices and packs.

It may not

Certify a valuation, serve a notice, instruct site, agree a variation, or make any decision touching safety.

One record, in full

Package 12 · application 7With the QS
DIDChecked the application and listed four lines that do not reconcile, with the difference on each.
BECAUSETwo variations claimed are not in the agreed variation register. One line duplicates application 6.
SOURCESThe application, the contract sum analysis, the variation register, and application 6.
DATESThe payment notice is due in 4 days, counted from the due date in clause 34. Notice prepared, unsent.
WITHThe quantity surveyor named on the package, with the four lines itemised.

If the account is disputed a year later, the record shows the application as submitted, the register as it stood, and who certified what.

Decisions and replay →

What stays with your people

Commercial judgement

What to accept, what to challenge and what to settle to keep the programme moving. Reconciliation is arithmetic; this is not.

Certification

The valuation and the payment notice carry a person’s name, because under the contract they have to.

Site decisions

Sequence, method, safety and instruction. None of that is document work and none of it is delegated here.

Next industryAdministration, kept clear of the clinical.Correspondence, invoices and information requests worked as admin, with clinical judgement entirely out of scope.Healthcare administration →

One package, one month of applications. That is the pilot worth running.