PRRC services: qualifications, availability and written responsibilities
MDR Article 15 distinguishes a manufacturer’s internal PRRC from the permanent, continuous availability arrangement allowed for qualifying micro and small enterprises. It separately addresses authorised representatives. Check the actual organisation and evidence of expertise before deciding that an external service fits.
Evidence retrieved 2026-10-06. Source versions and topic-specific limits are listed below.
Sourced criteria · EU
What changes the service scope?
Decision or task
What the source describes
What to prepare
Which qualification route is evidenced?
Article 15(1) describes relevant formal qualifications plus at least one year of relevant experience, or four years of relevant experience; it separately describes custom-made expertise. [1]
Check the proposed person against the applicable route, including national professional-qualification provisions.
Internal person or external availability?
Article 15(1) says within the manufacturer organisation; paragraph 2 permits a different arrangement for qualifying micro and small enterprises, with permanent and continuous availability. [1]
Document enterprise eligibility and how continuous access, absence and urgent decisions will work.
What tasks are assigned?
Article 15(3) covers release conformity checks, current technical documentation/declaration, post-market obligations, reporting and the investigational-device statement where relevant. [1]
Match each applicable responsibility to records and access; split joint responsibilities in writing as paragraph 4 requires.
Does representation settle manufacturer responsibilities?
Article 15(6) addresses the representative’s own PRRC arrangement; Article 11(4) restricts delegation of manufacturer obligations. [1][2]
Scope the manufacturer and representative roles separately before accepting a combined quotation.
Eligibility, device context and evidence of actual availability remain incomplete. A directory listing is not evidence of qualification or a compliant PRRC arrangement.
A scoped evidence and handoff plan
Use this checklist to gather your business or product details before speaking with a specialist. The items below explain what to record and suggest useful supporting documents. You can add your own answers in the editable project brief.
Which qualification route is evidenced?
Check the proposed person against the applicable route, including national professional-qualification provisions.
Useful evidence: Qualification documents, dated experience and covered device responsibilities.
Internal person or external availability?
Document enterprise eligibility and how continuous access, absence and urgent decisions will work.
Useful evidence: Enterprise-size assessment, availability commitments, backup and escalation plan.
What tasks are assigned?
Match each applicable responsibility to records and access; split joint responsibilities in writing as paragraph 4 requires.
Useful evidence: Release/document/reporting responsibility matrix and access permissions.
Does representation settle manufacturer responsibilities?
Scope the manufacturer and representative roles separately before accepting a combined quotation.
Useful evidence: Two role descriptions with covered entities and deliverable ownership.
Work packages and dependencies
Conditional: Qualification, availability and responsibility assessment — For this work package, agree the supported criteria, evidence access, covered entities/products and unresolved facts in the table above. Additional services require their own justified scope.
Questions for providers
Which exact actor, product or processing facts support the quoted scope, and what is still unresolved?
How will the listed records reach the responsible people, and who owns each change or authority request?
Which tasks and entities are excluded from the agreement, and which additional services need a separate assessment?
Sources and data dates
Read the official document in context. The audit details identify the precise locators and preserved versions used for this page.