An AI assistant for your driving school diary: what it means
What connecting Claude or ChatGPT to your driving school data does — read-only questions, the checks before you connect, and what Passdesk exposes.
“Connect your AI assistant to your diary” can mean a read-only helper that answers questions about your week, or an agent that can book and cancel lessons. Those are very different things to hand your learner records to.
This post is about what the useful version looks like for a driving school, what to check before you connect anything to your learner records, and exactly what Passdesk does and does not let an assistant do as of October 2026.
What “connecting” means
An AI assistant on its own knows nothing about your school. It has never seen your diary. The way it gets to is a standard called MCP — the Model Context Protocol — which is a way for a product like Passdesk to publish a small set of named “tools” that an assistant can call: look up a learner, list lessons in a date range, and so on.
When you connect, you are not uploading your database. The assistant calls those tools one at a time, on your behalf, with the answers coming back as text it can read and reason over. Ask “who hasn’t booked next week?” and it calls the lesson list for next week, calls the learner list, works out the difference and writes you an answer.
Whatever the assistant can do is bounded by what the tool list lets it do. A provider that publishes only read tools has given the assistant no way to change anything, however it is prompted.
The questions that are worth asking
The value is in questions that are tedious by hand because the answer lives across several screens.
- “Which learners haven’t had a lesson in three weeks?”
- “Who has an unpaid balance, and how much?”
- “Which instructors have gaps on Thursday afternoon?”
- “Which learners have a theory pass but no practical test date?”
- “Summarise last week — lessons taught, cancellations, no-shows.”
- “Draft a friendly reminder to everyone who owes money.”
None of these change anything; they read, summarise or draft. You still send the reminder and make the booking.
What to check before you connect anything
Whatever software you use, four questions before you paste a URL into an assistant.
1. What can it read? Get the list of tools, by name. If the provider cannot show you one, that is the answer. Learner records include date of birth, guardian contacts and sometimes health notes — you are the data controller for those, and you should know which of them leave your system.
2. Can it write? Read and write are different products. A read-only connection cannot double-book a car, cancel a lesson or charge a card. If writes are available, they should be a separate, explicit choice, and each one should show you what it is about to do before it does it.
3. Can you revoke it? A connection should die the moment you say so, not at the end of a session. Look for a key or a grant you can see and delete.
4. Where does the data go? Whatever the assistant reads ends up with that AI provider under your agreement with them, not with your diary software. Pick an assistant your school is comfortable with, and put that decision in your records the same way you would any other processor. Our GDPR primer for driving schools covers the controller and processor split.
What Passdesk exposes
Passdesk publishes an MCP endpoint that every school plan can connect to, and the tool list is short enough to print. There are eight named read tools:
| Tool | What it returns |
|---|---|
get_school_overview |
Your school at a glance — name, timezone, headline counts |
search_students |
Find learners by name, email or phone |
get_student |
One learner — licence, theory and practical test, preferences |
get_student_progress |
Skill ratings logged against a learner, newest first |
list_lessons |
Lessons by date range, status, learner or instructor, in your timezone |
list_instructors |
Instructors with working patterns and badge details |
list_purchases |
Packages, deposits and fees, filtered by learner or status |
list_products |
Your lesson packages and add-ons, with prices |
Plus two more, search and fetch, that exist only because ChatGPT’s deep-research mode insists on those exact names. They search and open the same records as the tools above; nothing extra is exposed to make them work.
Every tool is scoped to your school, enforced on each query.
Connecting works two ways. Hosted assistants — Claude on the web and desktop, ChatGPT connectors — use OAuth: you add the Passdesk URL as a connector, get sent to Passdesk to sign in as the school owner, and approve read-only access. That works on every school plan. On the Scale plan, command-line and desktop tools can also use an API key you mint under your school’s API keys page. Tick read-only when you create it.
Write access is off by default, and only on the Scale plan. If you deliberately turn it on — ticking Let AI assistants book and cancel lessons on a full-access key, or approving write access on the sign-in screen — two more tools appear: book_lesson and cancel_lesson. Both are two-step: the first call is a preview with no side effects (who, when, and any late-cancellation fee), and nothing happens until the assistant calls again with your confirmation. There is no way to make either tool act without that second step, and a confirmed booking goes through the same checks and notifications as one made by a member of staff. Nothing else can be written — no payments taken, no learner records edited. Learners’ health notes never reach the assistant, and notes your learners and staff write come back labelled as information, not instructions.
Revoking is the same as the raw API: delete the key or disconnect the grant, and the next call fails. A school whose subscription lapses loses the endpoint entirely until it is reinstated.
The full connection guide, with the settings for each assistant, is at /docs/mcp/.
The other kind of AI in Passdesk
There is one place Passdesk runs a language model itself: AI lesson debriefs. When an instructor ends a lesson and saves the rubric, Passdesk can write the learner a short, specific debrief — what went well, one thing to practise, a line of encouragement — from the skill ratings and the instructor’s notes.
It is off by default and switched on per school. Nothing is generated for a school that has not opted in, and the model is given only the rubric and the instructor’s notes for that lesson, with the instruction to stick to them. It is also capped per school per day, so a bulk of lessons marked complete in one go cannot fan out into a bill.
A sensible way to start
Connect read-only. Ask the Monday-morning question — what happened last week, what is booked for this one — and see whether the answer is one you would otherwise have built from three screens. Ask the balance question. If those two are useful, you have most of the value already.
Turn on writes only when you have used the read tools long enough to trust the assistant’s understanding of your diary, and read the preview each time.
Plans and pricing show which tier includes API and assistant access.