Mobile Repair Queue Status Board

A busy phone repair counter runs on a paper job sheet and the technician's memory. Customers call repeatedly to ask "is my phone ready?", technicians lose track of which jobs are waiting for parts, and nobody knows the real queue order. This project builds a digital queue system with three views. The front-desk display shows live columns — Received, In Repair, Ready for Pickup — with token numbers, devices, faults and progress, plus a "Now Serving" call. Technicians log in to see only their assigned jobs, update statuses, and record parts and customer approvals. Customers enter their token on the website and get a timeline: received, diagnosed, estimate approved, repair in progress, QC passed — with ETAs and warranty terms. The design goal is a realistic small-business system with proper role separation, built on plain PHP/MySQL so every query and state transition is explainable in a viva.

1. The counter staff creates a job: customer name, device, reported fault — the system issues the next token number and prints the job sheet.
2. The job appears in the Received column of the live board; a technician is assigned and starts diagnosis.
3. After diagnosis the technician records the fault found and an estimate; the job waits in "awaiting approval" until the customer approves.
4. On approval, repair begins — the technician updates progress, and the board's In Repair column reflects it with the ETA.
5. Finished jobs go through a QC checklist; on pass, the job moves to Ready for Pickup and the customer is notified.
6. The customer picks up the device, pays the balance, and the token leaves the active queue into history.

Tech stack:

• PHP 8 (backend)
• MySQL (jobs, customers, technicians, parts, timeline events)
• HTML5, CSS3, JavaScript (front end, auto-refresh board)
• Role-based sessions (manager, technician, counter)
• Printable job-sheet layout (CSS print)

• [Live queue board] A big-display view with Received / In Repair / Ready columns, token numbers, device and fault details, per-job progress bars and a "Now Serving" announcement panel.
• [Token lifecycle] Every job gets a token (T-1087…) that moves through defined states — received, diagnosed, awaiting approval, in repair, testing, QC passed, ready — with timestamps at each step.
• [Technician work view] Role-based login showing each technician only their jobs, with actions to start repair, mark QC, request parts and add notes.
• [Customer token tracker] No-login lookup: enter a token and see the full repair timeline, agreed estimate, warranty terms and technician contact.
• [Estimate & approval flow] Estimates are sent to the customer (simulated SMS link in the demo) and the job proceeds only after approval is recorded.
• [Parts inventory states] Jobs can be flagged waiting-for-part, and parts availability is tracked per job so counters stop promising impossible ETAs.
• [Daily stats] Jobs received, completed, average turnaround and technician workload on the manager view.

• Complete web app source (board, technician view, tracker, manager stats)
• MySQL schema with a sample repair shop's data
• Printable job-sheet template
• Project report PDF (requirements, state machine, ER diagram, screenshots, testing)
• PPT presentation for final review
• Viva Q&A preparation document (queues, state machines, roles, polling vs websockets)