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. A week before the client even hears.
Access to Tower B's east wing is denied — the site team flags it the same day, exactly as they should, in the group.
GCC Cl. 40.2 only requires notice ‘as soon as reasonably practicable’ — no fixed deadline, just a judgment call on how fast word moved. It still has to travel up the chain before anyone writes to the client. A week gone before the client even hears is exactly the kind of delay that judgment turns on.
Catching the liability reset
Leak resealed same day, logged and closed. Clock reset, unnoticed.
A waterproofing joint at Podium starts leaking — the crew reseals it the same day, logged as a routine fix in the site group. Nobody connects it to anything.
Under GCC Cl. 27.8, repairing a defect during the liability period resets that portion's clock by another 12 months. A third repeat failure lets the client deduct the cost directly — the team finds out only when retention release falls short.
Disputed — the record doesn’t hold
Extra work done on the engineer's word. Disputed at the bill.
At a site walk, the client's engineer asks for extra work. The team does it that week and posts photos in the group — nobody asks for it in writing.
Under GCC Cl. 40.4, extra claims are settled principally on the jointly signed registers, meeting records and written notices from the client's Project Manager. Photos in a WhatsApp group are none of those — once the client disputes it, it's your word against theirs.
The Fix
Hindrances and delays — matched to the clause and deadline they may trigger.
One message. No one connects it to the contract.
Flagged the same day — raised by the book, with the record to back it.
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 Velora to your site WhatsApp groups and upload your contract once. Hindrances, repairs, delays — captured as they happen, not just the obvious ones.
Field updates and contract clauses, both structured
Site updates structured into hindrances, delays and repairs; the contract structured into its clauses, notice periods and obligations — two data sets, both machine-readable.
Checked against the clause that’s actually relevant
A routine repair, a late drawing, a missed notice — each checked against the specific obligation or threshold it triggers, whichever clause that turns out to be.
Flagged to your project team while there’s still time
Your project team gets the clause, how and when to raise it, and what to document — no contract expertise needed.
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 — FIDIC, CPWD or your own EPC form — tracked against the project calendar. Hindrances and delays reported on site are matched to the clause they fall under automatically, and flagged to the project team with the notice it calls for and the records to keep — before the window closes.
Commercial Risk Alerts
Flagged with the clause and the deadline — before it compounds.
Small delays and routine repairs rarely look serious alone. Velora rolls them up against the LD threshold and watches for clauses like a liability-period reset — flagging both to the project team with the specific clause and the date that matters, so they're raised while they still count.
The impact
The operational shifts that happen from your first live contract.
Notice windows surfaced early. Cumulative risk visible early. A record you can defend. These are the shifts project 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
Hindrances and delays reported on site are matched to the clause they likely fall under — so notice windows surface while there’s still time to act.
Exposure, visible early
Cumulative delay rolled up before it becomes a real number
Small delays that look harmless alone are tracked together against the liquidated-damages threshold — so you see the exposure building, not just the final account.
A record you can defend
Every notice, every delay — dated and attributable
Every flagged event is logged with its source and timestamp, structured and ready if the claim is ever contested.
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 projects and existing WhatsApp groups.
Frequently Asked Questions
Common questions from project and commercial teams evaluating Velora.
No. Site teams keep reporting in WhatsApp exactly as they do today. Velora reads hindrances, delays, and scope changes from the same groups and matches them to the relevant contract clause automatically.
Your contract's clause structure — FIDIC, CPWD GCC, or your own EPC form — is loaded once. 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 — it means the project team doesn't need to know which clause applies or when to raise it: Velora flags it, the team raises it. Whoever handles claims — a contracts team, or your GM Projects — still decides what to file and how.
Individual delays are rolled up across packages against your liquidated-damages threshold, so the exposure is visible as it builds — not just totalled up at the final account.
It flags the event with the clause and deadline that matters, and keeps a dated, attributable record behind it — the evidence a formal submission is built from, not the submission itself.
Both — FIDIC, CPWD GCC, and your own EPC or infrastructure contract form. The clause structure is configured once per contract.
We run a discounted pilot for the first three months — full product, no long-term commitment. See what it surfaces on your own projects before committing to a subscription.
Yes. Data is stored securely with role based access control, and privacy data is encrypted at rest using AES-256 standard.
What we keep hearing
The longer the contract runs, the more this compounds.
Verbal promise, no notice filed. Window closed in 14 days.
Drawing changed at execution. HO finds out two months later, in the ERP.
Payment withheld over an LD clause nobody knew existed.