Journey Management Plans: What Every Driver and Dispatcher Needs to Know

Journey Management Plans are one of the most consistently required safety documents in Alberta's oil and gas sector — and one of the least consistently understood. At STL, we've been implementing JMPs as a standard practice since our founding in 2013, and I've seen firsthand both the administrative friction they can create and the incidents they prevent.

What a Journey Management Plan Actually Is

A Journey Management Plan is a documented safety protocol for a specific road journey. It's not a generic company policy — it's a trip-specific document that captures the route, timing, check-in schedule, hazards, emergency contacts, and driver fitness status for a particular dispatch. The purpose is simple: if something goes wrong on a remote road, someone knows where the driver was supposed to be and when they were supposed to check in — and can act when they don't.

JMPs emerged from the oil and gas sector's upstream operations, where workers regularly drive alone on remote roads with limited cellular coverage, severe weather exposure, and limited emergency response capacity. A driver who rolls a truck on a cutline road at -35°C with no JMP in place may not be found for hours. With a JMP and a missed check-in protocol, the response starts within 30 minutes.

Check-In Schedules: The Most Critical Element

A JMP without a functioning check-in schedule is a form without a purpose. The check-in interval should be set based on the remoteness of the route and the communication technology available. On routes with reliable cellular coverage, 2-hour check-ins by phone are typical. On remote roads where cellular coverage is intermittent, satellite communicators (Garmin inReach, SPOT, or similar devices) should be required equipment.

The overdue protocol must specify exactly who takes action when a check-in is missed, and what that action is. "Contact the driver" is not a protocol. A proper overdue response specifies: first attempt within 5 minutes of missed check-in by phone, second attempt by radio or satellite message, third attempt by contacting the destination site, and activation of emergency response if contact cannot be established within 30 minutes. Every person named in the protocol must know their role before the driver departs.

JMPs for Oilfield Site Access

Most major Alberta energy operators require a completed JMP before a contractor vehicle can receive a gate pass for site access. The format varies by operator — ATCO, Cenovus, MEG Energy, and Pembina all have their own JMP templates — but the content requirements are consistent with the elements listed above. When STL dispatches to a new operator's site for the first time, we request their JMP template in advance to ensure our dispatch process generates a document that meets their specific format requirements.

Operators typically retain JMP records for a minimum of three years. In the event of an incident, the JMP becomes part of the investigation documentation — it's evidence of due diligence, and its absence becomes evidence of negligence. Carriers who can't produce JMPs in post-incident investigations face significantly greater regulatory and civil liability exposure.

Building JMPs into Dispatch Workflow

The practical challenge with JMPs is making them a genuine pre-departure step rather than an afterthought or a form filled in retroactively. At STL, JMPs are generated as part of the dispatch process — the dispatcher and driver review the document together before departure, and the dispatcher files the signed copy and sets the check-in schedule reminder. This takes 5–7 minutes per dispatch and adds meaningful safety value for every remote run.

Digital tools have made JMP management easier. Several fleet management platforms include JMP modules that automatically generate a trip record, schedule check-in reminders, and alert a supervisor if a check-in is missed. For fleets of 5 or more vehicles operating in remote areas, the investment in a platform with automated JMP functionality pays for itself with the first prevented incident.