20 May 2026 4 min read Assessment
Good scoping makes the rest of compliance tractable — how to define the product boundary and context.
Define the boundary
Decide what the 'product' is: the device, its firmware, companion apps and the remote services that are part of its intended use.
Capture the context
- Sectors and markets.
- Connectivity and data processed.
- Intended users and use.
Why it matters
Scope drives applicability. Too narrow and you miss obligations; too broad and you over-invest.
This is an educational explainer. For the canonical regulation reference, see the dedicated Assessment page — or run an assessment to see how it applies to your product.