What slips at month-end
Work done in block windows. Measured weeks later.
A rail section runs earthwork, bridges, track and OHE at once, much of it inside traffic and power blocks, each front reporting in its own group. The Railway's engineer measures later, so small things slip: work done that never reached the measurement, cancelled blocks nobody put on record, loads nobody can trace.
Missed in the measurement
Bonds fitted in every block. Some never reach the measurement.
"Rail bonds 18 nos fixed Km 119/10 to 119/16 UP line": a few dozen rail and structure bonds a block, on both lines, one post among hundreds.
When the joint measurement comes round, someone counts them back from scroll-back, and some are missed. The bonds are fitted; the bill never saw them.
Blocks
Block cancelled on the night. The time is never claimed.
The crew and crane were in position; control cancelled the block. Site posted it, then moved on to the next night.
The delay is the Railway's, but notice has to go within the contract's window, and weeks later nobody can list which blocks were lost.
Change of scope
Bridge drawing revised. The extra work is measured at the old size.
The box for a road under-bridge was widened on a revised drawing, mid-construction. The site built it, and the post said so.
At the measurement the item goes in at the original size, and the extra concrete is never claimed.
Material cost
Ballast tipped at three depots. The quarry bills for all of it.
Ballast and blanketing material arrive by the tipper from more than one quarry, each load with a challan, tipped at depots along the section.
At month-end, checking each quarry's bill means finding challans spread across groups and depots.
What Velora picks up
What your site groups already carry, in railway terms.
Velora reads text, voice notes and photos in the groups your teams use today, and files each update by section, km and line.
Earthwork and blanketing
Formation, blanketing and side slopes by km and line, with quantities and photos.
Bridges
Minor bridges and road under-bridges, stage by stage, counted when complete.
Track
Track linked, ballast spread and tamping, by km and line.
OHE
Mast foundations, masts erected and wiring, by location.
Blocks
Traffic and power blocks given, cancelled or cut short, with the work each one held.
Deliveries
Ballast, blanketing material, rails, sleepers and cement by vendor and depot, with challans.
Fuel
Diesel issued to excavators, rollers, tampers and road vehicles.
Instructions
Site visits, instructions and revised drawings reported from the Railway's engineer, logged with date and km.
Site teams change nothing. Velora joins each group as one more member.
What each team gets
Every team gets its part of the section.
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 measurement.
Work done is matched to your BOQ or schedule of items and totalled for the month: cubic metres of earthwork and blanketing, track kilometres linked, masts erected. Each total opens into the km, dates, photos and inspection records behind it, so your team goes into the joint measurement with its own record. 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 traffic block cancelled, a power block cut short or another contractor in the way, but also a revised drawing that adds work or a modification on the engineer's word: each is logged with its km 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 block, without the calls.
Earthwork, bridges, track and OHE by km and line, the blocks given and lost, 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 sections: 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 IntelligenceWorked example
The month's work, ready for the measurement.
The Railway's engineer records the measurement. Velora gives your team its own record of every item, traced to the km and line, before that happens.
Totals per item
Cubic metres of earthwork and blanketing, track kilometres and masts erected, each matched to its item in the schedule.
Ready for the joint measurement
Every total lists its km, dates and photos, so the record is in hand when the Railway's engineer measures.
Documents per line
Joint inspection records and test certificates, received or still missing, before the measurement.
Changes kept on record
Work added by a revised drawing or an instruction stays on record, so it can reach the bill at the right size.
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, blocks, bridges, stores and plant groups where updates are posted today.
Your scope
The BOQ or schedule of items, and the section's km limits and lines. 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 section and we'll set up a pilot against its live WhatsApp groups and your BOQ or schedule of items.
Frequently Asked Questions
Common questions from rail project heads and billing engineers.
Yes. Velora doesn't replace the Railway's measurement. It keeps your own record of work done, by km, line and date, with photos and documents, so your team can check it against the e-MB and raise anything missing.
From the km and line in the post, like "Km 118.200 to 118.650, UP line", matched to the stretches set up for the section. A quantity stated in the post is used as posted. A post that can't be placed 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, block registers and inspection records, and keeps each original message with the record it created.
Every block posted as given, cancelled or cut short is logged with its date, km and the work it held, so the record is ready when a delay is argued. Velora flags the ones that may trigger a clause in your contract; your team decides what to raise. Contract Intelligence is in early access.
No. EOT and LD are the clauses every team watches. Velora also checks routine updates against the rest of your contract: a modification that adds work, a delay by another contractor or by the Railway's staff, a revised drawing, 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 metro civil works, piling, piers and spans are captured by location the same way, and matched to your BOQ or work scope.
Yes. On road, water and transmission line works, progress posted by chainage or location is totalled per scope item, 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.