Digital timesheets for construction: replace paper and save 11%

The cost of paper timesheets

Every construction site in the UK uses some form of time recording. HMRC requires employers to maintain records of hours worked for at least six years. The Working Time Regulations 1998 require records demonstrating compliance with the 48-hour weekly limit. CDM 2015 requires attendance records showing who was on site at any given time. And of course, workers need to be paid accurately for the hours they work.

Despite these requirements, a significant proportion of UK construction companies still rely on paper timesheets, handwritten sign-in books, or at best, a shared spreadsheet that a site manager manually fills in at the end of each week. The process is familiar: workers sign a sheet when they arrive and when they leave. At the end of the week, someone (usually the site manager or a quantity surveyor) collects the sheets, deciphers the handwriting, resolves any obvious errors, and sends them to head office for payroll processing.

This process has been standard in construction for decades. It is also deeply, structurally flawed. The flaws are not the result of dishonesty (though that plays a part). They are the result of a system that makes accuracy almost impossible and errors systematically one-directional: in favour of overpayment.

Where the 11% goes

The 11% overpayment figure comes from multiple industry studies comparing actual hours worked (measured by independent observation or digital tracking) against hours claimed on paper timesheets. The gap is consistent across company sizes, trades, and regions. It breaks down into several distinct categories:

Buddy punching (estimated 3-4% of the total). One worker signs in on behalf of another who is not yet on site, or not on site at all. In construction, this is more common than in other industries because of the informal culture around start times. A worker running 20 minutes late asks a mate to sign them in at 7:00. Over a week, that is an hour and a half of paid time not worked. Scale that across 200 workers and it adds up quickly. Paper sheets have no way of verifying that the person signing is the person named.

Systematic rounding (estimated 3-5% of the total). When workers fill in their own timesheets, they round in their favour. A 7:12 arrival becomes 7:00. A 16:45 departure becomes 17:00. This is not malicious; it is human nature. But the rounding is always one-directional. Nobody rounds their start time up or their finish time down. Over a week, an average of 15 minutes per day of favourable rounding adds up to 1.25 hours. Over a year, across a workforce, it is substantial.

Disputed hours (estimated 2-3% of the total). When a worker's claimed hours do not match the site manager's recollection, there is no independent evidence to resolve the dispute. In practice, the dispute almost always resolves in the worker's favour. The worker says they worked until 17:30. The site manager thinks they left at 17:00. There is no GPS record, no clock-out timestamp, no photo. The worker gets paid for the extra 30 minutes because challenging it without evidence creates conflict and risks tribunal claims.

Ghost workers (estimated 0.5-1% of the total). In the worst cases, workers appear on timesheets who were never on site. This can be collusion between a supervisor and a worker, or simply a data entry error where a worker is carried forward from a previous week's sheet. Paper systems make this almost impossible to detect until a detailed forensic audit is performed.

Admin error (estimated 1-2% of the total). Transposing digits when transferring handwritten hours into a payroll system. Applying the wrong pay rate. Counting a bank holiday as a normal day. These are genuine mistakes, but they add up, and they disproportionately favour overpayment because underpayment errors generate complaints while overpayment errors go unreported.

How GPS clock-in eliminates fraud

Digital clock-in using a mobile device addresses each of the failure modes that make paper timesheets unreliable. The core principle is simple: replace a subjective, unverifiable, self-reported record with an objective, verified, timestamped one.

GPS geofencing. Every site has a defined geographic boundary (a geofence). When a worker opens the app to clock in, the device captures GPS coordinates. If the coordinates are outside the geofence, the clock-in is rejected or flagged. This prevents clocking in from home, from the car park of the site next door, or from the cafe down the road. The geofence boundary can be drawn to match the site hoarding line, so it is accurate to within a few metres.

Device ID tracking. Every clock-in event is stamped with a unique device identifier. If the same device is used to clock in two different workers within a short window, the system flags it as a potential buddy punch. If a worker's device changes unexpectedly, that is also flagged. This does not prevent workers from sharing devices in a genuine emergency, but it creates a visible audit trail that makes systematic fraud detectable.

Face ID verification. Modern smartphones have biometric verification built in. Requiring Face ID or fingerprint authentication before a clock-in event confirms that the person holding the device is the registered owner. This is the single most effective control against buddy punching. It does not require any additional hardware: the worker uses the biometric capability already built into their iPhone or Android phone.

Timestamped to the second. Digital clock events are recorded to the exact second, with both the device timestamp and the server timestamp captured independently. There is no opportunity for rounding. If a worker arrives at 07:12:34 and leaves at 16:47:22, those are the recorded times. Pay calculations use the exact minutes, not rounded quarter-hours. The difference between device time and server time is also captured, which helps detect devices with deliberately altered clocks.

Photo audit trail. Some systems capture a timestamped photograph at clock-in. This provides visual evidence that the worker was physically present, in PPE, at the recorded time. The photo is stored as part of the attendance record and is available for audit. For principal contractors who need to demonstrate compliance to clients or the HSE, this is significantly more compelling than a signature in a book.

The approval workflow

Raw clock-in and clock-out data is not a timesheet. It needs to be validated, adjusted where necessary (for legitimate reasons such as a worker who forgot to clock out), and approved before it reaches payroll. A structured approval workflow prevents errors from propagating and gives multiple people the opportunity to catch mistakes.

The standard construction timesheet approval workflow has four stages:

1. Draft. Clock events from the week are compiled into a draft timesheet for each worker. The draft shows daily start and finish times, total hours, any breaks deducted, and any anomalies flagged by the system (GPS outside geofence, missing clock-out, unusual hours). The worker can view their own draft via the mobile app and flag any errors.

2. Site approved. The site manager reviews the draft timesheets for their site. They resolve any anomalies: adding a missing clock-out time based on witness evidence, noting why a worker clocked in outside the geofence (they were doing a delivery run), or adjusting hours where a system error occurred. The site manager cannot change a GPS-verified clock-in time, but they can add notes and adjustments with a reason code. Once satisfied, they approve the timesheet for their site.

3. Payroll approved. The payroll team or commercial team reviews all site-approved timesheets across the business. They check for consistency, apply any contractual rules (overtime thresholds, shift premiums, bank holiday rates), and verify that the total aligns with budget expectations. They can query individual entries with the site manager. Once satisfied, they approve for payment.

4. Export. The approved timesheet data is exported in CSV or other format for import into the payroll system. The export includes worker name, employee or subcontractor reference, hours by category (normal, overtime, weekend, bank holiday), applicable pay rate, CIS status, and any adjustments with reason codes. The export file becomes the authoritative record for that pay period.

Each stage creates an audit trail showing who approved, when, and what (if anything) they changed. If a dispute arises months later, every decision point is traceable.

Integration with payroll and CIS

Construction payroll is more complex than most industries because of the Construction Industry Scheme (CIS), the prevalence of subcontracted labour, and the variety of pay arrangements across different trades and contracts.

CIS deductions. Under the Construction Industry Scheme, contractors must deduct money from payments to subcontractors and pass it to HMRC. The deduction rate depends on whether the subcontractor is registered (20%) or unregistered (30%). A digital timesheet system flags each worker's CIS status and includes the appropriate deduction rate in the payroll export. The worker's Unique Taxpayer Reference (UTR) is stored in the system so it flows through to the payroll file without manual re-entry.

Pay rate cascading. Construction pay rates vary by site, trade, seniority, and contract type. A good digital system supports rate cascading: a default company rate, overridden by a site-specific rate, overridden by a worker-specific rate where applicable. This means the correct rate is applied automatically based on which site the worker clocked in at, without anyone needing to remember or manually select it.

Overtime rules. Different sites and contracts have different overtime thresholds. Some pay time-and-a-half after 8 hours. Others after 10. Some have different weekend rates. Digital timesheets apply these rules automatically based on the site configuration, so the site manager does not need to manually calculate overtime hours for each worker.

BACS and direct payment. The export file is formatted for direct import into standard UK payroll systems. For companies paying subcontractors via BACS, the timesheet data provides the authoritative record of hours that drives the payment amount. No more disputes about whether the subcontractor invoiced correctly because both parties can see the same verified clock data.

Paper vs digital: side-by-side comparison

Factor	Paper timesheets	Digital timesheets (GPS-verified)
Identity verification	Signature (easily forged)	Face ID + device ID + GPS
Time accuracy	Rounded to nearest 15 minutes (by worker)	Exact to the second (by system)
Location verification	None	GPS coordinates checked against site geofence
Buddy punching prevention	Impossible to detect	Flagged by device ID and biometric check
Dispute resolution	Word against word (defaults to worker)	GPS + timestamp + photo evidence
Payroll processing time	2-4 hours per site per week	Minutes (automated export)
HMRC audit readiness	Boxes of paper, weeks to compile	Searchable digital records, instant export
Overtime calculation	Manual calculation, error-prone	Automatic based on site rules
Real-time visibility	None until end of week	Live view of who is on site right now
Cost of overpayment	8-15% of labour bill	Near zero (verified data, no rounding)

The AttendIQ approach

AttendIQ was built specifically for UK construction time and attendance. It is not a generic HR tool adapted for construction, and it is not an access control system with a timesheet bolted on. Time tracking, compliance verification, and payroll export are integrated into a single workflow.

Mobile-first clock-in. Workers clock in using their own smartphones. No hardware to install, no tablets to mount at the gate, no biometric scanners to maintain. The worker opens the app, the GPS confirms they are within the site geofence, Face ID confirms their identity, and the clock-in is recorded. The entire process takes under 10 seconds. It works with gloves on, in the rain, and with a cracked screen. It also works fully offline with automatic sync when connectivity returns.

Four-stage approval workflow. Clock events flow into draft timesheets at the end of each week. Site managers approve for their site. The payroll team approves across the business. Then the data is exported. Every stage has an audit trail. Anomalies are flagged automatically: missing clock-outs, GPS mismatches, excessive hours, and unusual patterns.

Pay rate cascading. Set a default rate at company level. Override it at site level. Override it at worker level where needed. The system applies the most specific rate automatically based on where the worker clocked in. No manual rate selection at payroll time. Overtime rules, weekend rates, and bank holiday rates are all configured per site and applied automatically.

CIS-ready export. The payroll export separates PAYE and CIS workers, includes UTR numbers, and flags the appropriate deduction rate. The file is formatted for direct import into Sage, Xero, or any standard UK payroll system. No re-keying of hours, no manual CIS calculations.

Working Time Directive compliance. AttendIQ monitors cumulative hours against Working Time Regulation limits. If a worker is approaching the 48-hour weekly average, the system alerts the site manager before the worker clocks in, not after they have already worked a 13-hour day. Opt-out records are stored and auditable.

Supply chain transparency. When a subcontractor's workers clock in on your site, their hours are visible in your timesheet view. You can see who is on your site, how long they have been there, and whether their hours match the subcontractor's invoice. This is not just about catching fraud. It is about having a single source of truth that both parties can refer to when reconciling payments.

HMRC-ready records. All attendance data is retained for the HMRC-required period and can be exported at any time. If HMRC requests records during a tax investigation or CIS compliance check, you can produce them in minutes rather than weeks. Every record includes the original clock event, the approval chain, any adjustments with reason codes, and the final payroll export timestamp.

Frequently asked questions