Where entitlement gets lost
Every one of these was logged. Every one still slipped through.
It slips one of two ways: the clock runs out before anyone acts, or the client disputes a record that doesn't hold.
Missed — the clock runs out
Flagged same day on site. Weeks before the Project Manager hears.
Access to the east wing isn't given on the date in the programme. The site team flags it in the group the same day, exactly as they should.
Under NEC4 that's a compensation event (cl. 60.1(2)), and cl. 61.3 gives the Contractor eight weeks from becoming aware of it to notify. Miss that and the Prices, the Completion Date and any Key Date are not changed. It still has to travel up the chain before anyone notifies the Project Manager, and eight weeks go quickly.
Missed — the damages at stake
Slab running late, mentioned in the group. Nobody checked the delay damages.
Formwork arrives late from your own supplier for the second week running. The site team mentions it in the group and moves the slab pour back. Nobody connects it to the contract.
Late formwork from your own supplier is your risk. If it delays Completion, Option X7 delay damages run at the rate in the Contract Data for every day, and the time to recover the programme is now, not when they come off a payment.
Disputed — the record doesn’t hold
Extra work done on a verbal instruction. Disputed at valuation.
On a site walk, the client's Project Manager asks for extra work. The team does it that week and posts photos in the group. Nobody asks for the instruction in writing.
Under NEC4 cl. 13.1, instructions and notifications count only when they're communicated in a form that can be read, copied and recorded. Photos in a WhatsApp group aren't an instruction: ask the Project Manager to confirm it in writing, or notify it yourself under cl. 61.3. Once the change is disputed, it's your word against theirs.
Clause references are from the NEC4 Engineering and Construction Contract, used for illustration.
The Fix
Your site team sees the event — Velora flags the clause it may trigger, the deadline and the steps your contract requires.
A routine update. No one connects it to the contract.
Flagged the same day, with the slippage on record.
How it works
Upload the Contract. Connect WhatsApp. Zero Change for Your Teams.
Add Velora to your existing WhatsApp groups and upload your contract once. Your teams keep working exactly as they do — the same whether you're tracking one clause or every live contract.
Picks up the site updates that matter contractually
Connect your site WhatsApp groups and upload your contract once. Delays, repairs, instructions and notices are captured as they happen, not just the obvious ones.
Site updates and contract clauses, both read for what they mean
Site updates become delays, repairs, instructions and notices. Your contract becomes its obligations, notice periods, compensation event and extension of time terms, delay damages and defects terms.
Checked against the clause that’s actually relevant
A routine repair, a late drawing, a verbal instruction — each checked against the obligation or threshold it may trigger, whichever clause that is.
Flagged to the right person while there’s still time
Your commercial team or contracts manager gets the clause, the deadline and what to document; site is told what records to keep.
Data Sources
Involved Parties
Velora AI
What You Get
What Velora Delivers
Contract intelligence — entitlement and risk, flagged in time.
Claim Entitlement
Notice periods tracked against real dates, not memory.
Contract clauses (NEC, JCT, FIDIC or your own amended form) are tracked against the contract calendar. Site events, from access and instructions to ground conditions and notices, are matched to the clause they may trigger, for your team to confirm. The site team is told what notice each one calls for and what records to keep, before the window closes.
Commercial Risk Alerts
Flagged with the clause and the deadline, while there’s time to act.
Small delays rarely look serious alone. Velora flags each delay with the delay damages or LADs rate from your contract, and watches for compensation events, delay notices and defect correction deadlines, flagging each with its clause and date while there's still time to act. A running total against the Completion Date is something the team is still working on.
The impact
The operational shifts that happen from your first live contract.
Notice windows surfaced early. Delay damages exposure flagged on each delay. A record you can defend. These are the shifts commercial teams notice first.
What changes when nothing has to be remembered, reconstructed, or discovered too late.
Windows surfaced early
Notice periods tracked against real dates, not memory
Site events, from delays and instructions to ground conditions and notices, are matched to the clause they may trigger, for your team to confirm — so deadlines surface while there’s still time to act.
Exposure, visible early
Each delay flagged with the delay damages at stake
Small delays that look harmless alone are each flagged with the delay damages or LADs rate from your contract, while there’s time to recover or notify. A running total against the Completion Date is something the team is still working on.
A record you can defend
Every notice, every delay — dated and attributable
Every update traces back to the WhatsApp message and site photo it came from.
See it against your live contracts.
Talk to us about your contract and claims process and we'll set up a pilot against your live sites and existing WhatsApp groups.
Frequently Asked Questions
Common questions from site and commercial teams evaluating Velora.
No. Site teams keep reporting in WhatsApp exactly as they do today. Velora reads delays, repairs, instructions and notices from the same groups and matches each to the contract clause it likely triggers, for your team to review.
Velora reads the clauses as written from the contract you upload, whatever the form, amended or not. Site events are matched against notice periods and obligations using the type of event and the dates involved; Velora flags what it detects; your team makes the call.
Velora reads the site updates that carry contractual weight and flags what it detects — with the clause and the source message, so your team can verify it. Your contracts team stays the final check; Velora's job is to make sure far fewer events go unnoticed.
No. Your commercial team gets the clause, the deadline and what to record; site is told only what records to keep. Whoever handles notices — your commercial team or your commercial director — still decides what to notify and how.
Each delay is flagged on its own, with the clause, the notice it calls for and the delay damages or LADs rate from your contract, so you see what’s at stake while there’s time to recover or notify. A running total against the Completion Date is something the team is still working on.
It flags the event with the clause and deadline that matters, and keeps a dated, attributable record behind it: the evidence a notification, quotation or notice with particulars is built from, not the document itself.
No. Velora flags the event with the likely clause, the deadline and the proof to raise it; your team decides whether to raise it and sends any notice.
No. Velora flags where a site update may trigger a clause, with the likely clause, the deadline and the proof to keep. Your team, with your contracts or legal advisers where needed, decides what to raise.
Your main contract with the client, whatever the form, including NEC, JCT and amended or bespoke building, infrastructure and term maintenance contracts. Velora reads the clauses as written from the contract you upload, and you enter the key dates they count from, such as the starting date and the Completion Date. Text-based PDFs in English work today; scanned contracts are something the team is still working on.
We run a discounted pilot for the first three months — full product, no long-term commitment. See what it surfaces on your own sites before committing to a subscription.
Yes. Access is controlled by role, and your data is encrypted at rest (AES-256).
What we keep hearing
The longer the contract runs, the more this compounds.
Verbal promise, no notice filed. Window closed in 14 days.
Payment withheld over a repair clause nobody knew existed.