Four legal acts, one pattern, one file
NIS2 under BSIG, the KRITIS umbrella act, Section 11 EnWG and EASA Part-IS follow the same pattern: determine applicability, register with an authority, provide evidence, report incidents. That is why the file exists once and not again in every specialist module. It answers four questions in one place: who is in charge, under which reference the matter runs, which obligations fall due when, and what has gone back and forth with the authority. A file is created in the specialist module once a facility’s applicability has been determined; there is deliberately no "add supervisory file", because a file without applicability would have no anchor for a deadline.
An authority’s confirmation can take weeks and is nothing an evidence cycle may wait for. So follow-up obligations run from "submitted on". The field "confirmed on" documents the reply; only where a legal act expressly ties to it does it count from there.
In preparation, submitted, confirmed, change to report, deregistered: each status determines which deadlines run. The deadline for a change notification runs in days, not months, and a deregistered file remains as evidence while all warnings fall silent.
What applies for a regime is set by the regime: the specialist module supplies the obligations with legal basis, you maintain the status, not the catalogue. If no specialist module is active, the page says exactly that and stays empty, because there is nothing to keep.
An answer to the question "what falls due with which authority when" that does not have to be searched for in four modules and three mailboxes.
Schedule a no-obligation demo – we will show you the module with your own use cases.
