Driving instructor booking system

Compare driving instructor booking systems on prepaid hours, pickup details, recurring dates and payment records. A practical checklist for UK instructors.

5 min readYouzse TeamUpdated

A driving instructor sells hours in a car, in a fixed geography, to pupils who mostly pay in blocks and occasionally in cash at the kerb. The software problem is not fitting lessons into a week. It is keeping track of who has hours left, getting paid before the lesson rather than after it and protecting the hour somebody cancels at nine the night before.

Prepaid hours are the whole model

Almost every instructor sells blocks of ten and almost every instructor tracks the balance in a notebook or a spreadsheet that is one lesson out of date.

Keep a running count of every block. Each lesson takes one hour off it, the pupil knows what is left. You find out that somebody is on their last hour before the lesson rather than at the end of it.

It changes the cash flow too. Ten hours paid up front is ten hours you are not chasing. A pupil with hours in credit is considerably less likely to drift to another instructor.

Getting paid without the kerbside cash

Cash at the end of the lesson means a trip to the bank, no record either of you can check and an awkward conversation when somebody has not got it.

A payment link sent with the booking confirmation settles most of it before the lesson happens. For the pupil who wants to pay in the car, Tap to Pay on iPhone takes a contactless card or phone against the back of the handset with no reader in the glovebox.

Bank transfer works and is cheap, but it puts the work on the pupil and it is the method most likely to still be outstanding a week later. Keep it as an option rather than a default.

The cancellation you cannot fill

A cancelled two hour lesson on a Saturday is not two hours of admin, it is two hours of income in a week with a hard ceiling on how many hours exist.

Publish a notice period, put it on the booking confirmation and let it be enforced automatically. Instructors who set a 24 or 48 hour window and deduct the hour from the block when it is broken report the problem shrinking rather than the pupils leaving.

Reminders matter more here than in most trades because pupils are often teenagers with a parent paying. Reminders go to whoever made the booking, so where a parent books and pays, the parent gets them. Keep the pickup address in the appointment notes so it sits against the lesson.

What to look for

  • Blocks of prepaid hours, with a clear record of how many are left
  • Payment links and card payments taken in the car
  • A cancellation window the system enforces
  • Reminders that reach whoever made the booking, including a parent who pays
  • Pickup details kept in the lesson notes, not in your head
  • Recurring weekly slots for regular pupils

Move one lesson and check the rest

Record or actionWhat to check
Regular slotRecord the agreed lesson date and duration.
Pickup detailCheck the current arrangement and contact information.
Changed lessonMove one date and inspect the confirmation.
Remaining datesReview the other appointments and payment arrangement.

Inspect the pupil view as well as the diary

Create a sample repeating arrangement and move one lesson. Read the message the pupil receives and check the pickup information. A payment for lessons, a scheduled lesson and an attended lesson are distinct records; use the actual records when answering a question about what remains agreed.

Clear answers before you switch

The details that usually slow down a move: setup, pricing, bookings, records and how Youzse fits into your day.

Most sell blocks of hours in advance and take the balance by payment link or bank transfer. For the pupil who pays on the day, Tap to Pay on iPhone takes a contactless card against the back of the phone with no card reader. Cash still works but leaves neither of you a record.

We value your privacy

Cookies keep Youzse running, improve the platform and help deliver relevant content. Read our privacy policy and cookie policy.