Did you know? A teacher can display one QR code on a projector and ask a room of learners to scan it. Minutes later, an attendance dashboard may list who checked in. But the squares cannot see who is seated in the room, whether the person stayed for the lesson or whether they understood the subject.
Quick answer: an attendance QR code often points to a session-specific check-in page. The learner scans it, completes the required identification or submission steps, and the attendance system records the event. More robust systems use identity checks, time limits or other controls to reduce false records. Scanning alone is not necessarily verified attendance or evidence of learning.
The 30-second explanation
- Organiser creates a session: a class, training course or workshop has a time and participant list.
- QR code is displayed: the code links to the appropriate attendance workflow.
- Learner scans: a phone camera opens the session page.
- Verification happens: the service may require login, identity confirmation, a time check or other approved evidence.
- Attendance is submitted: a successful record is stored for the appropriate session.
- Staff review exceptions: missing, duplicate and disputed records need an official correction or appeal process.
A QR code does not take attendance by itself
Think about the old-fashioned attendance sheet. The teacher writes the students’ names, then marks who is present. A QR system replaces part of the input process: students can submit a check-in through a digital form instead of having an administrator enter each name manually.
But the meaning of the data still depends on the system’s checks. A basic public form may ask only for a name. Someone could type a classmate’s name without being in the classroom. A more carefully designed system can require authentication, enforce a session time window and check that the learner’s record matches the correct class.
The QR code provides a convenient path into that system. It does not automatically solve identity verification, educational quality or privacy.
Step 1: Every session needs an identity of its own
Suppose a science enrichment course meets on four consecutive Saturdays. An attendance system should know which date and class the learner is checking into. If the same generic QR code links to the same unchanging form for every week, organisers need some other reliable way to distinguish the sessions.
A session-specific link can contain or reference an identifier associated with that particular lesson. In other designs, the code or link can change over time. The software should check that the session is active and that a submission is allowed according to the organiser’s rules.
It is important not to call all such codes “secure” simply because they change. A rotating QR code helps only when the server properly validates the session and the user.
Step 2: The learner opens the check-in page
A phone reads the code and opens the link. The page may identify the course and require the learner to complete a check-in. A simple classroom poll may only collect a name and time. A regulated training programme can require a more structured identity-verification procedure.
Learners should verify that the destination belongs to their school or training provider before entering personal details. A code displayed by an authorised instructor is a useful context clue, but a malicious replacement image or false sign can still lead to an unrelated website.
Singapore example: SkillsFuture e-attendance via Singpass
A real-world example is the SkillsFuture Singapore (SSG) e-attendance process for registered training providers, described in official TPGateway guidance. This is a specific arrangement for applicable training courses, not a claim that every primary or secondary school in Singapore uses Singpass for class attendance.
SSG announced an enhanced QR process effective 26 July 2025. Its circular explained that multiple trainees could scan the displayed code at the same time, and that the code could be read using a phone camera or ordinary QR scanning app, rather than requiring the Singpass app itself to scan the code.
After opening the relevant attendance flow, the learner follows the supported authentication and submission steps. TPGateway explains that a session’s attendance is complete only after the trainee successfully scans and completes the required e-attendance process. Opening the link but stopping before the last submission step is not equivalent to a recorded check-in.
Why the login step matters
Consider a class where everyone types their own name into a public form. If someone enters another learner’s name, the form may have little independent evidence of who really submitted it. An authenticated process can connect a submission to an account whose identity has been verified according to the service’s rules.
Singpass is a Singapore digital identity service, so an applicable course can use the login flow as part of verifying who submitted attendance. But the existence of Singpass does not mean the QR code knows whether the person participated throughout the entire lesson. The organiser and service still apply attendance rules and procedures.
Different school and private training systems use other methods, and some rely on teacher confirmation. The right design should match the educational and regulatory purpose instead of collecting more information than necessary.
Why session timing is important
A class attendance record should describe the right lesson, not simply a learner’s ability to open a webpage someday. Training systems may limit when a QR code can be used or display refreshed codes. SSG guidance describes time validity and session-specific e-attendance controls.
Imagine a code from last week’s lesson is forwarded in a class chat. A robust service should not blindly record a new attendance just because an old pattern is still readable. It needs to check the current session and whether the submission is authorised.
As with a one-entry event ticket, the image is unchanged or readable and the permission to use it are separate facts. The database defines the second one.
Can classmates share a QR image?
A photo can reproduce the visible squares perfectly. Whether another person can use it depends on the surrounding controls. If a public form accepts any name, sharing the image may make false check-ins easier. If the service requires authenticated identity, a session window and appropriate attendance rules, the risk may be reduced.
For funded training, SSG’s published FAQs and training-provider guidance emphasise attendance integrity and limitations on misuse. Learners should follow the provider’s procedures, scan only for sessions they actually attend as required and never share credentials or submit attendance on behalf of another person.
One technical caveat: even a correctly logged check-in is not a universal proof of continuous physical presence. A responsible provider may need additional evidence or instructor oversight according to the course’s actual requirements.
What about online classes?
QR e-attendance can also appear in synchronous online learning. The learner may see a code on a laptop screen and use a mobile device to access the attendance flow. SSG’s enhanced process also introduced a way for learners in certain circumstances to click a code or link rather than needing a second camera device.
The exact workflow depends on the training mode. A live online class, an in-person lesson and an asynchronous course are not interchangeable. A system should associate attendance with the right type of participation and apply the relevant requirements.
If a student cannot scan because of a camera fault, device limitation or connectivity failure, the provider should direct them to the official technical-support or alternative attendance procedure. Do not assume that a chat message saying “I was here” automatically satisfies formal funding or audit rules.
A good attendance system collects only necessary data
Attendance information can identify individuals, their schedules and their participation in an educational activity. It deserves appropriate privacy protection. The provider should explain what is being collected, why it is needed, who can see it and how long records are retained under applicable rules.
Avoid putting a full roster or sensitive student details inside a publicly displayed QR code. The code may be photographed and redistributed. Use an authenticated server to associate the session with the learner rather than exposing personal data in the visible pattern.
For younger students, parents and educators should pay particular attention to whether a check-in requires personal accounts, geolocation or unnecessary contact information. Convenience should not create disproportionate privacy costs.
What if a learner appears absent even after scanning?
- Check completion: did the learner finish the final attendance submission or only open the page?
- Check the session: was the code for the correct course, date and class?
- Check connectivity: did the service confirm receipt, or did the phone stop before the request completed?
- Check policy: were there timing, location or authentication requirements?
- Use official support: report errors promptly through the school or training provider’s approved process.
TPGateway’s attendance FAQ explains how training providers can review e-attendance records and what to do when technical difficulties require an official alternative route. A provider should use current guidance rather than secretly altering audit records.
Why attendance and learning are different
There is a bigger educational idea here. A QR check-in can record that someone completed an attendance workflow. It does not show whether they can solve a mathematics question, explain a science concept or apply what they learned in a new context.
Good teaching uses other evidence: explanations in a learner’s own words, checked practice, feedback, retrieval over time and application in unfamiliar questions. Attendance data is useful for administration, but it should never be confused with a full measure of progress.
For an example of how lesson design and diagnostic feedback differ from simple attendance, read Secondary 1 Mathematics Tutor Clementi | Small Groups Tutorials.
A five-minute classroom experiment
Draw a row of five fictional learners. Give each a session ID and three columns labelled code scanned, identity confirmed and attendance submitted. Create three scenarios: a learner opens the page but forgets to submit; another scans an old screenshot; a third signs in and completes the process.
Which cases should appear as successful attendance? What extra rules would you want for a real class? Now add a fourth column labelled understood today’s lesson. Can the check-in system fill that last column automatically? No. This simple exercise explains the difference between administrative records and learning evidence.
Questions readers often ask
Does scanning a classroom QR code always mark attendance?
No. It may only open a check-in form. Many systems require authentication, session selection or an explicit final submission.
Do Singapore schools all require Singpass QR attendance?
No. The official Singpass e-attendance guidance discussed here applies to certain SSG training-provider workflows. School attendance methods differ.
Can a time-limited QR code stop all false attendance?
Not by itself. It can reduce some forms of reuse, but reliable records also depend on identity verification, policy and appropriate oversight.
Does a successful QR check-in prove a student learned the material?
No. It provides attendance-related evidence according to the system’s rules. Understanding needs separate educational assessment.
The idea to remember
QR attendance is a fast entry point into a recordkeeping process. The real work is in the verified identity, correct session, successful submission and responsible use of that record. The code should make administration simpler without pretending that attendance is the same as learning.
Continue with How Event Tickets and Check-In Prevent Reuse, How a Phone Signs In to a Computer and Scan Safely and Spot QR Code Scams.
Sources and further reading
- SSG: Enhanced QR Code for Singpass E-Attendance (July 2025) — supported scanning and enrolment workflow.
- TPGateway: Attendance FAQ — when digital attendance is recorded and how exceptions are handled.
- SSG: Identity Verification for Singpass E-Attendance — enrolment and training-session distinctions.
- Singapore Police and CSA: Protecting Yourself From Malicious QR Codes — safer scanning habits.
Explore the How QR Codes Work series
These guides connect the mathematics of QR codes with the everyday services that use them. Choose the question you want to explore next.
How QR technology works
- How a Square Stores Words, Links and Numbers
- Why a Damaged Code Can Still Scan
- Static vs Dynamic QR Codes Explained
- Scan Safely and Spot QR Code Scams
- Why Cameras Can Read Tilted and Rotated Codes
- Why QR Codes Have Different Sizes and Versions
Everyday use cases
- How Scan-to-Pay Connects to Banks and Wallets
- How Event Tickets and Check-In Prevent Reuse
- Share Wi-Fi Without Typing a Password
- How Product Packaging Connects to Digital Information
- Share Contacts and Calendar Events Without Typing
- How Authenticator Apps Set Up Two-Step Verification
- From Restaurant Menus to Kitchen Orders
- How Parcel Lockers Verify Collection and Returns
- How a Phone Signs In to a Computer
- Museums, Exhibits and Public Information
- Boarding Passes and Airport Gate Scanning
- Warehouse Inventory and Stock Tracking
- CDC Vouchers and One-Time Redemption
- Verify Digital Certificates and Education Records
- Library Books, Borrowing and Digital Catalogues
- Digital Receipts and Warranty Registration
- School Worksheets, Homework and Learning Videos
- Hospital Visitor Passes and Clinic Check-In
- Cross-Border Payments and Currency Conversion
- Food Traceability, Batch Numbers and Recalls
- Train Tickets, Fare Gates and Contactless Cards
- Charity Donations and Safer Giving in Singapore
- EV Charging Stations and Payment Sessions
- Equipment Maintenance and Inspection Records
- Printing, Colours, Logos and Design Mistakes