· EvoPoint team
What to keep after an incident, and why it matters
When a safety advisory group, an insurer or a client asks what happened, a timeline and a branded report answer faster than radio logs and notebooks. Here is what a useful incident record holds.
The question always comes later. Weeks after an event, someone asks when a problem was reported, who went, and how long it took. If the answer lives in radio chatter and a notebook, it takes days to piece together.
What a useful record holds
- When: reported, acknowledged and resolved, and how long each step took.
- Where: the site, the location and the spot on the map.
- What: the category, the severity, the description and the photos.
- Who: who reported it, and how to reach them if they left details; who was assigned, and how.
- What changed: every status change, in order, with its time and who made it.
EvoPoint records all of this as the incident happens, so there is nothing to reconstruct.
Reports people outside the control room can read
An incident report is a PDF in your branding: your document title, logo, accent colour and footer text. A report covering more than one incident opens with a summary page, with totals, severity and status bars, and an index giving each incident's page.
Generate one for any date range and filters, or put it on a schedule: daily, weekly or monthly, at the hour and time zone you pick. A weekly digest for one site every Monday at 08:00, or a monthly board pack, are two ways to set it up.
An audit log that only grows
Behind the reports sits an append-only audit log. Privileged actions, such as role changes and branding updates, are marked with a shield, so they stand out when someone reviews the history.
Your data, when you want it
A company admin can request a full export of the workspace at any time and see past exports on the same page.