A journey management plan (JMP) is a written plan for a single work trip that records the route, timing, driver, vehicle, hazards, check-in schedule and emergency actions before travel begins.
A journey management plan (JMP) is a document prepared for one specific work-related trip. It records who is traveling, where they are going, which route they will take, when they will leave and arrive, what hazards they may face, how and when they will check in and what will happen if they do not. The plan is completed and approved before departure and closed out when the traveler arrives safely.
The JMP is the practical, trip-level tool within a wider journey management program. The program sets the rules, roles and escalation process. The JMP applies those rules to a single journey, so that the traveler and the person monitoring the trip share the same clear, written expectations.
JMPs are widely used in oil and gas, mining, utilities, forestry, pipeline construction, humanitarian work and any field operation where workers drive long distances, travel alone or enter remote areas. A good plan is short enough to complete quickly, but specific enough that someone else could find the traveler using only the information on the form.
The exact format varies by organization, but most JMPs include the following sections.
The JMP lists the known hazards for this trip and the controls in place. Common entries include weather and road conditions, night driving, wildlife, steep grades, poor or no mobile coverage, security concerns, heavy industrial traffic and driver fatigue. For each hazard, the plan notes a control, such as departing later to avoid fog, traveling in convoy or carrying a satellite messenger. This step is similar in purpose to a field level risk assessment (FLRA), but focused on travel rather than a work task.
The plan states exactly when and how the traveler will make contact. For example, a check-in at departure, at a named waypoint, at arrival and before any return trip. It also names the communication method, such as phone, radio, text or satellite device, and notes any areas where contact will not be possible.
The JMP names the journey manager or trip monitor responsible for watching the trip, along with backup contacts and the supervisor who approved the trip. It should include phone numbers that will be answered for the full duration of the journey.
Every JMP includes a clear trigger for action. It defines how long after a missed check-in the monitor will try to reach the traveler, who will be contacted next and when emergency services will be called. It may also include what the traveler should do in a breakdown, such as staying with the vehicle, and the nearest medical facilities along the route.
The plan is signed or approved by an authorized person before travel. On arrival, the traveler confirms safe arrival and the journey manager closes the plan. Any problems, delays or near misses during the trip are noted for review.
Plans change. Roads close, meetings run late and weather shifts. A JMP only works if changes are communicated. If the traveler decides to take a different route, stop overnight or delay departure, they should update the journey manager first. An unreported change can lead to a false alarm or, worse, searchers looking in the wrong place.
A JMP is especially important when a worker travels alone. With no passenger to raise the alarm, the check-in schedule and overdue procedure are the main safeguards. Where travel risk is high, organizations may require two people or use the buddy system instead of solo travel.
Fatigue is another common focus. The JMP should account for hours already worked before the trip and the time needed to drive back. Linking JMP approval to shift work fatigue limits helps prevent workers from driving long distances at the end of a long shift.
A pipeline inspector needs to drive from a regional office to a valve site about 180 miles away, the last 40 miles on a gravel lease road with no cell service. Before leaving, she completes a JMP listing her truck details, the highway and lease road route, a 7:00 a.m. departure and an estimated 11:00 a.m. arrival. The hazards she lists include wildlife on the highway at dawn, loose gravel, a stretch with no coverage and heavy truck traffic near a gas plant. Controls include delaying departure until after sunrise, reduced speed on gravel and a satellite messenger for check-ins.
Her supervisor approves the plan and names the office coordinator as journey manager. She checks in at departure, at the turnoff onto the lease road and on arrival. The plan states that if a check-in is more than 45 minutes late, the coordinator will try her phone and satellite device, then call the field supervisor, and then contact emergency services with the planned route. When a washout forces her onto a different lease road, she sends an update through the satellite messenger before changing course, and the coordinator records the new route on the plan.
Usually the driver or traveler prepares the JMP, since they know the trip details. A supervisor or authorized person then reviews and approves it, and a journey manager monitors it during travel.
Not always. Most organizations set criteria, such as distance, remote destinations, night driving or travel in high-risk areas. Short, routine trips may only need a simple notification.
A JMP manages the risks of a worker traveling between locations. A traffic control plan manages vehicles and pedestrians around a work zone or site.
It is closed out once the traveler confirms safe arrival. Completed plans are often kept for a period so the organization can review missed check-ins, delays and route problems.
Part of SafetyIQ's EHS glossary: plain-English definitions of workplace health and safety terms.
> Keep learning
> See it in action
Capture hazards, run inspections, track training and close out corrective actions in one platform built for high-risk, field-heavy work.
Book my free demo
Get a demo built around your sites, your teams, and the way your people work.
EHS, journey, and fatigue management software for field-heavy teams.
.png){kind=logo}
.png)