Short answer. Driving school software in Algeria in 2027 holds five things. A candidate file: enrolment, documents, chosen package, instructor, instalments, hours counter, skills grid. Theory revised in the app, series and mock test, without network at home, with progress the instructor and management can see. A schedule where a slot exists only once, for one instructor and one vehicle: booking, cancellation per the written rule, WhatsApp reminder the day before, an immobilised vehicle that moves its lessons before candidates leave home. A lesson checked in by the instructor on their phone as it starts, without network, and rated at the end on the grid management wrote; a no-show is counted by the rule, not by mood. Instalments collected at the desk or online from France, each with a receipt, reminded before the due date, with a written rule that blocks the next lesson until the due instalment is collected. And a management view that reads occupancy per instructor and vehicle, hours actually done, no-shows, immobilisations, and exports to the accountant.
This guide is for the manager of a driving school with two to ten vehicles, the group opening a second one, and the founder living in France who passed their licence with an app where you choose the time, the instructor and the meeting place, and who wants to build the same for Algeria. In the common description, a driving school is an establishment giving theory and practical training for the highway code and driving, for the licence category sought; in France, the platforms on that market offer online theory with series and a progress dashboard, lessons booked in the app, and payment in several instalments. This guide builds the equivalent for an Algerian driving school, with what changes: cash at the desk, the network dropping mid-lesson, WhatsApp before the app, and the father paying from Lyon. It does not cover licensing rules, the official syllabus or the exams: the application schedules, counts and collects what management writes, and the twenty-lesson package in the example is a manager’s rule, not a standard.
Driving school software, in five layers
The schedule is the accented layer: a slot exists only once, and everything else, the checked-in lesson, the counter, the instalments, occupancy, follows from it.
Candidate file. One enrolment per candidate with documents, the chosen package, twenty one-hour lessons in the example, the assigned instructor, the gearbox, the planned instalments, the hours counter and the skills grid; what the private school guide describes for a pupil, plus a vehicle and a counter. Theory. Series and sheets live in the candidate’s app, downloaded once and played without network per the offline application guide; each completed series goes up when the network returns, with its score, and the instructor sees before the lesson where the candidate stands. Schedule. One schedule per instructor and per vehicle, not one notebook per instructor: a slot is a single row, instructor, vehicle, hour, candidate; two bookings on the same row are impossible by construction, not by vigilance; a cancellation follows the written rule, before so many hours it does not count, after it counts; the reminder goes out the day before per the notifications guide.
Lesson. The instructor checks the start in on their phone, without network, and fills the grid at the end: eight skills in the example, acquired, in progress, not seen, written by management; a no-show is checked in as such and counted by the rule; every check-in says who and when, per the roles guide. Instalments and management. Instalments are collected at the desk or online from France per the two-currency guide, each with a receipt sent to the payer and the candidate; the due date is reminded beforehand, and the written rule blocks lesson fifteen until the third instalment is collected; management reads in their board occupancy, hours done per instructor, paid on actuals, no-shows, immobilisations, and exports to the accountant per the integration guide.
One candidate’s path: theory, twenty counted lessons, skills grid, instalments
The figure follows a candidate enrolled on 12 January, from theory revised without network to the third instalment reminded on 25 February.
Theory: one thousand four hundred and twenty questions done in the app, six hundred and forty of them without network; last mock test thirty-six of forty; theory exam on 9 February, passed; the instructor saw the progress before the first lesson. Lessons: twenty boxes, one per lesson; fourteen done with their date and the grid score rising from three of eight to seven of eight; two cancelled in time, not counted; one no-show on 30 January, counted because the written rule says so; three remaining. The grid: five skills acquired, two in progress, one not seen, driving in rain, which the instructor schedules first.
Instalments: fifteen thousand dinars on 12 January at the desk, receipt; thirteen thousand on 2 February, paid online by the father from Lyon, receipt to the father and the candidate; ten thousand due on 1 March, WhatsApp reminder sent on 25 February; and the written rule that blocks lesson fifteen until that instalment is collected, shown to the candidate when they try to book. Twenty-eight thousand collected of thirty-eight thousand, and nobody recounted in a notebook. Candidate, dates, prices and figures are a constructed example; the package, the price and the grid are the ones management writes.
«Each lesson is counted by the written rule, rated on the grid by the instructor, and paid by an instalment with a receipt; the candidate, her father in Lyon and management read the same counter.»
Six real situations, and what the application does
Each row is a sentence heard in a driving school, and the answer is a written rule and a single slot, not a better-kept notebook.
The candidate does not show up: the reminder went out the day before; the no-show is checked in by the instructor and counted per the written rule; the slot is reopened and offered to the first on the day’s waiting list. Two candidates at the same hour: impossible, because a slot is a single row per instructor and vehicle; the second booking is refused on screen, not discovered in the car park. “How many hours do I have left?”: the candidate’s counter, done, cancelled in time, no-shows counted, remaining, is in their app and in their father’s; the desk no longer recounts.
The father pays from France: the instalment is paid online in euros, the dinar amount is frozen at invoice, both collections are matched, and the receipt goes to the father and the candidate. The vehicle breaks down: management declares it immobilised for the day; the seven lessons are moved to free slots on the following days; candidates are told at 7:40 by WhatsApp, before leaving home. The candidate wants to revise theory at home: series are in the app, without network; each series goes up with its score, and the instructor sees before the lesson what was done.
The week’s schedule: three instructors, three vehicles, six days
The figure is the schedule management reads on Saturday morning and on Tuesday at 7:30, when vehicle B does not start.
The grid: three instructors, each with their vehicle, eight slots a day, six days; each cell says booked over capacity, cancellations in time, no-shows counted; a full cell is gold. Tuesday: vehicle B is immobilised, garage; its seven lessons are moved, four to Wednesday and three to Thursday, onto the slots Nadia still had free; the seven candidates are told at 7:40, and none travelled for nothing. Totals: one hundred and eighteen lessons scheduled over one hundred and forty-four slots, eighty-two percent occupancy; nine cancelled in time, not counted; four no-shows counted; twenty-three day-before reminders; zero duplicates; one hundred and eighteen instructor hours, paid on what was checked in, not on the notebook.
What management does with it: it sees that Yacine, automatic gearbox, is at seventy-five percent while automatic candidates are waiting; it sees Thursday is quiet for Karim, and opens Thursday slots to the waiting list; it sees no-shows per candidate, and applies the written rule without argument. Instructors, vehicles and figures are a constructed example.
«A slot exists only once, for one instructor and one vehicle; a cancellation follows the written rule, and an immobilised vehicle moves its lessons before candidates leave home.»
Putting a driving school under software, in six beats
Scheduling is the accented beat: one slot per instructor and vehicle, and everything after it is only a reading.
Write the rules: packages and their hours, instalments and due dates, the cancellation rule, the rule that blocks a lesson without a collected instalment, the skills grid, slots per day and per instructor; with the manager, without code. Take over the files: current candidates with hours already done, instalments already collected, their instructor; a take-over in one week with the desk, each opening balance signed by the candidate. Schedule: a single slot per instructor and vehicle, booking by the desk or by the candidate in the app, cancellation per the rule, day-before reminder, the day’s waiting list.
Check in and rate: the instructor checks the lesson start in and fills the grid at the end, on their phone, without network; a no-show is checked in as such. Collect and remind: instalment by instalment, receipt every time, reminder before the due date, payment from France, accounting export; reminders go out through a background job per the background jobs guide. Read the board: occupancy per instructor and vehicle, hours done, no-shows, immobilisations, late instalments, Saturday morning review.
Driving school software in 2027, in weeks
Six weeks, the first without code, and two for the schedule and lessons, because the counter, instalments and the board are only readings of what was scheduled and checked in.
- What the manager sees: on Saturday, the week’s occupancy per instructor and vehicle; every morning, yesterday’s no-shows and late instalments; on Tuesday at 7:30, an immobilised vehicle with its lessons already moved.
- What the desk stops doing: keeping three notebooks, booking two candidates at the same hour, recounting hours by phone, collecting without a receipt, calling eight candidates one by one when a vehicle breaks down.
- What is measured: occupancy per instructor and vehicle, hours done, cancelled in time, no-shows counted, reminders, instalments collected on time, immobilisations, theory series done per candidate.
Week 1, rules and files: packages, instalments, cancellation rule, grid, slots; current candidates taken over with signed balances. Weeks 2 and 3, schedule and lessons: single slot per instructor and vehicle, booking, cancellation, day-before reminder, day’s waiting list; offline check-in and grid on the instructor’s phone; immobilised vehicle and moved lessons. Week 4, theory: offline series and sheets, mock test, progress seen by the instructor and management.
Week 5, instalments: collection with receipt, reminder before the due date, payment from France, written block of the lesson without instalment, export to the accountant. Week 6, management: occupancy, instructor hours paid on actuals, no-shows, immobilisations, Saturday review. A driving school that wants to equip other schools then builds the subscription layer of the SaaS guide, same rules, one schedule per school. The agent of the WhatsApp agent guide then answers “when is my next lesson?” from the schedule, never from memory.
- Does driving school software in Algeria start with the candidate’s app?
- No, with the schedule. A slot exists only once, for one instructor and one vehicle; that is what makes the counter right, the instalments computable and occupancy readable. The candidate’s app comes afterwards, to book into that schedule, read their counter and revise theory; the first week, reminders and confirmations go through WhatsApp.
- How is a no-show counted?
- By the rule management writes, for example: a cancellation more than twenty-four hours before does not count, less than twenty-four hours counts one lesson, a no-show without cancellation counts one lesson. The instructor checks the no-show in on their phone, the application applies the rule, and the candidate sees it in their counter with the reason. The notice period and the rule are the manager’s, not the guide’s.
- And when the instructor has no network during the lesson?
- They check in anyway: local database on their phone, queue, unique id per check-in; when the network returns everything goes out, without duplicate even if the send is repeated. The grid filled at the end of the lesson takes the same path. Management sees the last sync time of each instructor.
- How is the instalment collected and reminded?
- At the desk in cash, by transfer, or online from France; every collection produces a receipt sent to the payer and the candidate, and a collection without a receipt does not exist in the application. The due date is reminded beforehand by WhatsApp with the amount and the link; the written rule can block booking the next lesson until the due instalment is collected, and the candidate sees why.
- Can the father in France pay the instalment?
- Yes, online, in euros, with the dinar amount frozen at invoice and a matching of the two collections, as the two-currency guide describes; the receipt goes to the payer and the candidate. The exchange framework is for counsel; the application records what was paid, by whom, and at which frozen rate.
- Does online theory replace the course?
- The application makes revision possible: series, sheets, mock test, progress; it does not say what the official syllabus requires or how the exam is organised, which is outside this guide. The instructor sees the series done and the scores before the lesson, and management sees who is not revising.
- How long to put this in place?
- Six weeks in the standard calendar, the first without code and two for the schedule and lessons. A two-vehicle school with clean files takes less; a group of several schools, or a school with many packages and different cancellation rules, takes more, the time to write each one’s rules.