Web QR Student Attendance System

Job ID: 40471636

Budget: $30 – $100 NZD

I’m building a lightweight, web-based platform that lets our teaching staff track attendance without any logins, badge readers or paper sheets. Before the semester starts the team will upload or manually enter each student’s name, ID and email. The application must then create a unique, scannable QR code for every student and automatically email it to them.

During class a student will simply open the site on their phone, present the QR that was mailed to them and scan it with the phone’s camera. The system recognises the code, records the check-in against that student in a local database and stores the exact time of the scan. No further authentication is required; the QR code acts as the single source of truth.

At any moment the lecturers need to pull attendance, they should be able to hit an “Export” button and receive a clean CSV download that lists each session, student ID, name and timestamp. A minimal admin screen for uploading the initial roster, resending lost QR codes and viewing basic counts per class will round out the tool.

Deliverables
• Responsive web application (HTML5/CSS, JavaScript front end; PHP, Python or Node back end with MySQL/SQLite)
• Automatic QR code generation and email dispatch module
• Mobile-first check-in page that reads the QR via device camera (JavaScript QR reader library)
• Admin panel: roster upload, resend QR, CSV export
• Setup guide and commented source code so we can self-host on a standard LAMP/LEMP server

Acceptance criteria
• QR code emailed successfully to every student entered
• Scan marks attendance instantly and inserts a single row per event in the database
• CSV export matches database records exactly and opens in Excel without formatting fixes
• All pages load quickly on modern mobile browsers and desktop

If you’ve built similar QR or barcode systems, or have experience with libraries like jsQR, ZXing, qrcode.js, or frameworks such as Django, Flask, Laravel, or Express, that would be ideal. Let’s create a simple, reliable tool the lecturers can trust from day one.

DDL: 3 days