All projects
ProductDriving education

More driving. Less admin.

A booking platform for driving schools. Learners find a lesson and follow it from request to approval. Instructors run their day from their phone. Owners see the whole school in one place.

Industry
Driving education
Built for
Learners, instructors and school owners
Platform
Web workspace and Flutter apps
Made by
Authguard
Built for the real day to dayReal screens from the product, shown with demo data.
01 / The problem

One hour, three people, and a lot that can go wrong.

A lesson needs a learner, an instructor and a free hour. It also needs a fee that makes sense, a record of what happened and a payment that actually arrives. When those live in different places, the office spends its day holding them together.

10:00, Tuesday

Two learners. One instructor.

Both tap Book on the same slot in the same moment. Without a firm rule the diary ends up with two lessons in one hour, and someone has to make a difficult call.

See how it is handled
Every Monday

The same lesson, again and again.

A learner wants a weekly slot for two months. Typing the same details in for every lesson wastes staff time.

See how it is handled
The day before

Can I cancel, and what will it cost?

Learners phone to change plans. The office coordinates approval and explains the fee, and the terms are not always applied the same way.

See how it is handled
11:00, lesson over

The lesson is done. The work is not.

Notes, progress and payments drift away from the teaching, and revenue slips between the calendar and the accounts.

See how it is handled

We designed the platform against those four moments. Here is what it does about each one.

02 / What we built

Built for the moments that can go wrong.

A system that only lists appointments is a diary with a login. This one handles the awkward parts: clashing requests, repeat taps, cancellations and money that still needs collecting.

Simulation, illustrative
Learner A10:00 to 11:00Still one booking
Learner B10:00 to 11:00Conflict prevented
One instructor, one diary
Learner A

The repeat is recognised as the same request, so there is still one booking.

01Prevent conflicts

Two people. One time slot. Only one booking.

When two learners try to reserve the same instructor at once, the server protects that slot and stops overlapping bookings. It also handles repeat taps and connection retries safely, so a shaky signal never turns into a double booking.

Under the hood
  • Server-side clash checks
  • Instructor time-slot locking
  • Idempotent booking requests
  1. Pick the weekdays
  2. A count or an end date
  3. Untick a date to skip it

Click a screen to enlargeTap a screen to enlarge

02Plan ahead

Book eight lessons. Not eight times.

Instructors can create weekly repeating lessons: pick the weekdays, set a lesson count or an end date, and review every occurrence before confirming. Dates that cannot be booked are shown, so the series can be adjusted.

Under the hood
  • Weekly series builder
  • Per-date checks
  • Preview and selective skipping
  1. The policy, in plain words
  2. The cost, before you confirm
  3. Refund status on the lesson

Click a screen to enlargeTap a screen to enlarge

03Apply fair rules

Clear charges. Fewer disputes.

Before cancelling, learners see the policy, the charge and what comes back to them. Behind that, the backend keeps the original policy and supports cooling-off rules and credit-backs when a charged slot is filled again.

Under the hood
  • Policy-aware calculations
  • Fees shown upfront
  • Automated rebooking credit
  1. Unpaid invoices
  2. Unposted completed lessons
  3. Record the payment without leaving

Click a screen to enlargeTap a screen to enlarge

04Close the gaps

A finished lesson should not mean unfinished work.

Booking Ops lists unpaid booking invoices, completed lessons still waiting for an invoice, and cancellations that need accounting follow-up. Staff go straight from the problem to recording a payment.

Under the hood
  • One exception queue
  • Actions in context
  • Record a payment in place
03 / The learner’s side

From “I need a lesson” to “I’m booked.”

Six screens, one request. Each one has a job to do, and none of them needs a phone call to the office.

  1. Step 01

    Your next lesson, front and centre.

    The learner starts with their next confirmed lesson, upcoming requests and a direct way to book another session.

    Less searching, clearer next actions.

  2. Step 02

    Find a real, free slot.

    The app offers available times for the chosen instructor and shows the lesson price before the request is sent.

    Fewer clashes and fewer surprises.

  3. Step 03

    A request is not an approval.

    After submitting, the screen says plainly that the lesson is requested and awaiting instructor approval.

    Clear feedback and honest expectations.

  4. Step 04

    Every lesson in one place.

    Upcoming lessons show their status, such as pending approval or confirmed, next to the essential details.

    Less back and forth with the office.

  5. Step 05

    The right detail at the right time.

    Start time, duration, instructor and the actions that are still open, including rescheduling and cancelling.

    Nothing to remember, nothing to hunt for.

  6. Step 06

    Control without the clutter.

    Profile tools are grouped into sections that make sense, for editing details and managing the account.

    Simple self-service.

Click a screen to enlargeTap a screen to enlargeShown with demo data.

04 / Behind every lesson

One calm control centre for a busy school.

The learner app is half of the story. Instructors carry their day in a pocket, and the school runs lessons, calendars and access from a connected web workspace.

For instructors

The working day, in your pocket.

Review approval requests, see today’s lessons, create repeating sessions, record lesson outcomes and collect payments from the instructor app.

  • Approval requests
  • Today’s lessons
  • Repeating sessions
  • Lesson outcomes
  • Payments

Click a screen to enlargeTap a screen to enlarge

For the school
  • Daily lesson and financial overview
  • Calendar and appointment management
  • Role-based access and responsibility
DashboardLessons and school activity at a glance.
CalendarScheduling and appointment visibility.
Roles and permissionsPermission-based access for school teams.

Click a screen to enlargeTap a screen to enlarge

05 / Why it works

Thoughtful engineering. Visible everyday value.

What the design and the workflows give a school, in plain terms.

Bookings without clashes

Availability and conflict checks happen on the server, and repeated mobile requests have safeguards against duplicate bookings.

Clarity before committing

Booking and cancellation flows show the status, the available times and the fees that apply, so learners know their next step.

From lesson to record

Instructor workflows connect lesson completion, notes, assessments and payments to the wider school system.

To add: verified numbers, such as lessons booked or admin hours saved, once a school shares figures we can quote.

Built with
  • Flutter
  • Web workspace

Scroll sideways to see the whole screen

Want something like this?

Tell us what you want to build and who it is for. We reply within 1 to 2 business days.

Email
info@authguardtech.com
Phone
+94 777246384

Real Challenges. Better Solutions.

© 2026 Authguard Technology Private Limited. Case study draft for review.