Moving a driving school online means connecting the learner’s choice with the school’s next action. Start by separating a package selection, a booking request, a confirmed lesson, and a payment. They may be related, but treating them as the same event creates confusion for students and staff.
PermiFast provides a concrete reference: its public journey lets learners choose an agency and training package, while administrators, instructors, students, and the secretariat have separate dashboards. The planning lessons below use those confirmed capabilities. Proposed workflow rules are recommendations for a school to evaluate, not a disclosure of PermiFast’s private implementation.
Map the work that currently happens between calls
Follow one learner from the first question to the next agreed action. Who explains the package? Who checks the agency? Where is the selection written down? Who contacts the learner if something is missing? Include the paper, spreadsheet, messages, and people involved, because the handoffs are often where uncertainty begins.
Then follow an exception: a learner changes agency, a member of staff is absent, or a request arrives twice. A digital form that ignores those situations can leave the same coordination work in place, just with an extra inbox to check. Agree what should become clearer before selecting software.
Document the vocabulary. If reception calls something a booking while instructors call it a request, settle the meaning in the interface. A learner should be able to tell whether they have expressed interest, selected a package, or obtained a confirmed place without interpreting internal terminology.
Make package selection understandable on a phone
Explain what each package includes, which agency it belongs to, and what the learner should expect after choosing it. Put important conditions beside the decision, rather than relying on someone to find a separate document after submitting. The right level of detail depends on the school’s actual offer and responsibilities.
Connect the learner’s choice to someone’s next action.
Learner’s journey
& package
Agree the next action
A selection is not automatically a confirmed lesson.
Responsibility workshop
- Student
- Understand their own next step
- Secretariat
- Clarify an incomplete request
- Instructor
- See relevant assigned work
- Administrator
- Oversee the agreed process
Ask only for information needed at that step. A long form may collect details that staff cannot yet use, while a short form without enough context can trigger another phone call. Test the journey with someone unfamiliar with the school and ask them to describe what they think will happen next.
Confirmation should describe the real state. If a person must review the request, say so and explain how the learner can contact the school. Do not present a selection as a reserved lesson unless the system and operating process truly guarantee that reservation.
Give each person the view their work requires
Start with responsibilities rather than a dashboard design. Students need a clear account of their own activity. Instructors need information relevant to their work. Reception or the secretariat may need to resolve missing details and coordinate next actions. Administrators may manage the wider service. Confirm the exact boundaries with the people doing those jobs.
Different screens alone do not enforce privacy. Decide which records each role can access, whether access depends on an agency or assignment, and which actions require approval. OWASP’s authorization guidance recommends checking permissions on every request; the same rule must hold if someone bypasses the intended navigation.
Reference: OWASP: Authorization Cheat Sheet
| Person | Question to resolve | Example acceptance check |
|---|---|---|
| Learner | Which of their own records should be visible? | Another learner’s record cannot be accessed |
| Instructor | Does visibility depend on assignment? | Reassignment changes access as agreed |
| Secretariat | Who owns an incomplete request? | A pending item has a clear next action |
| Administrator | Which changes require oversight? | Important changes can be reviewed |
Swipe to compare columns, or focus the table and use the arrow keys.
Resolve booking rules before automating a calendar
If the planned system includes lesson scheduling, define instructor availability, vehicle availability, location, lesson length, travel time, and cancellation rules. A blank time slot does not necessarily mean the school can safely offer it. These are requirements to investigate, not features that should be assumed from a package-selection website.
Specify the state transitions: requested, under review, confirmed, cancelled, or another vocabulary that matches the school. Decide who can move an item between states and what the learner sees. If two people request the same resource, the server must resolve the conflict consistently; hiding the slot after a click is not sufficient.
Test reminders and notifications against these states if they are included in scope. A reminder sent for a cancelled lesson is worse than no reminder, and a failed message should not silently change the booking itself. Keep communication status distinct from the underlying operational record.
Plan the move with the people running the school
Choose what information must be carried into the new system and what can stay in an archive. Clean a representative sample, check duplicates, and agree who signs off the imported records. Retain a workable reference to the previous process until the school is confident it can operate the new one.
Introduce a limited workflow or agency first if that fits the business. Give staff a safe way to practice, define who handles exceptions, and write a short operating guide around real tasks. Running paper and software side by side indefinitely can create conflicting records; decide which source takes precedence and when the temporary arrangement ends.
The rollout needs a named business owner. They can resolve conflicting requests, make policy decisions, and ensure that feedback from instructors and the secretariat reaches the development team. Software cannot independently decide a school’s cancellation policy or staff responsibilities.
Read the outcome with its attribution intact
In his approved testimonial, Ahmad Raza, Owner of PassPermisFacile Driving School in France, reported approximately 180 online package selections in the first month and phone bookings dropping by half. These are the client’s reported results, not independently audited measurements or a prediction for another school.
The practical takeaway is to measure the handoff you intend to improve. A school could track completed selections, incomplete requests, duplicate contacts, and staff time spent resolving missing information. Define each measure and its starting point before rollout; otherwise a change in demand can be mistaken for a change caused by the software.
The same review described a first-version problem with CPF forms that the team fixed. That is a useful reminder to test real administrative cases, keep a reporting channel open, and plan the work after the first release. An honest rollout plan includes the possibility of corrections.
Bring a process brief, not a wish list
A useful brief describes agencies, packages, staff responsibilities, current tools, and one complete learner journey. Include anonymized examples of a straightforward request and a difficult one. Identify the information that is sensitive, who should see it, and any existing software that must remain in place.
Separate the public website, operational dashboards, and any future scheduling or payment work. They can be planned together without pretending every part belongs in the first release. Ask a supplier to demonstrate the handoffs and failure states, then agree acceptance with the people who will run the system.
- Define selection, request, reservation, and confirmation in plain language.
- Assign a business owner to every unresolved request.
- Agree access boundaries for every role and agency.
- Test real administrative exceptions with non-sensitive data.
- Plan migration, staff practice, support, and measures of success.
Further context
Sources & project evidence
Platform guidance changes. Consult the linked primary documentation when planning an implementation. Project details come from the linked Zyrox case studies; general recommendations are editorial guidance.
- OWASP: Authorization Cheat Sheet
Primary reference for server-side authorization. Project facts and client-reported outcomes are linked to the PermiFast case study and approved review.