What slips at month-end
Many towers, many trades. Each with its own proof.
A township runs structure, finishes and MEP at once, across towers and phases, each trade reporting in its own group. Nothing is totalled until month-end, so small things slip: finishes that missed the bill, checklists nobody collected, repairs nobody connected, loads nobody can trace.
Missed in the bill
Tiling finished in 37 flats. 34 reached the bill.
"Flat 1204 and 1205 bathroom tiling done": a flat or two a day, across towers, one post among hundreds from the finishing contractors.
At month-end someone counts flats back from scroll-back, and a few are missed. The flats are tiled; the bill never saw them, so they wait for next month.
Checklists
Slab poured on time. The pour card turned up after the bill.
A pour card is signed off by your engineer and the client's before every slab, column and pile cap is poured, and photographed into whichever group is nearest.
Where the client wants them with the bill, the billing engineer hunts for each one across groups at bill time. The lines without one wait, and the client may hold back more of the bill until the paperwork is complete.
Repeat repairs
The same joint resealed a third time. Nobody read the clause.
The podium joint leaked again and the site resealed it, as it had twice before. Each repair was posted; nobody connected them.
Some contracts restart a repaired part's liability period, and let the client recover the cost directly once a defect keeps coming back. By the time anyone reads the clause, the deduction is on the bill.
Material cost
Steel arrives by the truckload. Challans are scattered.
Cement, steel, blocks and tiles arrive from several vendors all month, each load with a challan photographed into a store group.
At month-end each vendor bill is checked against challans nobody can find, so it gets paid as billed.
What Velora picks up
What your site groups already carry, in building terms.
Velora reads text, voice notes and photos in the groups your teams and subcontractors use today, and files each update by tower, floor and flat.
Progress by location
Pours, blockwork, plaster, tiling and MEP by tower, floor and flat, with photos.
Checklists and tests
Pre- and post-pour checklists, inspection records and cube tests, filed against the work they prove.
Deliveries
Cement, steel, blocks, tiles and fittings by vendor, with their challans.
Hindrances
Areas not handed over, material held, work stopped, with the tower or floor each one holds.
Instructions
Site visits and instructions from the client's engineer or architect, logged with date and location.
Repairs
Leaks, cracks and rework reported on site, with photos, so a repeat repair on the same element shows up.
Manpower
Crews and subcontractor labour on site, by tower and trade.
Commitments
Who promised what, by when: a slab cycle, a delivery, a flat handover.
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 tower 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 towers, floors, flats, dates and photos behind it, with the pre- and post-pour checklist for every slab and column, 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. An area not handed over or a client-side delay, but also an instruction on site, extra work beyond the scope, or the third repair on the same joint: each is logged with its location 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 tower, every day, without the calls.
Progress by tower, floor and flat, the hindrances holding each front, deliveries by vendor and commitments followed up, from the groups your teams and subcontractors already post in. Daily, weekly or monthly reports are drafted from the same record, ready to review and send to your client.
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 tower, 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.
Building work is billed per BOQ item or work scope line, floor by floor. Velora keeps each total and its proof together.
Totals per scope line
Cubic metres of concrete, square metres of blockwork, plaster and tiling, and counts of doors and fixtures, for each BOQ item or work scope line.
By tower, floor and flat
Every total lists where the work was done, with dates and photos, so your engineer can check it before it goes to the client.
Checklists per pour
The pre- and post-pour checklist for every slab, column and pile cap, 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, checklists, deliveries and hindrances are posted today, including your subcontractors' groups.
Your scope
The BOQ or work scope, and the project's towers and floors. 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 residential project heads and billing engineers.
Yes. Scope is loaded from the document that holds it, an item-rate BOQ or a lump-sum billing break-up, and work done is matched to its lines and totalled for the month, with the towers, floors and flats 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.
Each slab, column or pile cap that needs a checklist is listed for the project. When a signed checklist is posted in a site group, it is filed against that element; the ones still missing go out in a daily digest to the people who owe them, once you switch follow-ups on. At bill time, every line shows which checklists are in.
Yes. Velora reads text, voice notes and photos in the languages your teams and subcontractors use, including photos of checklists and challans, and keeps each original message with the record it created.
Yes. Daily, weekly or monthly reports are drafted from the site record, by tower and floor with photos, for your team to review before they go out.
Case study: weekly client reports for a luxury residential contractor →
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 beyond the scope, a late drawing reported by site or a repeat repair, 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.