Your site already
knows how to use it.
Site teams send messages and photos through WhatsApp — the system infers progress and queues every claim for the planner's review.
A WhatsApp message
becomes a progress update.
“Block B slab done, about 80%” with a photo — the system resolves the activity, infers the claim, attaches the evidence, and queues it for review.
Nothing enters the programme without approval
Every inferred update queues with its source message, the interpreted claim, and the confidence — the planner accepts or rejects before it touches a date.
Review queue — inferred claims awaiting approval
Each claim shown with its source message, interpretation, and confidence.
2880 × 1800
Every measurement carries its source
Who sent it, when, from what message or photo — provenance travels with every claim, so the record is traceable to the conversation that created it.
Evidence store — photographs linked to activities
Photographs and messages held against the work they evidence.
2880 × 1800
“Waiting on client drawings” — with the party named
A site engineer reports a blocker the moment it happens, and the system captures the blocking party, the affected work, and the evidence — because the reporter wants it on record.
Constraints surface — blockers by party
Open blockers, the party responsible, and the work each one holds.
2880 × 1800
The lookahead and the master programme are one model
The site's week and the planner's six months are views of the same schedule — progress flows up, programme changes flow down.
Lookahead — the site's three weeks from the master programme
A filtered window on the same programme, not a separate spreadsheet.
2880 × 1800