SiteTour Attend · Included with SiteTour Diary Early access
Sign-in that becomes evidence.
One QR code per project, printed at the gate. Workers sign in on their own phone — no app to install, induction confirmed before they start, one tap on every return visit. The diary pulls the day's verified attendance straight into its labour log.
01 · At the gate
No app. No queue. No excuses.
Scanning the QR opens a plain, fast web page — built to load on site signal. First visit, a worker gives their name, company, trade, and purpose, and confirms the site induction before they can sign in as working. Their phone remembers them, so every visit after that is one tap — including sign-out and re-entry through the day.
- 1 Scan the QR at the gate Opens in the phone's browser — nothing to install, loads fast on poor signal.
- 2 First visit: details + induction Name, company, trade, purpose — and a required "induction completed" confirmation for anyone working.
- 3 Every visit after: one tap The phone remembers the worker. Multiple in/out spans collapse to first-in / last-out in summaries.
02 · At the desk
The live board, the register, the export.
- Who's on site now — a live board in the dashboard, with the same counts on the engineer's phone at the gate.
- Induction register — every confirmation on record, and a flag against anyone working who hasn't confirmed.
- Manager sign-in mode — a manual-add form on dashboard and mobile for workers without smartphones.
- CSV export — the full raw attendance log, whenever you need it.
- QR everywhere — print it from the dashboard, or show it straight off the engineer's phone on sites with no signage.
03 · The point
From sign-in sheet to labour log, one tap.
In the diary's labour section, "Pull from sign-in sheet" drops the day's verified attendance straight into the entry — workers into labour with company, trade, and gate times; visitors and deliveries into visitors. No duplicates, existing rows kept, and a warning if anyone working hasn't confirmed induction.
That turns the diary's workforce count from a head-count from memory into a verified attendance record — and the sign-in log travels with every diary export as evidence.