Skip to content
HMRC CIS return month ending 5 Aug · due Wed 19 Aug 12 days
CIS return due Wed 19 Aug 12 daysCDM 2015, RIDDOR and the compliance registers, built in rather than bolted onUnlimited users, every module, £0 per helmet30+ modules, one login, and the 15-app stack retiredQuickBooks, OneDrive, WhatsApp and email, wired into the jobGlove-friendly field app, QR-first, timed by the server not the phoneExpired subcontractor insurance drops a firm out of approved status overnightFree migration from whatever you run todayUK built, UK support desk, UK hours30-day free trial, no card, no obligation
Start the 30-day trial
Book a demo→
Rate valuations

Measure it on site.
Get it signed. Get it paid.

Your supervisor records the week's labour, plant and materials against the job. The platform prices it from that contract's own rate card. The client signs on the screen before anyone leaves site. Approved work then reaches the application for payment without being rebuilt from a spreadsheet at month end.

See rate valuations working → Where it ends up
priced from the job's own rates capped against the estimate signed on site running since 2016
Where measured work leaks

The work was done.
Getting paid for it is
a separate problem.

If your business is won on measured rates, this is where the margin actually goes, and none of it is visible until it is too late to act.

Wednesday
Hours written on a scrap of paper in a van, and lost before Friday.
Never claimed
Materials
Used on site, never written down, so they never make it onto a claim at all.
Absorbed
The extra
Done on a nod, remembered by two people differently, disputed three months later.
Argued down
Month end
The measure is rebuilt from memory and a diary, then argued over line by line.
≈ 3 days
Worse
Over claiming discovered by the client's surveyor rather than caught internally.
Credibility
In a folder
Approved work sitting unbilled, because nobody knows which valuations have been claimed.
Cash stuck
The mechanism that fixes it Capture the measure where and when the work happened Everything downstream follows
What is in the module

Six capabilities, built by a
business whose income
depends on all of them.

This is the operational core of a temporary site services provider that has run on it since 2016.

Priced from the
job's own rates

01

Labour, plant and materials value themselves from that contract's rate card and its assigned price list, with the job's markup applied.

  • Every job carries its own rate card across all rate types
  • Its own markup and its own price list
  • Two jobs the same week value the same hours differently
  • Correctly, without anybody remembering which is which
The deal you actually wonLive

Capped against
the estimate

02

On estimate driven jobs, claimable hours for a section are capped at the estimated allowance less whatever has already been approved.

  • The cap applies in the app, at the point of entry
  • A claim inside the allowance can approve automatically
  • One that exceeds it is refused before it is submitted
  • Over claiming prevented rather than corrected
Before it becomes an argumentLive

Signed on site,
while it is fresh

03

The client signs on the device, with their typed name, the date and space for a remark, for work they have just watched being done.

  • Captured before anyone leaves site
  • A considered acceptance rather than a scrawl
  • The month end argument becomes a reference
  • The valuation still works without one
Agreement while it is freshLive

Evidence attached
to the claim

04

Photographs with descriptions, delivery notes and certificates, so the valuation is a documented record rather than a number.

  • A photograph only evidence pack you can send on its own
  • Attached to the claim, not to somebody's phone
  • Retrievable when the final account is argued
  • Attendance data alongside it
Documented, not assertedLive

Nothing left
unclaimed

05

The platform separates billed from unbilled and lists approved work that has never reached an application, as a queue rather than a hope.

  • Approved but not applied for, in one list
  • It cannot be billed twice
  • Unsigned variations flagged separately
  • Worked through rather than noticed
Work in progress, visibleLive

A full
lifecycle log

06

Added, edited, submitted, signed, approved, rejected. Every step carries the person, the time and whether it came from the app or the web.

  • A rejection requires a written reason
  • The reason reaches the person who raised it
  • Resubmission alerts the office
  • A correction is visible rather than silent
Attributable throughoutLive
From the measure to the money

Six steps, and the office
does not rebuild any of them.

  1. 01

    Measured

    On siteThat weekBy whoever did it
  2. 02

    Priced

    Job rate cardAssigned price listJob markup
  3. 03

    Capped

    Against the allowanceLess what is approvedRefused at entry
  4. 04

    Signed

    Client name typedDate capturedRemark optional
  5. 05

    Approved

    Or rejected with a reasonLogged either wayResubmission alerts
  6. 06

    Applied for

    Straight into the applicationMarked as billedCannot go twice
The join that matters The measure signed on site is the measure on the application One record, not two
Where it sits commercially

A measured valuation is a
commercial instrument before
it is a piece of software.

Housing Grants, Construction and Regeneration Act 1996
The signed, measured valuation is what an application for payment is built from. Note the honest boundary: the platform implements the Act's payment mechanism on the payable side, in the deed it issues to your subcontractors. Serving a payment notice or a pay less notice to your own client is not built, and it is set out plainly on the applications page rather than hidden.
Contractual evidence in delay and disruption
Dated, signed and photographed valuations created in the week the work was done carry more weight than a reconstruction assembled afterwards, and the full lifecycle log shows when each step actually happened rather than when somebody wrote it up.
Working Time Regulations 1998
Labour lines carry hours per operative per day. The primary working time record is the timesheet module rather than this one, and the two record different things: the timesheet is attendance, the valuation is chargeable measured work.
On the weight of the signature
What the platform captures is a signature image, the signatory's typed name, the date and any remark, against a dated record of the work, held in a system that logs who wrote it and when. Whether that constitutes agreement to the measure or acknowledgement of attendance is a question for your contract and your own advisers, and any software supplier who answers it confidently on a website should worry you.
What you need to know

Four things, including
which system we would
demonstrate this in.

01
We would show you the site services deployment
Two businesses run on this platform. Rate valuations are the operational core of one of them and have been since 2016. The other, a construction contractor, has never switched them on, because its commercial model is different. A demonstration in the wrong system shows empty screens, so we will show you the one where this carries a decade of records.
02
The counted figures are being collected
The deployment where this module is proven has never had its volumes counted, which is our own gap rather than yours. We are collecting them properly rather than quoting the other deployment's numbers against a capability it does not use. Until then this page carries no volume claim, and you should treat any supplier who cannot say where a number came from the same way.
03
Automatic approval applies to estimate driven jobs only
The cap works by comparing a claim against the estimated allowance, so on a job that did not come from a structured estimate there is no allowance to check against and no automatic approval. That is a real distinction and it is worth establishing early which of your jobs would be which.
04
It suits measured work, not lump sum
If your contracts are lump sum, this module is not the answer for you and we would say so rather than sell it. Lump sum work generally runs through day work sheets and the payment application instead, and the scoping conversation establishes which shape your commercial model actually takes.

The capability has run a business every working day since 2016. The counted evidence for it is work we owe you.

Questions

Asked by commercial managers
and quantity surveyors.

Our rates differ from job to job. Does that work?+
That is the normal case here rather than the exception. Every job carries its own labour rate card across all rate types, its own markup, and its own assigned price list. The valuation prices from those, so two jobs running in the same week value the same hours differently, correctly, without anybody having to remember which contract is which.
What stops a supervisor claiming more than was priced?+
On jobs that came from an estimate, the claimable hours for each section are capped at the estimated allowance less whatever has already been approved. A claim within the allowance can approve automatically. One that exceeds it is refused in the app at the point of entry, before it becomes an argument. The commercial position is protected without the office checking every line, which is the only version of this control that survives a busy month.
Our clients will not sign on a phone.+
Some will not, and the valuation still works without a signature. Most site representatives sign readily when they are being shown exactly what is being claimed for work they have just watched being done. The signature is captured with their typed name, the date and space for a remark, so it reads as a considered acceptance rather than a scrawl on a pad. The alternative you are comparing it against is usually no record at all.
What if a valuation is wrong after it has been approved?+
It is rejected with a mandatory reason, which notifies the person who raised it by email and by push, and the resubmission alerts the office. The whole sequence stays in the lifecycle log, so a correction is visible rather than silent. That matters more than it sounds: a system where corrections are invisible is a system nobody trusts by the third month.
Does this replace our timesheets?+
No, and conflating the two would cause you real problems. They record different things. Timesheets are the working time record, captured by QR punch in and out, and they are what your payroll and your working time obligations rest on. The valuation records the measured, chargeable work against the contract. On estimate driven jobs the two can be tied together through the clock in and clock out data captured against the labour lines.
We work on lump sum contracts, not rates. Is this relevant?+
Less so, and we would rather say that than sell you something you will not use. Lump sum work generally runs through day work sheets and the payment application instead, both of which are covered elsewhere on this site. The scoping conversation establishes which shape your commercial model takes, and if the answer is that this module is not for you, that is a useful thing to establish in the first meeting rather than the third month.
How does approved work actually reach an invoice?+
The application for payment draws on approved variations directly, so the month end job is assembling rather than reconstructing. Once a variation is pulled into an application it is marked as billed and cannot be claimed again, which is the part most spreadsheets get wrong in the other direction. Everything that is approved and not yet billed sits in a queue you can work through.
Next step

Bring one job you
measured badly.

The point If work gets done on your sites and never quite makes it onto a bill This is the part to see first
See it working → The allowances that cap it
Phone · UK hours
+44 7587 557546
Email
[email protected]
Where it ends up
Applications
Demo calendar
unibuild.co.uk/demo