Help
How to use FerryFold
FerryFold works best when you already have a real booking or a credible route scenario. The point is not to replace the ferry operator. The point is to turn the booking into one cleaner terminal plan before the trip fragments across different bags and passengers.
1. Start with the real sailing
Add the route label, sailing date, and departure time first. FerryFold uses those three fields to produce the visible arrival target and the document-ready time.
2. Describe the friction honestly
The most important inputs are vehicle type, border mode, terminal complexity, document discipline, and any slower boarding need such as a stroller, pet setup, or accessibility requirement. Understating those usually creates a false sense of calm.
3. Read the lane before the checklist
The lane tells you the posture of the trip:
- Clean-glide window: ordinary discipline should be enough.
- Buffer-first window: the crossing is still calm, but only if the arrival and handoff pack are protected early.
- Terminal-friction window: the trip needs active simplification before you reach the port.
- Red-flag window: treat the original plan as fragile and rebuild around time, documents, and reduced clutter.
4. Use the copy blocks
Most people do not need to forward the whole app result. They need one block pasted into the family chat, shared notes, or driver handoff:
- Terminal brief for the departure timing and booth posture
- Embark bag checklist for the items that must stay with you during the crossing
- Vehicle and deck note for lane discipline and what should stay accessible
- Delay fallback for the moment the queue or document flow starts slipping
5. Check the operator rules last
FerryFold gives a planning posture, not a contractual boarding guarantee. Before relying on the plan, compare the arrival target with the operator’s current check-in advice, passport/customs requirements, and live terminal notices.