Where should a late-starting team begin?
Begin with the legal actor, the portfolio boundary, and the evidence of what is already registered. Those three questions help separate a genuine submission backlog from an identity, scope, or search problem. Resist treating every uncertain row as an identical task.
The legacy device registration deadline is , as confirmed by the Commission’s devices and certificates timeline. Read the deadline guide to assess which records are covered by the transition.
This triage plan is a practical project recommendation. It does not determine whether a device qualifies for a transition or whether continued market placement is lawful. A qualified professional should review those decisions against the actual regulatory route and evidence.
What belongs in the first portfolio pass?
Create one working inventory that links each in-scope device to its legal manufacturer, regulatory route, known identifiers, and registration evidence. Keep unresolved questions visible. Do not infer status from a commercial product family or a past sales date alone.
The Commission’s UDI/Device resources distinguish Regulation and legacy datasets. Record the route before choosing a template or preparing identifiers. Where further units continue to be placed on the market, make that fact explicit for the person assessing the transition.
A useful initial work queue separates records that appear complete, records that need internal evidence, and records that need action or professional review. These are your project categories, not official EUDAMED statuses. Give each category a clear definition so colleagues use it consistently rather than silently changing what “complete” means.
How should you check the actor dependency?
Verify the manufacturer’s legal identity and SRN before assuming a product-data upload can proceed against the correct actor. If the SRN is unknown, identify the person who holds the registration evidence or can check the request. An AR’s actor record is not a substitute for the manufacturer’s own record.
The official Actor registration guidance describes the request, authority assessment, and identifier generation. For a non-EU manufacturer, also confirm the active AR relationship and mandate summary. Track an outstanding request as an external dependency without inventing an approval date.
Prepare product data in parallel where sensible. The key is to label that work accurately: a reviewed source file is ready data, while an accepted record is a different milestone. This distinction keeps progress reports useful when several people are working on different parts of the chain.
Which gaps deserve separate owners?
Assign identity questions to the person who can verify the legal actor; grouping questions to the responsible regulatory and technical owners; data gaps to the source-data owners; and submission questions to the authorized operator. A single generic task owner may lack the information or authority to resolve every category.
For each gap, write the next decision, the owner, the evidence needed, and the expected completion evidence. If the action depends on an AR, notified body, or authority, name the dependency. An explicit escalation path is more useful than a deadline attached to an undefined task.
Hold a short review of blocked items. Ask what is preventing the next concrete action and whether the right person has been asked to decide. Avoid using the review merely to repeat the number of unfinished rows. The goal is to turn uncertainty into an answerable question.
How should identifier and device-data work be sequenced?
Confirm the applicable identifier structure before reproducing it across the portfolio. Regulation-device grouping involves Basic UDI-DI and specific UDI-DIs; legacy devices require their own identifier assessment. Read Basic UDI-DI explained if the source inventory uses a single undifferentiated UDI column.
Select a representative set of records with different relevant characteristics and review the mapping before scaling it. This is a recommended quality check, not a substitute for reviewing the full in-scope portfolio. Capture the rationale for exceptions so the next preparer does not have to rediscover the same issue.
Then compare the prepared data with the current official dataset and submission rules. Do not fill unknown values simply to make a file pass a superficial completeness check. Preserve the question, obtain the source evidence, and keep the decision attributable to the appropriate owner.
Should automation be the first rescue step?
Choose the entry method after understanding the data and recurring workload. EUDAMED supports manual input, XML bulk upload, and M2M exchange. The Information Centre provides indicative volume tips, but portfolio size alone does not decide the best project plan.
Ask whether a proposed automation route can be set up, checked, operated, and handed over within your actual schedule. A large backlog may justify bulk preparation without requiring a permanent integration. Our input-method guide explains the distinction between an upload and an ongoing system connection.
Whatever method you select, retain an owner for failed records and reconciliation. A transmission success message cannot explain which source rows were excluded or which unresolved decisions were deferred. The project needs evidence at the record level as well as the file or interface level.
What should the completion review include?
Compare the approved scope with the resulting actor and device records, identify any unresolved exceptions, and confirm who accepts the handover. A completion review should let another authorized colleague understand the result without relying on the preparer’s memory.
Keep the actor reference, identifier mapping, reviewed data version, submission outcomes, and correction log together. Confirm who maintains the records when devices or business relationships change. This supports continuity beyond the November deadline and makes the next update easier to assess.
Coordinate certificate questions separately with the notified body. The transition concerns qualifying earlier MDR/IVDR certificates, rather than extending every new certificate’s registration timing. Do not let the later date obscure an unresolved issue relevant to the present portfolio.
When is outside help useful?
Outside support is useful when the missing piece is professional assessment, data preparation capacity, or coordination your team cannot resolve internally. Describe the specific gap and expected output before asking for a quote. A bounded scope makes the provider’s proposal easier to evaluate.
Request a free public-record check for an initial dated observation, or share your qualification details for an independent specialist introduction. We provide information and referrals; we do not register the devices or guarantee the result. Any professional engagement is agreed directly between your company and the provider.