What slips at month-end
Many main contractors, many applications. All due the same week.
A specialist subcontractor works for many main contractors at once, on many sites, each job reported in a different group. Applications for payment fall due around the same dates each month, each needing its own proof, so small things slip: jobs that missed the application, test records nobody collected, snags nobody proved closed.
The last week
Every application is due the same week.
Each main contractor wants its own application, with the photos, checklists and test records for every job, gathered from site, QA and stores.
All of it lands in the same week, and a line without its proof is left out of that month's valuation.
Missed in the application
A roof terrace finished mid-month. It never reached that contractor's application.
"Roof terrace waterproofing done, Block C, 420 m²": posted in the main contractor's group, one job among dozens across sites.
At month-end each contract's jobs are pieced together from many groups, and some are missed. The work was done; that application never saw it.
Test records
Flood test passed. The record stayed on a phone.
Each treated area is flood-tested before it is handed over, and the photo of the test sits in a supervisor's chat or a group nobody checks at application time.
Without it the main contractor leaves the line out, and the payment waits another month.
Snags
Leak fixed on site. Never proven, so the second half of retention waits.
A leak is fixed and the photo is posted, but nobody files it against the snag the main contractor raised.
At the end of the defects period the item still shows open, and the final retention release waits until someone finds the proof.
What Velora picks up
What your site groups already carry, in specialist terms.
Velora reads text, voice notes and photos in the groups your operatives post in today, including the main contractor's groups you're part of, and files each job by contract, site and area.
Jobs by contract and site
Areas treated, injections and installations by main contractor, site and area, with photos.
Test records
Flood, ponding and pressure test records, filed against the job they prove.
Checklists
Surface preparation and application checklists, when they are posted.
Snags
Leaks fixed and snags closed, with photos, logged against the job.
Deliveries
Membranes, coatings, chemicals and pipes by supplier, with their delivery notes.
Labour
Which gang worked on which site, each day.
Instructions
Instructions from the main contractor or the client, logged with date and site.
Commitments
Who promised what, by when: a test, a revisit, a handover.
Site teams change nothing. Velora joins each group as one more member.
What each team gets
Every team gets its part of the work.
Your QS gets each contract's quantities in a report, operations sees every site today, and directors see every project. Nobody has to ask site for an update.
Every contract's quantities, ready for its application.
Work done is matched to each subcontract's BoQ, schedule of rates or activity schedule and totalled for the month. Each total opens into the sites, areas, dates and photos behind it, with the test records and checklists that main contractor asks for, and missing ones are followed up on WhatsApp once you switch follow-ups on. Velora tracks quantities; your QS adds rates and finalises each application.
See Billing IntelligenceEvery site, every day, without the calls.
Which gang did what, on which site, with photos, the snags closed, and deliveries by supplier, from the groups your operatives post in, including the main contractor's. Reports for each main contractor are drafted from the same record, ready to review and send.
See Field IntelligenceEvery project in one view.
For the managing director or operations director running jobs for many main contractors: the blockers that have waited longest for a decision and, where Billing is on, which quantities are still waiting on proof.
See Portfolio IntelligenceWorked example
The month's applications, built from the site record.
Each subcontract is valued on its own BoQ, schedule of rates or activity schedule. Velora keeps every job's total and its proof together, contract by contract.
Totals per contract
Square metres treated, metres injected and tanks lined, for each line of each subcontract.
By site and area
Every total lists where the work was done, with dates and photos, so each application can be checked before it goes out.
Test records per job
Flood, ponding and pressure test records and checklists, received or still missing, before each application goes out.
Gaps before the application
Jobs that match no line, and lines posted without a measurement, flagged to your QS before each application goes in.
Illustrative figures
Getting started
What we'd need to start a pilot.
A pilot runs on a few of your subcontracts and their live site groups. Your operatives 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 your operatives post jobs, tests and deliveries today, including the main contractor's groups you're in.
Your scope
Each subcontract's BoQ, schedule of rates or activity schedule. Loaded once per contract.
A sample chat export lets us test on your own messages before going live.
See it on your own jobs.
Talk to us about your subcontracts and we'll set up a pilot against your live WhatsApp groups and their BoQs or activity schedules.
Frequently Asked Questions
Common questions from specialist subcontractors and their commercial teams.
Yes. Each subcontract's BoQ, schedule of rates or activity schedule is loaded once, and every job is matched to the contract and site it belongs to, so each application is built on its own, with its own proof.
Yes, once the group admin agrees to add Velora's number. Velora reads only the groups it's a member of.
Flood, ponding and pressure test records and checklists posted in a group are filed against the job they prove. The ones still missing are listed for the people who owe them, once you switch follow-ups on, so each application shows which records are in.
Velora doesn't issue or answer notices. It keeps each line's proof dated and filed against the job, so when a main contractor's payment notice or pay less notice leaves a line out, your QS has the record to respond with.
Yes. Velora reads text, voice notes and photos in the languages your operatives use, including English, Polish and Romanian, and photos of test records and delivery notes, and keeps each original message with the record it created.
No. Velora joins the groups your operatives already use as one more member and reads what they post today. There is no new app and no form to fill.
We run a discounted pilot for the first three months on a few of your subcontracts: the full product, with no long-term commitment.