# Mock driving test marking on the instructor’s phone

Mock driving test marking on the instructor’s phone is a SaaS idea for independent driving instructors and small driving schools, priced to test at $12 a month per instructor. Mock tests are marked on paper sheets that pupils lose by the next lesson. With it, driving instructors mark mock tests on their phone during the drive, and pupils get a fault summary straight after.

_Published 19 Oct 2026. A starting point we wrote, not market research: run the 7-day test before you build._

## What problem does it solve?

Mock tests are marked on paper sheets that pupils lose by the next lesson. Nobody sees which faults keep coming back, so lessons repeat what’s already fine.

**Why now:** Test slots are scarce in many areas, so pupils and parents want proof of readiness before the date.

## What do they use today?

Most instructors tick faults on a printed sheet during the drive, or jot notes to type up later. The sheet ends up in a pupil’s bag or the car door pocket, and trends are guessed from memory.

## How does it work?

During a mock test the instructor taps the phone to record each minor or serious fault under its category, keeping their eyes on the road. When the drive ends, the pupil gets a fault summary by email, and a parent can get one too if wanted. Over several lessons the instructor sees which faults keep coming back for that pupil, and a school owner can add every instructor to one account.

## What goes in the first version?

- Tap to record minor and serious faults by category
- Fault categories you can edit to match your test
- Summary emailed to the pupil and, if wanted, a parent
- Fault trends across lessons for each pupil
- Several instructors under one driving school account

## Who pays, and how much?

- **Who pays:** Independent driving instructors and small driving schools
- **Price to test:** $12 a month per instructor

Charging per instructor matches how driving schools already count: each instructor has their own car, pupils and diary. A solo instructor pays for one, and a school pays for each instructor it adds to the account.

## How to test it in 7 days

1. Ask ten instructors how they mark mock tests and what pupils do with the sheet.
2. Post a screenshot mock-up in driving instructor groups on Facebook and count sign-up requests.
3. Have two instructors mark one mock test each on a simple phone form and share results.

## Where to find the first customers

- Driving instructor groups on Facebook
- Local driving-instructor associations
- Driving instructor training providers

## What are the risks?

- Instructors must watch the road, so marking has to work in quick single taps.
- Existing instructor apps may add mock test marking; stay focused and cheap.

## How to build it on shipanysaas

4 of the parts it needs are already in the kit, the phone app with the All-in plan. Get the kit, open it in Claude Code, Codex or Cursor, and paste the starting prompt.

**Already in the kit:** Teams and roles, Billing, Emails, Phone app with All-in

**You build:**

- Mock test marking screen with fault categories
- Fault summary emails and trends
- Offline marking that syncs later

[Get the kit](https://shipanysaas-demo.vercel.app/pricing)

### The starting prompt

```text
You are in a fresh copy of the shipanysaas starter kit, a pnpm and Turborepo monorepo: the Next.js web app is in apps/web and the Supabase database, with its migrations, in apps/web/supabase; with the All-in plan, the Expo phone app is in apps/native. Help me build the first version of Mock driving test marking on the instructor’s phone.

Read AGENTS.md first, then the AGENTS.md in every folder you work in: the kit's rules there win over your defaults. When a skill in .agents/skills (also in .claude/skills and .cursor/skills) matches a task, use it.

## The product
- What it does: Driving instructors mark mock tests on their phone during the drive, and pupils get a fault summary straight after.
- Who pays: Independent driving instructors and small driving schools
- Their problem: Mock tests are marked on paper sheets that pupils lose by the next lesson. Nobody sees which faults keep coming back, so lessons repeat what’s already fine.
- Price to test: $12 a month per instructor (a plan in apps/web/config/billing.config.ts)

## Build only this first version
1. Tap to record minor and serious faults by category
2. Fault categories you can edit to match your test
3. Summary emailed to the pupil and, if wanted, a parent
4. Fault trends across lessons for each pupil
5. Several instructors under one driving school account

## Already in the kit: reuse it, never rebuild it
- Teams and roles: team accounts with members, roles and invitations
- Billing: Stripe or Lemon Squeezy subscriptions, per seat or usage-based, and one-off payments
- Emails: transactional email through Resend or Nodemailer
- Phone app: an iPhone, iPad and Android app on the same backend (All-in plan)

## New code it needs
- Mock test marking screen with fault categories
- Fault summary emails and trends
- Offline marking that syncs later

## How to work
1. Plan first: list the database tables (with row-level security, so each team only sees its own rows), the pages and the server actions for the first feature. Then stop and wait for my OK.
2. Build one feature at a time with the kit's own UI and form components, with a migration for every schema change and user-facing text in the translation files.
3. After each feature, run the verification steps in AGENTS.md, fix what they find, and tell me what you built and what comes next.

## Rules
- Ask me before you add a dependency, delete a file, or change sign-in, billing or the admin panel.
- Leave the parts of the kit this product doesn't use as they are.
- If apps/native is not in your copy (the Starter plan), build the web app only.

Done when every first-version feature works for a signed-in team and the AGENTS.md checks pass.
```

### Guides for the parts it uses

- [Expo Supabase setup: one backend for your web and phone apps](https://shipanysaas-demo.vercel.app/blog/expo-supabase-one-backend)
- [Multi-tenant SaaS architecture: teams, roles and invitations done right](https://shipanysaas-demo.vercel.app/blog/multi-tenant-saas-teams-roles-invitations)
- [How to add Resend email to a Next.js + Supabase app](https://shipanysaas-demo.vercel.app/blog/nextjs-supabase-resend-email)

## More ideas: Education

- [Term rebooking and weekly timetables for music teachers](https://shipanysaas-demo.vercel.app/saas-ideas/music-term-timetable-rebooking): Music teachers open next term’s lesson times, returning families pick first, and the timetable fills without chasing anyone by text.
- [Trip consent forms for small schools](https://shipanysaas-demo.vercel.app/saas-ideas/school-trip-consent-forms): Small schools send trip consent forms online, parents sign on their phone, and staff see who’s missing before the day.
- [Post-workshop recall questions for corporate trainers](https://shipanysaas-demo.vercel.app/saas-ideas/post-workshop-recall-questions): Corporate trainers send attendees short questions for weeks after a workshop and give the client a report on what stuck.

- [All SaaS ideas](https://shipanysaas-demo.vercel.app/saas-ideas)
- [Try the free generator](https://shipanysaas-demo.vercel.app/saas-ideas#generator)