gaash.ai

Strategy & Planning · 7 min read · September 24, 2026 · , gaash.ai

The class of 2027: how a driving school reaches next year's new drivers

A driving school reaches next year's new drivers by knowing when they start asking, which its own booking records show, and by having the answers on its pages before then: next season's course dates and prices, written for the parent who often pays as much as for the learner. Then it measures the same questions before the season and all the way through it.

When do next year's learners start looking for a school?

Only your own records can say. If your enrollment has a season, it is shaped by things like school holidays, exam calendars, the age at which learners become eligible where you operate, and the weather. The shape differs by town and by market, and we publish no figure for it. What a school can do is find its own, because the customer journey for a driving lesson starts with an inquiry the school can date.

  1. Export two years of first inquiries and first lessons from your booking system or diary, one row each, with the date.
  2. Count both by month, side by side.
  3. Mark on the same months the school holidays and exam periods where you operate, and any months when road-test dates were hard to get.
  4. Work out the lead times: the weeks between a first inquiry and a first lesson, and between a first lesson and the test.
  5. Write the result in one sentence, such as "inquiries rise [n] weeks before the summer holiday, and first lessons follow [n] weeks later".

That sentence anchors everything else. Each step in the calendar further down is counted back from it, so a school whose inquiries peak before the winter holidays and one whose peak comes in spring run the same plan in different months.

Why next season's dates and prices should go up early

With web search on, an assistant asked in spring about summer intensive courses can repeat only what the pages it fetches say that day. Without it, the answer comes from training data that stops at a knowledge cutoff. Either way, a page that still lists last summer's runs answers the question with the wrong dates, and a page with no dates leaves the answer to the schools whose pages have them.

So publish as soon as the dates and prices are set, even if booking opens later. State the day bookings open, the price that will apply, and how to join a waiting list. Keep the current season's page beside it until that season ends, so that both questions, the one about now and the one about next season, have a true answer.

Date the page. A line saying when the schedule was last updated tells a reader the page is current, and a sitemap that records the page's last change in its lastmod field, as Google's sitemap documentation describes, says the same to a crawler. That is freshness in a form a machine can read: the page and the server stating when something changed.

Writing next season's pages for the parent who pays

The parent is often the one who asks and the one who pays, which makes the parent as much the target audience as the learner. Their questions differ. The learner wants to know about automatic cars and how soon the test can be. The parent wants the total cost, how the instructors are vetted, how they will hear about progress, and what happens if the learner is not ready when the course ends.

  • The total to test-ready, as a range taken from the prices page, with what the range depends on.
  • Payment: when it is due, and whether a package can be paid in installments.
  • The instructors: their names, the certification each holds where you operate, and the checks they have passed.
  • Progress: how, and how often, a parent hears how the lessons are going.
  • Pickup from school: the area covered and the times lessons can start.
  • The end of a course: what happens if the learner is not ready, and what it costs.

Write those as answers, not reassurance. "Safe, patient, professional" is a claim any school can make; "every instructor holds [certification] and has passed [check] where we operate" is a fact a parent can check. How to write such blocks is in what learners and parents ask an assistant, and the prices they point to are in the prices page article.

A calendar counted back from your own peak

The calendar has no months in it, because your peak is not anyone else's. Each row is a phase measured from the sentence you wrote from your records, in the order the phases come.

A planning calendar for next season, in order. Place each phase against your own peak and lead times.
WhenWhat to doWhere
As soon as next season is setPublish the course dates and prices, the day bookings open and how to join the waiting list, and date the pagePrices page and course pages
Before inquiries start to riseAnswer the season's questions on the pages they belong to: dates, test booking, what happens on a course's last dayCourse pages and the questions page
Before inquiries start to riseRun your question panel once as a baseline, with the season's questions already in itYour measurement record
While inquiries riseUpdate the places left and any runs that fill, and change the page's date each timeCourse pages
After each testAsk the learner, or the parent of a minor, for a review that names the instructor and the testReview platforms, then quoted on your pages
When the peak has passedCompare the panel's monthly runs, record what filled and when, and set next season's datesYour own records

The row that cannot slip is the second. Answers that go up after the peak are answers to next year's questions. What the reviews should say, and what they must not, is covered in pass rates and reviews.

Schools with more than one location

A school with several locations is several answers. A parent asking for lessons in one town needs that location's pickup area, instructors, languages, course dates and phone number, not the head office's. Give each location its own page, with its own address, hours and schedule, and link them all from one locations page.

Keep the identity the same everywhere. Our audit of 9,483 small business websites found 43.1% inconsistent about who and where they are across their own three main pages, 36.9% publishing more than one phone number and 34.1% with no postal address a machine can parse. The audit publishes no cut for driving schools and the figures cover all 40 trades, but a school with more locations has more pages on which to slip. Write the name one way, give each location one number, and use both identically on every page and listing.

In the markup, each location page carries its own LocalBusiness block with that location's address, telephone, opening hours and areaServed, in the form Google's local business documentation describes. The overview for driving schools has a template block to start from.

Measuring the season without moving the goalposts

Take the baseline before the season, with the season's questions already in the panel. "Intensive driving course in [town] over the summer" belongs in it from the first run, not added when summer starts. Our methodology keeps a panel fixed for that reason: a question added halfway through has no earlier readings to be compared with.

Then run the panel every month, through the season and after it. A rise during the peak can be noise or a real change in the answers, and the arithmetic for telling them apart is in how to measure AI visibility. The season adds one question for every monthly run: were next season's dates and prices on the page when parents started asking?

Building the panel itself, in the learner's voice and the parent's, is covered in what AI visibility means for a driving school.

Common questions

We are fully booked every summer. Why publish anything early?

Because full is an answer too. Publish the dates, the day bookings open and when places tend to run out, and offer a waiting list, and a parent asking in spring gets a true answer instead of last year's page. It also spares the phone: a parent who can read the dates and the price does not need to call to ask for them.

What if our prices change before the season starts?

State the date each price applies from, and say whether a booking made before a change keeps its price. Change the page on the day the price changes, and its date with it, so the page never shows two prices for the same course. A parent who booked at a stated price can then point to the page, and so can your front desk.

Should our pages mention licensing rule changes that affect next year's learners?

Only what a change means for your courses, dated, with a link to the licensing authority's own page for the rule. Do not restate the rule in your own words or predict how it will be applied, because the authority's page will change when the rule does and yours may not. A short, dated note saying what the school is doing about it is enough.

Does a school with one location need any of this?

All of it except the part about locations. Finding the season, publishing early, writing for the parent and taking a baseline apply to a one-car school as much as to a group; a single location only means one set of pages to keep current instead of several.

Sources

The figures are this site's own, sample-wide across 40 trades; we publish no driving-school-only cut and no figure for when enrollment peaks. The calendar is a template keyed to each school's own records.

Sources: our audit of 9,483 small-business sites, with its method · Google, build and submit a sitemap · Google, local business structured data · schema.org, LocalBusiness · schema.org, areaServed · gaash.ai methodology

All articles