Dispatch
Sending routes to charter captains without taking the helm
Planning a charter route in the office and sending it to the captain sounds like control. Done right it is the opposite: the captain gets a better plan, keeps every decision, and the office stops calling to ask where the boat is.
Updated · 6 min read
Why plan routes in the office
- Tours run the same way every time, so the customer gets the trip that was sold.
- Timing fits the booking: the route is planned to be back before the next charter.
- Safety notes travel with the route: a bridge with low clearance, a shoal, a no-wake stretch.
- New captains learn the area faster with a known-good route to start from.
- The office can answer "where are they and when are they back?" without a phone call.
Check every leg for the boat that will sail it
A route that is fine for a 22 foot center console can be wrong for a 40 foot cruiser. Before a route goes to a captain, check each leg for that boat:
- Land and piers: no leg should cut across either.
- Charted depth against the boat's draft, with a margin for tide and swell.
- Bridge clearance against the boat's air draft, mast or tower included.
- Charted no-entry zones, such as security zones around naval facilities.
A leg that fails a hard check should not be sendable at all. Softer cautions belong in the notes that go to the captain with the route.
The captain stays in command
A dispatched route is a plan, not an order to the boat. The person at the helm is responsible for the vessel, its passengers and every decision about weather, traffic and conditions. Good dispatch respects that:
- The captain reviews the route and accepts it, or declines it with a reason the office can act on.
- Navigation starts only when the captain starts it.
- Dispatch never steers the boat and never touches the autopilot.
- A captain can always leave the plan for good reason: the office sees it, it does not prevent it.
Changing the plan mid-trip
Plans change: weather, a passenger who is seasick, a closure on the water. Send an updated route instead of a phone call. Until the captain accepts the update, the original route stays in force, so nobody ends up navigating a plan they never saw.
Following the trip without micromanaging
Once under way, the office needs three things: how far along the route the boat is, when it will be back, and whether it has left the route. An ETA based on the route's plan copes with planned stops and slow stretches better than one based on the current speed, which reads hours late every time the boat idles. An off-route warning should need a real deviation (Pathr Fleet uses 150 meters) and should clear by itself when the boat is back on the line, so a captain giving a wide berth to a sailboat does not set off a call.
Plan for gaps in coverage
Charter areas often have patchy cell coverage. The accepted route should be stored on the captain's device so it stays available offline, and the boat's tracking should keep recording and fill in the gap when it reconnects.
Route dispatch in Pathr Fleet