Methodology
How FerryFold chooses a boarding lane
FerryFold combines a base arrival expectation with the main sources of terminal friction. The output is deliberately practical rather than predictive: it creates a safer planning window, not a promise about live queue speed.
Base timing model
Every scenario starts with a simple base arrival allowance, then adds pressure for factors that routinely slow ferry boarding:
- route profile (regional, international, overnight)
- vehicle type and loading complexity
- party coordination complexity
- passport or customs friction
- terminal size and peak-season confusion
- document discipline
- slower boarding needs such as strollers, accessibility, or pet kits
- windy or rough boarding conditions
Lane meanings
- Clean-glide window: modest friction, with enough space to keep the trip tidy.
- Buffer-first window: several normal frictions stack, so the plan needs early protection.
- Terminal-friction window: the route is still viable, but the original loose travel style will probably fail.
- Red-flag window: the scenario has enough stacked drag that you should simplify, repack, or move earlier rather than trust improvisation.
Why the output focuses on handoffs
On ferry days, the failure point is rarely “forgetting the whole holiday.” It is usually smaller: passports split between bags, medicines in the boot, child layers inaccessible, pet paperwork in the wrong pouch, or everyone assuming someone else knows the booth sequence. That is why FerryFold emphasises document handoff, embark bags, and vehicle/deck notes.
What FerryFold does not do
FerryFold does not calculate route drive time, verify border eligibility, replace operator instructions, or monitor live port delays. It is a planning scaffold that helps users create a safer buffer around those realities.