The two models: employee scans the site, or the site scans the employee

Every QR code attendance system uses one of two arrangements, and choosing the wrong one for your workforce is the most common reason deployments stall. In the first model, a QR code is displayed at the site (a printed poster at the gate, or a code on a tablet screen) and each employee scans it with the attendance app on their own phone. The app already knows who the employee is because they are logged in; the scan proves they were at the code's location at that moment.

In the second model, the arrangement is reversed. A tablet or phone in kiosk mode at the gate runs the attendance app, and each employee presents a personal QR code, on a printed ID card or on their own phone screen, to the kiosk camera. Here the kiosk knows where it is, and the scan proves who arrived. This model works when workers do not carry smartphones or when the company does not want to install an app on personal devices.

The choice follows the workforce. Office staff, field teams and supervisors with their own phones suit the first model. Daily-wage labour, housekeeping teams, canteen staff and visitors suit the second. Many companies run both: staff scan the site code, while contract workers present their card to a kiosk at the same gate. The QR code attendance glossary entry summarises the terminology.

• Model A: site displays QR, employee scans with their phone; identity comes from the login
• Model B: kiosk scans the employee's QR card or phone; location comes from the kiosk
• Pick by whether workers reliably carry a smartphone with data
• Running both models at one gate is normal for mixed staff and contract workforces

Static versus dynamic QR: why printed codes get photographed and shared

A static QR code encodes a fixed value, such as a site ID. It is cheap to print and never changes, which is exactly its problem. Within a week someone photographs the poster at the gate and forwards it on WhatsApp, and from then on a colleague can 'arrive' at the site from home by scanning the photo on their own screen. The attendance record shows a valid scan of the correct site code at 08:58, and nothing distinguishes it from a real one.

A dynamic or rotating QR code changes at short intervals, commonly every 30 to 60 seconds, because it encodes a time-based token generated by the app running on the site tablet or by the server. A photograph of the code is useless within a minute. This is why serious QR attendance systems display the site code on a screen rather than a poster, or, where a poster is unavoidable, pair the static code with a second check such as GPS.

For Model B, where the employee presents a personal QR, the equivalent risk is card lending: a worker hands his ID card to a friend who scans it on his behalf. Dynamic personal codes generated on the worker's phone help, but the cleaner fix is a photo or face capture at the kiosk when the card is scanned, so the register shows who actually stood in front of the camera. The guide to stopping buddy punching covers these proxy patterns across methods.

• Static printed codes will be photographed and shared; assume it, do not hope otherwise
• Rotating codes on a screen expire in seconds and defeat the photo
• For personal QR cards, capture a photo or face at the kiosk to defeat card lending
• If you must use a printed static code, pair it with a GPS check on the scanning phone

Pairing QR with GPS and selfie for a trustworthy punch

A QR scan on its own answers one question: was this device pointed at this code at this time? It does not, by itself, prove the person was who they claim, or that the code was where it should be. Layering solves this. In Model A, the app can record the phone's GPS position at the moment of the scan and check it against the site's geofence, so a scan of a photographed code from home fails the location test even if the code itself was valid. Adding a selfie with liveness at the moment of scan ties the punch to a face.

In Model B, the kiosk is fixed, so location is not in doubt, and the weak point is identity. Capturing a photo at the scan, or running face verification against the enrolled worker, closes it. For a construction site processing 200 labourers at 08:00, the practical setup is a tablet in kiosk mode at the gate: the worker presents the card, the kiosk scans, snaps a photo, and the supervisor can review a grid of faces against names at the end of the day.

The combination you choose should match the cost of a wrong punch. For an internal training hall, a scan is enough. For a client-billed security post or a daily-wage muster roll that drives payment the same evening, QR plus GPS or QR plus photo is the minimum. The QR code attendance system and attendance kiosk mode pages describe how these layers combine in a single punch.

• Model A: QR + GPS geofence check on the scanning phone; add selfie for high-value roles
• Model B: QR + photo or face capture at the kiosk to prove identity
• Match the layers to the payroll or billing consequence of a false punch
• Give supervisors an end-of-day photo grid to spot card lending fast

Where QR attendance fits best

QR attendance shines where face terminals are too expensive per site and per-person phone apps are unrealistic. Construction plots, warehouses with daily-wage loaders, agricultural processing units and housekeeping teams at housing societies often have workers without smartphones or with phones that have no data. One tablet in kiosk mode and a stack of printed QR ID cards covers the whole site, and the cards double as the digital ID the contractor needs anyway.

Gates that handle visitors and contractors benefit because a QR pass can be issued in advance and scanned on arrival without enrolling anyone in a biometric system. A vendor's electrician visiting for two days gets a time-limited QR pass, scans at the gate, and appears in the visitor log with entry and exit times and the host who approved him. The same mechanism handles temporary event staff, where a promoter agency deploys 80 people for a three-day exhibition and needs attendance by shift for payment and client billing; the event staffing attendance app use case is built on exactly this.

Training halls, induction sessions and toolbox talks are a quieter but valuable use. A rotating QR on the trainer's screen, scanned at the start and end, produces a signed attendance record for the safety audit without a paper sheet being passed around. Schools and coaching centres use the same pattern for staff attendance across multiple buildings.

• Sites where many workers lack smartphones or data: one kiosk, printed cards
• Visitor and contractor gates using pre-issued, time-limited QR passes
• Event, exhibition and promotional staffing with shift-wise attendance for client billing
• Training, induction and safety briefings needing audit-ready attendance

Setting up: steps, printing and placement

Setup begins with defining sites and, for each, whether it will use a displayed site code, a kiosk, or both. For a displayed code, decide whether it will rotate on a screen (a tablet or an old Android phone mounted at the gate is sufficient) or be printed. For a kiosk, choose a tablet with a decent front camera, a wall or stand mount at roughly chest height, a power supply and a protective case; a dedicated device rather than the supervisor's personal phone, because the supervisor will take it home.

Generate employee QR codes from the attendance system so each code carries a unique, non-guessable identifier tied to the employee record, never the employee's name or phone number in plain text. Print them on laminated ID cards or issue them digitally to workers with phones. For sites with contractors, issue cards per contractor with a distinct colour band so a supervisor can see at a glance which agency a worker belongs to.

Placement decides throughput. Put the kiosk or displayed code where the queue can form without blocking the gate, under a shade so screen glare does not defeat the camera, and with light on the face of the person scanning rather than behind them. Test at the actual shift start time with the actual crowd; a setup that works for five people at 11:00 may collapse for 150 people at 07:55.

• Define per site: rotating screen code, printed code, kiosk, or a combination
• Use a dedicated mounted tablet for kiosks, with power and a protective case
• Generate QR IDs from the system; never encode names or phone numbers in the code
• Place at chest height, out of glare, with light on the scanner's face; test at peak time

Offline handling and reporting

Sites that suit QR attendance are often the sites with the worst connectivity: basements, remote plots, industrial estates on the city edge. The system must record scans locally when the network drops and sync them with the original timestamp when it returns. Ask the vendor specifically whether the kiosk continues to accept scans offline, whether rotating codes keep rotating offline (time-based codes can, server-generated ones cannot), and how conflicts are resolved if the same person scans twice during an outage. The offline attendance app page explains the sync model.

Reports are where QR attendance earns its place. Because each scan carries a site, a person, a time and optionally a photo and GPS result, the system can produce a daily site muster showing who is present by contractor, a late and early-exit list against shift timings, a man-hours summary per site for client billing, and an exception list of scans that failed the GPS or photo check. Supervisors should see the day's grid on their phones, not wait for HR to send an Excel sheet.

For contract labour, the daily site muster doubles as the register the principal employer must keep, which the guide to tracking attendance of contract workers explains. Export in CSV or Excel to feed the contractor's wage sheet and the principal employer's compliance file.

• Require offline capture with original timestamps and automatic sync
• Confirm rotating codes and kiosk scanning keep working during outages
• Daily outputs: site muster by contractor, late/early list, man-hours per site, exception list
• Export to CSV/Excel for contractor wage sheets and principal-employer records

Limitations to be honest about

QR attendance proves a scan, not a person, unless you add photo, face or GPS layers. A static code is a shared password. A kiosk is a single point of failure if the tablet is stolen, uncharged or taken home by a supervisor. Scanning one at a time is slower than a face terminal that recognises people as they walk past, so a gate handling 500 workers in ten minutes will need several kiosks or a different method. Printed cards get lost, laminated cards fade, and reissuing them is a recurring administrative chore.

QR also tells you nothing after the scan. A worker who scans in at 08:00 and leaves at 09:00 shows a full day unless there is a scan-out rule enforced with consequences, or mid-shift checks. For guard posts and other presence-through-the-shift roles, QR at the gate is a complement to patrol checkpoints and GPS, not a replacement.

Used within these limits, QR is one of the most cost-effective ways to bring a smartphone-poor workforce onto a digital register. Attend Mitra includes QR check-in and kiosk mode alongside its GPS, geofencing, face and offline capabilities, so a site can start with QR cards and a tablet today and add face verification or GPS checks later without changing the register. Compare it with the other options in attendance machine versus attendance app.

• A scan is not identity; add photo, face or GPS where the punch affects pay or billing
• Kiosk throughput is limited; multiple kiosks or face terminals for very large gates
• Enforce scan-out and use mid-shift checks for roles paid for continuous presence
• Budget for card reissue and a spare tablet per site