Your week, stated plainly
Start region, days available, departure date, crew (solo to baby-aboard), lane tolerance and ferry appetite. Six inputs, ten seconds — no account, no email, no wizard with a progress bar.
01 / WHY BUILD IT
A shelf needs a librarian.
The archive holds twenty-two complete journey files, from five-day minis to a twenty-eight-day Grand Quest — each with a verified campsite spine, a day-by-day route and an honest operations briefing. Which is wonderful, and useless, at the moment you actually have nine days in late May and a start point in Yorkshire.
Generic trip planners answer that question with someone else’s averages. The Engine answers it with this site’s own files: it was built to read the archive natively — every route, every seasonal wildlife window, every ferry, every membership card — and to be honest about the thing most planners fudge: how far away the start of a trip really is from your driveway.
That last point does more work than it sounds. A fortnight in the Highlands is a different proposition from Manchester than from Maidstone — not slightly different, but two-driving-days different — and a UK motorhome route planner that ignores the approach is really a brochure. So every expedition file publishes a gateway table of honest driving hours from each region of the UK and Northern Ireland, and the Engine reads it first. The same twenty-two files produce a genuinely different ranking for a Yorkshire briefing than for a Cornish one, which is exactly what a recommendation should do.
02 / HOW IT THINKS
Briefing in, ranked deck out.
Approach hours tell the truth
Every expedition carries a gateway table: real driving hours from each UK region to its first pitch. The scorer weighs those against your days, penalises files that would rattle loose in a too-long window, and respects the tier ladder — MINI TRIP to GRAND QUEST — so a weekend never gets handed a month’s route.
Cards that show their working
The result is a ranked deck, each card wearing its tier and its reasons — why this file, why now, what the honest trim looks like if your days shrink. No black box: the why-strings are the argument, printed.
Route, wildlife, season, order
Load a file and the dashboard builds: route rows deep-linking straight into the journey page’s day cards, a nature calendar filtered to your actual month with a rarity ladder from COMMON to RARE, the season’s honest note, and the booking order — what sells out first, stated first.
03 / WHAT IT WEIGHS
The signals behind the ranking.
Beyond distance and days, the briefing carries the quieter preferences that make or break a campervan holiday, and the scorer treats each one seriously. Ferry appetite swings island files hard: tell it the van rides boats happily and the sailings-built routes surface with their crossings counted as features; tell it never, and they sink rather than ambush you at the booking screen. Lane tolerance reads each file’s single-track honesty — the passing-place miles, the hedge-canyon warnings — so a driver who wants main roads isn’t handed a peninsula. Crew mode shifts the weighting toward files with pram-flat set-pieces, carrier terrain flagged, and fit-day/family-day splits already written.
Then the calendar joins in. Every expedition carries its wildlife windows month-coded — puffin boats that stop sailing, osprey nests that empty in September, seal pups that only arrive in November — plus the season’s honest warnings, from firing-range calendars to a certain motorcycling fortnight that books an entire island. Brief the Engine for June and for October and the same destination reads as two different trips, because it is.
Finally the tier ladder holds the shape: MINI TRIPS to GRAND QUEST, with a window-gap penalty stopping a five-day file rattling around inside a three-week briefing. Long weekends get long-weekend answers; a month gets the summit files.
03 / PRIVATE BY DESIGN
Your plans stay in your browser.
The Engine follows the same doctrine as every calculator on this site: it runs entirely in your browser, saves to your device’s local storage and nowhere else, and asks for nothing — no account, no email, no cookie banner theatre. The Hangar at the foot of the page berths your saved plans; load one and the whole briefing and dashboard restore exactly as you left them.
Free means free: there is nothing to unlock, no premium tier waiting behind the third click. The Engine exists because the archive needed it.
The Hangar treats plans like berthed vessels: name one, save it, and the whole state — briefing answers, ranked deck, loaded dashboard — restores on a tap. Keep a spring plan and an autumn plan side by side; print the dashboard for the passenger seat. Clear your browser data and the plans go with it, which is the honest cost of nothing ever leaving your device.
05 / THE TEN-MINUTE WORKFLOW
From blank calendar to printed plan.
Answer the six questions
Start region, days, date, crew, lanes, boats. Change any answer at any time — the deck re-ranks live, so playing with the sliders is half the planning.
Read the why-strings
Each ranked card argues its case: the approach hours, the season fit, the tier match. Disagree with a reason and you’ve learned something about your own brief — adjust and watch the argument change.
Open the dashboard
Route rows deep-link into the journey file’s day cards; the nature panel filters to your month with its rarity ladder; the booking order tells you what sells out first. This is the trip, provisionally assembled.
Save, compare, print
Name the plan in the Hangar, brief an alternative beside it, and print the winner for the glovebox. Ten minutes, zero accounts, and a fortnight that started as a blank square on the calendar.
04 / RUN IT
Feed it your dates.
The Trip Engine Room takes about ten seconds to brief and gives back a ranked answer you can interrogate, trim, save and print. It pairs naturally with the archive guide — read how the files are built there, then let the Engine argue about which one is yours.