What slips at month-end
Spread over kilometres. Lost between the groups.
A road package runs many fronts at once, kilometres apart, and each reports in its own group. Nothing is totalled until month-end, so small things slip: work done that missed the bill, vendor loads nobody can trace, hold-ups nobody put on record.
Missed in the bill
212 delineators fixed this month. 7 missed the bill.
"Delineators fixed 46+100 to 46+400 RHS, 18 nos": a few dozen at a time, on both fronts, one post among hundreds. At month-end someone counts them back from scroll-back, and some posts are missed.
The gap turns up after the bill is submitted: 7 delineators installed, waiting for next month's bill. The work was done; the bill never saw it.
Material cost
Every vendor bill gets paid. Not every load can be traced.
Aggregate, sand and earth come from several crushers and quarries all month, each load photographed in a group with its weighbridge slip and royalty papers.
At month-end, vendor bills are checked against loads nobody can find, so they get paid as billed. Where royalty papers can't be produced for the material used, the client can deduct the royalty from your bill.
Hindrances
A utility line held 600 m for five weeks. The record is a scroll.
Site posted it every few days: poles still standing, crew moved to another stretch. Nobody logged when it started or when it cleared.
Months later, when time is argued, the record is photos across three groups, and the notice window in the contract closed long ago.
Fuel
Forty machines and haul trucks. One diesel total.
Diesel goes to rollers, pavers and the plant, and to the tippers and dumpers hauling aggregate and earth. It's posted as a day's total, if at all.
By month-end nobody can say which machine or truck used what, so one running high stays hidden in the fuel bill.
What Velora picks up
What your site groups already carry, in road terms.
Velora reads text, voice notes and photos in the groups your teams use today, and files each update by package, chainage and side.
Progress by chainage
Layer or stage completed, with its span, side and photos.
Structures
Culverts and minor bridges, stage by stage, counted when complete.
Deliveries
Aggregate, sand, bitumen, cement and steel by vendor, with weighbridge slips and royalty papers.
Fuel
Diesel issued to each roller, paver and plant, and to every tipper and dumper on haul.
Hindrances
ROW, utility shifting, tree felling and encroachments, with the stretch each one holds.
Instructions
Site visits and instructions from the client's engineer, logged with date and stretch.
Manpower
Crews on site, by stretch and trade.
Commitments
Who promised what, by when: a tanker, a survey, a handover.
Site teams change nothing. Velora joins each group as one more member.
What each team gets
Every team gets its part of the package.
Billing gets the month's quantities in a report, contract triggers reach whoever you choose, project heads see every stretch 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 spans, dates, photos, level surveys and lab results 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 not handed over or a utility still in the way, but also the engineer's verbal instruction to extend a drain, extra work outside the drawings or a drawing that came late: each is logged with its chainage 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 stretch, every day, without the calls.
Progress by chainage and side, the hindrances holding each stretch, deliveries by vendor and fuel by machine and haul vehicle, 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 several projects: the blockers that have waited longest for a decision, by stretch, and, where Billing is on, which quantities are still waiting on proof.
See Portfolio IntelligenceWorked example
The month's bill, built from the site record.
Road work is billed as a total for each BOQ item or work scope line. Velora keeps the total and its proof together.
Totals per scope line
Completed length, area or count for each BOQ item or work scope line, from the spans your site posted.
Completed stretches only
Work in progress is tracked, but a staged item counts toward the bill only when its final stage is posted.
Proof that opens up
Every total lists its spans, dates and photos, so your engineer can check it before it goes to the client.
Documents per line
Level surveys, lab results and checklists, received or still missing, before the bill goes out.
Illustrative figures
Getting 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. 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 road project heads and billing engineers.
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, with chainage as the proof behind each total. Billing by stage payment or HAM milestone is something the team is still working on; until then, the completed lengths behind each stage are tracked and ready for your billing team. Velora tracks quantities; your team adds rates and finalises the bill.
A post like "DBM done 42+300 to 42+850 LHS" is read as a 550 m span on that layer and side, matched to its scope line and counted, marked as calculated from site updates so your billing engineer can check or correct it. Where an item is built in stages, such as a lined drain, only its final stage counts toward the completed length. A span that can't be read cleanly is held for review, not guessed.
Yes. Velora reads text, voice notes and photos in the languages your teams use, including photos of challans and weighbridge slips, and keeps each original message with the record it created.
Each delivery is recorded by vendor, material and quantity, with its weighbridge slip and royalty papers kept on the record. A deliveries report by vendor, daily, weekly or monthly, lets your team validate each vendor's bill, and royalty proof is to hand when the client asks. Velora doesn't match deliveries to purchase orders or invoices itself.
Guide: how to reconcile material deliveries on road and linear projects →
No. EOT and LD are the clauses every team watches. Velora also checks routine updates against the rest of your contract: an instruction given on site, extra work outside the drawings, a late drawing or a repeat repair, each matched to the clause it may trigger, with the deadline and the record behind it. Whoever you choose, whether site, project controls or your contracts specialist, is alerted the same day. Velora doesn't send notices; your team decides what to send. Contract Intelligence is in early access.
Yes. Patch repairs, road furniture and painting reported with chainage are matched to your maintenance BOQ or work scope the same way, with the photo behind each repair, and work outside the BOQ stays on record.
We run a discounted pilot for the first three months on one project: the full product, with no long-term commitment.