Regulatory decision system
CYBER RESILIENCE ACT ENTERPRISE READINESS 2026–2027
Product Security, Vulnerability Reporting & Compliance Decision System
A technical enterprise reference for live Article 14 reporting and 2027 product-readiness decisions, connecting legal status, product facts, evidence, engineering controls, conformity dependencies and executive governance.
295 pages · 25 chapters · 32 Decision Assets
Explore Decision Assets
Enterprise problem
CRA readiness now spans a live reporting obligation and a separate 2027 product-compliance transition.
Enterprise teams must distinguish immediate Article 14 incident-reporting capability from product-level readiness for the broader CRA regime. The decision problem includes scope, product boundary, operator role, classification, legal awareness, SRP execution, Annex I controls, technical documentation, supplier/component evidence, conformity dependencies, legacy products and executive release blockers.
What the publication delivers
A 295-page publication with 25 chapters and 32 decision assets.
Trigger architecture, legal-awareness timing, stage reporting, SRP/CDaC operations, evidence sufficiency and user communication.
Product boundary, commercial activity/FOSS, sectoral exclusions, economic-operator role and important/critical classification.
Cybersecurity risk assessment, Annex I Parts I/II, PSIRT, coordinated disclosure, support period and security updates.
SBOM/component evidence, supplier questionnaires, build/version traceability and evidence ownership.
Annex II, Annex VII, requirement-control-evidence assurance, standards/certification/NANDO routing, DoC and CE readiness.
Market-surveillance response, Product Readiness Gate™, portfolio visibility, legacy products and substantial-modification control.
Operating architecture
One Entry Gate, two controlled readiness lanes.
Product and legal facts
Scope, product boundary, operator role, classification, legacy placement, substantial modification, cross-regulation relevance and evidence certainty.
Article 14 reporting readiness
Trigger tests, LEGAL_AWARENESS_T0, statutory clocks, CDaC/SRP execution, filing evidence and required user communication.
Full CRA product-compliance transition
Risk assessment, Annex I, Annex II, support/update controls, component evidence, Annex VII, conformity, DoC and CE prerequisites.
High-cost enterprise problem areas
Built around the issues large product organisations cannot afford to discover late.
Article 14 + ENISA SRP
Operational trigger, T0, 24h/72h/final-stage, routing, receipt and communication controls for a live reporting regime.
Conformity routing
Standards status, certification, third-party assessment dependencies and NANDO evidence remain separate from assumptions.
SBOM & supplier evidence
Component/build/version relationships and supplier evidence are tied to product decisions and vulnerability impact.
Legacy products
Article 69 transition, Article 14 overlay and substantial-modification review are treated as separate decision questions.
Cross-regulation routes
High-risk AI and EHR interactions are handled through explicit product-level routes rather than by stacking legal summaries.
Authority response
Market-surveillance records keep product version, technical evidence, authority requests and response history reproducible.
Decision Assets
32 documented decision assets, grouped by enterprise task.
The public view shows purpose, timing, input categories, output types, owners and dependencies without reproducing the full publication logic.
Applicability & classification
01CRA Date & Obligation Map
Separate CRA operating horizons and map the applicable obligation/status context for a product or programme.
- What you receive
- A document-based CRA Date & Obligation Map inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Separate CRA operating horizons and map the applicable obligation/status context for a product or programme.
- When to use it
- When planning transition work, reviewing which CRA obligations are already live, or determining what must be revalidated as dates or legal instruments change.
- Information your team brings
- Product/market context, relevant actor facts, target release/market timing and the current controlled legal-source status.
- What your team can document
- A documented date, status, actor and revalidation output used to sequence later CRA work.
- Who should own the output
- Product Compliance with Legal input.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
02CRA Scope & Applicability Engine
Document whether a product is in scope, out of scope or unresolved before later classification/reporting/conformity work begins.
- What you receive
- A document-based CRA Scope & Applicability Engine inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Document whether a product is in scope, out of scope or unresolved before later classification/reporting/conformity work begins.
- When to use it
- At the start of a product CRA assessment and whenever the product boundary, intended use, market context or relevant law changes.
- Information your team brings
- Product identity, functionality, distribution/market facts, product boundary, intended use, exclusions and evidence supporting those facts.
- What your team can document
- A traceable scope/applicability state, including unresolved treatment where authoritative interpretation is not sufficient.
- Who should own the output
- Legal and Product Compliance.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
03Commercial Activity & FOSS Determination
Structure the commercial-activity/open-source route rather than assuming that source availability alone determines CRA treatment.
- What you receive
- A document-based Commercial Activity & FOSS Determination inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Structure the commercial-activity/open-source route rather than assuming that source availability alone determines CRA treatment.
- When to use it
- Where open-source components, distribution models or commercial activity may affect the CRA route.
- Information your team brings
- Licensing/distribution facts, monetisation or commercial-activity context, product/component role and available legal evidence.
- What your team can document
- A documented commercial/FOSS route with unresolved issues routed for legal review instead of being forced into certainty.
- Who should own the output
- Legal and the Open Source Program function.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
04CRA Sectoral Exclusion Matrix
Check whether a sectoral exclusion or overlapping regulated-product regime changes the CRA route.
- What you receive
- A document-based CRA Sectoral Exclusion Matrix inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Check whether a sectoral exclusion or overlapping regulated-product regime changes the CRA route.
- When to use it
- After product boundary is understood and before relying on a general CRA path where a sector-specific exclusion may apply.
- Information your team brings
- Product category, sector/regulatory context, intended use, applicable Union legislation and authoritative evidence.
- What your team can document
- A documented exclusion/no-exclusion/unresolved state with the supporting legal context.
- Who should own the output
- Legal and Product Compliance.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
05Economic Operator Determination Engine
Determine and document the relevant economic-operator role because obligations and responsibilities differ by role.
- What you receive
- A document-based Economic Operator Determination Engine inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Determine and document the relevant economic-operator role because obligations and responsibilities differ by role.
- When to use it
- After scope is established and whenever the organisation's market role, supply relationship or product flow changes.
- Information your team brings
- Manufacturer/importer/distributor or other role facts, placing-on-market context, contractual/supply-chain relationships and legal evidence.
- What your team can document
- A documented economic-operator role and responsibility basis for later obligations and evidence ownership.
- Who should own the output
- Legal and Compliance.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
06CRA Product Classification Engine
Prepare the product classification decision needed to route conformity and assurance work.
- What you receive
- A document-based CRA Product Classification Engine inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Prepare the product classification decision needed to route conformity and assurance work.
- When to use it
- After scope and operator role are established and before selecting a conformity-assessment path.
- Information your team brings
- Product functions, intended purpose, relevant category/classification criteria, product boundary and supporting technical/legal evidence.
- What your team can document
- A documented product classification state or unresolved state where the available facts do not support a final route.
- Who should own the output
- Product Compliance and Legal.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
Article 14 reporting
07CRA Incident Decision Clock™
Structure legal-awareness and staged reporting timing for Article 14 cases without relying on an informal stopwatch.
- What you receive
- A document-based CRA Incident Decision Clock™ inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Structure legal-awareness and staged reporting timing for Article 14 cases without relying on an informal stopwatch.
- When to use it
- When a potentially reportable actively exploited vulnerability or severe incident enters the organisation's Article 14 process.
- Information your team brings
- Case facts, awareness evidence, event type/status, responsible roles and the current operational/legal reporting requirements.
- What your team can document
- A documented T0 basis and statutory deadline set for the case, suitable for controlled case management.
- Who should own the output
- PSIRT and Legal.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary. It does not run automatically or monitor incidents in real time.
08Article 14 Operational Suite
Coordinate trigger assessment, filing, communication and closure records for an Article 14 case.
- What you receive
- A document-based Article 14 Operational Suite inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Coordinate trigger assessment, filing, communication and closure records for an Article 14 case.
- When to use it
- For live Article 14 operations from initial triage through staged submissions and closure.
- Information your team brings
- Product/case identity, vulnerability/incident facts, awareness evidence, filing information, communication records and accountable approvals.
- What your team can document
- A traceable case record covering trigger, filing, communication and closure states.
- Who should own the output
- PSIRT, Product Security and Legal.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
09AEV Evidence Sufficiency Matrix
Assess whether the available evidence is sufficient to support the organisation's AEV-related case determination.
- What you receive
- A document-based AEV Evidence Sufficiency Matrix inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Assess whether the available evidence is sufficient to support the organisation's AEV-related case determination.
- When to use it
- During incident/vulnerability triage when actively exploited vulnerability status is material to the reporting route.
- Information your team brings
- Vulnerability facts, exploitation evidence, source quality, product impact and the current case record.
- What your team can document
- A documented evidence-sufficiency state that can support action, further evidence collection or escalation.
- Who should own the output
- PSIRT and Product Security.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary. The method must be applied with current organisation-specific facts and legal/source status, with specialist review where the route remains unresolved.
10Coordinator Determination Record
Document the basis for coordinator/CDaC-related routing in the Article 14 operational process.
- What you receive
- A document-based Coordinator Determination Record inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Document the basis for coordinator/CDaC-related routing in the Article 14 operational process.
- When to use it
- Where the reporting workflow requires a coordinator/routing determination and the responsible path must be recorded.
- Information your team brings
- Case/product context, relevant operational platform information, legal/authority context and current routing evidence.
- What your team can document
- A documented coordinator/routing basis for the controlled case record.
- Who should own the output
- Legal and PSIRT.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
11Article 14 User Communication Record
Record who must be informed, what communication was approved and what delivery evidence exists for an Article 14 case.
- What you receive
- A document-based Article 14 User Communication Record inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Record who must be informed, what communication was approved and what delivery evidence exists for an Article 14 case.
- When to use it
- When user/customer communication becomes part of the case response and at subsequent communication/closure reviews.
- Information your team brings
- Affected audience/product facts, approved message content, delivery method, dates, legal/comms review and evidence of distribution.
- What your team can document
- A communication record covering audience, message, delivery and retained evidence.
- Who should own the output
- Product Security, Legal and Communications.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
Product lifecycle & security
12CRA Cybersecurity Risk Assessment
Create a versioned product cybersecurity risk decision that can be linked to CRA product controls and later evidence.
- What you receive
- A document-based CRA Cybersecurity Risk Assessment inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Create a versioned product cybersecurity risk decision that can be linked to CRA product controls and later evidence.
- When to use it
- During product design/readiness work and when product architecture, threats, components or risk-relevant facts materially change.
- Information your team brings
- Product architecture and intended use, threat/risk evidence, security controls, components, lifecycle/support context and accountable product decisions.
- What your team can document
- A versioned lifecycle cybersecurity-risk record that feeds control, evidence and readiness work.
- Who should own the output
- Product Security.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
13Annex I Part I Engineering Control Matrix
Map product cybersecurity requirements to engineering-control status and evidence without treating a marketing claim as implementation proof.
- What you receive
- A document-based Annex I Part I Engineering Control Matrix inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Map product cybersecurity requirements to engineering-control status and evidence without treating a marketing claim as implementation proof.
- When to use it
- During product design, implementation verification and release-readiness evidence collection.
- Information your team brings
- Product architecture, implemented controls, requirement context, test/verification evidence, exceptions and responsible engineering owners.
- What your team can document
- A requirement-level engineering-control status with evidence gaps and remediation ownership visible.
- Who should own the output
- Engineering and Product Security.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary. The website does not reproduce the reusable control matrix.
14Annex I Part II Vulnerability-Handling Matrix
Document vulnerability-handling capability against the relevant CRA product-lifecycle requirements.
- What you receive
- A document-based Annex I Part II Vulnerability-Handling Matrix inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Document vulnerability-handling capability against the relevant CRA product-lifecycle requirements.
- When to use it
- When establishing or reviewing vulnerability intake, remediation, disclosure, update and lifecycle practices.
- Information your team brings
- PSIRT processes, vulnerability handling records, update practices, disclosure/communication evidence, support-period information and responsible roles.
- What your team can document
- A documented vulnerability-handling control state with open evidence and remediation needs.
- Who should own the output
- PSIRT and Product Security.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
15CRA PSIRT Operating Model
Describe and record the organisation's intake-to-closure responsibilities for CRA-relevant vulnerability and incident work.
- What you receive
- A document-based CRA PSIRT Operating Model inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Describe and record the organisation's intake-to-closure responsibilities for CRA-relevant vulnerability and incident work.
- When to use it
- When designing or reviewing the operational handoffs between Product Security, PSIRT, Legal, Engineering and Communications.
- Information your team brings
- Existing PSIRT workflow, roles, escalation paths, systems of record, evidence-retention practices and product ownership.
- What your team can document
- A documented intake-to-closure operating model with accountable roles and handoffs.
- Who should own the output
- PSIRT.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
16Vulnerability Evidence Register
Maintain product/component-linked vulnerability evidence so later reporting, remediation and audit decisions have a traceable source record.
- What you receive
- A document-based Vulnerability Evidence Register inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Maintain product/component-linked vulnerability evidence so later reporting, remediation and audit decisions have a traceable source record.
- When to use it
- Throughout vulnerability handling and whenever relevant evidence is added, superseded or needs revalidation.
- Information your team brings
- Product/component/version identity, vulnerability facts, source/evidence references, remediation status, dates and accountable owners.
- What your team can document
- A traceable vulnerability evidence record linked to product/component context.
- Who should own the output
- PSIRT and Product Security.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
17Coordinated Vulnerability Disclosure Procedure
Structure coordinated disclosure activities and retain the decision/communication trail.
- What you receive
- A document-based Coordinated Vulnerability Disclosure Procedure inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Structure coordinated disclosure activities and retain the decision/communication trail.
- When to use it
- When external researchers, suppliers, coordinators or other parties are involved in disclosure and timing/communication must be governed.
- Information your team brings
- Vulnerability/case facts, stakeholder identities/roles, communication history, remediation status, disclosure constraints and approvals.
- What your team can document
- A coordinated disclosure record showing key decisions, communication and closure evidence.
- Who should own the output
- PSIRT and Security Communications.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary. The procedure should be implemented within the organisation's controlled systems of record and governance process.
18Support Period Decision Record
Document the approved product support duration and its basis so lifecycle obligations are not detached from the product decision.
- What you receive
- A document-based Support Period Decision Record inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Document the approved product support duration and its basis so lifecycle obligations are not detached from the product decision.
- When to use it
- During product planning/release and whenever support commitments, expected use or relevant product facts change.
- Information your team brings
- Product characteristics, expected use/lifetime context, support strategy, component/supplier constraints and accountable management inputs.
- What your team can document
- An approved support-duration record with rationale and review context.
- Who should own the output
- Product Management and Product Security.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
19Security Update Governance Register
Track the governance state of security-update release, availability and distribution evidence.
- What you receive
- A document-based Security Update Governance Register inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Track the governance state of security-update release, availability and distribution evidence.
- When to use it
- When security updates are prepared, released, distributed or later reviewed for product evidence completeness.
- Information your team brings
- Product/version, update identity, release status, availability/distribution channels, supporting records, owners and dates.
- What your team can document
- A documented release/availability/distribution state linked to evidence and responsibility.
- Who should own the output
- Release Engineering and Product Compliance.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
Evidence & conformity
20Component Evidence Register
Link component evidence to the exact build/product context so supply-chain evidence remains usable in product decisions.
- What you receive
- A document-based Component Evidence Register inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Link component evidence to the exact build/product context so supply-chain evidence remains usable in product decisions.
- When to use it
- During product composition/SBOM evidence work, supplier updates and release-readiness reviews.
- Information your team brings
- Component identity/version, supplier/source, build/product mapping, vulnerability/security evidence, licence/support context and freshness.
- What your team can document
- A component-build-product trace with evidence status and unresolved dependencies.
- Who should own the output
- Product Security and Supply Chain.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
21Supplier CRA Evidence Questionnaire
Collect CRA-relevant supplier evidence in a structured way and make incompleteness visible before relying on a supplier assertion.
- What you receive
- A document-based Supplier CRA Evidence Questionnaire inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Collect CRA-relevant supplier evidence in a structured way and make incompleteness visible before relying on a supplier assertion.
- When to use it
- During supplier onboarding, procurement, renewal, component change or evidence refresh.
- Information your team brings
- Product/component/version context, supplier responsibilities, security/vulnerability-handling evidence, support/update information and other requested assurance material.
- What your team can document
- A supplier evidence-completeness record with follow-up needs that can feed component and product-readiness decisions.
- Who should own the output
- Supply Chain Security and Procurement.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary. The questionnaire should be used with the exact supplier, product/version and evidence context relevant to the procurement decision.
22Annex II User Information & Release Matrix
Coordinate the required user-information/release material for the relevant market/language/product context.
- What you receive
- A document-based Annex II User Information & Release Matrix inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Coordinate the required user-information/release material for the relevant market/language/product context.
- When to use it
- During release preparation and whenever product/version, market, language or required user information changes.
- Information your team brings
- Product/version and market facts, intended user information, language/release-pack content, responsible publication owners and retention evidence.
- What your team can document
- A market/language release-pack status and retained information record.
- Who should own the output
- Product Compliance and Technical Publications.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
23Annex VII Technical Documentation Master Index
Provide a controlled index of technical-file content so missing, stale or ownerless documentation is visible before a readiness decision.
- What you receive
- A document-based Annex VII Technical Documentation Master Index inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Provide a controlled index of technical-file content so missing, stale or ownerless documentation is visible before a readiness decision.
- When to use it
- During technical documentation build-up, release-readiness review and later revalidation.
- Information your team brings
- Product/version, required documentation categories, document owners, repository references, version/freshness and evidence status.
- What your team can document
- A technical-file completeness/index record with open documentation dependencies.
- Who should own the output
- Product Compliance.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
24Requirement-Control-Evidence Traceability Matrix
Connect a requirement to the implemented control and supporting evidence so product readiness can be reviewed as a traceable chain.
- What you receive
- A document-based Requirement-Control-Evidence Traceability Matrix inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Connect a requirement to the implemented control and supporting evidence so product readiness can be reviewed as a traceable chain.
- When to use it
- During assurance, engineering verification, audit preparation and release/readiness reviews.
- Information your team brings
- Applicable requirement, implemented product/control information, test or documentary evidence, product/version, owner and remediation status.
- What your team can document
- A requirement-to-control-to-evidence trace showing verified items and unresolved remediation.
- Who should own the output
- Compliance and Product Security.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary. The traceability method depends on current product facts, evidence ownership and review of unresolved legal or technical questions.
25Conformity Assessment Routing Engine v0.3.1
Prepare a legally supportable conformity-assessment route using product classification and current standards/certification context.
- What you receive
- A document-based Conformity Assessment Routing Engine v0.3.1 inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Prepare a legally supportable conformity-assessment route using product classification and current standards/certification context.
- When to use it
- After scope, operator role and classification are established and before the organisation commits to a conformity route.
- Information your team brings
- Product classification, applicable legal provisions, standards/certification status, notified-body dependencies and current legal evidence.
- What your team can document
- A documented conformity-routing state, including unresolved/legal-review status where a route cannot responsibly be concluded.
- Who should own the output
- Product Compliance and Legal.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary. “Engine” is the name of a document-based method, not executable software.
26Standards, Certification & NANDO Status Register
Maintain current evidence for standards, certification and notified-body/NANDO dependencies that may affect conformity planning.
- What you receive
- A document-based Standards, Certification & NANDO Status Register inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Maintain current evidence for standards, certification and notified-body/NANDO dependencies that may affect conformity planning.
- When to use it
- When conformity work depends on time-sensitive standards, certification or notified-body availability/status.
- Information your team brings
- Exact standard/certification references, OJ/NANDO or other authoritative status evidence, dates, applicability and product dependency.
- What your team can document
- A current dependency/status record that identifies what must be revalidated before reliance.
- Who should own the output
- Compliance, Standards and Procurement.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
27EU Declaration Readiness Checklist
Check whether the organisation has the required inputs and evidence to prepare the EU declaration workstream.
- What you receive
- A document-based EU Declaration Readiness Checklist inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Check whether the organisation has the required inputs and evidence to prepare the EU declaration workstream.
- When to use it
- Near declaration/release readiness and whenever product, conformity route or evidence changes materially.
- Information your team brings
- Product identity, conformity route, required declaration information, supporting technical evidence, responsible sign-off and version control.
- What your team can document
- A documented declaration-readiness/completeness state with outstanding items visible.
- Who should own the output
- Product Compliance and Legal.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary. The website does not publish the complete checklist.
28CE Marking Readiness Gate
Document whether prerequisites for the CE/market-access step are established without representing the result as an authority-issued approval.
- What you receive
- A document-based CE Marking Readiness Gate inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Document whether prerequisites for the CE/market-access step are established without representing the result as an authority-issued approval.
- When to use it
- At the controlled release/readiness gate after upstream scope, classification, technical documentation and conformity work.
- Information your team brings
- Product/version, applicable route, declaration/technical evidence, required markings/information, unresolved dependencies and accountable approvals.
- What your team can document
- A CE/market-access prerequisite state identifying open blockers or review needs.
- Who should own the output
- Product Compliance.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary. It does not certify conformity or grant market access.
Cross-regulation & portfolio
29CRA / High-Risk AI Interaction Record
Document cross-regulation dependencies where a product may also fall within the relevant high-risk AI context.
- What you receive
- A document-based CRA / High-Risk AI Interaction Record inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Document cross-regulation dependencies where a product may also fall within the relevant high-risk AI context.
- When to use it
- When CRA product work intersects with high-risk AI obligations/routes and teams need a single record of unresolved interactions.
- Information your team brings
- Product/use-case facts, AI regulatory classification/context, CRA scope/classification, authoritative source status and accountable legal/product review.
- What your team can document
- A documented AI cross-route state and open dependencies for specialist review.
- Who should own the output
- Legal and Product Compliance.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
30EHDS / CRA Interaction Record
Document the staged interaction between CRA and relevant EHDS/EHR-system context without collapsing distinct legal regimes.
- What you receive
- A document-based EHDS / CRA Interaction Record inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Document the staged interaction between CRA and relevant EHDS/EHR-system context without collapsing distinct legal regimes.
- When to use it
- Where product scope or market planning involves an EHR-system/EHDS route that can affect CRA implementation planning.
- Information your team brings
- Product/use-case facts, applicable EHDS/EHR context, CRA status, source/version status and accountable legal/compliance review.
- What your team can document
- A documented cross-regulation route state with unresolved dependencies visible.
- Who should own the output
- Legal and Product Compliance.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary.
31Market Surveillance Response Pack
Organise authority-response and corrective-action evidence for a market-surveillance interaction.
- What you receive
- A document-based Market Surveillance Response Pack inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Organise authority-response and corrective-action evidence for a market-surveillance interaction.
- When to use it
- When an authority request, surveillance case or corrective-action process requires controlled evidence and response coordination.
- Information your team brings
- Authority/case details, product/version, requested evidence, technical file references, response/corrective actions, owners and deadlines from the actual case.
- What your team can document
- A controlled authority-response/corrective-action record for the organisation's system of record.
- Who should own the output
- Legal and Product Compliance.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary. It does not predict or guarantee an authority outcome.
32CRA Product Readiness Gate™ / Enterprise CRA Portfolio Dashboard
Combine product-level readiness outputs into a controlled release/readiness decision and, only after traceability is established, an executive portfolio view.
- What you receive
- A document-based CRA Product Readiness Gate™ / Enterprise CRA Portfolio Dashboard inside the report, with defined purpose, evidence expectations and a recordable output.
- The decision it supports
- Combine product-level readiness outputs into a controlled release/readiness decision and, only after traceability is established, an executive portfolio view.
- When to use it
- At product readiness/release gates and for portfolio reporting after each product-level decision is traceable.
- Information your team brings
- Product-level scope/classification, Article 14 status where relevant, technical/evidence completeness, conformity dependencies, open blockers, owners and review dates.
- What your team can document
- A documented product readiness state plus a portfolio-level summary that preserves unresolved and blocking dependencies.
- Who should own the output
- CISO, Legal and Compliance.
- Boundaries and dependencies
- This is a document-based decision aid within a regulatory decision-support publication, not legal advice, executable software or an automated compliance determination. Organisation-specific product facts, current legal/source status and accountable review remain necessary. The dashboard is a document-based reporting method, not a live dashboard or automated monitoring application.
Organisation-specific inputs
Current product facts and evidence drive the result.
Exact product boundary, version, intended purpose, market facts, economic-operator role, legacy status and classification inputs.
Chronology, awareness evidence, exploitation/impact facts, mitigations, affected versions and filing/receipt history.
Architecture, Annex I controls, component/build mapping, SBOM, supplier evidence, tests and remediation state.
Annex II/VII records, standards/certification status, notified-body dependencies, DoC/CE prerequisites and approvals.
Outputs leadership can use
Product-specific readiness states preserve hard blockers instead of averaging them away.
Live reporting state
Article 14 capability, control gaps and blockers remain visible independently of the 2027 transition programme.
Product readiness
Transition-on-track, remediation, conformity preparation, evidence hold and release-blocker states are recorded by product.
Evidence traceability
Requirement → control → evidence → test → result → remediation → retest provides a reproducible assurance chain.
Executive escalation
Deadline risk, unresolved legal route, market-access blockers and authority dependencies are routed without hiding the cause.