System Incidents

The System incidents section is the failure register of the platform itself (EN ISO/IEC 17025:2017 §7.11.3(e)). It shows when your data management system did not work as it should have, what was affected, and what was done about it.

Navigation: Settings → System → System incidents

Why it exists

Clause §7.11.3 treats the data management system as equipment: it must be maintained, protected, and its failures recorded along with the actions that followed. When the system is run by a provider rather than by you, you cannot keep that record yourself — but the assessor will ask you for it.

This page solves exactly that: the provider keeps the register and surfaces it inside the application, ready to be shown.

What it shows

Column	Description
Period	When the failure started and ended; one that has not ended is marked "ongoing"
Severity	Minor, Major or Critical
Affected system	Which part of the platform it concerned
Summary	What happened
Immediate action	What was done at once to contain it
Corrective action	What was done so it does not happen again

Notes

The page is read-only. The entries are recorded by the provider; they are not added or edited by the laboratory.
The last 24 months are shown. An empty list means no failure was recorded in that period — and that is itself the evidence you show.
Your own internal failures — an instrument, a method, a procedure — do not belong here; they are recorded as Deviations.
Change control for systems that affect laboratory data (§7.11.2) happens in Change Requests.