What should you prepare before opening the registration screen?
Prepare the exact legal actor identity, intended role, required signed declaration, and the person responsible for responding to the request. Non-EU manufacturers also need the active Authorised Representative relationship and mandate summary. The Commission’s Actor registration page is the starting source for those requirements.
This walkthrough focuses on preparation and evidence. Use the current EUDAMED user guides and templates for the live interface. Screen labels and detailed workflows can change; a preparation pack should support the current process rather than preserve an outdated set of clicks.
How do you establish the right legal entity?
Check the manufacturer or other actor’s exact legal name, country, registered address, and role against reliable business records and the relevant product documentation. A trading name alone may not identify the actor. Resolve contradictions before copying the identity into the request.
Create an identity sheet that names the source of each detail. This is a suggested internal aid, not an official EUDAMED form. If a parent company, subsidiary, or brand appears in different documents, ask the appropriate owner to determine which entity is relevant instead of choosing the most recognizable name.
Search known public records and ask internal colleagues for any existing SRN or request reference. Avoid assuming that an unsuccessful search under one name means no registration exists. If the issue is access to an existing record, keep that separate from the question of whether a new actor request is needed.
How should you confirm the actor role?
Determine the activity of the legal entity in the actual supply chain. The Commission lists manufacturers, Authorised Representatives, importers, and system/procedure-pack producers in its standard actor-registration description. A commercial job title or website category should not replace this role assessment.
If your business distributes devices, check whether it also performs importer or manufacturer activities. Additional roles and national requirements may need professional review. The Commission’s listed MDCG actor guidance helps identify the appropriate questions without assuming that every distributor needs the same registration.
Write unresolved role questions down with the facts that would answer them. A well-defined question can be reviewed by a qualified adviser. An uncertain dropdown selection hidden in a completed request is harder for the team to recognize and correct later.
Which information-security document is needed?
The Commission states that actors must upload a signed declaration on information-security responsibilities. Obtain the current template from the official actor-registration resources. Confirm the correct organizational details and the appropriate signatory before requesting a signature.
Keep the reviewed version and the signed version together so the preparer can identify what was actually submitted. Do not assume an old copy signed for another entity or purpose is suitable. Where the organization is uncertain about who may sign, resolve that question through its normal authorization process.
This document should be treated as part of the real registration request, rather than an administrative placeholder. The website does not supply invented signatory details or suggest signing on behalf of a company without authority.
What extra preparation does a non-EU manufacturer need?
Confirm the active EU Authorised Representative and prepare the mandate summary identified by the Commission. Reconcile the manufacturer and representative names with the underlying arrangement. An importer relationship should not be treated as an AR appointment without confirming the actual roles and mandate.
Ask the representative who will review the registration relationship and who will respond if details need correction. Confirm which project tasks it is handling and which remain with the manufacturer. Our US manufacturer guide explains why the AR’s record does not replace the manufacturer’s own actor record.
Keep professional review of the mandate separate from uploading its summary. A file can be technically ready while the relationship it describes remains unresolved. The person responsible for the agreement should confirm the substance before an operator treats it as a completed input.
What happens after the actor request is submitted?
The concerned competent authority assesses the request; EUDAMED generates the actor identifier following approval. Record the submission reference and keep a clear owner for questions. Do not interpret a submitted request as an approved actor record or promise an approval date on behalf of the authority.
Follow the current official process for the role and concerned authority, including any relevant national instructions. If information is returned for correction, preserve the question and the corrected version. A short change log helps the next colleague understand what changed and whether further action is pending.
For an urgent portfolio, use the waiting period to prepare device information and resolve identifier questions. Label the milestones accurately. “Source data reviewed” and “actor approved” are different results and should remain distinct in the project status.
Who can work on behalf of the registered actor?
Individual access is a separate step. The Commission explains that people who intend to act for a registered actor need an access request. Confirm the authorized users and appropriate permissions for the work being planned instead of assuming that actor approval grants everyone access automatically.
Identify an internal owner for user continuity and provider changes. Use the authorized process for adding or changing access, and avoid informal credential sharing. A robust handover should explain who can authorize future work without publishing private account details in public prospect files or project notes.
What should the final preparation and handover pack contain?
Keep the approved identity, actor role, SRN, submitted document versions, request history, and current access owner together. Document outstanding questions and the next person responsible for each one. This is a practical project pack, rather than a claim that the Commission requires a separate filing in this format.
Then connect the actor work to the device-identifier structure and the applicable deadlines. An SRN is the start of the database identity chain, not proof that the full portfolio is registered or that every regulatory condition has been met.
If you need to establish what is currently visible, request a free public-record check. If the gap needs professional assessment or preparation support, share your situation for an independent specialist introduction. Any engagement and its responsibilities are agreed directly with that provider.