Skip to main content

Stop piecing the pipeline together at month-end. Bill every metre, claim every hold-up.

Trenching, laying, testing and restoration run on different stretches at once, each posted in its own group, with house connections and pipe deliveries in between, so the month's quantities wait on reports pieced together at month-end. Velora reads every group and files each update by chainage. No new app for site teams.

BillEvery metre laid on this month's bill. Laid, tested and restored lengths totalled per BOQ item or work scope line, with the chainage, photos and test sheets behind them.
ClaimContract triggers caught the same day. A road-cutting permission still pending, a crossing not cleared, the line shifted on the engineer's word: each matched to the clause it may trigger while there's time to raise it.
PayEvery pipe and litre accounted for. A deliveries report by vendor and pipe size to validate their bills, and diesel tracked by machine and vehicle.

30–45 daysAfter third-party inspection, under the Jal Jeevan Mission guidelines, a running bill is due for payment. The inspection checks your work against the bill, so the bill waits on your records.

Stretch A · Site Updates
Ch 4+000 – 8+000 · Prakash, Velora +7
Prakash
DI 300 mm laying done Ch 6+120 to 6+380, 22 pipes jointed
3 photos
4:40 PM
Stretch B · Site Updates
Ch 8+000 – 12+000 · Naveen, Velora +5
Naveen
Line shifted 4 m RHS at Ch 8+460 to 8+500 as AE asked, sewer line in the way
2 photos
5:05 PM
Stores · Pipes
Ravi, Velora +3
Ravi
DI K7 300 mm pipes received, 48 nos, Shree Ductile
Challan, inspection release note
5:30 PM
+5 More Groups
Velora
This month · Trunk Main Package 2Updated 5:31 PM
DI 300 mm laying1,800 m
3 records this month, each with its chainage and photos
Ch 4+200 – 5+020Stretch A · LHS9 Oct820 m
Ch 5+400 – 6+120Stretch A · LHS21 Oct720 m
Ch 6+120 – 6+380Stretch A · LHSToday260 m
BillOn this month's bill
Line shifted off the drawing40 m
Ch 8+460 – 8+500 · Stretch B · engineer's verbal instruction, posted today
ClaimWritten confirmation tracked
DI K7 300 mm pipes48 nos
Shree Ductile · challan and inspection release kept
PayIn the deliveries report by vendor
Stretch A · QC
QC Team, Velora +3
Inspection Record Pending
DI 300 mm laying Ch 6+120 – 6+380 done today. Please share the third-party inspection record for this stretch before the bill cut-off.
4:44 PM ✓✓
Karthik · Project Head
Contract alert
Potential Change of Scope
Potential change of scope: line shifted 4 m at Ch 8+460 – 8+500 on the engineer's verbal instruction, off the drawing. Written confirmation tracked from today; keep the dated photos of the shifted line.
5:08 PM ✓✓
Sent on WhatsApp, the day it's detected

What slips at month-end

Four jobs on every stretch. Each one billed on its own.

A water main is dug, laid, tested and restored stretch by stretch, with house connections and deliveries in between, each posted in its own group. Each is its own BOQ item, so small things slip: work done that missed the bill, sections without their inspection records, loads nobody can trace.

Missed in the bill

House connections made all month. Not all reach the bill.

"HSC done, 14 nos, Ward 6": a photo per connection, posted between laying updates, a few a day across every ward or village.

At month-end someone counts them back from scroll-back, and some posts are missed. The connections were made; the bill never saw them.

Inspection records

Section tested. The inspection record never followed.

The hydraulic test held and the gauge photo went into a group. The signed test sheet and the third-party inspection record were never asked for.

When the running bill goes up, the inspection checks the work against what is claimed, and a section without its records waits for the next bill.

Measurement missing

Road restored over the trench. The area never posted.

"Restoration done Ch 5+400 to 6+120": the length is there, the width is not. Road restoration is paid by area.

Without the figure the item can't go on this bill, and once traffic is back on the road, nobody goes back to measure it.

Material cost

Pipes strung along the route. The challans are scattered.

Pipes arrive by the truckload from more than one supplier, each load with a challan and an inspection release, and are strung along the route ahead of laying.

At month-end, checking each supplier's bill means finding challans spread across groups and matching them against lengths laid on different stretches.

None of it is a big miss. Along a whole pipeline, it adds up.

What Velora picks up

What your site groups already carry, in pipeline terms.

Velora reads text, voice notes and photos in the groups your teams use today, and files each update by stretch and chainage.

  • Laying by chainage

    Pipe laid and jointed, by size and stretch, with the span and photos.

  • Trenching and restoration

    Excavation, backfill and road restoration, with the length or area posted.

  • Tests

    Hydraulic tests by section, with the gauge photo and test sheet when they are posted.

  • House connections

    Service connections counted by ward or village, a photo each.

  • Structures

    Thrust blocks, valve chambers and crossings, counted when complete.

  • Deliveries

    Pipes, fittings, sand and cement by vendor and size, with challans and inspection release notes.

  • Fuel

    Diesel issued to excavators, tippers and dewatering pumps.

  • Instructions

    Site visits, instructions and inspections by the client's engineer or the inspection agency, logged with date and stretch.

Site teams change nothing. Velora joins each group as one more member.

What each team gets

Every team gets its part of the scheme.

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.

Billing Intelligence

This month's quantities, ready for the bill.

Work done is matched to your BOQ or work scope and totalled for the month: metres laid and tested, square metres restored, connections made. Each total opens into the chainage, photos, test sheets and inspection records 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 Intelligence
Contract IntelligenceEarly access

The contract triggers that are easy to miss.

Not just EOT and LD. A road-cutting permission still pending or a crossing not cleared, but also the engineer's verbal instruction to shift the line, extra work off 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 Intelligence
Field Intelligence

Every stretch, every day, without the calls.

Laying, testing and restoration by chainage, house connections counted, deliveries by vendor and fuel by machine, from the groups your teams already post in. An excavator down or a permission pending shows up the same day. The DPR and weekly report are drafted from the same record, ready to review.

See Field Intelligence
Portfolio Intelligence

Every project in one view.

For the MD or project controls head running several schemes: 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 Intelligence

Worked example

The month's bill, built from the site record.

Laying, testing and restoration are billed as separate items. Velora keeps each total and its proof together, ready for the inspection.

  • Totals per scope line

    Metres laid, metres tested, square metres restored and connections made, each matched to its BOQ item or work scope line.

  • Each item on its own line

    Laying, testing and restoration of the same stretch are separate items, so each is counted on its own, never added together.

  • Proof that opens up

    Every total lists its stretches, dates and photos, so your engineer can check it before the inspection.

  • Documents per line

    Test sheets and third-party inspection records, received or still missing, before the bill goes up.

October bill · Trunk Main Package 2
Prepared from the site record
For your billing engineer to review
Scope lineThis monthProofDocuments
DI 300 mm laying and jointing1,800 m3 stretches · 41 photosDocuments: All in
Ch 4+200 – 5+020 LHS820 m9 Oct
Ch 5+400 – 6+120 LHS720 m21 Oct
Ch 6+120 – 6+380 LHS260 m31 Oct
Hydraulic testing700 m1 section · test sheet · gauge photoDocuments: Inspection record missing
Road restoration—720 m restored, width not postedDocuments: Area not posted
House service connections146 nos146 photosDocuments: All in
Thrust blocks12 nos12 records · photosDocuments: All in
Velora tracks quantities. Your team adds rates and finalises the bill.

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.

  1. A spare WhatsApp number

    Linked to Velora and added to your site groups as one more member. No personal chats are connected.

  2. Your site groups

    The stretch, testing, stores and plant groups where updates are posted today.

  3. Your scope

    The BOQ or work scope, and the scheme'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 scheme and we'll set up a pilot against its live WhatsApp groups and your BOQ or work scope.

Frequently Asked Questions

Common questions from water scheme project heads and billing engineers.

Yes, where work is paid on measured quantities against a BOQ or work scope. Laying, testing, restoration and connections are matched to their items and totalled for the running bill, with the test sheets and inspection records behind them. Velora tracks quantities; your billing team adds rates and finalises the bill.

A post like "DI 300 mm laying done Ch 6+120 to 6+380" is read as 260 m of that pipe size, matched to its scope line and counted, marked as calculated from site updates so your billing engineer can check or correct it. Laying, testing and restoration on the same stretch go to their own items. Anything unclear is held for review, not guessed.

Yes. Velora reads text, voice notes and photos in the languages your teams use, including photos of challans, test sheets and gauge readings, and keeps each original message with the record it created.

It keeps what the inspection checks in one place: each stretch's photos, test sheets and inspection records, against the quantity claimed. Velora doesn't carry out the inspection or certify the work.

Each delivery is recorded by vendor, size and quantity, with its challan and inspection release kept on the record, and each length laid by size and chainage. A deliveries report by vendor lets your team validate each supplier's bill. 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 off the drawings, a late drawing or a pending permission, 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 road works, progress posted by chainage is totalled per BOQ item or work scope line, and on maintenance contracts every repair is measured from its caption.

Road construction →

We run a discounted pilot for the first three months on one project: the full product, with no long-term commitment.