How time and money are lost
Hindrances are always mentioned. Few reach the contract in time.
Most contracts give more time for delays the employer or its other contractors cause, if the contractor gives notice in time and keeps a record of the hindrance. They charge liquidated damages for the delay that isn't excused, and carry clauses nobody on site has read. Site talks about every hindrance. The record, the clause and the notice are where it slips.
Mentioned, never registered
A gate pass on hold, mentioned for six months.
On one power-plant package, workers held at the gate came up again and again in the site group, on and off for half a year.
Not once did the chat mention a hindrance register, a notice or an EOT.
The notice clock
The hindrance started on the 3rd. The notice went months later.
Contracts ask for written notice within a set time of the event, or as soon as practicable, and many name the hindrance register as the record for any extension.
A notice sent late, or never, is the first thing the client contests.
The clause nobody read
Another contractor's soil on your laydown area. Nobody called it a hindrance.
On the same package, another of the employer's contractors dumped soil on the laydown area. Site posted about it as something to work around.
Under most EPC contracts, interference by the employer's other contractors is grounds for more time. When nobody records it, the delay ends up counted against you.
Small delays add up
A day here, two days there. Then liquidated damages.
Each delay is too small to raise on its own, so none of them is.
At the end, the project is late, the delays that weren't yours have no record, and liquidated damages fall on all of it.
How Velora does it
From a passing mention to a flagged clause.
Your site teams keep posting the way they do today. Nobody has to fill in a register.
- Read
Every hindrance, as it's posted
Fronts not handed over, work held by another contractor, drawings, approvals or free-issue material awaited, gate passes and shutdowns: picked out of the site chats, in any language.
- File
Logged as a hindrance
Each logged with the date it was first posted, the place, what it's holding and the photos, and kept open until site reports it cleared. Filter your issues by hindrance and you have the register.
- Check
Against your contract
Each matched to the clause it may trigger in the contract you upload, whatever the form, including EPC, Railways and CPWD-based conditions: the extension of time, the notice it calls for, the liquidated damages rate and cap, and the records to keep.
- Flag
To the project team, in time
Whoever you choose is alerted the same day and reminded before the notice period runs out. Your team decides what to raise and sends the notice.
Recording hindrances is part of Field Intelligence. Matching them to your contract, with the notice and LD flags, is Contract Intelligence, in early access.
Worked example
Your hindrances, logged from the chats.
Every hindrance on a package, logged from the day it was first posted. Filter your issues by type and they read as a register. Each entry opens into the messages and photos behind it.
Dated from the first post
The start is the day site first mentioned it, not the day someone got round to the register.
Open until cleared
Each stays open while site keeps reporting it, and closes when site reports it cleared.
With what it held
The front, the crew or the activity it stopped, as site described it.
Ready when the EOT is due
The messages and the photos are there for the notice and the claim, not rebuilt from memory.
Illustrative figures
Where it fits
Recorded in Field, flagged by Contract.
Hindrances come from the same site record as progress and deliveries. These pages show the rest, or teach the job by hand.
- ProductContract IntelligenceSite events matched to the clause they may trigger, flagged before the window closes. Early access.
- ProductField IntelligenceProgress, blockers, deliveries and manpower, recorded from your site groups.
- GuideClaim an extension of timeHow to document a delay and claim the time, step by step.
- GuideVariations from verbal instructionsWhen an instruction given on site can still be claimed, and what to record.
- IndustryIndustrialPlants and factories, where late free-issue material and other packages hold the work.
- IndustryRail & metroBlocks given, cancelled or cut short, each logged with its km and the work it held.
Keep the time and money your contract gives you.
Talk to us about one live project and we'll set up a pilot against its WhatsApp groups and your contract.
Frequently Asked Questions
Common questions from project heads, planning engineers and contracts teams.
A running log of everything that stops or slows the work: what happened, where, when it started and ended, and which activities it held. On EPC contracts, joint hindrance register entries are often a principal basis for deciding extensions of time; on CPWD works, hindrances are recorded in the site order book. Velora logs each hindrance from your site groups as it's posted, so the register can be filtered from your issues rather than written up afterwards.
Guide: how to claim an extension of time and document the delay →
Liquidated damages: each flagged delay shows the LD rate and cap from your contract. A running total as delays add up is something the team is still working on. Also the notice periods your contract sets, and the clauses that are easy to miss, like repeat repairs, rectification deadlines and defect-liability terms. Each is flagged for your team to look at.
No. Velora records the hindrance, flags the clause it may trigger and the notice it calls for, and reminds whoever you choose before the window closes. Your team decides what to raise, writes the notice and makes the claim, with the record ready behind it.
The contract you upload, whatever the form, including EPC, Railways and CPWD-based conditions. Its notice periods, extension of time and liquidated damages terms are read from it as written, and you add the key dates they count from, such as the appointed date and the completion date. Text-based PDFs in English work today; scanned contracts are something the team is still working on.
No. Hindrances are recorded from your site groups from the first day, with or without a contract. Uploading the contract adds the clause matching and the notice reminders.
Those are logged too. A late drawing or an approval awaited is logged with its date and checked against the clause it may trigger, the same way.
Recording hindrances is part of Field Intelligence and available today. Matching them to your contract and the notice reminders are Contract Intelligence, in early access: we set it up with you on a pilot project.
We run a discounted pilot for the first three months on one project: the full product, with no long-term commitment.