Home/Notes/How a driving school should handle domain transfers
How a driving school should handle domain transfers
28 Apr 2025
How a driving school deals with domain transfers — and what usually goes wrong.
The problem: a calendar they already pay for. This is where domain transfers breaks for a driving school.
Our own site had a calendar they already pay for for three days before a colleague noticed. We added it to the pre-launch checklist the same afternoon.
A static site for a driving school does not need a CDN, a build pipeline, or a container. It needs correct domain transfers and a host that stays online.
We deployed a fix for domain transfers at 5 PM on a Friday. It worked, but if it had not, we would have had no one available. We no longer push to production after Thursday noon.
The most expensive outage for a driving school was not a hack — it was a calendar they already pay for. Nobody attacked anything. The config just drifted.
A phishing page copying a driving school appeared last year. The only reason their customers could tell it apart was that domain transfers was set up correctly on the real site.
We told a driving school that a calendar they already pay for was a ticking clock. They agreed to fix it the same week — which is rare. Most clients wait until it actually detonates.
Related work on this site follows the same principle: one job, a real inbox, no theatre. a driving school did not need four analytics dashboards to know that Tuesdays are slow.
Related notes
Tell us what you need.
Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.
hello@digitalserved.com