Web App
Vehicle service management system
A three-role workshop system — customers raise service requests, mechanics work them, admin approves, assigns and invoices.
Own buildPersonal build
01The problem
What it had to solve.
A service workshop runs on phone calls and a notebook. Nobody can say what state a vehicle is in without asking the mechanic, and the owner has no view of cost, attendance or workload until month end.
02The build
How it was put together.
- Three separate roles — customer, mechanic and admin — each with their own dashboard and permissions
- Service requests carrying vehicle details and a status workflow: Pending, Approved, Repairing, Repairing Done, Released
- Admin approval flow for both incoming requests and new mechanic registrations
- Mechanic attendance recorded per day, with salary and skill held against each mechanic
- Customer feedback capture and an admin reporting view over requests and cost
Stack
DjangoPythonSQLiteHTMLBootstrap
What it demonstrates
- Modelling a real operational workflow rather than CRUD screens
- Role-based access where three user types share one system safely
- Server-rendered Django across roughly forty templates, kept consistent
Next step
Tell us what you are trying to build.
A first call is thirty minutes, costs nothing, and ends with a straight answer about whether we are the right group for it — plus the names of the specialists who would actually do the work.