Full Multi-Perimeter Assessment

Whatever inventory exists, however incomplete, plus the protocol and any amendments already executed. Beyond that: your target markets and the submission sequence you intend to follow, the supplier and economic-operator arrangement in each market — who manufactures, who relabels, who imports, under whose name — and any quality documentation or prior assessments already held. Where the inventory has holes, we tell you which questions to put to which supplier.

A Full Multi-Perimeter Assessment covers the devices and jurisdictions frozen into scope at the written quote. It does not include: devices added to the protocol after scope freeze — those are assessed by agreement or by Snapshot RIA; execution of any remediation identified; preparation or submission of a regulatory filing in any market; validation testing or evidence generation; notified body engagement on your behalf; and it is not legal advice. It records a regulatory position per device per market and the reasoning behind it — it does not bind a regulator, notified body or inspector to the same conclusion.

The comparative matrix shows you where the answers diverge, and divergence is what sets sequence: the market with the tightest classification usually determines the evidence everything else inherits. The consolidated trigger register tells you which changes would move which device in which market. From there you choose whether to close the gaps yourself, with us, or not at all — only the modules that apply are recommended. Portfolios of this size normally move into scheduled re-assessment, because a portfolio assessed once and left alone is out of date on the first firmware release.

You receive a single controlled package:

1. Assessment report: the decision for each of the seven perimeters, for each device, in each jurisdiction in scope, with the reasoning and the regulatory basis cited to article or clause level.

2. Comparative jurisdiction matrix: one view showing where the answers diverge by market, and why, so the divergence is a decision you made rather than a surprise during submission.

3. Decision register: a per-device entry recording what was decided, on what basis, by whom, on what date, and what would change it. Versioned, so the history survives.

4. Consolidated trigger register: every re-assessment trigger across the portfolio in one place: firmware releases, OS updates, protocol amendments, supplier changes, algorithm retraining.

5. Evidence index and gap list: every document relied on, indexed so an inspector can follow the reasoning without asking you to reconstruct it, with the gaps prioritised by what they block.