Identify the legal entity and actual services
Begin with the legal name, establishments, organisational group structure and services provided. Map each activity to the relevant specific entity type in Annex I or Annex II rather than assigning a category based solely on a broad industry description.
One corporate group can contain companies with different NIS2 status. Consider direct suppliers, hosting or technology partners only in the context of the services and legal relationships being assessed.
Apply size rules and qualifying exceptions
Article 2 generally refers to medium-sized enterprises and entities exceeding the medium-sized thresholds in covered categories, with specified exceptions. Assess employee numbers, financial measures and relationships with linked or partner enterprises using the relevant enterprise-size methodology.
Do not assume that fewer than 50 workers automatically excludes an entity. Some categories or designated entities may fall within scope regardless of ordinary size thresholds. Document the particular provision supporting an exception.
Assess essential or important classification
After determining potential coverage, examine Article 3 and the entity's size and category to assess essential or important status. Legal classification affects supervisory treatment but should not be used to imply that important entities are exempt from core risk-management and incident-reporting duties.
Keep classification rationale separate from operational cyber-risk rankings. A business classified as important may still face severe security exposure requiring immediate remediation.
Determine the Member State and authority
Record where the entity is established and which Member State has jurisdiction. Article 26 contains jurisdiction rules, including specific treatment of some cross-border digital service providers. National rules establish practical supervisory and registration arrangements.
Locate the relevant national implementing law, competent authority, registration process and sector guidance. A multinational should not assume that every subsidiary follows one identical administrative procedure.
Create a defendable evidence record
Store the assessment date, services, sector mapping, size calculation, group relationships, exceptions considered, jurisdiction conclusion, source references and reviewer. Mark unanswered questions and obtain advice where legal interpretation is material.
Use version control when the business launches a new service, enters a country or changes its group structure. A changed service model can alter scope even when headcount remains constant.
Avoid treating a checklist as legal confirmation
A checklist structures evidence and questions but cannot replace a competent legal assessment or official classification decision. Member State implementation may differ in its administrative details, and the Commission's January 2026 proposed amendments should not be treated as enacted requirements.
Use the outcome to start relevant governance, risk-management and incident-readiness work when coverage is plausible, while clearly documenting which conclusions remain provisional.
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.