Skip to main content

Stop piecing the pipeline together at month-end. Value every metre, record every delay.

Trenching, laying, testing and reinstatement run on different stretches at once, each posted in its own group, with service transfers 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 and location. No new app for site teams.

ValueEvery metre laid in this month's valuation. Laid, tested and reinstated lengths totalled per BoQ item or activity schedule line, with the location, photos and test records behind them.
ClaimContract triggers caught the same day. A permit refused or its conditions changed by the highway authority, access to a site not given, the route moved at the client's request: each matched to the clause it may trigger while there's time to notify it.
PayEvery posted pipe and litre on record. A deliveries report by supplier and pipe size to check their invoices, and diesel tracked by machine and vehicle.
Stretch A · Site Updates
Ch 4+000 – 8+000 · Craig, Velora +7
Craig
300 mm DI main laid Ch 6+120 to 6+380, 44 pipes jointed
3 photos
4:40 PM
Stretch B · Site Updates
Ch 8+000 – 12+000 · Bogdan, Velora +5
Bogdan
Route moved 4 m north at Ch 8+460 to 8+500 as the client's team asked, sewer in the way
2 photos
5:05 PM
Stores · Pipes
Dave, Velora +3
Dave
300 mm DI pipes received, 48 no., Pennine Pipe Supply
Delivery note
5:30 PM
+5 More Groups
Velora
This month · Trunk Main Package 2Updated 5:31 PM
300 mm DI main laying1,800 m
3 records this month, each with its chainage and photos
Ch 4+200 – 5+020Stretch A9 Oct820 m
Ch 5+400 – 6+120Stretch A21 Oct720 m
Ch 6+120 – 6+380Stretch AToday260 m
ValueIn this month's valuation
Route moved off the drawing40 m
Ch 8+460 – 8+500 · Stretch B · verbal request from the client's team, posted today
ClaimWritten instruction tracked
300 mm DI pipes48 no.
Pennine Pipe Supply · delivery note kept
PayIn the deliveries report by supplier
Stretch A · QC
QC Team, Velora +3
Inspection Record Pending
300 mm DI laying Ch 6+120 – 6+380 done today. Please share the signed inspection record for this stretch before the valuation date.
4:44 PM ✓✓
Rachel · Project Director
Contract alert
Potential Compensation Event
Potential compensation event: route moved 4 m at Ch 8+460 – 8+500 at a verbal request from the client's team, off the drawing. Ask for the Project Manager's instruction in writing; keep the dated photos of the moved route.
5:08 PM ✓✓
Sent on WhatsApp, the day it's detected

What slips at month-end

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

A water main is laid, tested and reinstated stretch by stretch, with service transfers and deliveries in between, each posted in its own group. Laying, testing and reinstatement are often separate items, so small things slip: work done that missed the valuation, sections without their test records, loads nobody can trace.

Missed in the valuation

Service transfers made all month. Not all reach the valuation.

"Service transfers done, 14 no., Elm Road": a photo per transfer, posted between laying updates, a few a day across every street.

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

Test records

Section tested. The test certificate never followed.

The pressure test held and the gauge photo went into a group. The signed test certificate was never asked for.

When the valuation is assessed, the client checks the work against what is claimed, and a section without its records waits for the next one.

Measurement missing

Reinstatement done over the trench. The area never posted.

"Reinstatement done Ch 5+400 to 6+120": the length is there, the width is not. Where reinstatement is paid by area, the width matters.

Without the figure the item can't go in this valuation, and once the road is open again, nobody goes back to measure it.

Material cost

Pipes strung along the route. The delivery notes are scattered.

Pipes arrive by the lorry load from more than one supplier, each load with a delivery note, and are strung along the route ahead of laying.

At month-end, checking each supplier's invoice means finding delivery notes 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 length and photos.

  • Trenching and reinstatement

    Excavation, backfill and reinstatement, with the length or area posted.

  • Tests

    Pressure tests by section, and disinfection and bacteriological sample results, with the gauge photo and certificate when they are posted.

  • Service transfers and new connections

    Counted by street, a photo each.

  • Structures

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

  • Deliveries

    Pipes, fittings, aggregate and concrete by supplier and size, with delivery notes.

  • Fuel

    Diesel issued to excavators, tippers and dewatering pumps.

  • Instructions

    Site visits, instructions and inspections by the client's team, 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.

Your QS gets the month's quantities in a report, contract triggers reach whoever you choose, project directors 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 valuation.

Work done is matched to your BoQ or activity schedule and totalled for the month: metres laid and tested, square metres reinstated, service transfers and connections made. Each total opens into the chainage, photos, test certificates and inspection records behind it, and missing documents are followed up on WhatsApp once you switch follow-ups on. Velora tracks quantities; your QS applies rates and finalises the application.

See Billing Intelligence
Contract IntelligenceEarly access

The contract triggers that are easy to miss.

Not just extensions of time and delay damages. A permit refused or its conditions changed, or access not given, but also a crossing held by another party's works or design information that came late: each is logged with its chainage and the date it was first posted, matched to the clause it may trigger, such as a compensation event under NEC4, and whoever you choose is alerted the same day, whether that's site, your commercial team or your contracts manager, then reminded before the notice period runs out. Your team decides what to notify.

See Contract Intelligence
Field Intelligence

Every stretch, every day, without the calls.

Laying, testing and reinstatement by chainage, service transfers counted, deliveries by supplier and fuel by machine, from the groups your teams already post in. An excavator down or a permit pending shows up the same day. The daily and weekly reports are drafted from the same record, ready to review.

See Field Intelligence
Portfolio Intelligence

Every project in one view.

For the managing director or commercial director 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 valuation, built from the site record.

Laying, testing and reinstatement are often valued as separate items. Velora keeps each total and its proof together, ready for the assessment.

  • Totals per scope line

    Metres laid, metres tested, square metres reinstated and connections made, each matched to its BoQ item or activity schedule line.

  • Each item on its own line

    Where laying, testing and reinstatement of the same stretch are separate items, each is counted on its own, never added together.

  • Proof that opens up

    Every total lists its stretches, dates and photos, so your QS can check it before the application goes in.

  • Documents per line

    Test certificates and inspection records, received or still missing, before the valuation date.

October valuation · Trunk Main Package 2
Prepared from the site record
For your QS to review
Scope lineThis monthProofDocuments
300 mm DI main laying and jointing1,800 m3 stretches · 41 photosDocuments: All in
Ch 4+200 – 5+020820 m9 Oct
Ch 5+400 – 6+120720 m21 Oct
Ch 6+120 – 6+380260 m31 Oct
Pressure testing700 m1 section · test certificate · gauge photoDocuments: Inspection record missing
Permanent reinstatement—720 m reinstated, width not postedDocuments: Area not posted
Service transfers146 no.146 photosDocuments: All in
Thrust blocks12 no.12 records · photosDocuments: All in
Velora tracks quantities. Your QS applies rates and finalises the application.

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 activity schedule, 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 activity schedule.

Frequently Asked Questions

Common questions from water project directors and QSs.

Yes. On Option C capital schemes, where you're paid Defined Cost, Velora gives you the progress and compensation event record behind the activity schedule and target, not the payment itself. Where work is paid on rates, such as mains renewal and repair on a schedule of rates or price list, laying, testing, reinstatement and connections are matched to their items and totalled for the valuation, with the test certificates and inspection records behind them. Velora tracks quantities; your QS applies rates and finalises the application.

A post like "300 mm DI laid 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 QS can check or correct it. Laying, testing and reinstatement 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 delivery notes, test certificates and gauge readings, and keeps each original message with the record it created.

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

Each delivery is recorded by supplier, size and quantity, with its delivery note kept on the record, and each length laid by size and chainage. A deliveries report by supplier lets your team check each supplier's invoice. Velora doesn't match deliveries to purchase orders or invoices itself.

No. Those are the clauses every team watches. Velora also checks routine updates against the rest of your contract: late design information, a permit refused, a crossing held by another party's works, each matched to the clause it may trigger, such as a compensation event under NEC4, with the deadline and the record behind it. Whoever you choose, whether site, your commercial team or your contracts manager, 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 activity schedule line, and on highways maintenance term 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.