Your shift begins with three questions arriving almost together. A customer wants to know whether their vehicle has left, a colleague mentions an outstanding alert, and someone asks about a unit that still appears in the same place. Before opening more windows, you need to decide what deserves your attention. The Plaspy Dashboard brings vehicle states, alerts and device information together to help you choose that first case. The priority becomes clearer when you connect those signals with their possible consequences for your operation.
This is an illustrative situation, but it raises a practical difficulty: a screen can contain accurate information without telling you where to begin. A useful review needs a clear question, information recent enough to answer it, and someone who can confirm what is missing. Having more figures in view helps when you know which decision those figures might change. Otherwise, checking another number can simply postpone the conversation you actually need.
The first question of the shift gives the screen a purpose
A delivery operation does not necessarily start the day with the same concern as a fleet returning from longer journeys. The first may need to establish which vehicles can begin their routes; the second may be considering which units need attention before their next departure. Even within one company, a routine morning can look different from a day with unexpected changes. Choosing the question you need to answer gives your reading of the dashboard a direction.
That does not mean looking only for what you expected to find. It means recognizing which information matters to the next decision and which situation could require you to change it. While preparing departures, an alert that calls for checking a vehicle may interrupt the usual review. A stationary vehicle in the agreed loading area, however, may be exactly where the operation expects it to be. The state becomes meaningful through that context.
In Plaspy, you can bring different blocks into one dashboard and work with the group of devices relevant to your responsibility. Before interpreting a total, it matters which vehicles it includes. A block may follow the dashboard's selected group or have its own group setting. Two figures displayed alongside each other therefore do not necessarily describe the same vehicles. The configuration helps establish whether the comparison makes sense.
Your opening question might be as simple as, “Is there anything we need to resolve before the next departure?” It is specific enough to guide a conversation while remaining open to new information. Later in the shift, it might become, “Which case still needs confirmation?” The dashboard supports that change of focus. Deciding what needs to be known remains a responsibility of the people running the operation, rather than a conclusion generated by the layout.
Three vehicles may call for three different conversations
Return to the illustrative morning. One van appears stationary at the warehouse, another has an outstanding critical alert, and a third has not sent information for some time. Considered separately, all three situations might seem urgent. Adding context changes the conversation. The warehouse van may be waiting for an agreed load. The outstanding alert needs to be read for its type and time. For the third vehicle, you first need to establish how recently its situation was known.
Priority does not come from putting those states in a fixed order and applying it every morning. A signal may matter more because of the service being performed, information received directly from the vehicle, or a condition already known to the team. The dashboard brings indications together. Calls, operational agreements and checks by the people involved provide information that the screen cannot observe on its own.
A helpful question for each case is which decision would remain on hold if you did not clarify it. Perhaps you cannot confirm a departure, answer a customer or decide whether an installation check is needed. That turns a number into a specific information gap. It also gives a purpose to opening a vehicle's details, rather than going through every record out of habit without knowing what would make the review sufficient.
Selecting a vehicle in a block opens its information, and you can move to the Map when you need its geographical context. This brings you closer to the case you have chosen. The device information can support the conversation, but it does not by itself establish that a delivery was completed, a driver received an instruction or a technical cause was resolved. Those conclusions require their own confirmation.
The time of a report is part of the answer
It is easy to read a location as a photograph of the present. Yet a position needs its report time to explain what you actually know. If the latest information arrived before a change in the vehicle's assignment, it may help describe the last known situation while being insufficient to confirm the current one. That distinction matters particularly when someone else is waiting for a precise answer before acting.
Dashboard states are calculated from the latest information received. Some describe movement or a stationary state; others indicate that recent information is missing. Preserve that distinction when communicating: “The last report placed it there” says something different from “It is there now.” This is more than careful wording. It helps prevent another person from making a decision on the assumption that something has been checked when it still needs confirmation.
You may also find that a vehicle has resumed reporting after an alert was generated. The new information matters to its current state, but it does not automatically explain the earlier gap. The purpose of the review may change from establishing whether communication is still missing to identifying whether anything remains to be checked. When the situation changes, the interpretation needs another look rather than simply carrying forward the first assumption.
Some dashboard information changes as new positions arrive, while certain changes to devices, groups or service expiry information require the page to reload. If a colleague has just changed one of those items, a screen that has remained open may need refreshing. Separating the operational event, the information received and the view you are reading helps explain why two colleagues may initially describe different situations without either deliberately overlooking something.
One dashboard can contain several different time windows
The dashboard can display figures that answer different questions about time. Vehicle states rely on the latest device information. Daily figures follow the day defined by the account's time zone. Other counters, including certain incoming alerts, trips and observed maximum speeds, begin when the page is opened and restart when it reloads. Being visible on one screen does not give all those figures the same reporting period.
Outstanding critical alerts use another window: the last 24 hours, including alerts from before the dashboard was opened. An alert can leave that window without anyone acknowledging it. When choosing a case, also consider what the previous shift knows about it; a clear list does not by itself establish that nothing remains unresolved. Acknowledging an alert removes it from the account’s outstanding alerts, while the decision to check a situation again depends on what still needs to be established.
Imagine one colleague opened the dashboard at the start of the morning and another has only just signed in. When they discuss a counter that runs from opening, they may be describing different observation windows. Neither necessarily misread the screen. The difficulty arises if they compare those figures as though both covered the whole working day. The start of the observation is therefore part of the information worth sharing.
A recent view may be exactly what you need to decide on the next call. Explaining everything that happened yesterday requires information covering yesterday. A figure becomes useful when its period matches the question. A partial observation can be valuable during supervision while still being insufficient for a complete shift review. Recognizing that boundary lets you use the information for the purpose it can actually serve.
The Dashboard blocks documentation explains these distinctions for individual blocks. It is the place to check how a figure is formed when your decision requires that detail. During an everyday conversation, preserve three references when sharing the figure: which group was in view, which period or moment it represents, and what has been confirmed separately by the operation. Those references make the number easier to interpret after the screen has changed.
A useful call starts with what is known
There is a difference between calling to ask, “What is going on with that vehicle?” and explaining which fact you need confirmed. For the stationary van in the example, the conversation might begin by asking whether the planned loading is still underway. For the device without recent information, it may be more helpful to ask whether the responsible person knows of a change to power, service or installation. Different evidence leads to different questions.
The dashboard does not establish which of those possible causes explains a missing report. Nor does an alert automatically support a conclusion about someone's behavior. Describing the observation precisely leaves room for an explanation that the tracking data cannot contain. The purpose of the conversation is to obtain the next verifiable fact, rather than persuade the other person to confirm an interpretation you had already settled on.
Sometimes the answer will be, “We do not know yet.” The review can still be useful if it leaves clear what is missing, who can check it and when it makes sense to follow up. That work belongs in the communication and tracking arrangements your team already uses. Describing this practice does not mean that the Dashboard creates tasks, assigns their owners or automatically manages those conversations for you.
Once confirmation arrives, keep the original observation separate from what was learned afterwards. “The vehicle appeared stationary; the warehouse confirmed loading was underway” preserves both facts and explains why the priority changed. Saying only that everything is fine removes information the next colleague may need to understand the case. The more specific account also makes it easier to notice if a later situation is materially different.
A new answer can change which case comes first
Suppose the warehouse confirms that the van is loaded but still needs clearance to leave. The other unit has not resumed reporting, and a colleague is already checking the situation behind the critical alert. The three signals may remain on the screen, but the available decisions are different. The first vehicle needs clearance, the second needs confirmation you do not yet have, and the third already has a check underway.
This helps avoid two opposite mistakes: spending the whole morning on the case you know least about, or ignoring it because nothing new has appeared. You can contact someone able to establish the non-reporting vehicle’s situation and, while waiting through your usual communication channels, address a decision that is ready to be made. The information gap remains open; it does not become less important simply because you have dealt with another conversation. If new information indicates a situation requiring immediate action, follow your operation’s response procedures.
Now change one detail. The customer expecting the loaded van says they cannot receive it yet. Clearing the departure is no longer the useful next decision. The same reported position and vehicle state now accompany a different plan because of information that arrived outside Plaspy. This contrast explains why a fixed order of colors or states cannot, on its own, determine which work should come first.
The question that separates the cases is what you can decide from the information already available and which answer would change that decision. Sometimes you need to open the Map; sometimes a brief confirmation from the warehouse or the person responsible for the vehicle is more useful. The dashboard helps when it directs attention toward that missing fact and makes it easier to recognize when another screen will not answer the outstanding question.
A useful dashboard fits how your team works
This view is available to accounts and subusers with access to more than ten devices visible on the Map. Each subuser works with their permitted devices and has their own dashboards. The demo provides example dashboards for viewing. These access conditions matter before building a shared routine around a screen that different people may not see in exactly the same way, or may not have permission to access.
The information also depends on the devices' reports, available sensors and configuration. Adding a block does not create a measurement that a device does not provide. Organizing the view around information you understand is therefore more useful than collecting indicators whose source you have not checked. A larger collection of blocks cannot substitute for a well-defined question or make an unsupported reading reliable.
When introducing the dashboard into daily work, start with a review you already perform: preparing a departure, checking an alert or clarifying missing information. Consider whether the view helps you identify the case and ask a more precise question. If the blocks or groups need adjustment, the guide to organizing dashboards covers those options. It provides the interface detail when you need it without making every operational discussion a lesson in settings.
The next time you open Plaspy, begin with the decision in front of you. Look for signals that could change it, check when they apply and confirm what the screen cannot know. The Dashboard guide introduces the view and its access requirements. From there, the useful next step may be a single well-informed conversation that establishes which case deserves your attention now.