Case · Driving school

A whole driving school in one place

City Køreskolen in Randers, Denmark is family-run in its second generation. Classes, students and appointments were scattered across spreadsheets and calendars. Today the school has a website where students sign up and pay on their own, a page where each student can follow her own course, and a management system the instructors run the rest from — all built from scratch by Adlure.

Client
City Køreskolen, Randers
Industry
Driving school
Services
Webdesign · Custom Software
Delivered
Website, student portal and admin system
Pages built from scratch
14
Licence categories in the system
6
Interfaces in one system
3
Third-party scripts on student pages
0

The challenge

The school ran on memory and spreadsheets

No two days at a driving school are alike. Classes move, students cancel, and somebody has to remember who is still missing a medical certificate.

No off-the-shelf system fit. The big ones are built for the average business — not for a family-run driving school with six licence categories, mandatory skid-pan and manoeuvring sessions, and theory nights on Tuesdays and Thursdays. And you cannot have that kind of system changed when everyday life changes.

At the same time the website had to do far more than look good. Students needed to find the right package, see when the next class starts, and sign up without calling during office hours.

Before

  • Classes in one spreadsheet, students in another, appointments in separate calendars
  • Signing up meant a phone call during office hours
  • Students called in to ask when they were due next
  • Cancellations arrived by text — if the instructor saw it
  • No single view of who had paid what

After

  • One system for classes, students, lessons, tests and payments
  • Students sign up and pay their deposit themselves — around the clock
  • Each student sees her own calendar and her own progress
  • Cancellations land on the instructor's phone right away
  • The outstanding balance sits on the student card — and on the dashboard

The tour

Three interfaces, one system

A visitor, a student and an instructor need completely different things. So it became three interfaces sharing the same data — not three systems that have to be kept in sync.

The website

A site that sells the seats — not just lists them.

Fourteen pages covering the six licences the school offers. The visitor answers a few questions and is recommended the package that fits her situation, sees when the next class starts, and signs up on the spot. The site pulls the classes straight from the school's own system, so a date never appears that the office does not know about.

  • A guide to the right package: prices, instalments and discounts worked out along the way.
  • Next class with a countdown: live from the system, not typed in by hand.
  • Sign-up around the clock: the deposit is paid by card and the seat is held for 30 minutes.
  • A chat for the obvious questions: prices, class dates and everything the office was asked again and again.
See the site live

The illustrations are drawn by us. Real student data never leaves the school's own system.

How we did it

From first conversation to daily use

We built in the order that gave the school the most: first the part that brings in students, then the part that saves time every day.

  1. 01

    We learned the everyday

    What happens from the moment a student calls until she holds the licence? We mapped the modules, the mandatory sessions, the tests and every exception no standard system knows about. That became the list of what version one had to do — and what it did not.

  2. 02

    The website first

    The site had to pay for itself before we built further. We made the fourteen pages, the guide to the right package, and a sign-up that works without anyone picking up the phone — deposit paid online and the seat reserved straight away.

  3. 03

    The system behind it

    Then came classes, students, lessons, tests, signatures and payments. Access was placed in the database — not in the browser — so an instructor can only see her own students, whatever happens on the screen in front of her.

  4. 04

    And we stayed on

    The system has been fixed and extended as the instructors have used it — reminders, a cancellation history, students without a class, and a helper that can explain the panel. It is still going.

Security

Student data stays where it belongs

A driving school system holds dates of birth, phone numbers, medical certificates and payments. That is not a place to guess.

So security was not bolted on afterwards but built in from the first line. The browser decides nothing — it simply asks, and the database answers only if the person logged in is actually allowed to see it. And the pages that show student data load no scripts from anyone but the site itself.

How it is built

  • Only the site's own code may run. A strict Content Security Policy refuses everything else — even if someone managed to slip code into a page.
  • Access lives in the database. Rows are locked per user, and everything goes through locked functions — not through the tables.
  • Nothing typed in becomes code. Names, class titles and notes are inserted as text, never as HTML.
  • The amount is set on the server. A tampered page cannot pick its own price, and neither the school nor the site ever sees card details.
  • The login dies with the tab. A forgotten computer at the office is not still logged in tomorrow.
  • No tracking on student pages. Analytics runs only on the ordinary pages — never where student data is shown.

The result

What the school got

Two products working together: a website that welcomes the student, and a system that knows her the rest of the way.

  • Sign-up without the phone

    The student picks a package, signs up and pays the deposit herself — outside office hours too. The seat is reserved before the office opens the next morning.

  • Fewer calls about the same thing

    "When am I due?" and "what am I missing?" now sit on the student's own page. The chat on the website handles the rest of the repeats.

  • One place instead of five

    Classes, students, lessons, tests, signatures and payments live in the same place. The dashboard shows how full the classes are and who still owes.

  • The system comes along in the car

    Both the instructor's panel and the student's page can be added to the home screen. Signatures are taken on screen, and cancellations arrive as a notification right away.

  • Data that does not leak

    Access is controlled in the database, not in the browser, and the pages with student data load nothing from outside. It is the same approach we build everything else on.

  • It is still evolving

    The school asks for something, we build it. The system has been extended several times since it went live — with no licence per user and no waiting weeks.

“They are truly professional and have given us fantastic service. Everything was tailored to what we wanted, and they simply delivered a top-notch product. Our students pick up the system right away. Highly recommended.”
JesperOwner, City Køreskolen, RandersTranslated from Danish Read the review on Trustpilot

Is something in your business running on spreadsheets?

That is usually exactly what is worth building. Get a no-obligation conversation about what it would take at your place.

Book a demo

All cases