Digital timesheets and site attendance: matching pay to who was on site

A builder who runs three or four crews across a handful of sites will often have three records of the same week. There is the timesheet app, which shows what each worker logged. There is the paper sign-in sheet on the site office door, which shows who turned up. And there are the figures keyed into payroll at the end of the fortnight. The three rarely agree, and when they do not, nobody can say with confidence who was paid for what.

The cost of that disagreement is practical. A worker queries a pay slip and the builder cannot show the hours. A subcontractor invoices for a crew of four on a day when only two of them were on the job. A safety incident happens at the start of the day and the site manager cannot say from memory who was on the scaffold. Each of these is an ordinary problem with an ordinary fix, but the fix depends on the records agreeing before the question is asked. The employer carries the risk when the pay rules are not followed, and the risk shows up at the worst possible moment, usually when a worker or a subcontractor disputes the figures.

The organising idea of this article is that attendance records earn their keep only when the site roll, the timesheet and the pay run all say the same thing. This is not a review of timesheet features, and it is not about wearables or location tags as safety technology. It covers the work that happens at the join between the records: the identifiers, the daily check, the approval, the export and the subcontract match, and what to keep so that the records can be produced when someone asks.

What the three records are supposed to show

Each record answers a different question, and it helps to be clear about which one is which before setting anything up. The site roll answers who was physically on the site at a given time. The timesheet answers how many hours a person worked, on which job and in which trade. The pay run answers what was paid, at which rate and with which deductions. A subcontract claim answers how many crew days were charged, and for whom. A single misunderstanding about which record is the authority is a common source of disputes, because each record is treated as the answer to a question it was never designed to answer.

The sensible approach is to treat the site roll as the evidence of presence, the timesheet as the evidence of work, and the pay run as the consequence of both once they have been approved. The subcontract claim should be checked against the presence record, not against the timesheet of the foreman. When the records are kept this way, a disagreement points to a specific place to look.

Why the app is rarely the real problem

When a timesheet system produces bad data, the cause is almost never the software itself. The app records what it is given. The failures happen at the join. A worker is entered as Mick in one record and Michael in another, so the hours never reach the right pay line. A casual worker is set up under the wrong employment type, so the overtime rules are applied to the wrong hours. A subcontractor’s crew signs in under the foreman’s login, so the only record of who was there is a single name for the whole group.

The fix is one identifier per person, used in every record. An internal employee number is a better choice than a personal document number, because it does not spread sensitive details across the systems. The identifier should be set up before the first day on site, not added later when the pay run is due. Every crew member, including the subcontract crews, should have one, and the supervisor should be able to see at a glance whether a name on the site roll has an identifier behind it.

Reconciling the timesheet with the site roll each day

The most useful habit in the whole process is a short daily reconciliation. At the end of each day, or first thing the next morning, the supervisor compares the timesheet entries with the site roll and asks a single question for every difference: why is this person recorded here, and not there? Most gaps have a simple explanation. A worker signed in at the yard, drove to the site late and was on the job from mid-morning. A labourer was moved to a different site and forgot to sign out. A subcontractor’s apprentice was on site but nobody recorded the sign-in.

The daily check works because the explanations are still in people’s heads. By the end of the week the same gap is a guess, and by the end of the pay period it is an argument. Keep the check short and specific. The supervisor should not be re-entering hours, only confirming presence and explaining gaps. Where a gap cannot be explained, it should be flagged rather than silently corrected.

Location data can help with this check, but it has limits. A phone can be left in a ute at the yard, a worker can sign in for a mate, and a signal can drop at the bottom of a deep excavation. Treat location as one input to the reconciliation rather than as the answer. The supervisor’s knowledge of who was on the job is still the final check, and the record should say when a gap was explained by a person rather than by the app. Tools that log measurements on site raise the same issue of trusting the record, and digital measuring tools that log results covers that side of it.

Turning approved hours into the pay run

Once the daily check is done, the approved hours should move into payroll without being typed again. Re-keying is where most of the errors creep in. A figure written by hand from a printed sheet can be one digit wrong, and the mistake is invisible until the worker queries the pay. The export from the timesheet system should carry the same identifiers and the same hours that the supervisor approved, so the pay run is a copy of the approved record rather than a second version of it.

The pay rules are set by the modern award or enterprise agreement that applies to each worker, and the timesheet system has to reflect them. Rounding rules, unpaid breaks, the point at which overtime starts and the allowances for particular work all have to be set up correctly for each worker, not applied as a single rule across the crew. A system that rounds every entry to the nearest quarter hour may be perfectly fair for one worker and quietly wrong for another. Check the rules once when the system is set up, and check them again when an award or an agreement changes.

Changes after approval need a trail. If a supervisor adjusts an approved entry, the record should show who made the change, when and why. An approved record that can be quietly edited is not an approved record. This matters most when the change is to the hours of a worker who has since left the business, because the employer may need to show what was paid and why.

Subcontract crews and the claims you did not pay out of your own payroll

Subcontract crews are where site attendance records are most often weak, and where the money is most often at risk. The builder is paying for a crew, not for an individual, and the claim arrives as a number of days or a sum for the week. Without a presence record, the builder is taking the subcontractor’s word for who was on the job. The safe approach is to treat each subcontract crew as a group on the site roll, with a named person responsible for signing in the crew each day.

Check each claim against the presence record before it is approved. A claim for a day when the site roll shows only two of a crew of four is not necessarily dishonest, because the subcontractor may have had people on another job, but it is a query that needs an answer. The answer may come back with the subcontractor’s own timesheets, a reason for the absence or a corrected claim. What the builder should not do is pay the claim and find out later that the crew was somewhere else.

The same record helps with the workers who are not on the payroll at all. Site inductions, the subcontractor’s workers’ compensation details and the names of the people on the roll should all match. A site roll that lists a name nobody can account for is a problem on the day an incident happens, not only when the bills come in.

Privacy and what the workers are told

Sign-in records, timestamps and any location data about individual workers are personal information. The business should know why it collects that data, what it keeps and for how long, who can see it and where it is stored. Check whether the Privacy Act applies to the business, and if it does, make sure the collection is covered by a clear notice to the workers. A worker who finds out that their location was being logged, without being told, will treat the whole system as a surveillance tool, and the goodwill the builder needs for the next job goes with it.

Ask the vendor direct questions before signing up. Where is the data stored, who can access it, how long is it kept, and can the business export and delete it? The Safe Work Australia material on digital technologies and AI is a reasonable starting point for the questions to put to a vendor about how the data is used and what the system is allowed to decide on its own. Wearables and tracking tags raise a separate set of questions, which are covered in the article on wearables and tracking for small teams.

The commercial reality is that a timesheet system that workers do not trust is a system that gets worked around. People sign in for each other, leave the app open on the phone, or stop using it altogether. The fix is not more monitoring. It is a clear, written explanation of what is recorded and why, and the same explanation given to every worker, including the subcontract crews.

What the attendance record is for when something goes wrong

When an incident happens on a site, the first question is who was there. The site roll answers that question in seconds if it is current and in minutes if it is not. The builder needs to be able to produce a list of the people on the site at the time, to account for them during an evacuation and to give the investigators an accurate picture of the morning. Those are obligations under the work health and safety laws, and the attendance record is part of meeting them.

The record should not depend on the app being available. Export the daily site roll at the end of each day, keep a copy outside the system and test that the export can be opened. A printed roll in the site office is a sensible backup for the first hours of an emergency, when the phone signal may be poor and the people who need to be accounted for are not all in the app. Make sure the supervisor knows where the backup is kept and that the copy is updated each day.

A worked example from a subcontract claim

A builder in the outer south-west of Sydney runs a timesheet app across three sites. A framing subcontractor submits a claim at the end of the week for a crew of four across five days. The supervisor runs the reconciliation as usual, and the site roll shows that the crew was on the job for only three of those days, with two of the four people on site on the other two.

The builder does not pay the claim. The supervisor contacts the subcontractor, who explains that one of the crew was on a different job on one of the days, and that a labourer had been recorded against the wrong site. The subcontractor sends its own sign-in sheets, which confirm the explanation for two of the days. The claim is adjusted, the site roll is corrected with the explanation recorded and the labourer’s entry is fixed in the timesheet system.

The lesson the builder takes from the job is practical. The claim was not a fraud, and the subcontractor was not trying to cheat. The problem was that the builder had no way to check the claim against the people on the site, and the first time anyone looked, the two records disagreed. A daily roll and a claim check would have caught the difference before the week closed.

Setting it up so the records survive a dispute

Most of the work is in the set-up, and it is worth doing once, properly. The checklist below covers the points that decide whether the records will hold up when a pay query, a subcontract dispute or an incident review arrives. Each item is something the builder can confirm before the first pay run goes out.

The timeline below shows the same flow as a sequence, from the sign-in at the gate to the retention of the records. Each stage should have a named person responsible for it, so a gap at any point can be traced to the stage where it happened rather than to the software in general.

Builders who run their own crews also need to keep their professional learning current, and the records for that sit in a different system again. The PointCPD guide to how NSW builder CPD works explains what counts and how to keep the evidence. Keeping the site records and the professional records in a single, well-indexed place makes both easier to produce when someone asks.

Questions builders ask

• Admin
• Payroll
• Site Records

Published 4 October 2026. General information for builders, not legal, financial or engineering advice for a specific job. Check current requirements with the relevant regulator or standard before relying on them.