UK-built · CDM · CIS · MTD
QR code clock-in at the construction site gate, in your own app, with a photograph and a time written by the server rather than read from the phone. About three seconds, and a PIN instead of a password.
Not because anybody is careless. Because the record is made somewhere other than where the work happened, and by the time it reaches the office it is a reconstruction. Everything below is what a reconstruction costs you.
Your operatives punch in through your own app, published under your company name and built during implementation. You print a QR code poster for each gate, the operative scans it in the app, and the hours reach the office already attributed to the job, with a photograph and a time the server wrote, priced at that person's rate for the day into the job cost position while the job is still running. What your payroll system does with them afterwards is covered further down this page, honestly.
Add your sites in five minutes. The platform generates a numbered QR code poster for each gate, in your branding. Print on A4, laminate, screw it to the site board. That is the install.
The operative opens your app, points it at the QR code, and the scan screen opens. It asks for a photograph, records the location with it, and the office sees the punch at the same instant the operative sees the confirm screen.
Every day line carries the project it was worked on, at the cost rate in force on that day, and the pay type set on that day drives the money through one cost formula on the timesheet, the timesheet report and the monthly analysis. Site managers approve on the phone rather than transcribing on a Friday.
The field half either gets opened on a wet Tuesday with gloves on or it does not, and if it does not, the rest of the platform stops mattering. Everything below exists because of that.
Open your app, scan the QR code poster, take the photograph. Three seconds at the construction site gate, and the server writes the time.
A camera photograph at punch in, the location recorded with it, and a time written by the server. Buddy punching becomes harder than turning up.
Three pay types on the day line: normal, time and a half and double time. Once the type is on the day, the multiplier is applied to the money by the same cost formula on the timesheet, the timesheet report and the monthly analysis, so nobody is rebuilding Sunday night's spreadsheet on Monday.
Tracked separately from worked hours, with its own daily ceiling, so travel does not quietly become overtime on the same line.
Punch events, near misses and accidents reach a manager who may never open the app, as an outbound template message. It is not a WhatsApp Business integration and it is not a two way channel.
Per person, per project, per week, at the cost rate in force on the day. The labour half of the job cost position, while the job is still running.
Draft, submitted, approved, rejected. Site managers sign off on phone before payroll. Workers cannot edit after submission.
Every person carries a dated cost rate. The rate in force on the day worked is stamped onto the line as it saves, so a rise in April cannot rewrite last quarter's job costs.
Hours are attributed at day-line level, so somebody who worked three sites in a week produces three costed rows rather than one lump nobody can split later.
We are not going to put a saving figure on this page. Any number we invented for your firm would be wrong, and you would know it. What we can set out is exactly what changes about the record itself, which is the thing every downstream saving depends on.
A QR code on a construction site is only worth having if the record it produces survives an argument eighteen months later. Below is what the code is, where the poster goes, what the scan captures and, just as importantly, the two things it deliberately does not do.
A numbered code generated by the platform for one scan point, printed on an A4 poster in your branding and fixed to the site board. It is not a web address. A phone camera pointed at it opens nothing, because only your own app resolves the code, and only for somebody already signed in.
Wherever the gang passes anyway. On a housing site that tends to be one QR code per plot, so the hour lands on the plot rather than the site. On a spread-out civils job it is the cabin. In a building it can be a floor code.
A photograph taken at the moment of the punch, the location stored against it, the IP address, and a time written by our server rather than read from the handset. The job comes from the code that was scanned, so the hour is attributed before anybody types anything.
It is not a geofence. A punch made away from the construction site is shown to the approver as a map link rather than rejected automatically, and adding a distance check is tailoring rather than something switched on. It also cannot prove intent: it makes buddy punching harder than turning up, not impossible.
The module is the same in every case. What differs is where the poster goes and how the rates are set up, and that is a configuration decision taken with you. Below is how each shape of business tends to work.
One poster per plot, so the hour lands on the plot rather than the site. Location is recorded on the punch and shown to the approver as a map link. It is not a geofence: nothing is rejected automatically.
Call-out work means unpredictable hours. Overtime multipliers cover normal, time and a half and double time, and travel time is tracked separately from worked hours with its own ceiling.
Sites spread across a wide area, often with the cabin as the only fixed point. The scan point goes where the gang passes anyway, at the cabin or the gate, and the office can enter hours on an operative's behalf with a manual flag and the same audit trail.
Night shifts and weekend work, where the multiplier matters and the arrival time is the thing that gets argued about. The server writes the time, so it is not a claim about when somebody arrived.
Work spread across many buildings, where the question is who is actually where. Live presence shows who has punched in, on which site, on a map coloured by job, so a no-show is visible rather than reported.
Multiple sites, mixed trades and different rates, with one approval route. Hours are attributed per day line, so somebody who worked three sites in a week produces three costed rows rather than one lump.
A timesheet ends up in front of an auditor, a client's surveyor or a solicitor. Everything below is about the record surviving that, and each claim is one we can show you rather than one that reads well.
Every action on a timesheet is logged with who did it, when, and whether it came from the app or the portal. The hour, the location and the photo are stamped against the shift.
who · when · from whereAWS eu-west-2, London. Data does not leave the UK. No third-party trackers, no analytics brokers.
aws · eu-west-2AES-256 at rest, TLS 1.3 in transit. Backup and key management arrangements are set out in the agreement, where they can be held to, rather than summarised on a web page.
AES-256 · TLS 1.3A forgotten clock-out is corrected by the office with a manual flag on the record, so the change is visible rather than silent. The original and the correction both survive, with the person and the time against each.
Flagged, not overwrittenThe full list lives at /faqs. These eleven are the ones we hear in every demo.
There is no price list on this site and we are not going to invent one here. What we can set out is the shape of the figure and what moves it, which is where a construction timesheet system differs from a generic per-seat time tracking app.
Same platform, same login. These are the modules that plan the work, record it, and hold the evidence it was done properly.
What a scan can and cannot prove, and why a rollout stalls in week three.
