Event metrics and the Event list tile

Events (incident, near miss, disturbance, field report…) appear in Analytics in two forms: as metrics (counts, with breakdowns and a trend) and as an Event list tile (the period’s events row by row). Both can go on any dashboard, and the list can also be sent by e-mail with the scheduled report — with no new setup.

The “Events” dashboard — at company, site and unit level

There is a ready-made view too: the Analytics → Events tab (or Events (built-in) in the view picker). Nothing to set up — events occurred and still open, the trend, the breakdowns by type / severity / source / status / age / closing reason and the event list of the period, in one place.

Company level (the default): the bar reads Level: Company — all sites. The figures are the sum of the sites you can see — if you have access to one site only, you see that site only. The Site filter can combine several sites.
Site level: pick a site in the Level picker. The same view runs on one site’s data.
Unit level: at site level, pick a unit in the unit picker (or the Site level row for events not tied to a unit).

The line under the bar always says which level you are on (Company level — summed over: …, Site level — …, Unit level — … › …). The level picker is there for every company-level view, your own saved views included; a “by site” tile at site level says it is shown at company level only.

“Awaiting classification”: if there are reports without a site, a line at company level shows their number and the filtered Reports → Events view — they are not in the figures. Only people who can see unclassified events (company-wide access or the right to reassign) see the line.
Every type is shown: a tile holds at most six columns, so with many types the type (and closing-reason) breakdown is split over several tiles (By type — over time (1/2), (2/2)) — together they always add up to all events. The order is that of your event-type list (as you arranged the types); an archived type gets a column only if it had events.
To schedule it, save the view: in the editor From template → Events overview — the same tiles in the same order, as your own named, schedulable view. (The saved copy keeps the type list as of saving; reload the template to pick up a type added later.)
PDF: the PDF view button on the Events tab gives this view’s document, at the level and period on screen.
No data ≠ 0: on a unit with no events in the period the tile says there is no such event — it does not show zero.

Before you start

Permission: editing a tile needs analytics:manage; viewing needs analytics:view. The Event list tile additionally needs access to Reports → Events (report:events) — the list shows the same as the Events table. Without the right the tile does not disappear; it says: No permission for the event list.
Module: the Analytics module must be switched on. Events are projected in the background for every organisation, so the history exists even if Analytics is switched on later.

Steps — an event metric on a tile

Open Analytics → Overview and switch the view to editing (or create a new one).
Add a KPI, trend or ranking tile and pick Events (occurred) or Events — still open in the metric picker, or a breakdown such as Events — severity: Accident.
Save the view.

Steps — the Event list tile

In edit mode add a new tile and choose its kind: Event list.
The number of rows (up to 50) is set in the usual “top N” field. If the period has more events, the tile says: N more events do not fit on the tile (M in total).
Save. The list starts with the newest event: ID, time, place, type (with subcategory), severity, status and closing reason, title.
It also works in a scheduled report: the list goes out with the existing scheduled delivery (Scheduled report), in the PDF with the same content as on screen.

What do the metrics measure?

All event metrics answer the same set: the events that occurred in the period, by their current state.

Metric	Meaning
Events (occurred)	The number of events that occurred in the period (counted by their start if given, otherwise by when they were logged). It counts every record, including those closed as “False / duplicate”.
Events — still open	Of these, the ones not closed at the time of the last refresh.
Open events — age band	The open ones by time since logging: younger than 1 day · 1–7 days · 7–30 days · older than 30 days.
Events — breakdown	The occurred events split by type, subcategory, severity, source, status or closing reason.

Good to know about the numbers:

The “current state” moves the day’s row. If last year’s event closes today, last year’s “closed” row grows and “open” shrinks — an event counts in exactly one daily row per breakdown, so the daily values add up to the monthly one.
The source breakdown uses the primary source (automatic › field › diary / off-diary). A site-level field report carries two badges in the Events table, but here it counts once, as “field” — so the source parts add up to the total. (The Events table’s Off-diary filter, by contrast, follows the badge set.)
Events “Awaiting classification” (no site) are not included — once classified they count at the target site. The metric and tile help say so.
The age band does not move instantly: an hourly maintenance job refreshes it, and the row’s “computed” time tells how recent the age is.
No data is not 0. An empty period has no row; the tile says “no data”, not zero.
Status and closing reason are report data here, as in the Events table; in the diary and the shift PDF they still do not show.

What the list NEVER shows

The list (on screen and in the delivered PDF) contains no internal comment, no detailed description and no personal data of the reporter (the logging user, the field reporter’s name and contact) — the tile does not even read them. The full event opens through the Open: Reports → Events link and the row IDs (there you see it according to your own rights).

What it cannot do (yet)

Event metric tiles have no drill-down: you cannot click from a metric to the events behind it, because the Events table cannot be filtered by period today. The Open link takes the table to all events, not the period’s.
If someone changes an event by direct database operation or with the old (pre-update) code, the metrics may lag until the next hourly self-check; the self-check detects a missing or surplus count, not a change in content.

If it worked

A metric tile shows a number; the Event list shows the rows, with the note about the exclusion of “Awaiting classification” events below. In the scheduled report’s PDF the Event list has the same rows.

Common problems

What you see	Why	What to do
“The Analytics module is not enabled — the event list is unavailable.”	The Analytics module is off.	Ask for it to be switched on.
“No permission for the event list (requires viewing Analytics and Reports → Events).”	`analytics:view` or `report:events` is missing.	Ask your admin.
“No events were recorded in this period.”	There are no events in the period (and the chosen sites).	Choose another period or site.
The number is lower than the rows of the Events table	Events “Awaiting classification” (no site) are not included.	Classify them; after that they count at the target site.

Find and export eventsThe Events table — what the list tile summarises.

Scheduled reportThe list by e-mail, as a PDF, with the existing delivery.