What slips at month-end
Many blocks, many trades. Each with its own proof.
A residential scheme runs structure, finishes and M&E at once, across blocks and phases, each trade reporting in its own group. Nothing is totalled until month-end, so small things slip: finishes that missed the valuation, checklists nobody collected, repairs nobody connected, loads nobody can trace.
Missed in the valuation
Tiling finished in 37 flats. 34 reached the valuation.
"Flats 1204 and 1205 bathroom tiling done": a flat or two a day, across blocks, one post among hundreds from the finishing subcontractors.
At month-end someone counts flats back from scroll-back, and a few are missed. The flats are tiled; the valuation never saw them, so they wait for next month.
Checklists
Slab poured on time. The pre-pour checklist is in someone's camera roll.
A pre-pour checklist is signed off by your engineer, sometimes witnessed by the clerk of works, before every slab, column and pile cap is poured, and photographed into whichever group is nearest.
When it's needed, to release the frame subcontractor's payment, for the warranty inspector or the handover file, it's hunted across groups.
Repeat repairs
The same joint resealed a third time. Nobody connected the repairs.
The podium joint leaked again and the site resealed it, as it had twice before. Each repair was posted; nobody connected them.
A repair that keeps failing points to a cause someone has to own, the waterproofing subcontractor or the design, and if it isn't fixed at source it carries into the rectification period and holds the second half of retention. By the time anyone pulls the three repairs together, the argument has started without the record.
Material cost
Blocks arrive by the lorry load. Delivery notes are scattered.
Blocks, plasterboard, tiles and fittings you buy direct arrive from several suppliers all month, each load with a delivery note photographed into a stores group.
At month-end each supplier invoice is checked against delivery notes nobody can find, so it gets paid as invoiced.
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 block, floor and flat.
Progress by location
Pours, blockwork, drylining, tiling and M&E by block, floor and flat, with photos.
Checklists and tests
Pre-pour checklists, inspection records and cube tests, filed against the work they prove.
Deliveries
Blocks, plasterboard, tiles and fittings by supplier, with their delivery notes, including materials free-issued to labour-only gangs.
Delays
Areas not given, information awaited, work stopped, with the block or floor each one holds.
Instructions
Site visits and instructions from the Contract Administrator, Employer's Agent 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.
Labour
Gangs and subcontractor labour on site, by block 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.
Your QS gets the month's quantities in a report, contract triggers reach whoever you choose, project directors see every block today, and leadership 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 blocks, floors, flats, dates and photos behind it, with the pre-pour checklist for every slab and column for the handover file and subcontractor payments, 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 given or late information, but also work held by another package or a defect to correct: each is logged with its location 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 block, every day, without the calls.
Progress by block, floor and flat, the delays holding each block, deliveries by supplier 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 managing director or commercial director running several projects: the blockers that have waited longest for a decision, by block, 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.
Building work is valued per BoQ item or activity schedule line, floor by floor. Velora keeps each total and its proof together.
Totals per scope line
Cubic metres of concrete, square metres of blockwork, drylining and tiling, and counts of doors and fittings, for each BoQ item or activity schedule line.
By block, floor and flat
Every total lists where the work was done, with dates and photos, so your QS can check it before it goes to the client.
Checklists per pour
The pre-pour checklist for every slab, column and pile cap, received or still missing, for the handover file and before subcontractor payments.
Gaps before the valuation
Work done that matches no BoQ item, and 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, checklists, deliveries and delays are posted today, including your subcontractors' groups.
Your scope
The bill of quantities or activity schedule, and the project's blocks 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 bill of quantities or activity schedule.
Frequently Asked Questions
Common questions from residential project directors and QSs.
Contractors building flats and housing for housing associations, build-to-rent and student accommodation operators and private developers, where the work is valued monthly and site teams report on WhatsApp.
Yes. Scope is loaded from the document that holds it, a bill of quantities, a contract sum analysis or an activity schedule, and work done is matched to its lines and totalled for the month, with the blocks, floors and flats 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.
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. Every line shows which checklists are in, for the handover file and before the frame subcontractor is paid.
Yes. Velora reads text, voice notes and photos in English, Polish, Romanian and the other languages your teams and subcontractors use, including photos of checklists and delivery notes, and keeps each original message with the record it created.
Yes. Daily, weekly or monthly reports are drafted from the site record, by block and floor with photos, for your team to review before they go out.
No. Extensions of time and LADs are the clauses every team watches. Velora also checks routine updates against the rest of your contract: late information reported by site, work held by another package or a defect to correct, each matched to the clause it may trigger, with the notice it calls for and the record behind it. A repair that keeps failing is kept on record, to recover from the trade that owns 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.