QR-code crew check-in
On a commercial solar site, the sign-in sheet lives on a clipboard at the gate trailer. Half the crew signs in. The other half arrives while the foreman is on the radio with a delivery driver. By...
The problem
On a commercial solar site, the sign-in sheet lives on a clipboard at the gate trailer. Half the crew signs in. The other half arrives while the foreman is on the radio with a delivery driver. By 3:30 the superintendent is writing the daily log from memory: how many electricians, how many laborers, how many from the pile-driving sub, and what they worked on.
The headcount ends up as a guess. Labor hours by cost code get reconstructed later from timecards that don't match the log. When a dispute comes up over who was on site the day a trench was backfilled before inspection, the paper sheet is illegible or missing.
The problem isn't that people won't sign in. The sign-in method is slow, unreadable, and disconnected from the daily record.
How the agent workflow works
A QR code is posted at the site entrance, laminated and mounted at scanning height. Each crew member scans it with a phone and fills a short form: name, company or crew, and the cost code or work area they are starting in. A scan at the end of the day records departure.
The agent watches the form responses as they come in. It does four things:
- Reads each new check-in and matches the name and crew against the approved roster for the job.
- Builds a running headcount by crew and cost code through the day.
- Flags anything odd: a name not on the roster, a crew with no check-in when the schedule shows them working, a check-in with no check-out, or a cost code that doesn't match the day's planned work.
- Drafts the headcount section of the daily log at a set time, say 2:30 p.m., so the superintendent has something to correct instead of something to write.
The human checkpoint is the superintendent or foreman. They review the flags, resolve unknown names, fix cost codes where a crew changed tasks midday, and approve the draft before it is saved to the daily record. The agent never posts to the log on its own and never edits payroll or timecards. It produces a draft and a list of questions.
What you need to set it up
- A form tool that can generate a QR code and write responses to a spreadsheet. Most form and spreadsheet subscriptions you already have will do this.
- A current roster of people and crews approved for the site, kept in the same spreadsheet.
- Your cost code list, entered as a dropdown so people pick rather than type.
- An AI agent or automation tool that can read the spreadsheet on a schedule and write a draft summary to a document or message.
- A laminated QR sign at each gate, plus a short note for subs explaining what to do.
Setup time is a few hours for the form, roster, and sign. Plan another few hours across the first week to tune the flag rules against real check-ins.
Where it breaks
Cell coverage. Many solar sites sit in open ground with weak signal. If the gate has no service, scans fail and people skip it. Test at the gate at 6 a.m. before you rely on it, and consider a hotspot or a printed fallback sheet.
Buddy scans. One person scans for three others, or someone scans from the truck and never enters the site. The agent can't see who is physically present. It only sees who submitted. If headcount affects safety or billing, the foreman still walks the site.
Missed check-outs. People leave without scanning out. Expect this to be the most common gap. The agent will flag it, but the fix is a foreman habit, not software.
Roster drift. A sub sends two new hires and nobody updates the roster. The agent flags them as unknown, which is correct, but a pile of daily flags gets ignored. Keep the roster current or the flags lose meaning.
Cost code errors. Crews pick the first code in the dropdown or the one they used yesterday. The agent can compare against the schedule, but it can't know a crew moved to a different task at noon.
Privacy and policy. Check-in data is time and location data on workers. Tell crews what is collected and who sees it, and confirm it fits your contract and any labor agreements.
The bottom line
This replaces the clipboard and the end-of-day guess with a draft the superintendent can verify in a few minutes. It does not replace walking the site or confirming who is really there.
Start with one gate and one crew mix for a week. Compare the agent's headcount against what the foreman counts by eye. If they track, expand it. If they don't, the gaps will show you whether the issue is signal, habits, or the roster.
Related use cases
- Meter and tool check-out log Field Ops
- Ask the drawings Field Ops
- Two-week lookahead, built not typed Management