Choose the tool only after defining the compliance question
NIS2 covers a range of entities and activities, with scope and classification informed by Articles 2 and 3 and Annexes I and II of Directive (EU) 2022/2555. A readiness checklist can help capture known services and gaps, but it cannot reliably classify an entity without sector, size, jurisdiction and special-inclusion analysis.
Begin with an entity-level register recording legal names, establishments, provided services and the relevant Member State. A tool that starts with a generic percentage score before asking these questions risks presenting false precision.
Separate readiness checklists from legal determinations
A readiness checklist helps teams locate missing owners, incomplete security measures or undocumented incident-response processes. A legal scope assessment records the particular provisions and national implementing measures relied upon. Both are useful, but they answer different questions.
Use source-linked questions, dated decisions and reviewer names. Flag unresolved issues as unresolved rather than presenting a guessed yes-or-no answer. The January 2026 Commission proposal to amend NIS2 should be tracked separately from law already in force.
Structure templates around NIS2 obligations
Article 20 covers management-body responsibilities. Article 21 addresses cybersecurity risk-management measures, including risk analysis, incident handling, continuity, supply-chain security, secure development, effectiveness assessments, training, cryptography, access control and suitable authentication. Article 23 addresses significant-incident reporting.
A sensible document set therefore includes scope and risk assessments, a control register, incident reporting procedures, supplier reviews, business continuity tests and an evidence index. Each template should clearly state who maintains it, what evidence supports the entries and when it must be reviewed.
Evaluate software by its ability to preserve context
Useful features include mapped requirements, role-based access, assignments, linked evidence, dated review cycles, audit trails, incident escalation and exportable records. Organisations operating across Member States may need to associate requirements with different national authorities and applicable laws.
Do not confuse a software vendor's readiness score with a supervisory authority's finding. Systems should retain the reasoning and source behind an assessment and allow reviewers to distinguish a control that is implemented from one that has actually been tested.
Decide what to automate and what needs judgement
Routine reminders, evidence expiry checks, status reports and asset imports may benefit from automation. Whether a service falls under Annex I or II, whether an incident meets legal significance thresholds, and which legal deadlines apply may need expert assessment and current national sources.
Design workflows so responsible people can override erroneous classifications, document reasons and review material alerts. Automated notifications must be tested; a configured rule is not proof it delivered a critical escalation.
Maintain the programme after initial assessment
An NIS2 programme changes when services, suppliers, business structure and national guidance change. Establish review triggers, owners and records of decisions. Confirm that remediation is complete through retesting or other appropriate assurance rather than relying only on tickets marked closed.
For specified digital and ICT service providers, Commission Implementing Regulation (EU) 2024/2690 establishes more detailed requirements. Confirm whether it applies before adopting its detailed provisions as mandatory for every entity.
Questions on the text
Does completing a NIS2 checklist prove compliance?
No. A checklist helps organise a documented assessment, but the applicable national law and operating effectiveness of measures must still be assessed.
Can software decide whether an entity is essential or important?
Software can structure the inputs and record an assessment. Classification still depends on the relevant legal provisions, entity facts and national implementation.
Should proposed NIS2 amendments be applied immediately?
No. Proposals should be distinguished from law currently in force, and monitored for subsequent legislative changes.