QR site attendance with a geofence

Every scan sends a GPS position, and the distance to the site is computed as a great-circle distance. Outside the radius, the clock-on is refused.

• The default radius is 100 metres and it is set per job, anywhere from 10 to 5,000 metres.
• A refusal names the actual distance and the limit, for example that you are 340 metres away against a 100-metre limit.
• No attendance record is created on a refusal. There is no override and no manager approval path.
• The clock-in and clock-out positions are both stored on the record.
• The scan page will not submit without a location fix, and says so if location services are off.

NoteIf the job has no site coordinates set, the distance check is skipped rather than blocking everyone. Set the site location for the geofence to do anything.

Yes. Clocking out creates a timesheet entry from the elapsed time, less the unpaid break the operative declares.

• Hours are computed from clock-in to clock-out, minus the declared break, and rounded to two decimal places.
• The entry records the worker name, the date, the hours and the clock-in time, and describes itself as a QR attendance scan.
• The hourly rate is left blank, so nothing is costed until somebody rates it deliberately.
• Clocking out matches the person’s open clock-in on that job; if there is not one, it says so rather than inventing a record.

Yes — on site induction, an in-date CSCS card and acceptance of the current RAMS version, each set independently to off, warn or block for that job.

• Block refuses the clock-on and names the check that failed. Warn lets them on and records the warning.
• The scan page can show the current issued RAMS and capture the operative’s acceptance there and then, recorded with the scan method and the IP address.
• If the job has no active RAMS, that check passes — nothing to sign is a pass, not a silent block.
• Clocking out is never gated. You do not trap someone on site with a compliance rule.

NoteAll three gates ship off by default and are configured per job in the Health & Safety module.

Yes, as a single daily digest at 09:30 emailed to the site manager for that job.

• Expected workers are the distinct people who scanned onto that job in the previous seven days.
• Anyone in that list who has not clocked in today appears in the email.
• The job needs QR attendance enabled, a site manager email and a shift start time, or it is skipped.

NoteIt is a 09:30 digest, not a real-time late alert, and it compares against who has been scanning rather than against a roster. Email only.

A live muster roll lists everyone currently clocked in and not clocked out, with how long each has been on site.

• It is the list a fire marshal reads out at the assembly point, so it is available without a module subscription.
• A record left open stays open, so a forgotten clock-out keeps someone on the roll until it is closed.