Pillar 02 — Valid8 Connect

The people on site.

Attendance captured at the point of entry — by shift, by discipline, by employing company — and reconciled against the hours that get claimed. So the manpower on the invoice is the manpower that stood on the floor.

The problem

Labour is the biggest line on the package and the least evidenced.

A timesheet is a claim. It arrives at the end of the week, it is compiled by the party being paid, and by the time anyone can dispute it the week is gone. On a floor with several contractors and rotating day and night shifts, nobody can reconstruct who was actually there.

  • Hours claimed cannot be checked against anything independent.
  • Day and night shifts blur across midnight, so night crews get counted badly.
  • Company attribution is loose — the same firm spelled three ways is three firms.
  • Missing data reads as absence, which is the fastest way to accuse a good crew wrongly.

How it works

Capture at the door, reconcile at the invoice

Step 01

Clock in on site

A site device takes the operative's name, their discipline — installation or validation — their shift, and a personal PIN. Two seconds at the door, no app to install, no phone required.

Step 02

Attribute to the right company

Every record carries the employing company at the moment it is taken, so a later change to someone's details cannot retroactively move historic hours onto a different firm's invoice.

Step 03

Reconcile against the claim

Weekly hours per person, per date, per shift, per company — set against the timesheet submitted, with any estimated record flagged as estimated rather than quietly averaged in.

Design principles

Built by people who have been on the wrong end of a manpower dispute.

Attendance data is only useful if everyone trusts it — including the crews it counts. Three rules keep it honest.

  • Missing is not absent. A gap in the data means a gap in the data. Nobody is marked absent because a device was flat or a signal dropped; the record says "not captured" and it stays that way until someone resolves it.
  • Estimated is labelled estimated. A shift that was never clocked out is closed conservatively and flagged. It is never presented as a measured hour, and it is never invoiced as one without agreement.
  • Corrections are audited, not quiet. Records get amended — people forget. Every amendment is attributed and time-stamped, so the correction history is part of the evidence rather than a hole in it.

Status

Where Connect is today

We would rather tell you what is running and what is coming than describe a roadmap in the present tense.

Site clock-in — shift, discipline, PIN Running on the Valid8 platform today. Live
Weekly hours per person, date, shift & company Reporting available today, with uncaptured clock-outs surfaced explicitly. Live
Point-in-time company attribution on every record In build — removes retroactive re-attribution of historic hours. In build
Timesheet-versus-actual reconciliation view In build — per-company weekly variance against claimed hours. In build
Audited correction workflow & offline capture In build — role-restricted amendments and resilience to site connectivity loss. In build

Next step

See it counting a real shift.

Twenty minutes, live, on the platform — clock-in, the weekly view, and exactly how an uncaptured clock-out is presented.