Skip to main content

Stop compiling tower-by-tower progress at month-end. Value what's built, record every change.

Hundreds of towers, each at its own stage of foundation, erection or stringing, reporting through site groups every day, so each tower's stage waits on reports pieced together at month-end. Velora reads every group and files each update by section and tower. No new app for site teams.

ValueEvery tower's work in this month's valuation. Excavation, concrete, towers erected and kilometres strung, totalled per BoQ or activity schedule item, with the tower and photos behind each one.
ClaimContract triggers caught the same day. Landowner access not given, ground at a tower that differs from the Site Information, an outage cancelled or moved by the system operator: each matched to the clause it may trigger while there's time to notify it.
PayEvery posted tonne and litre on record. Tower steelwork, concrete and conductor by supplier and tower, and diesel tracked by crane, machine and vehicle.
Section 2 · Foundations
T120 – T175 · Gareth, Velora +8
Gareth
T148 foundation concreted, all 4 legs, 38.4 m³
4 photos
4:35 PM
Section 3 · Site Updates
T176 – T230 · Lukasz, Velora +6
Lukasz
T196 trial pit shows running sand and high groundwater, pad won't work, designer going to piled
3 photos, trial pit log
5:02 PM
Stores · Laydown Yard
Steve, Velora +3
Steve
Tower steelwork for T150 to T152 received, 2 lorries, 31.2 t
Delivery notes
5:28 PM
+6 More Groups
Velora
This month · Sections 2 – 3Updated 5:29 PM
Foundation concrete612 m³
16 towers this month, each with its photos
T141Section 2 · 4 legs9 Oct37.6 m³
T144Section 2 · 4 legs18 Oct41.2 m³
T148Section 2 · 4 legsToday38.4 m³
ValueIn this month's valuation
Foundation type changed · T196Pad → piled
Section 3 · ground differs from the Site Information, posted today
ClaimNotice deadline tracked
Tower steelwork · T150 – T15231.2 t
Kestrel Steel Fabrications · 2 loads · delivery notes kept
PayIn the deliveries report by supplier
Section 2 · QC
QC Team, Velora +3
Pour Record Pending
T148 foundation concreted today. Please share the signed pour record for this tower before the valuation date.
4:39 PM ✓✓
Helen · Project Director
Contract alert
Potential Compensation Event
Potential compensation event: ground at T196 differs from the Site Information (trial pit log); foundation changing from pad to piled. May be physical conditions under 60.1(12): notify within eight weeks of becoming aware (61.3). Keep the trial pit log and dated photos.
5:05 PM ✓✓
Sent on WhatsApp, the day it's detected

What slips at month-end

Hundreds of towers. Each at its own stage.

A line runs foundations, erection and stringing at once, across sections miles 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 generators. One diesel total.

Diesel goes to cranes and excavators at the towers, the stringing machines on each pull, the generators at the compound 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 invoice is paid as it comes and one running high stays hidden.

Ground conditions

Pad became piled at one tower. Valued at the old type.

A trial pit at the tower showed running sand and high groundwater, so the designer changed the pad to a piled foundation. The post said so; nothing else did.

If the ground differs from the Site Information, it may be a compensation event for physical conditions. Unrecorded, the tower is valued at the old type and the change is never notified.

Access

Landowner access held a stretch for weeks. The record is a scroll.

Site posted it each time the gang was turned away: access not agreed, crops still standing, a gate locked. Nobody logged when each tower was first held.

When time is argued, the record is photos across groups, and the notice period has long run out.

Material cost

Tower steelwork at the yard. Members short at the tower.

Tower steelwork, concrete and conductor drums arrive from several suppliers, each load with a delivery note, and move from the laydown yard to the towers.

When an erection gang reaches a tower to find members missing, nobody can say which load was short or where it went.

None of it is a big miss. Across hundreds of towers, it adds up.

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.

  • Foundations

    Excavation and concreting by tower and leg, with quantities and photos.

  • Erection

    Towers erected by number and type, counted when complete.

  • Stringing

    Kilometres strung by section, with the towers it runs between.

  • Access and outages

    Landowner access, outages and crossings, with the towers each one holds.

  • Changes

    Foundation or tower type changes, logged with the tower and the trial pit log or instruction.

  • Deliveries

    Tower steelwork, concrete, reinforcement, conductor drums and insulators by supplier, with delivery notes.

  • Fuel

    Diesel issued to cranes, excavators, stringing machines, generators and vehicles.

  • Quality

    Pour records, 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.

Your QS gets the month's quantities in a report, contract triggers reach whoever you choose, project directors see every tower 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: cubic metres excavated and concreted, towers erected, kilometres strung. Each total opens into the towers, dates, photos and pour 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. Landowner access not given or an outage cancelled or moved by the system operator, but also ground at a tower that differs from the Site Information, or work ready but waiting on another contractor's: each is logged with its tower 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 tower, every day, without the calls.

Foundations, erection and stringing by section and tower, the access issues holding each one, deliveries by supplier and fuel by machine, from the groups your teams already post in. 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 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 Intelligence

Worked example

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

Foundation quantities, towers erected and kilometres strung are each valued against their item. Velora keeps every total traced to its towers.

  • Totals per scope line

    Excavation and concrete in cubic metres, towers erected and kilometres strung, each matched to its BoQ or activity schedule item.

  • A tower on every line

    Every quantity keeps its tower and section, so your QS can trace it.

  • Proof that opens up

    Every total lists its towers, dates, photos and pour records, before the application goes in.

  • Changes kept on record

    A foundation or tower type changed on site stays on record with its trial pit log or instruction, so it can reach the valuation at the right type.

October valuation · Sections 2 – 3
Prepared from the site record
For your QS to review
Scope lineThis monthProofDocuments
Foundation excavation1,940 m³16 towers · photosDocuments: All in
Foundation concrete612 m³16 towers · 64 photosDocuments: Pour record missing for 2
T141 · Section 237.6 m³9 Oct
T144 · Section 241.2 m³18 Oct
T148 · Section 238.4 m³31 Oct
+13 more towers · 494.8 m³
Tower erection14 towers14 towers · by typeDocuments: All in
Stringing6.4 kmT120 – T141 · photosDocuments: All in
Foundation, T196Type changedPhysical conditions · trial pit logDocuments: Potential change
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 section, stores, plant and QC groups where updates are posted today.

  3. Your scope

    The BoQ or activity schedule, and the tower schedule with its towers 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 activity schedule.

Frequently Asked Questions

Common questions from overhead line project directors and QSs.

Overhead line work on National Grid ASTI and RIIO-T3 schemes, and DNO 132 kV and 33 kV lines: foundations, tower erection and stringing, filed by section and tower or pole number, wherever site teams report on WhatsApp.

Scope is loaded from your BoQ or activity schedule, with the tower schedule's towers and sections set up once. Work posted at a tower is matched to its item and totalled for the month. Comparing tower steelwork against the schedule's bill of materials needs a short setup at the start. Valuing by stage for each tower is something the team is still working on.

On a target contract you're paid Defined Cost, so Velora's quantities are your progress record against the activity schedule and target, and your compensation event record, not the payment itself.

From the tower number in the post, like "T148", matched against the towers set up for the line. A post with no tower, 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 delivery notes, pour records and ground investigation logs, and keeps each original message with the record it created.

Each delivery is recorded by supplier, material and quantity, with its delivery note and the yard or tower it went to, and each tower erected by number and type. 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: ground that differs from the Site Information, an outage cancelled, work held up by another contractor, 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 water mains and road works, progress posted by chainage is totalled per BoQ item or activity schedule line, with the photos and documents behind each total.

Water & pipelines →

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