Driving schools · CRM
Keep every enquiry, batch and instructor note in one list the front desk can read.
A CRM for a driving school is a single record of every enquiry, learner, course and session booked. It replaces the notebook, the phone contacts and the memory of whoever picked up the call. GullySales sets up a record that suits a school of your size and shows the team how to use it.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What CRM means
A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.
Last updated 14 Nov 2026.
For driving schools
Where it usually goes wrong, and what we would do.
“The instructor holds the number in the car”
A call comes in while the instructor is mid-lesson, and the number lives on a phone nobody else can see. A shared record lets the front desk see every enquiry whoever took it.
“A learner's progress is part of the relationship”
A learner who has finished several sessions and is nervous about reversing is a different case from a new enquiry. The record should hold sessions taken, the instructor and the concern noted.
“Batch space is the stock you sell”
Seats in a morning batch are all the school has to sell. A record that shows the open seats per batch lets the desk offer a real slot, not a vague promise.
“A heavy tool will not be used”
A system with endless fields and screens stays empty when the desk is busy. A short form with the facts that matter is filled in, and a filled-in record is the one that works.
What we do
What we deliver for driving schools.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
A simple enquiry and learner record
A sheet or light CRM with name, number, course asked, source, instructor, status and next step.
Result: Every enquiry has a line and every line has a next step.
Batch and seat view
A view that shows each batch, its instructor and the seats still open.
Result: The desk can offer a slot while on the phone.
Session and attendance notes
A short note after each session on attendance and the learner's concern.
Result: The next instructor knows what to continue.
Reminders for the desk
A list of enquiries with no reply and learners who missed sessions, shown to the front desk each time they open the record.
Result: Nobody is left unanswered because a note was lost.
Training for the team
A short walk-through for the desk and the instructors on adding and reading entries.
Result: The team can add and read entries without help.
How the result is measured
- Enquiries logged in the CRM
- Data completeness
- Reports generated from CRM data
Recorded as a baseline before work starts, so every later report has an honest comparison.
Fields worth keeping
The record travels from the desk to the car, so each field has a person who writes it.
- Course and vehicle
- Written by the desk at booking. It shows how many learners wait for a car, an automatic or a scooter.
- Batch and seat
- Updated by the desk. It shows which batch has an empty seat so the next enquirer can be offered it.
- Instructor assigned
- Set by the owner. It lets the desk offer a woman instructor or a patient one when the learner asks.
- Sessions attended and missed
- Marked by the instructor after each lesson. It shows who has stopped coming so the desk can call.
- Learner's licence and test status
- Updated by the desk after the learner books the test. It reminds the school to offer a test preparation session.
- Review asked and given
- Ticked by the desk. It shows which learners have been asked, so the same learner is not asked twice.
Who it is for
This is written for these driving schools.
- Car driving schools teaching first-time learners
- Two-wheeler and scooter training schools
- Women-only driving instruction
- Refresher courses for those who hold a licence but fear the road
- Automatic transmission and electric car training
- Driving schools that handle learner's licence and test booking support
- Heavy vehicle and commercial driver training
- Corporate and fleet driver training
Before you decide
When this may not be the right fit.
- Instructors save numbers on their own phones and will not hand them over, so a shared record would stay empty
- The school has few learners and a notebook already works, so a new tool would only add effort
- You have not decided who may open learners' details, and that must be fixed before the record is built
Before you decide
Agree the work. Know how to judge it.
CRM for driving schools: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.
Make the scope clear
Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.
Check the work in use
Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.
Know when to change course
If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.
These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.
Before we start
What to have ready before the work starts.
The records, access and decisions this work needs from driving schools. Anything missing is noted in the written scope, with who will supply it.
- The notebook or sheet you use today
- Whatever the desk uses now, however untidy. We load recent learners from it. If it is lost, the record starts from the next batch, and past learners are added only as they return.
- A list of batches, cars and instructors
- Each batch with its timing, car and instructor, and its number of seats. The batch view is built from it, and a batch missing from the list will show as full or empty by mistake.
- A person who owns the record
- One named person who keeps entries complete and closes old ones. Without an owner the record decays and the team returns to notebooks within a few weeks, and the desk and the instructors hold different versions of the same learner.
- A rule on who sees learner details
- Which staff see phone numbers and fees. Decide with your adviser how details are protected. We set permissions to suit, so an instructor sees the learner's schedule and notes while the fee column stays with the desk.
- Your decision on tool and spending
- Whether you will pay for software or use a sheet. We shape the plan to your answer. If undecided, we start with a sheet, because a school that has used a sheet for a season knows what it needs from paid software.
How it works
How the CRM work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Follow one learner from call to licence test
We take a learner from last month and follow the paper: the call, the notebook entry, the fee receipt, the batch, the attendance and the test booking. You and the desk fill the gaps. The trail shows what the school writes down, where, and which facts only live in an instructor's head, such as a learner who prefers a female instructor or one who cannot practise on Sundays.
- 2
Choose the few fields the desk will fill
We propose a short list: name, phone, course, source, car type, batch, fee paid, sessions attended, next step. The desk strikes out what it will not fill. The list is small enough to complete during a call, since a long form will be left blank.
- 3
Build the batch and seat view first
We build the view that tells the desk how many seats are left in each batch and car, because that is the stock you sell. You tell us how batches are made. A learner booking a morning batch should see at once whether there is room.
- 4
Test with the desk on live enquiries
The person at the desk uses the record for a few days on real calls while we watch. We note what slows them and what they skip. We fix it before the instructors are asked to add anything. Reminders are set only for events the desk needs, such as a fee due, a batch about to begin or an enquiry that has waited for a reply. Each reminder names the learner and the action, so it can be done in one call.
- 5
Decide how instructors add notes from the car
With your instructors we agree a simple way to record attendance and a short note after a session, perhaps by a voice note or a message the desk copies. You decide what an instructor may see. We keep the instructor's step short so it happens. An instructor who must type a paragraph after every session will stop, while one who sends a ten-second voice note will carry on.
- 6
Train the team and review after a season
We train the desk and the instructors with their own learners, and name the person who keeps the record clean. After a season we compare enquiries, bookings, missed sessions and repeat learners with the counts taken at the start. You choose what to add, and the owner of the record closes enquiries that nobody has touched, with a reason written against each.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales management. A target, a review routine and someone who owns the number.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3 · you are here
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
Do we need paid CRM software?
Is learner data safe in a CRM?
Can the CRM send reminders on WhatsApp?
Should instructors update the record from the car?
Should we store learners' licence details in the CRM?
What happens to the record if the desk person leaves?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for driving schools
Related work to consider.
Closest to this: leads and follow-up
Also for driving schools
Or start from the overview: sales and marketing for driving schools.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.