QR code site attendance and sign-in to Google Sheets — no app
With QR to Sheets, a phone at the gate scans each worker's QR badge on the way in and on the way out, and every scan writes a timestamped row to your own Google Sheet. No app, no worker accounts, no paper register to retype.
It records who was on site and when. It is not a time clock or a payroll system, and this page says plainly where that line sits.
Free for your first 300 scans on one phone, no card needed.
Updated
Short answer
To track site attendance with QR codes, print a badge code for each worker and have a gate phone scan it on arrival and departure, so every sign-in becomes a timestamped row in Google Sheets.
A free Google Form at the gate also works, but loses submissions with no signal.
QR to Sheets records presence, not payroll hours.
Replace paper sign-in sheets and shared tablets
Workers carry a badge. The register lives in Google Sheets. One phone at the gate does the rest.
One gate phone, any size of crew
A supervisor or gate attendant opens the scanner link in a phone browser and scans each worker's printed badge. Nothing to install, and nobody on the crew needs an account.
Every sign-in is a row in Google Sheets
Each scan writes the badge code, the link it came through and the time to your own spreadsheet. Map codes to names on a second tab and the sheet becomes your site register.
Keeps scans when signal drops
If the signal drops, the open scanner keeps saving scans on the phone and sends them when the signal is back, each with its original scan time. Keep the scanner page open at the gate.
One link per site, gate or direction
Create a Sign in link and a Sign out link, or one per gate. Each row names the link, so you know which entrance and which direction every scan came through.
Workers don't need access to your spreadsheet
The admin connects Google Sheets once. The scanner screen shows the scan result and nothing else: no rows, no names, no admin settings.
Presence, recorded to the second
Every scan is stamped in your workspace timezone. It is a record of who was on site and when, not a timesheet: hours and pay stay with your payroll system.
Set up your digital site register in minutes
Connect your site register spreadsheet
Sign in with Google and pick the spreadsheet that will hold the register. Set the workspace timezone in settings so times match the site clock.
Create a Sign in link and a Sign out link
Point both at the same spreadsheet. Each row names the link it came through, so the direction of every scan is explicit rather than guessed.
Give each worker a printed QR badge
Generate one code per worker from a list, print them on badges or hard-hat stickers, and keep a tab in the sheet that maps each code to a name.
Scan at the gate, in and out
The gate phone scans each badge on arrival on the Sign in link and on departure on the Sign out link. Every scan becomes a timestamped row in your sheet.
The free route: a Google Forms sign-in sheet
The free way to run a site register is a Google Form. Add a name field and an In / Out choice, link the responses to a spreadsheet, turn the form URL into a QR code and post it at the gate. Each worker scans it with their own phone camera, picks a name and submits. It costs nothing, every response arrives with a timestamp, and for a small crew on a site with good signal it may be all you need. Try it first.
Where it breaks on a site is the shift change. Forty people typing their own names at 6:58 in the morning produce queues and spelling variants that break every formula later. A submission attempted in a basement, a plant room or a remote yard with no signal is lost rather than queued. The form URL works from anywhere, so a sign-in from the car park looks identical to one at the gate. And several sites means several forms to reconcile. We build the paid alternative, so read the table with that in mind: Forms wins on cost, and a gate phone scanning badges wins on speed, on dead zones and on clean data.
| Capability | Google Forms QR code (DIY) | QR to Sheets |
|---|---|---|
| Who needs a phone | Every worker, to open and submit the form | Only the person at the gate |
| Who needs an account | Nobody, unless you restrict the form to your Google domain | The admin who connects the sheet. Never the workers |
| Cost | Free | Free for 300 lifetime scans on one phone, then 7 USD per phone per month |
| Shift change of forty people | Forty people typing names, with spelling variants that break formulas | One scan per badge, the same code every day |
| No signal at the gate | The submission fails and is lost | The open scanner keeps scans on the phone and sends them when signal is back |
| Signing in from somewhere else | The form URL works from the car park or from home | The badge has to be in front of the gate phone |
| Proves who presented the code | No | No. Someone at the gate seeing the person is the control |
A gate phone, or workers' own phones?
Two shapes work. In the first, one person at the gate holds a phone with the scanner link open and scans each worker's badge. Every row carries that worker's own code, the crew needs nothing but a badge, and the whole site is one scanning device. The free QR ID card maker prints a badge per worker from a pasted list, and QR code attendance covers the same setup for classes, trainings and events.
In the second, workers open the link on their own phones. That removes the gate attendant, but each phone counts as a scanning device, and if everyone scans the same code posted at the gate, every row carries the same value and the sheet cannot say who signed in. For a site register, the gate phone scanning individual badges is the shape we recommend.
Sign in, sign out, and the roll call
Use two scanner links named Sign in and Sign out, pointed at the same spreadsheet. Nothing alternates direction automatically, so a single link scanned twice would leave two identical rows and no way to tell arrival from departure. Our guide to setting up QR check in and check out in Google Sheets walks through the two-link layout and the formula that lists who is still on site, which is the list a fire warden needs. Keep Accept duplicate scans at Always, the default, on both links: Once ever would refuse tomorrow's sign-in, and Once a day would refuse a second visit the same day.
Presence, not payroll
A site register answers who was on site and when. It does not calculate hours, apply overtime or break rules, or produce a payroll-ready timesheet, and a spreadsheet that an admin can edit is not the right record for wage compliance. Where hours decide pay, in a unionised workplace, or where EU working-time rules require an objective and reliable system, use a dedicated timekeeping product and keep this for presence. Our guide to QR code clock in and clock out with two scanner links sets out exactly where that line sits.
The same honesty applies to proxy sign-ins. A scan proves a code was presented, not who presented it, and no QR system can prove more. The control is procedural: the person holding the gate phone sees who is in front of them as they scan.
Common questions
Do workers need to install an app or create an account?+
No. With the gate-phone setup, workers carry a printed QR badge and never touch a phone. The person scanning opens the scanner link in any phone browser, iPhone or Android, with no app and no account. Only the admin who connects the Google Sheet signs in, once.
How do I know which worker signed in?+
Each worker carries their own code, and each scan writes that code and the time to your sheet. Keep a tab that maps codes to names and look the name up with a formula. If workers instead scan one site code posted at the gate, every row carries the same value, so the sheet cannot say who it was.
How do I record sign-out as well as sign-in?+
Create two scanner links, Sign in and Sign out, pointed at the same spreadsheet. Each row names the link it came through, so the direction is explicit. The free plan allows one active link, which covers one direction only.
Can I see who is on site right now, for a fire roll call?+
Yes, as far as people sign out. A formula on a second tab that compares each badge's latest sign-in with its latest sign-out gives the list of people still on site, and a view-only share lets a fire warden open it on their phone. A scan stored on a phone with no signal appears once that phone reconnects.
What if there is no signal on site?+
If the signal drops, the open scanner keeps saving scans on the phone and sends them when the signal is back, each with its original scan time. Open the scanner before the shift starts and keep the page open, and the gate phone keeps scanning through a dead spot.
Can I use this for payroll or to calculate hours worked?+
No. QR to Sheets records presence: which code was scanned, where and when. It does not calculate hours, apply overtime or break rules, or produce a payroll-ready timesheet, and an admin-editable spreadsheet should not be the record of record for wage compliance. If hours decide pay, use a dedicated timekeeping system.
Can a worker sign in for a colleague?+
A scan proves a code was presented, not who presented it. No QR system can tell you otherwise. The practical control is that the person holding the gate phone sees who is in front of them as they scan.
What happens if a badge is scanned twice?+
By default both scans are saved and the scanner flags the second as a repeat. Keep the link's Accept duplicate scans setting at Always for site sign-in: Once ever would refuse the same worker's sign-in tomorrow, and Once a day would refuse a second sign-in the same day, such as after a break off site.
Can I run several sites or gates?+
Yes. Create a link per site or gate, each writing to its own tab or spreadsheet. One link can be open on any number of phones, and billing is per phone scanning, not per link or per worker.
What does it cost?+
Free for 300 scans in total, one scanner link, one Google Sheet and one device. After that it is $7 per phone per month with unlimited scans. One gate phone is one device however many people it scans; workers scanning on their own phones would each count as a device.
Also included
No code to scan? Collect it with a form instead.
Site sign-in is a scan, but inductions are not: contractor details, insurance numbers and safety declarations have to be typed once before anyone reaches the gate.
Build a form, share the link or embed it on your own page, and every submission lands as a row in the same Google Sheet and fires a webhook the moment it arrives, so Zapier, Make, n8n or your CRM picks it up in real time. Each person can get their own QR code by email, which you scan to record their arrival. Included with the paid plan; the free plan covers one form and ten submissions.
How forms and check-in fit togetherRelated guides
- QR code site access control and shift sign-in with Google SheetsLog who is on site, every shift, with QR codes and a Google Sheet: contractor sign-in, induction checks, and a live roll call for fire safety.Read the guide
- QR code sign-in sheet: replace the paper clipboard with Google SheetsMake a QR code sign-in sheet in minutes: a free printable poster that opens a Google Form linked to a Sheet, plus sign-out and who is still in.Read the guide
- Check in / check out with QR codes and Google SheetsA check in / check out QR code for people or equipment: two scans, one Google Sheet, and one formula that lists who or what is still out. Free to build.Read the guide
- QR code clock in and clock out into Google SheetsLog staff clock-in and clock-out in your own Google Sheet with two scanner links. The free Google Forms route, where it breaks, and why it is not payroll.Read the guide
Replace your paper site register today
Free to start. No credit card. No app for your workers.
Start for free