What slips at month-end
Hundreds of locations. Each at its own stage.
A line runs foundations, erection and stringing at once, across sections kilometres apart, each reporting in its own group. Nothing is totalled until month-end, so small things slip: diesel nobody totals by machine, foundation changes nobody put on record, loads nobody can trace.
Fuel
Cranes, stringing machines and DG sets. One diesel total.
Diesel goes to cranes and excavators at the locations, the stringing machines on each pull, the DG sets at camp and the vehicles moving gangs and material between them. It's posted as a day's total, if at all.
By month-end nobody can say which machine used what, so the fuel bill is paid as it comes and one running high stays hidden.
Change of scope
Foundation type changed on site. Billed at the old type.
The soil at the location turned out wet, so the site cast a heavier foundation on the engineer's word. The post said so; nothing else did.
At the bill the location goes in under the type in the schedule, and the extra concrete and steel are never claimed.
Hindrances
ROW held a stretch for weeks. The record is a scroll.
Site posted it each time the crew was turned back: crop standing, compensation not paid, tree cutting not approved. Nobody logged when each location was first held.
When time is argued, the record is photos across groups, and the notice window has long closed.
Material cost
Tower steel at the yard. Members short at the location.
Tower parts, cement and conductor drums arrive from several suppliers, each load with a challan, and move from the yard to the locations.
When an erection gang reaches a location to find members missing, nobody can say which load was short or where it went.
What Velora picks up
What your site groups already carry, in line terms.
Velora reads text, voice notes and photos in the groups your teams use today, and files each update by section and tower location.
Foundations
Excavation and concreting by location and leg, with quantities and photos.
Erection
Towers erected by location and type, counted when complete.
Stringing
Kilometres strung by section, with the locations it runs between.
Hindrances
ROW, crop compensation, tree cutting and crossings, with the locations each one holds.
Scope changes
Foundation or tower type changes, logged with the location and the instruction.
Deliveries
Tower parts, cement, steel, conductor drums and insulators by vendor, with challans.
Fuel
Diesel issued to cranes, excavators, stringing machines, DG sets and vehicles.
Quality
Pour cards, cube tests and tower checks before stringing, when they are posted.
Site teams change nothing. Velora joins each group as one more member.
What each team gets
Every team gets its part of the line.
Billing gets the month's quantities in a report, contract triggers reach whoever you choose, project heads see every location 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 price schedule and totalled for the month: cubic metres excavated and concreted, towers erected, kilometres strung. Each total opens into the locations, dates, photos and pour cards 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. A ROW hold-up or a crossing waiting on a shutdown, but also a foundation type changed after soil classification, a tower type changed after check survey, or an element ready but waiting on another party's works: each is logged with its location 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 location, every day, without the calls.
Foundations, erection and stringing by section and location, the hindrances holding each one, 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 several lines: the blockers that have waited longest for a decision, by section, 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.
Foundation quantities, towers erected and kilometres strung are each billed against their item. Velora keeps every total traced to its locations.
Totals per scope line
Excavation and concrete in cubic metres, towers erected and kilometres strung, each matched to its BOQ or price schedule item.
A location on every line
Every quantity keeps its location and section, so your engineer can trace it to the tower.
Proof that opens up
Every total lists its locations, dates, photos and pour cards, before it goes to the client.
Changes kept on record
A foundation or tower type changed on site stays on record with its instruction, so it can reach the bill at the right type.
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 section, stores, plant and QC groups where updates are posted today.
Your scope
The BOQ or price schedule, and the tower schedule with its locations and sections. 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 line and we'll set up a pilot against its live WhatsApp groups and your BOQ or price schedule.
Frequently Asked Questions
Common questions from transmission project heads and billing engineers.
Scope is loaded from your BOQ or price schedule, with the tower schedule's locations and sections set up once. Work posted at a location is matched to its item and totalled for the month. Comparing tower parts against the schedule's bill of materials needs a short setup at the start. Billing by stage for each location is something the team is still working on.
From the location in the post, like "Loc 148", matched against the locations set up for the line. A post with no location, or one that isn't on the line, is kept for your team to place, not guessed.
Yes. Velora reads text, voice notes and photos in the languages your teams use, including photos of challans, pour cards and soil test reports, and keeps each original message with the record it created.
Each delivery is recorded by vendor, material and quantity, with its challan and the yard or location it went to, and each tower erected by location and type. A deliveries report by vendor lets your team validate each supplier's bill. Velora doesn't match deliveries to purchase orders or invoices itself.
No. EOT and LD are the clauses every team watches. Velora also checks routine updates against the rest of your contract: a foundation or tower type changed on site, an instruction from the engineer, an element held up by someone else's works, 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. Contract Intelligence is in early access.
Yes. On water mains and road works, progress posted by chainage is totalled per BOQ item or work scope line, with the photos and documents behind each total.
We run a discounted pilot for the first three months on one project: the full product, with no long-term commitment.