A SAAQ inspection: what you'll be asked to produce

One thing to understand before anything else: an inspection doesn't test the quality of your teaching. It tests your ability to prove it happened.

That's an uncomfortable distinction, because a school can teach excellently and still fail a verification. The reverse is also true. What's assessed is traceability — and traceability is built across the year, not in the week you're told to expect a visit.

This article doesn't claim to reproduce the inspector's grid. The SAAQ alone publishes its official criteria, and you should always refer to them. What we describe here is the inverse, and it's more useful: the obligations you already have, restated as a single question — can you demonstrate it?

The stakes aren't theoretical

A school's recognition isn't permanent. A school recognized today can be temporarily suspended following an inspection.

A suspension isn't just an administrative penalty. It halts your enrolments, strands students who are mid-way through a thirteen-month program, and becomes public — since the list of recognized schools is searchable by any parent.

That's what makes this different from ordinary paperwork.

Run the exercise now

For each item, the question isn't "does it exist?" but "can I produce it?":

The four places schools actually fail

Working through compliance files shows that failures are almost never fraud. They're information gaps created by time.

1. The missing contract end date

This is the most frequently absent field, and the one the most other answers depend on.

Without a contract end date you can't compute your retention obligation. The file sits in a permanently undetermined state: neither deletable nor clearly still required. It accumulates by default rather than by decision.

The most common cause isn't negligence — it's the student who quits. Nobody formally closes a contract that the client stopped honouring without saying so.

2. The learner's licence that expires mid-program

The PESR runs over a year. That's structural: the program can't be completed faster.

The direct and underestimated consequence: it is entirely normal for a learner's licence to expire while a student is still with you. This isn't a rare exception to handle — it's a situation the program's own duration makes predictable.

The problem isn't the expiry. It's not having seen it — and therefore having outings recorded on dates when the licence was no longer valid.

3. A minor's parental consent

A large share of a driving school's clientele are minors. Parental consent isn't one more form: it's a condition.

And it has an unpleasant property: it can't be back-filled. Getting a signature in April for sessions delivered in January doesn't reconstitute January's compliance. A missing consent blocks at the moment it's missing.

4. The session recorded without its instructor

Many schools record that an outing happened, on such-and-such date. Fewer record who delivered it.

But it's precisely the link between the session and the person who gave it that makes the session verifiable. An outing with no identifiable instructor is an assertion, not evidence.

The real test: ten minutes

There's a simple way to find out where you stand, and it needs no preparation.

Pick a student at random, ideally someone who started more than a year ago. Pull their complete file: contract, dates, licence and its validity, consents, all 27 sessions with dates and instructors, attestations issued.

Time yourself.

If it takes ten minutes, you're ready. If it takes an hour because you have to cross-reference a filing cabinet, a spreadsheet and somebody's memory, you don't have a compliance problem — you have a retrieval problem, and it will become a compliance problem on the day of a visit.

That's an important distinction: holding the information and being able to produce it are not the same thing. An inspection only measures the second.

Why the week before doesn't help

There's a natural instinct when a visit is announced: block off a few days, pull everything together, tidy the files.

It rarely works, for a reason worth understanding. Almost everything an inspection examines is a historical fact that either was or wasn't recorded at the time.

You can't retroactively make a licence valid on a date when it had expired. You can't obtain in November a consent that was required in March. You can't reconstruct which instructor gave an outing eight months ago if nobody wrote it down — and reconstructing it from memory is precisely what you shouldn't be doing, because a record produced from recollection is worth less than an honest gap.

What the week before can do is tell you where you stand. That's genuinely useful: knowing about a gap before an inspector finds it lets you explain it, document what you're doing about it, and demonstrate that your process caught it. A school that says "we identified this, here's the correction we made" is in a different position from one discovering the problem in the room.

So the preparation that matters isn't tidying. It's the habit of recording things at the moment they happen — which is unglamorous, continuous, and the only thing that actually works.

What you can do this week

1. Count your files with no contract end date. It's the gap blocking the most other calculations.
2. Check learner's licences for students enrolled more than ten months ago. That's where expiries hide.
3. Run the ten-minute test on an old file. You'll learn more in ten minutes than from re-reading an internal policy.
4. Confirm no active minor has a missing consent. It's the only item on this list that can't be fixed retroactively.

The takeaway

• An inspection tests evidence, not teaching.
• The contract end date is the most frequently missing and most structural field.
• A learner's licence expiring mid-course is normal — not having noticed isn't.
• A minor's missing consent can never be back-filled.
• The real criterion is ability to produce, not possession.

For official, current criteria applicable to your school, refer directly to the SAAQ.