Skip to main content

Stop chasing site for checklists at month-end. Every line of the application goes in with its proof.

Pre-pour checklists, ITP sign-offs and test certificates are already posted in your site groups, mixed in with everything else, or never posted at all. Velora picks the work done and every quality record out of the chats and files each against the work it covers. Your team marks which documents are due, and Velora chases those in the site groups until they're in. The proof for your interim application is assembled as the work happens.

Work done, detected from the chats. Progress and completions read from site updates, with location, date and photos, so you know which work needs its proof.
Quality records picked out and filed. Signed checklists, ITP sign-offs, cube and compaction test certificates and signed inspection records, recognised in the groups and filed against the work they cover.
Due documents chased on WhatsApp. Mark a checklist, test certificate or measurement record due and a daily reminder asks the groups you choose until it's in. Velora recommends what to mark when work starts or finishes.

848 messagesRead into one month's measurement sheet on a maintenance contract: 898 patches, each with its chainage, size and date.

Block A · Structure
Riverside Hospital · Dan, Velora +6
Dan
Level 3 slab grid C–F poured, 62 m³. Cubes taken
3 photos
5:48 PM
Block A · QC
QC Team, Velora +4
Priya
Pre-pour checklist for the Level 2 slab, signed off by the Supervisor
Checklist
6:02 PM
Lab · Test Results
Arun, Velora +2
Arun
28-day cubes for the Level 1 slab, 47.6 N/mm² average
Test certificate
6:15 PM
+5 More Groups
Velora
October evidence · Riverside HospitalUpdated 6:16 PM
RC slab, C32/40 · Block A186 m³
3 pours this month, each with the proof found for it
Level 1 slab, grid C–FInspection 1 found · cube test filed1 Oct62 m³
Level 2 slab, grid C–FInspection 1 found18 Oct62 m³
Level 3 slab, grid C–FInspection none foundToday62 m³
ValueProof filed against each pour
Cube test · Level 1 slab47.6 N/mm²
Read from the test certificate in Lab · Test Results
ValueFiled against the Level 1 pour
Blockwork, 140 mm · Block A640 m²
14 updates · 2 inspection records marked due
ValueDue records chased in the QC group
Block A · QC
QC Team, Velora +4
Evidence Reminder
Inspection records pending, asked for by the billing team — 3 total, 1 carried forward from earlier periods: Blockwork — 2 pending: Level 2 east wing (work done), Level 1 core walls (work done) Slab pour — 1 pending: Level 3 slab grid C–F (work done) Carried forward (1): Level 1 core walls (work done)
9:04 AM ✓✓
Priya
Pre-pour checklist for the Level 3 slab attached, signed off this morning
Checklist
10:12 AM
Sent on WhatsApp each morning for documents marked due, until each one is in

Where the proof goes missing

The proof usually exists. It just isn't with the application.

The client's side assesses each line against its ITP sign-offs, test certificates and measurements. On site, those are posted in a dozen groups, filed in someone's phone or never filled in at all, and they're gathered in the last days before the valuation.

Held for proof

The quantity is in. The ITP sign-off isn't.

One unsigned hold point or a missing ITP sign-off, and the line can be held back from this month's assessment.

The document existed on site. Nobody chased it in time, so the work waits for next month.

Posted, then lost

The cube results came in. Nobody filed them.

The test certificate was posted in the QC group on the 21st, between a delivery photo and a labour count.

At valuation time, someone scrolls three weeks back to find it, or asks the lab to send it again.

Chased at month-end

Forty checklists, chased in the last three days.

Checklists pile up until the cut-off, then the QS calls every site engineer for them.

Some arrive unsigned. Some were never filled for work done three weeks ago, and can't honestly be filled now.

Never on the register

Work finished that nobody tracked.

A drain completed in a corner of the site never made it onto the checklist register, so nobody asked for its checklist.

It surfaces when someone asks why it isn't in the valuation, or it never does.

None of it is a big miss. Every month, on every project, it adds up.

How Velora does it

Proof gathered as the work happens, not at the cut-off.

Your site and QC teams keep posting where they post today. Velora does the sorting, filing and chasing.

  1. Read

    Work done and quality records

    Progress and completions, signed checklists, cube, compaction and other test results, and inspections, read from text, voice notes and photos of the documents, in any language.

  2. File

    Against the work they cover

    Each record is matched to its work, location and scope line. On planned work, a checklist Velora matched lands as reported, for your quality lead or QS to confirm; anything that fits more than one item is left for you to choose. Work started or finished where nothing is planned is proposed as a new entry.

  3. Check

    What each line still needs

    Every piece of work in the month's bill, with the inspection records and tests found for it and what's still missing. On the plan, last month's open items carry forward until they're in.

  4. Flag

    What's due, to the groups you choose

    You mark what's due, with Velora's recommendation and its reason beside each item. Each morning the groups you set up get the due documents by activity, until they're in. Documents posted back are matched and filed.

When the application goes in, export the pack: the inspection records, test certificates and work photos behind each line, with an index of evidence and quantities.

Worked example

The month's evidence register.

One plan per month: every planned item, the inspection record it needs and its status, with every piece of work done shown on the month's bill. Statuses move as documents are posted; your team confirms what Velora matched and marks what's due.

  • Read from the chats

    A pre-pour checklist posted in the QC group is recognised, matched to its pour and marked reported, for a person to confirm.

  • Chased once marked due

    Anything your team marks due goes into the next morning's reminder to the groups that take it.

  • Carried forward, not forgotten

    Last month's open items stay on the register until they're in, instead of dropping off with last month's application.

  • Work nobody tracked

    Work started or finished where nothing is on the plan is proposed as a new entry, with a recommendation to mark its checklist due.

October · Plan
Riverside Hospital · Evidence Reminders: On
Level 1 slab, grid C–F · Block A / Level 1
Inspection record
Received
Level 2 slab, grid C–F · Block A / Level 2
Inspection record · Velora matched it, to confirm
reported
Level 3 slab, grid C–F · Block A / Level 3
Inspection record
Due
Level 2 east wing · Block A / Level 2
Inspection record
Due
Level 1 core walls · Block A / Level 1
Inspection record · carried forward
Due
Level 3 columns, grid C–F · Block A / Level 3
Inspection record · Recommended: the work is done
Not due
Storm drain, service yard · Service yard
New work piece detected from field activity — nothing tracked for it yet
Confirm
From the Bills tab, the bill pack: inspection records, tests and work photos, with an index of evidence and quantities

Illustrative figures

See your next application go in with its proof.

Talk to us about one live project and we'll set up a pilot against its WhatsApp groups and your bill of quantities.

Frequently Asked Questions

Common questions from commercial managers, quality managers and QSs.

It's the contractor's application for payment, usually monthly, for the value of work done to date. Under NEC4 the Project Manager assesses the amount due at each assessment date and certifies it; under JCT the work is valued at each Interim Valuation Date. Under both, the Construction Act payment notice and pay less notice regime applies (through Option Y(UK)2 under NEC4). The QS supports each line with its measurements and the records the contract asks for: ITP sign-offs, test certificates such as cube tests, and measurement records. Velora gathers that proof from your site groups as the work happens.

For measured work, yes. Under NEC4 Option B each line is measured against the bill of quantities, and under JCT the work properly executed is valued; Velora assembles the work done and its quality records behind each line. Under Option A, Velora still files the records for each activity; paying by completed activity is something the team is still working on. Target and cost-reimbursable work (NEC4 Options C and E) is paid on Defined Cost, which needs cost records rather than quality records, so there the evidence register supports the record, not the payment.

Signed QC checklists, pre-pour checklists and ITP sign-offs, test certificates such as cube, compaction, plate load and pile tests, and signed inspection records, whether posted as photos, documents or text. Each is filed against the work it covers, with the original message kept.

Evidence Reminders asks only for documents your team has marked due: inspection records such as checklists, ITP sign-offs and level sheets, test certificates, the measurement record, and any extra document the project needs. Velora recommends what to mark when work starts or finishes, or an inspection is posted. Work photos are never chased; they're filed as they arrive.

Anyone can post a photo of it in the group, and it's read and filed like any other. Once it's in, the reminder stops asking for it.

No. Velora assembles the proof and tracks the quantities behind each line. Your QS applies rates, retention and deductions and finalises the application in your own format.

Billing Intelligence →

Yes. Velora reads text, voice notes and photos in the languages your teams use, including photos of checklists, test reports and letters, and keeps each original message with the record it created.

We run a discounted pilot for the first three months on one project: the full product, with no long-term commitment.