Statuses and colours
IFMS says a lot with small coloured labels. This page lists every one of them, exactly as it is written on screen, and explains what it is telling you.
How badges are drawn
Nearly every status in the portal is an outline pill with a coloured dot: a thin border, a small round dot on the left and the wording beside it. A few are solid instead. The same six colours are used everywhere:
| Colour | Where it is used for |
|---|---|
| Green (emerald) | Everything is as it should be — moving, legal, active, closed |
| Amber | Attention, but not an emergency — awaiting an answer, acknowledged |
| Red (rose) | A problem — critical, breached |
| Grey (slate) | Switched off, unknown or no answer — no signal, no decision, inactive |
| Blue (sky) | Neutral information — the lowest severity, a newly opened alert |
The movement states have colours of their own (green, orange, red and grey), described under Movement state below.
Every badge also carries its wording, and several colours do double duty. Read the words; the colour is only a shortcut.
Where a value is missing, the portal shows an **em dash — **, not a blank.
Vehicle statuses
Movement state
What the vehicle is doing right now, worked out by IFMS from the position reports. You meet these on Fleet, on the map legends on the Overview and the live map, in the live map's table, and on the vehicle's own page. The badge, the legend dot and the car on the map are always the same colour.
| On screen | What it means | Colour |
|---|---|---|
| Moving | Travelling faster than 3 km/h, whatever the ignition says | Green |
| Idling | Standing still with the engine on, or with the engine state not reported. The Overview counter explains it as "Engine on, stationary" | Orange |
| Parked | Standing still with the ignition off | Red |
| No signal | No fresh position for more than 10 minutes | Grey |
| Unknown | The portal received a state it does not recognise | Pale grey |
Unknown is not on the map legends or among the filter buttons, because it should not normally appear. If you see it, tell the IFMS team. A vehicle that has never sent a position has no movement state; on Fleet it is shown as Never reported.
Registry status
The vehicle's own standing in the national vehicle registry, shown on the vehicle's page and in a provider's vehicle table. It is separate from both the legality decision, and it is only filled in for vehicles the registry recognises.
| On screen | Colour | What it means |
|---|---|---|
| Active | Green | The registry holds the vehicle as in service |
| Suspended | Amber | In service but suspended |
| Retired | Grey | Taken out of service |
| Blocked | Red | Blocked in the registry |
| — | — | The registry has said nothing about this vehicle |
Vehicle legality (from IFTMS)
IFTMS decides whether a vehicle is legal. Verified and legal mean the same thing. Only legal vehicles appear in Fleet, maps, search, details and provider counts. Verification badges and filters are no longer shown.
When a legal vehicle stops being legal, IFMS hides it and refuses its new positions. One Legality violation alert is raised for each loss. It is Critical, shown in red, and stays in Events without a vehicle link. The alert carries the reasons IFTMS gave. An unfamiliar reason is shown as its code; ask the IFMS team what it means.
Decision source says how IFMS received the answer: Snapshot, Live event or Direct lookup.
Provider statuses
| On screen | Colour | What it means |
|---|---|---|
| Active | Solid, filled | The provider is enabled |
| Inactive | Grey, filled | Marked inactive by a System admin; its positions are still received |
| Unnamed | Outlined | The provider has not sent a readable name yet. It is listed as Unnamed provider (…) with its code in brackets |
Providers appear by themselves the first time they send data, and they arrive Active. A System admin can mark one inactive with Edit on its page.
A provider's vehicle count includes only legal vehicles. There are no separate verification counts.
Alert severities
IFMS uses two different severity scales, and they do not match.
On a policy, and in the filters — five levels
This is what you choose when you write an alert policy, and what the Severity filters offer on Events, on Alert Policies and on an alert-routing rule.
| On screen | Colour | Response window |
|---|---|---|
| Critical | Red | 5 minutes |
| High | Orange | 15 minutes |
| Medium | Amber | 60 minutes |
| Low | Green | none |
| Info | Blue | none |
| Unset | none | none |
Unset exists only on a policy — it means the policy does not set a severity at all. A policy row carries a left edge in its severity colour.
On a raised alert — three levels
The badges on the Events table, in an alert's panel, on the Events map and in the exported file collapse those five into three:
| On the alert | Colour | Which policy severities land here |
|---|---|---|
| Info | Blue | Info, Low, and policies with no severity |
| Warning | Amber | Medium |
| Critical | Red | High and Critical |
Because High is displayed as Critical, the red banner "N critical alerts need attention" counts both. Selecting Review in that banner filters to genuinely Critical alerts only, so you can be shown fewer rows than the banner counted, or none at all.
Two kinds of alert always carry a fixed severity: Legality violations are always Critical, and Integration health alerts are always High (shown as Critical).
Alert statuses
| On screen | Colour | What it means |
|---|---|---|
| Open | Blue | Raised, and nobody has picked it up. The row also shows the message in heavier type with a small blue dot in front |
| Acknowledged | Amber | Somebody has taken it on and left a note. The response clock has stopped |
| Closed | Green | Finished with, and a resolution note recorded. Final — an alert cannot be reopened |
The badge, the button, the timeline and the exported file say Closed. The counter card at the top of Events and the Status filter say Resolved. There is one state, with two names.
Response time (SLA)
| On screen | Colour | What it means |
|---|---|---|
| Breached | Red, with a warning triangle | The alert is still Open and its response window has passed |
| — | — | Everything else: inside the window, or already acknowledged or closed |
Those are the only two values. There is no "at risk" state and no countdown.
Only an Open alert can be breached, so acknowledging a late alert removes the Breached badge. The violet escalation badge is then the only remaining sign that it was late.
Escalation
| On screen | Colour | Where |
|---|---|---|
| L1 | Violet | Next to the status in the Events table |
| Escalated (L1) | Violet | At the top of the alert's detail panel |
Escalation happens by itself, about a minute after a breach: IFMS sends the notifications again and pushes the alert back to the front. It happens once per alert, so L1 is the only level you will ever see, and the badge stays for the rest of the alert's life — including after it is closed. There is no manual escalate button for anybody.
Alert kinds
The Alert kind filter and the wording on a row tell you where an alert came from.
| On screen | What it is |
|---|---|
| Rule events | Raised by one of your alert policies. The only kind that has a Type |
| Legality violations | A legal vehicle stopped being legal. Always Critical. The alert remains visible after the vehicle is hidden |
| Integration health | IFMS itself could not get an authoritative answer. Always High. Never a finding about a vehicle |
The list opens filtered to Rule events, not to everything.
Alert types
For rule events, the second line of the EVENT column and the title of the detail panel name the type:
| On screen | What raised it |
|---|---|
| Speeding | A speed condition |
| Geozone entry | A geofence condition, raised at the start of the match |
| Geozone exit | A geofence condition, raised at the end of the match |
| Excessive idling | An idle-time condition |
| Ignition state | An ignition condition — and also anything IFMS cannot classify |
| Legality violation | The legality kind above |
| Integration health | The integration-health kind above |
The Type filter offers the four policy conditions under their policy names: Speeding, Geofence, Ignition and Idle / distance.
Row colouring on Events
| The row looks like | Why |
|---|---|
| Red left edge, faint pink background | The response window has been breached, or the alert is Critical and still Open |
| Faint red left edge | Critical and already acknowledged |
| No colouring | Closed, or nothing urgent about it |
On the Events Map view a marker is a round dot in the alert's severity colour: blue for Info, amber for Warning, red for Critical. An open Critical alert pulses; a closed alert is faded.
Alert policy statuses
| On screen | What it means |
|---|---|
| Active switch on | The policy is being checked against every position report that arrives |
| Active switch off | The policy is kept but checks nothing. Alerts it raised earlier stay in the queue |
A new policy is Active from the moment it is created. The counters above the list read Policies, Active, Inactive and High severity (the last counts High and Critical policies together).
The APPLIES TO column says who a policy watches: All vehicles, Provider: name, or a count such as 12 vehicles.
Geozone statuses
| On screen | What it means |
|---|---|
| Active switch on | The zone is watched. Policies scoped to it can fire |
| Active switch off, with an Inactive badge | The zone stays in the list but is not drawn on the map, and no policy scoped to it will fire |
| The zone's name in grey | You have hidden it with the eye button. This only changes your own view |
| Listed under Show deleted | The zone has been deleted. Restore brings it back, switched off |
Geozone colours
A zone is drawn in its own colour if it has one. A zone set to Use group colour — the choice new and imported zones start with — takes the colour of its first group in alphabetical order, or the default teal when it is in no group. The selected zone is drawn with a thicker outline and a stronger fill. Other zones are drawn in plain grey while you are using the drawing map.
The colour choices are the same everywhere — a group offers eight, a zone Use group colour and then those eight plus teal:
| Swatch | Colour |
|---|---|
#0d9488 | Teal (the colour of a zone in no group; not offered for groups) |
#0ea5e9 | Sky blue (a group's default) |
#f59e0b | Amber |
#10b981 | Emerald green |
#8b5cf6 | Violet |
#ef4444 | Red |
#14b8a6 | Teal (lighter) |
#f97316 | Orange |
#ec4899 | Pink |
A group's section heading in the list shows the group's colour as a dot, the group name in small capitals and the number of zones. Zones in no group sit under UNGROUPED, always last, with a teal dot.
People and roles
| On screen | Colour | Where and what it means |
|---|---|---|
| Active | Green | On Users: the person can sign in. On Roles: the role grants its rights |
| Inactive | Grey | On Users: the person cannot sign in at all, and stays in the list. On Roles: the role is suspended and grants nothing, cannot be picked when adding a user, and is left out of the Target role list on Alert routing |
| System | Grey, with a padlock | A built-in role. Can only be looked at |
| Custom | Teal, with a sparkle | A role the Ministry created here. Can be changed, suspended and deleted |
On an alert-routing rule, the CHANNELS column shows one outline badge per channel — Email, SMS, or both — and the ENABLED column is a switch. For somebody who may look but not change, that column shows a plain ✓ or — instead of a switch.
Notifications
In the bell's list and in your Inbox, a small coloured dot or tile marks how urgent a message is:
| Colour | Meaning |
|---|---|
| Red / rose | From a Critical or High alert |
| Blue | Everything in between |
| Grey | From a Low or Info alert |
An unread item also has a small coloured dot before its title, a bolder title and a faintly tinted row. Alert messages carry a siren symbol; everything else carries a bell.
Colours on the Overview counters
The four Overview cards tint their symbol rather than their number:
| Card | Tint |
|---|---|
| Moving now | Green |
| Average speed | The portal's own blue |
| Idling | Amber |
| Events today | Red when the count is above zero, blue at zero |
Related pages
- Key concepts — the same ideas explained at length.
- Glossary — one-line definitions in alphabetical order.
- Known limitations — where these labels are known to mislead.