Blog Industry

A plant where the clock is the source of truth

6 min read

In some plants the timesheet is the record and the clock is a hint. In others the clock is the record and the timesheet follows from it. The second is a commitment, and it changes how overtime is worked out, what a corrected punch has to carry, and what a supervisor’s job becomes. One invented plant, making the switch, shows what follows.

Maintained by the TriblockHR Compliance Team. Updated 2 October 2026. This page describes terminal and timesheet settings in TriblockHR; it names no device maker and states no statutory figure.

The switch that decides it

Take an invented bottling plant, Blue Hole Beverages, with about 180 production staff on three shifts. For years, supervisors filled in timesheets at the end of each shift, including the overtime they thought each person had worked. The clock at the gate existed, but nobody checked it against the timesheets.

Blue Hole decides to make the clock the record. In TriblockHR, one account setting decides which is the source of overtime: overtime is either calculated from the threshold, using the hours the punches record, or taken as listed on the timesheet, using what someone wrote down.

The choice matters at audit. Under “taken as listed”, the record of overtime is a supervisor’s judgement, and the question “why was this person paid three hours of overtime?” is answered by “the supervisor wrote three”. Under “calculated from the threshold”, it is answered by the punches and the threshold for the person’s employment level. How that arithmetic works, daily against weekly, is covered in daily overtime is not weekly overtime divided by five.

Blue Hole chooses “calculated”. From that point, the punch is what pays.

The punch as an attributable record

If the punch pays, the punch has to be attributable: who made it, where, and how.

In TriblockHR, terminals are registered by serial and grouped. A punch records the device it was made on and the division. Each terminal identifies by face, fingerprint or keypad on the device, and the authentication method is captured on the punch. The method is reportable: punches can be filtered, sorted and grouped by it, alongside the device and division. Biometric time clocks covers the terminals.

The method matters on a production floor. Bottling-line staff wear gloves for much of the shift. Fingerprint reading through gloves, or with wet hands, is unreliable, so a line worker taking gloves off at the clock creates a queue and a hygiene problem. Face recognition does neither. Blue Hole chooses face for the line, with keypad as a fallback for anyone not yet enrolled.

Because the method is on the punch, Blue Hole can see afterwards how many punches were by face and how many by keypad, by line and by shift. A line where keypad use stays high is a line where enrolment needs a second visit.

Manual punches and edit reasons

When the clock is the record, every exception to it becomes visible.

Manual punches. Whether managers may add punches by hand is an account setting. During rollout, Blue Hole allows it, so a supervisor can add a punch for someone whose enrolment failed that morning. After rollout, it watches the count. A rising number of manual punches on one line, or by one supervisor, means capture is failing there: people are not clocking, and someone is covering for it. That is a reason to look.

Edit reasons. A changed punch carries an edit reason. If a supervisor moves someone’s clock-out from 22:00 to 22:45 because she stayed to clear a jam, the edit shows what changed, who changed it and why. Under “taken as listed”, that would have been a different number on a timesheet. Under “calculated”, it is a dated, explained change to the record.

The shift nobody closed. Auto clock-out at the end of a scheduled shift is a setting. It closes a shift someone forgot to end, at the scheduled time. That keeps an open shift from running overnight on the timesheet, but it records the scheduled end, so an auto clock-out is worth reviewing when it happens.

Late and unscheduled clock-in alerts tell a supervisor the same day when someone has not clocked in at their start, or has clocked in without a scheduled shift.

Before approval, before the run

A supervisor’s job changes. The supervisor checks the hours the clock recorded.

Before approval. A long-shift threshold flags an unusually long day in the bulk timesheet preview. A line worker with a seventeen-hour day is either a real emergency or a missed clock-out, and the flag puts it in front of the supervisor before the timesheet is approved.

Before the run. The pre-run review raises a warning, regular hours exceeded, when ordinary hours exceed the threshold in a run. It is one of sixteen pre-run flags. Time, attendance and overtime covers thresholds and the settings around them.

The supervisor’s job becomes approving exceptions: the long day, the auto clock-out, the manual punch, the edit. The ordinary days approve themselves, because the clock already recorded them.

A floor system already in place

Some plants already capture hours on a time-and-attendance system on the floor. Making the clock the record does not require replacing it. Hours from that system can be imported onto the same timesheets.

An import batch is previewed before it commits, so the hours can be checked before they become payroll. A batch can be rolled back, once, and only while the run is still draft or awaiting approval; a rolled-back batch refuses a second attempt. That keeps a bad import from being fixed by repeated tries after the run has moved on.

TriblockHR does not do MRP, production scheduling, inventory or shop-floor control. It records when people worked and pays them. TriblockHR Workforce covers the capture routes, and the manufacturing page the wider operation.

Questions

Can overtime be calculated from the clock?

Yes. An account setting decides whether overtime is calculated from the threshold or taken as listed on the timesheet.

Is the identification method recorded?

Yes. The authentication method is captured on the punch and is reportable with the device and division.

Are changes to punches recorded?

Yes. A changed punch carries an edit reason.

Can an imported batch be undone?

Once, and only while the run is draft or awaiting approval.

Make the clock the record, and turn supervision into approving exceptions.

Book a demo

  • SOC 2 Type II attested
  • AES-256 at rest
  • 99.9% uptime
  • Built in The Bahamas