When handing over an active truck trip, give the incoming dispatcher three things together: the vehicle assigned to the job, its last reported position and timestamp in Plaspy, and the decision they need to follow up. The map supplies the geographic reference. Dispatch supplies the job reference, the appointment and the name of the person taking responsibility. A handover built around those details gives the incoming shift enough context to continue working as soon as the outgoing shift leaves.
Consider an illustrative freight operation with a shift change at two in the afternoon. One dispatcher is coordinating a delivery, and a colleague is taking over the open jobs. “The truck is coming along the south corridor” sounds like a helpful update. The incoming dispatcher still needs to know when that location was reported and who is checking the warehouse entrance. Those details determine what the colleague can do while the truck approaches. A useful handover makes that decision visible alongside the position on the map.
Start with the question that remains open
Before opening the map, identify the decision the incoming dispatcher will inherit. In this example, they need to know whether the receiving warehouse can take the truck through its loading yard. The carrier already has a delivery appointment. Earlier in the day, the receiver mentioned that the afternoon entrance might change. The driver knows the main address and can continue towards it. Dispatch can work on the gate confirmation while the truck is on its way, with the warehouse as the appropriate source for that information.
That open question tells you which part of the tracking information matters. If the last report places the truck well outside the industrial area, the incoming dispatcher may have time to speak to reception. If the device has already reported near the yard, the same call becomes more urgent. The warehouse still confirms its own access arrangements. Plaspy provides the geographic context that helps dispatch decide when to make the call. Both pieces are useful, and they come from different places.
Deciding what the incoming person will do also keeps the handover manageable. A list of all the readings on the screen gives them another task to interpret before they can act. Speed, battery and other device information can matter in a different incident. Here the colleague needs the correct truck, a time-stamped position and the remaining obligation. Record those details where the team already manages the load so the next person can build on the record when a fresh report or confirmation comes in.
Preserve what the map said and when it said it
In the Plaspy map , select the device associated with the truck on the job. Open its marker and read the date and time shown with the device information. You can also use the details view to check the device name and update time. If several names look alike, compare the dispatch vehicle identifier before copying any position into a note. The position of another truck can be entirely accurate and still send this job's instructions to the wrong person.
Write down an observation that will retain its meaning when someone reads it later. At 2:00 p.m. in this illustration, the map shows a 1:54 p.m. report near the southern approach to an industrial site. The handover might read, “Truck 27, Centre Warehouse delivery. Map checked at 2:00 p.m. Position from 1:54 p.m. near the south approach.” That report is six minutes old at the time of the check. The arithmetic describes this example. The appropriate age for a decision depends on how quickly the situation can change and on the consequences of acting on an older observation.
Recording both times helps the next person compare like with like. The check time records when someone looked. The report time identifies the reading they saw. A dispatcher reading the note at 2:12 p.m. can open Plaspy to see whether a later report has arrived. Dates and a consistent working time zone matter on overnight journeys and whenever two dispatch desks work across regions. A time zone in the handover header may be enough when everyone uses the same one. Add the date to individual notes when a trip carries through midnight.
A Ruptela Eco5 Lite can supply positions to Plaspy when the unit is installed, configured and able to communicate over a mobile network. Reporting frequency and availability depend on the installation and on conditions along the route. For a handover, describe the reading in terms of what arrived. “Reported near the south entrance” preserves the observation. “At the gate now” is a more specific statement and may require confirmation from the site or the driver.
Hand over a responsibility as well as a location
The incoming person should be able to act on the note without calling the outgoing dispatcher to interpret it. “Gate pending” leaves the work undefined. “Laura checks the entrance with warehouse reception before dispatch sends the driver an access instruction” identifies the owner, the source and the condition for the next step. Laura is a fictional name in this example. Your team can use names or assigned roles according to its ordinary process, as long as the person receiving the job can see who has responsibility.
Include the outcome that will close the task. When reception confirms the gate, Laura can record the source and the time and send the instruction through the agreed channel. If the warehouse cannot yet give a gate, she can ask whether it has a holding area or another temporary instruction to share. If someone at the warehouse already replied, the note should identify that reply so the next shift does not ask the same question a second time. The point of the follow-up is to obtain a usable instruction and make it available to the people who need it.
The same logic works when another party holds the answer. A customer may need to confirm that a revised delivery window still works. Security staff may control entry to a trailer yard. A supplier may be the only party able to confirm that an outbound pallet is ready. In each case, the truck's position helps the dispatcher judge timing. The receiving party, gate staff or supplier provides the operational confirmation. Keeping the two sources visible makes it easier to follow up with the correct person when the shipment moves between shifts.
The recipient of the handover can read back the part they own. “I'll check the gate with reception and update the trip record” is enough to reveal a misunderstanding while the outgoing person is still available. The readback gives the team an agreed next action. If the trip carries over to another shift, the trip record can show both the original commitment and what was learned while following it up.
If the gate instruction is due before the next routine check, put the escalation condition in the same note. In the illustrative trip, Laura can take ownership at 2:00 p.m. and agree to call the warehouse coordinator if reception has yet to confirm the gate by 2:08 p.m. The note keeps the service date, reception as the source and the condition for involving the coordinator. If reception confirms the gate sooner, Laura records the time and entrance. A colleague can see why another call was made or what information closed the task.
Update the record when a new reading changes the decision
Imagine the map displays a later report near another entrance at 2:12 p.m. The driver might have received new instructions through the normal work channel. You have a later reported location and a gate question that may still be open. Add the reading to the trip record, review the instructions already in force and check with the receiving site if the new position changes which gate is relevant. Someone looking back at the handover should be able to see what was known at the original check and why the plan changed after it.
In a second illustrative outcome, the most recent reading at 2:12 p.m. is still the one from 1:54 p.m. It is now eighteen minutes old. The truck could have moved while no newer information was available. You can still ask reception to confirm the entrance. A decision that depends on whether the truck is physically at a particular gate needs additional evidence. Resolving the warehouse question first may be worthwhile even when the position is older than the dispatcher would normally use for an arrival update.
If you need the driver's input, use the agreed communication channel and allow a response when it is safe to give one. Ask for the detail that would change the decision. “Did you get the loading-yard instruction?” is more focused than a general request for a running update. When the receiving site needs proof that the truck has physically arrived, use the normal arrival confirmation for the job. That might be a site check-in or another record already used by the carrier and receiver.
When a customer calls during handover, state the observation and the status of the task separately. For example, “Our latest report places the truck near the south approach at 1:54 p.m. We're checking the gate with reception and will let you know when that is confirmed.” If a delivery estimate is necessary, supply it through your operating process and describe it as an estimate. A single location does not include traffic, gate access or unloading queues. Share only the information appropriate to that customer and shipment.
Keep several open loads straight at shift change
When several trucks are on the road, the list of open loads is useful even if only a few need immediate attention. Start with commitments that come due before the next routine review. The Centre Warehouse truck is approaching an entrance that still needs confirmation. Another truck may have a confirmed appointment and simply need an arrival check at the time the carrier has agreed. Presenting those jobs with equal urgency leaves the incoming dispatcher to infer which one to handle first.
In the dispatch record, give each load a short entry and put the additional detail where a decision is still open. The entry identifies the load, the next obligation and the person handling it. A time-stamped map reading adds context when it affects the priority. For a trip continuing to plan, the time for the next routine review may be enough. When both shifts work from the same record, they can attach updates to the right load even if several people are looking at the fleet map.
Internal references and customer updates serve different audiences. A load number helps colleagues distinguish several jobs for the same receiver. An approximate location and a time for the next update may be all the receiver needs. A screenshot showing the whole fleet could also show trucks and routes unrelated to that delivery. If you take an observation from the map into a customer message, take the portion that belongs to the job and include its time.
Named responsibilities also protect the handover when someone leaves early. If the record identifies an owner and a working channel, a replacement can find the task and record who has taken it over. A promise left in a private chat is harder for the desk to trace. If your desk has a backup coordinator, write down when the decision should pass to them so that the load keeps moving through its normal process.
Try the handover on a familiar route
Pick a delivery where you already know who owns the booking and which issue usually remains open when shifts change. Agree with another dispatcher how to identify the truck on the map and where to keep the handover note. During the trip, ask that person to take over from the information you recorded. The useful test is whether they can find the vehicle, tell the report time from the check time and know where to seek the next confirmation. If they need a second explanation, pay attention to exactly which part of the record was unclear.
After a few handovers, look for details the team keeps reconstructing. If every dispatcher has to find the same reception number, put it in the regular site record and use the handover note for changes. If vehicles have confusingly similar display names, agree on a reference that dispatch can match to the job. If someone relies on the same screenshot throughout a shift, identify the decision that calls for a fresh device check. These changes improve the next handover without requiring the team to document every move the truck makes.
If your fleet already uses tracking, begin with your current map and dispatch record. If you are assessing the Eco5 Lite, ask for a demonstration with a clearly identified vehicle, a reported position and its date in Plaspy. Check compatibility and configuration with a qualified installer and ask which mobile service and subscription conditions apply to your routes. Those questions connect the equipment choice to the work the incoming dispatcher will actually need to do.
At your next shift change, choose one active trip and leave a note on a single task another person can continue. Use the guide to the device information window to find the tracking detail you will record. If the incoming dispatcher can identify the observation, its time and the next confirmation without reconstructing the trip, the work can continue even though responsibility has changed hands.
