An incident registration in the transport sector is a documented account of what happened when a system failed, was compromised, or behaved unexpectedly: what went wrong, when you noticed it, which systems were affected, and what you did about it. In transport, it is often not about an office computer but about the planning system, the tracking connection with a client or the link between the dispatch centre and the vehicles. That registration is needed for yourself, for a possible notification to a supervisory authority, and increasingly because a client explicitly requests it.
Whether your company is required to report incidents to a supervisory authority depends on whether you fall under the NIS2 regulations as an essential or important entity. Transport is listed as a sector in Annex I of the directive, but the outcome differs per enterprise and is also determined by size and role in the supply chain. If you are uncertain about this, a check of a few minutes provides an initial indication. Even without a reporting obligation, maintaining your own registration is sensible: clients who are themselves subject to obligations increasingly ask their transport providers to demonstrate how incidents are handled.
What often goes wrong in the transport sector
Most incidents worth recording do not affect the vehicles themselves but the systems around them. A planning system that is inaccessible due to encryption, a tracking or telematics connection that fails, leaving a client without visibility of their shipment, a stolen driver login used by someone else to access trip planning, or a phishing email arriving via the invoicing system: these are all situations that belong in a registration, even if the damage was limited.
Client connections in particular deserve attention. Many transport operators work with a direct link between their own planning system and that of the client, allowing the client to follow in real time where a shipment is located. If that connection fails or is misused, the incident affects not only your own business operations but also the client's access to information. That is precisely the kind of event that a client must be able to demonstrate in their own duty of care that they knew about it and followed it up — and therefore something they will ask you about.
What a registration contains in practice
A useful registration first describes what happened and how it was noticed: a report from a driver, an error message in the planning system, or a signal from the IT supplier. Next, you record which systems and data were affected, including whether customer data such as addresses or trip information was accessed. You then document what actions were taken to stop the incident and restore the system, and whether and when the affected client was informed. Finally, you note who handled the incident and who approved the registration.
This structure resembles a checklist, but is mainly intended as a fixed pattern that you repeat each time. A loose email exchange or a phone note is often sufficient at the moment, but is difficult to find again once a client asks about it six months later. A fixed format, however simple, saves time then.
Who maintains this within your organisation
In many transport companies, knowledge about an incident is scattered: the dispatcher notices the system problem, the ICT supplier resolves it technically, and management only hears about it afterwards. Appointing an owner for incident recording — often the office manager or the person responsible for ICT — prevents those pieces of information from never coming together. That same person is usually also the one who answers a security questionnaire from a client, and can then draw on a record that already exists instead of having to reconstruct something afterwards.
How this relates to the reporting obligation
For organizations that do fall under the reporting obligation, certain incidents must be reported to the supervisory authority within established timeframes. The exact timeframes and conditions are set out in national legislation and the directive itself, and are best observed via the supervisory authority or a lawyer, because they can differ per situation. An organization's own incident record is in all cases the basis on which such a report is prepared: without a clear overview of what happened, a report is difficult to draw up afterwards.
Secria.eu prepares the text for a report or registration based on what has been recorded in the file; filing with the supervisory authority's portal remains the responsibility of the organization itself. If you want to see which of the ten due diligence measures are relevant for your situation, and how an incident record gets its own place within them, then an overview of all topics per situation a good starting point. How the platform maintains the record, the status and the owner per measure is explained on the page on our methodology.
If you do not yet have a clear picture of where your company stands, start with the free quick-scan or browse through the knowledge base; both are accessible without an account.