Hours on the phone, signed off by the foreman
Operatives and foremen fill in timesheets on their own phones. The foreman signs off the crew, and the week exports straight to payroll: BrightPay, or a CSV laid out for whatever package you run.
Timesheets arrive on paper and by WhatsApp photo, the office re-types them for payroll every Monday, and the certs live in a folder in the cabin. We build the system that takes all of it off paper: hours signed off on the phone, every worker’s tickets tracked to their expiry, built in Kanturk, Co. Cork, for Irish contractors.

Timesheets come in on paper, by text and as photos of a notebook, and someone in the office keys every one into payroll before the cut-off.

Once a day is split across two sites and a drive, nobody can say for certain which job the hours belong to, so the cost report is a guess.

Safe Pass cards, tickets and induction records sit in a folder, and the first sign one has lapsed is the main contractor asking for it.
Operatives and foremen fill in timesheets on their own phones. The foreman signs off the crew, and the week exports straight to payroll: BrightPay, or a CSV laid out for whatever package you run.
Clock in and out against a geofence drawn round the site. A clock-in outside it still goes through, flagged for the foreman to check. Split days, travel time and the job and site for every hour are logged in the same place.
Site inductions, compliance documents and certs held against each worker, each with its expiry date, so the office sees what lapses next month while there is still time to book the course.
Signed-off hours, labour cost per job and the certs about to lapse, read from the same records the foremen fill in. It runs as a web app on any phone, it is hosted in the EU, and you own the code.
Running jobs as well as crews? Quoting, scheduling, dockets and Sage or Xero are on the M&E contractors page.
| Worker | Mon | Tue | Wed | Thu | Fri | Status |
|---|---|---|---|---|---|---|
| Operative 1 | 8 | 8 | 8 | 8 | 7 | Signed |
| Operative 2 | 8 | 8 | 9 | 8 | 7 | Signed |
| Operative 3 | 8 | 4 | 8 | 8 | 8 | Split day |
| Operative 4 | 8 | 8 | 8 | 0 | 0 | Safe Pass expires |
| Operative 5 | 9 | 9 | 8 | 8 | 6 | Awaiting foreman |
A 30-minute scoping call with the engineers who would build it: how many on site, how hours reach payroll today and where it hurts.
We follow a week of hours from the site to the payslip, then send back a fixed-price scope and a delivery timeline.
Work starts against the agreed scope. The founders you spoke to are the ones who build it, through to handover.
No. It is a web app: it opens in the browser on any phone, Android or iPhone, from a link the office sends. Nothing to install from an app store.
The clock-in is recorded and flagged for the foreman. It is never refused, because a phone’s location drifts and an operative at the far gate of a big site should not lose a day’s pay over it.
Signed-off weeks export for BrightPay, or as a CSV laid out for the payroll package you already use. Split days, travel and the job behind each hour come across with them.
Whatever your sites ask for: Safe Pass, trade tickets, plant cards, your own site induction. Each one sits against the worker with its expiry date.
Hosted in the EU. You own the code, so the system stays yours whoever maintains it later.
Thirty minutes with the engineers who would build it. Pick a time that suits and tell us how hours get from site to payroll today.