Published 5 November 2025, updated 3 August 2026

Working from home removes the one thing that pushes most people into learning to drive: a commute they have had enough of. If your day starts when you open a laptop in the spare room, nothing is reminding you daily that you cannot drive, and the licence quietly stays on the list for another year. Then a role turns out to involve client sites, or you look at moving somewhere with more space and worse buses, and it goes from background to urgent in a fortnight.

Remote does not mean flexible enough to learn to drive

The trap for developers is assuming that because you already control your own hours you can fit driving around work. You cannot be in a dual control car and on a call at the same time, and an intensive course runs for several hours a day inside working hours. Standup, refinement, a code review that turns into a conversation, an incident: any of them will eat the session. Book real leave. Remote work makes it easier to hide a two hour absence, which is exactly why people try it and end up doing both things badly.

There is a second reason the daytime block suits this job. After eight hours of screen time your concentration is not what it was at ten in the morning, and evening lessons at the end of a day spent debugging are the ones people take least from. A course that runs while you would otherwise be at a desk gets your good hours rather than the leftovers.

Picking the week: sprints, freezes and the gap between jobs

If your team runs two week sprints, the cleanest week to be missing is one you have not been given stories in, and that decision happens at planning rather than on the Friday before. Flag the dates at least a sprint ahead so capacity is planned around your absence instead of discovering it. Teams that run a code freeze around a release, or wind down over the end of December, have an obvious candidate week where nothing is shipping anyway.

The other classic window is the gap between jobs. A notice period ending on a Friday with a new role starting a fortnight later is a genuinely free block: no leave to request, no handover to negotiate, nobody to apologise to. If you know a move is coming, put the course in that gap before you fill it with anything else.

Hand over on-call before you disappear for a week

If you carry a pager, being unreachable for several hours a day is not a small thing. Swap out of the on-call rota for the whole course week rather than the days you assume will be quiet, and get the swap recorded properly instead of agreed in a direct message that nobody else can see. Silence the alerts that would otherwise reach you mid lesson, because glancing at a phone in a car you are still learning to drive is worse than useless to everyone involved.

The rest of the handover is the familiar set of things only you know: an unmerged branch, a flag somebody may need to flip, a deploy nobody else has ever run, a service you happen to be the only person who understands. Merge it or write it down before the week starts. A week is long enough for a colleague to hit something you would have answered in two minutes, and short enough that nobody thinks to ask you in advance.

The theory test will be the easy half

Developers generally find the theory test comfortable. It is a bounded body of knowledge, a defined question bank, and a hazard perception section you can practise against immediate feedback. That is a familiar shape of problem, and people who are good at this job tend to be good at it.

The practical is a different kind of learning, and here the habit works against you. You cannot read the documentation and reason your way to clutch control, or to judging a gap on a roundabout while somebody behind you decides whether to go. It comes from seat time and repetition, which is precisely what a compressed course front loads. Sit the theory early and get it out of the way, then treat the course as the part that needs hours rather than understanding. Plenty of developers arrive expecting the reverse and lose a day adjusting to it.

What it costs, and the week you are not billing

Booking takes a deposit rather than a full payment, from £180 at the short end to £900 for a fifty hour course, scaled to the hours you book. It reserves the dates and an instructor; it is not the price of the course. The balance is your instructor’s tuition fee, agreed with them after booking and due before training starts, and it varies by region and by manual or automatic, so no one national figure exists to compare against. The DVSA charges separately, £23 for theory and £62 for a weekday practical. The price guide sets out how the deposit and balance work together.

If you contract rather than sit on a payroll, the real number is the week you do not invoice, which is an argument for choosing the week deliberately: between contracts, or in a lull, rather than in the middle of a delivery somebody is paying you to land. Since 12 May 2026 the DVSA practical booking lives in your own account, so the date is yours to place. Your instructor can tell you when you are genuinely ready and point out earlier slots, but nobody else can log in and move it. If you are unsure how many hours to book, the recommendation tool weighs up what you have actually driven before, and you can compare lengths across the full range of courses.