Contact person: Web-Based QR Code Event Management System

Phone:Show

Email:Show

Location: Dammam, Saudi Arabia

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Project Brief: QR Code Event Registration & Management Platform
1. Project Overview
The project is to develop a complete, web-based platform for managing event registrations and attendee check-ins using a secure, one-time-use QR code system. The platform must be multi-event, allowing an administrator to manage numerous events from a single, centralized dashboard. The system will cater to three distinct user roles: Public Visitors, Admin, and Scanners.
2. Core User Roles
The platform must support the following user roles:
• Admin: The superuser with full control over the entire system. Can create and manage events, customize registration forms, manage staff users, and view all data and statistics.
• Scanner: A limited-access staff member whose sole function is to log in and use the verification page to scan attendee QR codes at the event entrance. They cannot access any administrative data.
• Visitor: A public user who can browse active events, register for an event, and retrieve their ticket information.
3. Detailed Feature Requirements
3.1. Public-Facing Features (Visitor Experience)
• Homepage: A public homepage that displays all active events in a responsive, card-based grid. Each card must show the event's image, title, description, location, and date.
• Event Registration Page:
• Each event must have its own unique registration URL (e.g., /register/1).
• The page must display the event's title and details.
• The registration form must be dynamically generated based on the fields configured by the Admin for that specific event.
• Registration Success Page: After successful registration, the visitor is shown a success page that displays their unique QR code, event details (name, location, time), and a "Download QR Code" button.
• Ticket Lookup Page: A public page (/lookup) where a visitor can enter their National ID to find and view all tickets they have registered for across all events.
3.2. Admin Panel Features
The entire admin panel must be protected and accessible only to authenticated 'Admin' users.
• Secure Login: A login page (/login) for staff (Admins and Scanners). The system must use password hashing (e.g., bcrypt) for security.
• Admin Homepage: After logging in, an admin is directed to a central menu with two options: "Manage Events" and "Manage Users."
• Event Management (/admin/events):
• An interface to Create new events. The creation form must include fields for:
• Event Name
• Description
• Location
• Start Date & Time
• End Date & Time
• Event Image URL
• Background Image URL
• A table to Read (view) all existing events, showing their status, registration link, and a link to the event-specific dashboard.
• Ability to Update an event's status (toggle between 'Active' and 'Inactive'). Inactive events should not appear on the public homepage.
• Ability to Delete an event, which should also delete all associated registrations and form fields.
• Event-Specific Dashboard (/admin/dashboard/:eventId):
• Statistics: Display live stats for the specific event: Total Registrations vs. Total Attended.
• Attendee List: A table listing all registered users for the event, with columns for Name, Email, Status, and Registration Time.
• View Registration Details: Each user in the list must have a "View Details" link that leads to a page showing all submitted data for that user (including custom fields and National ID), as well as their QR code.
• Edit Registration Data: The details page must include an "Edit" button that allows the admin to correct any of the visitor's submitted information.
• Dynamic Form Builder: A section within the dashboard to manage the registration form for that specific event. The admin must be able to:
• Add new fields (Label, Programmatic Name, Type, Required status).
• Supported field types must include: text, email, number, and dropdown.
• For the dropdown type, the admin must be able to specify the options (e.g., "Option A, Option B").
• Delete existing custom fields.
• Export to Excel: A button to download a .xlsx file containing all registration data for the event.
• User Management (/admin/users):
• A page for Admins to perform CRUD (Create, Read, Update, Delete) operations on staff accounts.
• The creation form must include fields for Username, Password, and Role (Admin or Scanner).
• The admin must be able to change any user's password.
• The admin cannot delete their own account.
3.3. Check-in & Verification System
• Secure Verification URL: The QR code will point to a secure URL (e.g., /verify/:ticketId) that is only accessible by logged-in 'Admin' or 'Scanner' roles.
• One-Time Use Logic: Upon a successful scan, the system must update the ticket's status to USED in the database.
• Status Display: The verification page must clearly display the result to the scanner:
• Success (Green Screen): For a valid, unused ticket. It must display the attendee's full details (Name, National ID, etc.) for confirmation.
• Warning (Yellow Screen): For a ticket that has already been used.
• Error (Red Screen): For a ticket ID that does not exist.
4. Non-Functional Requirements
• Database: The application must use a persistent PostgreSQL database.
• Design: The UI must be clean, modern, and fully responsive for both desktop and mobile devices, using a framework like Tailwind CSS.
• Deployment: The application should be configured for deployment on a cloud platform like Render.
5. Deliverables
• Complete and commented source code for the Node.js/Express application.
• A [login to view URL] file with clear instructions for local setup and deployment.
• Deployment of the final application to the client's hosting provider." (client-provided description)