What slips at month-end
Different work, the same leaks. On every linear project.
Whatever the sector, the work is spread over kilometres and reported in many groups, and nothing is totalled until month-end. The same four things slip on every project.
Missed in the bill
Small work, posted one photo at a time.
Delineators on a road, house connections on a water main, bonds on a railway: done a few at a time, each posted among hundreds of messages.
At month-end some are missed, and they wait for next month's bill.
Work outside the BOQ
Done on site, with no item to bill it under.
Painting at two toll plazas matched no BOQ item on one maintenance contract. When the engineer asked for an item-wise statement, its 45 updates and 53 photos went in with it.
Without a record by place and date, that statement is rebuilt from scroll-back, or never made.
Contract triggers
Events nobody reads as contractual.
A traffic block cancelled, a foundation type changed on site, a pipeline shifted on the engineer's word.
Each can trigger a clause with a notice window, and by the time anyone checks, it has often closed.
Material cost
Loads spread across depots and groups.
Aggregate, pipes, tower steel and ballast arrive from several vendors, each load with a challan, at yards and depots along the route.
Checking each vendor's bill means finding challans spread across groups.
What Velora picks up
What your site groups already carry, on any linear project.
Velora reads text, voice notes and photos in the groups your teams use today, and files each update by the way your site refers to place.
Progress by location
Work done by chainage, km or tower location, with its span, side and photos.
Quantities
Lengths from chainage spans, areas from sizes in captions, counts and stated figures, each marked with how it was arrived at.
Tests and inspections
Level surveys, hydraulic tests, pour cards and inspection records, when they are posted.
Hindrances
ROW, permissions, blocks and crossings, with the stretch or location each one holds.
Instructions and changes
The engineer's instructions and changes made on site, logged with date and place.
Deliveries
Materials by vendor, with challans, slips and invoices, and where each load was unloaded.
Fuel
Diesel issued to every machine and vehicle.
Crews and commitments
Crews on site by stretch, and who promised what, by when.
Site teams change nothing. Velora joins each group as one more member.
What each team gets
Every team gets its part of the project.
Billing gets the month's quantities in a report, contract triggers reach whoever you choose, project heads see every front today, and leadership sees every project. Nobody has to ask site for an update.
This month's quantities, ready for the bill.
Work done is matched to your BOQ or work scope and totalled for the month. Each total opens into the chainage or locations, dates, photos and documents behind it, and missing documents are followed up on WhatsApp once you switch follow-ups on. Velora tracks quantities; your team adds rates and finalises the bill.
See Billing IntelligenceThe contract triggers that are easy to miss.
Not just EOT and LD. ROW and permissions, but also an instruction that changes the work, extra work off the drawings, or a delay caused by another party: each is logged with its place and the date it was first posted, matched to the clause it may trigger, and whoever you choose is alerted the same day, whether that's site, project controls or your contracts specialist, then reminded before the notice window closes. Your team decides what goes to the client.
See Contract IntelligenceEvery front, every day, without the calls.
Progress by chainage or location, the hindrances holding each stretch, deliveries by vendor and fuel by machine, from the groups your teams already post in. The DPR and weekly report are drafted from the same record, ready to review.
See Field IntelligenceEvery project in one view.
For the MD or project controls head running projects across sectors: the blockers that have waited longest for a decision, by front, and, where Billing is on, which quantities are still waiting on proof.
See Portfolio IntelligenceGetting started
What we'd need to start a pilot.
A pilot runs on one project and its live site groups. Your site teams don't change how they post.
A spare WhatsApp number
Linked to Velora and added to your site groups as one more member. No personal chats are connected.
Your site groups
The groups where progress, deliveries, fuel and hindrances are posted today.
Your scope
The BOQ or work scope, and the project's chainage limits or locations. Loaded once.
A sample chat export lets us test on your own messages before going live.
See it on your own project.
Talk to us about your project and we'll set up a pilot against its live WhatsApp groups and your BOQ or work scope.
Frequently Asked Questions
Common questions from infrastructure project heads and billing engineers.
Road construction and maintenance, water supply and pipelines, transmission lines, and rail and metro works, wherever work is paid on measured quantities against a BOQ or work scope and site teams report on WhatsApp.
No. Each project is set up with the way its site refers to place: chainage and side on a road or pipeline, tower locations on a line, km and line on a railway. Updates are filed against those.
Yes. Scope is loaded from the document that holds it, an item-rate BOQ or an EPC work scope, and work done is matched to its lines and totalled for the month. Velora tracks quantities; your billing team adds rates and finalises the bill.
Yes. Velora reads text, voice notes and photos in the languages your teams use, including photos of challans, test sheets and letters, and keeps each original message with the record it created.
No. Velora joins the groups your teams already use as one more member and reads what they post today. There is no new app and no form to fill.
We run a discounted pilot for the first three months on one project: the full product, with no long-term commitment.