Incidents & Issues

A risk is something that could happen — it lives in your risk register with a likelihood and impact score. An incident is something that has happened. In Dimeri, incidents are logged separately and then automatically linked back to the risk register. When an incident occurs, it can trigger a review of the associated risk score and prompt a check on the controls that were supposed to prevent it.

Incident tracking isn't just for physical safety. IT outages, data breaches, compliance failures, supplier failures, and governance lapses are all incidents. Any organisation that needs to demonstrate accountability to a board, regulator, or external auditor benefits from structured incident logging. Without it, there's no documented evidence that events were identified, investigated, and closed out properly.

When you log an incident, Dimeri walks you through a structured investigation — capturing what happened, contributing factors, and root causes. It supports both simple cause-and-effect analysis and more structured frameworks. The investigation is stored alongside the incident record, so months later (when the auditor asks) you still have the full story documented and traceable.

Yes. Dimeri includes a simplified incident reporting form that can be accessed without the full platform interface, making it easy for frontline staff to log incidents quickly. Management then receives the report and handles the investigation, classification, and escalation from there.

Each incident can have multiple corrective actions assigned to different owners with due dates. Dimeri sends reminders as deadlines approach and flags overdue actions. When an action is completed, the owner marks it done and the audit trail captures the date, the person responsible, and any evidence attached. Nothing falls through the cracks.