What slips at month-end
Groundworks, steel, pipework, equipment. All at once, area by area.
An industrial project runs every discipline at once, across areas and buildings, each subcontractor reporting in its own group. Nothing is totalled until the valuation, so small things slip: work done that missed the valuation, records nobody filed, client-side delays nobody put on record, free-issue nobody reconciled.
Missed in the valuation
1,180 pipe supports fixed this month. 1,120 reached the valuation.
"Area 200 supports fixed, 64 no.": a few dozen at a time, from the pipework crew, one post among hundreds.
At month-end someone counts them back by scrolling, and a few batches are missed. The supports are in; the valuation never saw them, so they wait for next month.
Test records
Line pressure-tested. The test pack never reached the valuation.
Each line is pressure-tested before insulation and its welds radiographed, and each test certificate is photographed into whichever group is nearest.
Where a line is valued only with its test pack, your QS looks for each one across groups at valuation time. Lines without one wait for next month.
Client-side delays
Client-supplied pipe arrived three weeks late. The record is a scroll.
The pipework crew posted it each day they waited for free-issue pipe. Nobody logged when it started or which area it held.
When time and cost are argued, the record is photos across groups, and the notice that was due forthwith under JCT, or within eight weeks under NEC4, went late.
Free-issue
Free-issue pipe and fittings from the client's store. Nobody knows what went where.
Pipe, fittings and valves are drawn from the client's store and issued to areas as the work needs them.
At the end the client asks for a free-issue reconciliation, and charges the shortfall nobody can explain.
What Velora picks up
What your site groups already carry, in plant terms.
Velora reads text, voice notes and photos in the groups your teams and subcontractors use today, and files each update by area, building and grid.
Progress by area
Groundworks, steel erection, cladding, pipework and equipment by area, building and grid, with photos.
Tests and records
Pressure tests, NDT reports, inspection records and cube tests, filed against the work they prove.
Deliveries
Pipe, fittings and consumables by supplier, with their delivery notes, including free-issue materials from the client's store.
Consumption
Material issued and used, by area, set against what arrived.
Delays
Areas not handed over, client-supplied materials late, work stopped, with the area each one holds.
Instructions
Instructions from the client's engineer, project manager or Employer's Agent, logged with date and area.
Labour
Operatives on site, by area and trade.
Commitments
Who promised what, by when: an area, a test, a delivery.
Site teams change nothing. Velora joins each group as one more member.
What each team gets
Every team gets its part of the project.
Your QS gets the month's quantities in a report, contract triggers reach whoever you choose, project directors see every area today, and the board sees every project. Nobody has to ask site for an update.
This month's quantities, ready for the valuation.
Work done is matched to your BoQ or activity schedule and totalled for the month. Each total opens into the areas, dates and photos behind it, with the NDT reports, test packs and inspection records it needs, and missing ones are followed up on WhatsApp once you switch follow-ups on. Velora tracks quantities; your QS applies rates and finalises the application.
See Billing IntelligenceThe contract triggers that are easy to miss.
Not just extensions of time and LADs. An area not handed over or client-supplied materials arriving late, but also work held by another package or late design information reported by site: each is logged with its area and the date it was first posted, matched to the clause it may trigger, such as a Relevant Event under JCT or 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 until it's dealt with. Your team decides what goes to the client.
See Contract IntelligenceEvery area, every day, without the calls.
Progress by area and trade, the delays holding each area, deliveries by supplier and materials used against what arrived, from the groups your teams and subcontractors already post in. Daily, weekly or monthly reports are drafted from the same record, ready to review.
See Field IntelligenceEvery project in one view.
For the managing director or operations director running several projects: the blockers that have waited longest for a decision, by area, and, where Billing is on, which quantities are still waiting on proof.
See Portfolio IntelligenceWorked example
The month's valuation, built from the site record.
Industrial work is valued per BoQ item or activity schedule line, area by area. Velora keeps each total and its proof together.
Totals per scope line
Tonnes of steel erected, metres of pipework welded, numbers of supports and square metres of cladding, for each BoQ item or activity schedule line.
By area and grid
Every total lists where the work was done, with dates and photos, so your QS can check it before it goes to the client.
Records per line
NDT reports, test packs and inspection records, received or still missing, before the application goes in.
Gaps before the valuation
Work done that matches no BoQ item, and BoQ items posted without a measurement, flagged to your QS before the application goes in.
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 groups where progress, test records, deliveries and delays are posted today, including your subcontractors' groups.
Your scope
The BoQ or activity schedule, and the project's areas and buildings. 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 project and we'll set up a pilot against its live WhatsApp groups and your BoQ or activity schedule.
Frequently Asked Questions
Common questions from industrial project directors and QSs.
Yes. Scope is loaded from the document that holds it, a bill of quantities, or the activity schedule or contract sum analysis on a design-and-build contract, and work done is matched to its lines and totalled for the month, with the areas behind each total. Valuing by stage or milestone is something the team is still working on. Velora tracks quantities; your QS applies rates and finalises the application.
Free-issue materials are recorded when they arrive and where they are used, like any other delivery. A wait for them is logged as a delay, with the area it holds and the date it was first posted, and checked against your contract for the clause it may trigger.
Yes. Quantities are read in the units your site posts and matched to the BoQ line they belong to. Where the unit or the line is unclear, the update is held for your QS to confirm, not guessed.
Yes. Deliveries are recorded by supplier with their delivery notes, and materials issued and used are recorded by area, so the two can be set side by side in daily, weekly or monthly reports. Velora doesn't match deliveries to purchase orders or invoices itself.
No. Extensions of time and LADs are the clauses every team watches. Velora also checks routine updates against the rest of your JCT, NEC, IChemE or amended contract: client-supplied materials arriving late, an area not handed over, work held by another package or late design information reported by site, each matched to the clause it may trigger, such as a Relevant Event or a compensation event, with the notice the contract requires and the record behind it. Whoever you choose is alerted the same day. Velora doesn't send notices; your team decides what to send. Contract Intelligence is in early access.
We run a discounted pilot for the first three months on one project: the full product, with no long-term commitment.