This template applies the four-block method — THE THINGS, THE LINKS, THE STATES, THE NUMBERS — to the driving school. It's filled in for a school with three instructors and two vehicles: the example shows how to describe a student's journey, from enrolment to exam, without ever describing a screen.
The trade's accounting heart is the package: a student buys hours, each lesson draws one down, and the typical dispute is born from a fuzzy count. The THINGS block makes that count mechanical: the recorded lesson decrements, the record shows the balance, nobody argues.
Filled with your vocabulary, this text briefs a developer — or is submitted as-is to Blueprint Maker, which turns it into an application plan you validate, then a generated application: database, screens, dashboard and demo data.
The template to copy
My business: driving school, three instructors, two vehicles, one person at the desk running the schedules. THINGS tracked: - Students (name, phone, enrolment date, course — standard licence, accompanied driving) - Packages (student, hours purchased, hours consumed, amount, paid or pending) - Lessons (date, time, student, instructor, vehicle, done or not) - Instructors (name) - Exam sittings (student, type — theory, driving —, date, result) LINKS: - A package belongs to a student. - A lesson commits a student, an instructor and a vehicle, and draws one hour from the package. - An exam sitting concerns a student. STATES of a student: enrolled, theory in preparation, theory passed, driving, presented at exam, passed, archived. NUMBERS to see every morning: - Today's schedule per instructor - Packages under 2 remaining hours - Exam sittings in the next 30 days - Exam passes this month
Adapting this template to your school
- Your formulas: standard licence, accompanied driving, refresher — keep your real names, they'll structure the records and filters.
- The hour count: decide whether a late-cancelled lesson draws down or not — write the rule in the template, it will apply mechanically and show on the record.
- Teaching progress: if you track competencies (parking, motorway, night), add them on the lesson — the student record becomes a progress logbook readable before the exam.
- Vehicles: when a vehicle is immobilised (service, breakdown), it must show in the schedule — add a simple state on the vehicle.
- Official administrative filings stay on dedicated tools: this register is your internal tracking — the code being exportable, a developer can add integrations if needed.