What slips at month-end
Civil, steel, piping, equipment. All at once, area by area.
An industrial project runs every discipline at once, across areas and buildings, each contractor reporting in its own group. Nothing is totalled until month-end, so small things slip: work done that missed the bill, records nobody filed, client-side delays nobody put on record, material nobody reconciled.
Missed in the bill
1,180 pipe supports fixed this month. 1,120 reached the bill.
"Area 200 supports fixed, 64 nos": a few dozen at a time, from the piping crew, one post among hundreds.
At month-end someone counts them back from scroll-back, and a few batches are missed. The supports are in; the bill never saw them, so they wait for next month.
Test records
Line hydrotested. The test pack never reached the bill.
Each line is hydrotested before insulation and its welds radiographed, and each test report is photographed into whichever group is nearest.
Where the bill is paid in stages, hydrotest and NDT among them, the billing engineer looks for each report across groups at bill time. Stages without one wait for next month.
Client-side delays
Client material arrived three weeks late. The record is a scroll.
The piping crew posted it each day they waited for free-issue pipe. Nobody logged when it started or which area it held.
When time and idle costs are argued, the record is photos across groups, and the notice window has closed.
Material
Steel issued from the yard. Nobody knows what went where.
Structural steel, pipes and fittings arrive from several vendors and are issued to areas from the yard.
At month-end, what was used can't be tied back to what arrived, so a shortfall shows only when the erection crew runs out.
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 contractors use today, and files each update by area, building and grid.
Progress by area
Civil, steel erection, PEB, piping and equipment by area, building and grid, with photos.
Tests and records
Hydrotests, NDT reports, inspection reports and cube tests, filed against the work they prove.
Deliveries
Steel, pipes, fittings and consumables by vendor, with their challans, including material the client supplies.
Consumption
Material issued and used, by area, set against what arrived.
Hindrances
Fronts not handed over, client material late, work stopped, with the area each one holds.
Instructions
Instructions from the client's engineer or consultant, logged with date and area.
Manpower
Crews on site, by area and discipline.
Commitments
Who promised what, by when: a front, 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.
Billing gets the month's quantities in a report, contract triggers reach whoever you choose, project heads see every area today, and leadership sees every project. Nobody has to ask site for an update.
This month's quantities, ready for the bill.
Work done is matched to your BOQ or work scope and totalled for the month. Each total opens into the areas, dates and photos behind it, with the NDT reports, test packs and inspection reports it needs, and missing ones 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 front not handed over or client-supplied material arriving late, but also an instruction that changes the work, extra work beyond the scope or a late drawing reported by site: each is logged with its area 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 area, every day, without the calls.
Progress by area and discipline, the hindrances holding each front, deliveries by vendor and material used against what arrived, from the groups your teams and contractors 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 MD or project controls head 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 bill, built from the site record.
Industrial work is billed per BOQ item or work scope line, area by area. Velora keeps each total and its proof together.
Totals per scope line
Tonnes of steel erected, inch-dia of piping welded, numbers of supports and square metres of sheeting, for each BOQ item or work scope line.
By area and grid
Every total lists where the work was done, with dates and photos, so your engineer can check it before it goes to the client.
Records per line
NDT reports, test packs and inspection reports, received or still missing, before the bill goes out.
Gaps before the bill
Work done that matches no BOQ item, and BOQ items posted without a measurement, flagged to your billing team before the bill 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 hindrances are posted today, including your contractors' groups.
Your scope
The BOQ or work scope, 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 work scope.
Frequently Asked Questions
Common questions from industrial project heads and billing engineers.
Yes. Scope is loaded from the document that holds it, an item-rate BOQ or an EPC billing break-up, and work done is matched to its lines and totalled for the month, with the areas behind each total. Billing by stage or milestone is something the team is still working on. Velora tracks quantities; your team adds rates and finalises the bill.
Free-issue material is recorded when it arrives and where it is used, like any other delivery. A wait for it is logged as a hindrance, 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 billing engineer to confirm, not guessed.
Yes. Deliveries are recorded by vendor with their challans, and material issued and used is 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. EOT and LD are the clauses every team watches. Velora also checks routine updates against the rest of your contract: client material arriving late, a front not handed over, an instruction that changes the work or a late drawing reported by site, each matched to the clause it may trigger, with the deadline 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.