Finish the Classification Before You Shop for a Notified Body
Plenty of wheelchair manufacturers open the conversation with "which notified body should we use?" On most projects that question arrives far too early. Under the EU Medical Device Regulation (MDR), the conformity assessment route is driven by the risk class of the device. Manual wheelchairs, powered wheelchairs and mobility scooters in their common configurations - non-invasive, no contact with the interior of the body, no therapeutic intended purpose - normally land in a lower risk class. Landing there means the manufacturer can complete CE marking inside a self-declaration framework: no notified body appears in the process, and there is no third-party certificate to obtain. Collecting quotations from notified bodies at that stage usually means paying and queueing for something that was never required.
The classification conclusion cannot rest on impression, and it cannot be copied from a competitor. Work through the classification rules currently in force item by item, and capture the reasoning - which rule applies, why the others do not - as a traceable record inside the technical documentation. Where the product carries additional functions, an unusual configuration or unusual accessories, the final class follows from the comparison against the text of the rules; where necessary, confirm with a notified body or the competent authority before fixing it. "Everyone in our category does it this way" is not an argument. This classification record is the starting point for everything downstream: it decides whether you need a notified body at all, and it decides how deep the technical documentation has to go.
What Actually Pulls a Notified Body Into the Project
| Trigger | Scope of notified body involvement | What the manufacturer still owns |
|---|---|---|
| Device supplied in a sterile condition (for example single-use care components shipped with the chair) | Only the elements tied to the sterile barrier, the sterilisation process and packaging integrity | All remaining conformity evidence: structural strength, stability, electrical safety and everything else |
| Device with a measuring function in the regulatory sense (for example an integrated measurement whose result is declared) | Only the parts related to metrological requirements | The rest of the technical documentation and the self-declaration process |
| Accessories handled as reusable surgical instruments | Only the reprocessing-related content | Conformity at whole-device level |
| Configurations integrating a medicinal substance, materials of biological origin, or a therapeutic active function | Full conformity assessment, including quality management system and technical documentation review | Supporting the audit and supplying the complete evidence set |
| Customers, distributors or tender documents demanding a third-party certificate | Issued to the scope agreed in the contract; the regulatory route itself does not change | Deciding first whether the demand is genuinely necessary - a commercial request is not a regulatory obligation |
The line most often misread in this table is the assumption that any notified body involvement means the whole technical file gets reviewed cover to cover. In the first three cases the review has clear boundaries; everything outside them stays under the manufacturer's own declaration and the manufacturer's own liability. The last row is not a regulatory question at all - it is a contractual one, and it is worth going back to the customer to find out what they actually want. Often a declaration of conformity plus a complete set of test reports settles it. Getting the boundary right is what makes quotations, lead times and workload estimates realistic.
The reverse point deserves saying too: self-declaration does not mean no testing. A lower risk class still demands a complete safety and performance evidence base. What disappears is the third-party certificate, not the evidence, and the completeness of that evidence rests entirely with the manufacturer. The usual technical basis for complete wheelchairs remains EN 12183, EN 12184 and the ISO 7176 series; the applicable test items, parameters and pass criteria are governed by the version of each standard currently in force. If you want to see where the test scope begins and ends, start with the standards and test item index.
What the Self-Declaration Route Requires You to Have on File
Most wheelchair projects stop right here. Getting the following solid is worth far more than researching how to pick a notified body:
- Technical documentation: description of intended purpose and use environment, design and manufacturing information, a clause-by-clause mapping against the general safety and performance requirements (stating which evidence supports each one, with a written justification for every requirement declared not applicable), the bill of materials, and the rationale for how the model family was drawn.
- Risk management file: established and maintained to ISO 14971, with every risk control measure pointing to the specific evidence that verifies its effectiveness rather than stopping at a paper statement.
- Test evidence: whole-device testing organised around EN 12183, EN 12184 and the ISO 7176 series; powered products additionally need electrical safety and electromagnetic compatibility coverage, together with a statement that the samples tested match the configuration intended for the market.
- Labelling, instructions for use and symbols: consistent with the technical documentation. Intended user, warnings and use restrictions cannot be described one way in one document and another way somewhere else.
- Post-market elements: post-market surveillance plan, complaint and adverse-event handling procedures, the necessary registration and unique device identification records, and arrangements covering the relevant economic operator roles inside the EU.
- Declaration of conformity: signed by the manufacturer. Once it is signed, the liability sits entirely with you.
The real exposure in self-declaration is not that nobody reviews the file - it is that nobody reviews it in advance on your behalf. Market surveillance by a competent authority, a customer's compliance review, a distributor's document request: any one of them can ask for exactly the materials listed above, and running the tests at that point costs far more time than running them early.
The sections below apply only where a notified body is genuinely required. If your classification lands on self-declaration and there is no contractual demand for a third-party certificate, you can skip all of it.
(Notified Body Route) Verify the Designated Scope Before Discussing Price
Notified body designations are granted by field. Each body has a defined list of device categories and technical scopes, and it cannot accept work outside them. Whether wheelchairs and scooters fall inside a given body's designation is something to confirm before any work starts. You can ask the body for its designation documentation, or check the official database yourself - the database result is what counts. We have seen companies pay an application fee only to be told afterwards that the category was not covered, with the schedule lost for nothing.
The second thing to settle is language. Which language the technical documentation body text, instructions for use, labelling and risk management file must be submitted in, whether English plus a native-language summary is acceptable, who is responsible for translation, and who carries the consequences of a translation error - agreeing this at contract stage is far cheaper than retro-fitting translations later.
The third is scheduling. Review slots and on-site audit windows are normally locked in well ahead, not booked on demand once your documents happen to be ready. Contract signature, application acceptance, document review, on-site audit, clarification rounds and certification each sit behind a queue. Setting internal milestones by working backwards from a target certification date tends to be far more realistic than pushing forward from your own development rhythm.
(Notified Body Route) What the Exchange Looks Like After Submission
Once the technical documentation goes in, the typical rhythm runs: completeness check (are the documents all there, do they meet the required format) - technical review - issue of a question list - manufacturer response - re-review - a further round of questions if needed - conclusion. Most projects do not clear in a single round. Preparing for several response cycles is normal practice, not a sign that something has gone wrong.
Response quality is where projects are won or lost. Notified body questions are usually "please explain" rather than "please send more" - what they want is a chain of reasoning, not another PDF. Structuring each answer in four parts (the question, where the evidence sits, the reasoning, and what was updated in the file) works better than attaching a pile of annexes. Every response should also carry a matching update to the technical documentation version record, otherwise the next round will raise the same point again because the file and the answer no longer agree.
Also worth understanding is the clock-stop mechanism: the period between the question list being issued and your response being received normally does not count against the notified body's processing time. If your internal team lets a response drift, the body's own performance window is unaffected - the only schedule that stretches is your launch plan.
(Notified Body Route) Recurring Themes in the First Round of Questions
The table below collects the question themes that come up frequently on wheelchair projects. It is a root-cause analysis at engineering and documentation level, not a statistical finding.
| Question type | Typical notified body question | Common root cause | How to close it before submission |
|---|---|---|---|
| Model family grouping | Why can these models share a single test report? | The family was drawn too broadly and only one variant was tested | Set out the grouping rationale and the logic behind choosing the representative configuration, explaining why it covers the rest |
| Sample representativeness | Do the samples tested match the product to be marketed? | Frame, cushion or controller changed after samples were submitted | Keep a configuration list and change record for the samples; assess whether retesting is needed after any change |
| Justification for untested items | Why are certain items not applicable? | "Not applicable" written with no reasoning behind it | Justify each item against the product structure and intended purpose, citing risk management conclusions as support |
| Bought-in component evidence | Compliance evidence for batteries, chargers and controllers | Only supplier component reports supplied, no verification at whole-device level | Add verification in the assembled condition and explain the limits of applicability of the component reports |
| Closing the loop between risk and test | What verifies this risk control measure? | Risk management file and test reports written independently of each other | In the ISO 14971 risk management file, tag every control measure with the reference of the verification evidence |
| Labelling and instructions | Are warnings, symbols and intended-user descriptions consistent? | Instructions drafted separately by marketing, diverging from the technical file | Run a cross-document consistency check before submission |
| Post-market plan | How will post-market surveillance actually work? | The plan treated as a template exercise | Write it as executable data sources, review cadence and trigger conditions rather than copying a template |
(Notified Body Route) QMS Audit: An ISO 13485 Certificate Is Not a Ticket In
Where a notified body has to be fully involved, a quality management system audit comes with it. The common misjudgement is "we already hold ISO 13485, so the system side should be fine." Two things need separating here. ISO 13485 certification is a voluntary third-party system certification; the MDR system requirements overlap heavily with it but are not identical. The notified body will examine, against the regulation, content the standard does not necessarily elaborate: the post-market surveillance system, the handling of vigilance and trend reporting, records relating to unique device identification, control of the supply chain and outsourced processes, and the mechanism for keeping technical documentation current.
Two things are worth doing in advance. First, build a mapping table between your ISO 13485 system documents and the regulatory requirements, marking each line as already covered, needs supplementing, or needs a new process. Producing it during the audit visibly cuts the time spent hunting for documents. Second, rehearse a traceability spot-check. Auditors commonly start from the serial number of a finished unit and work back to the batch record, incoming inspection, key component supplier and release record; a single break in that chain becomes a nonconformity.
(Notified Body Route) How Test Reports Are Used During Review
A notified body does not repeat the testing. What it reviews is whether the report can carry the conformity claim you are making. How to judge whether a report is usable in the first place - the competence of the issuing body, the coverage of the test items, the form of the report - is a separate discussion we handle elsewhere. This section is only about what happens to a report once it enters review.
During review, reports are rarely read on their own. They are always cross-checked against other documents: the sample description has to line up with the model family and bill of materials in the technical file; every test item not performed has to have a not-applicable justification traceable in the risk management file; every risk control measure has to point to the specific part of a specific report that demonstrates its effectiveness. Any deviation from the conditions specified by the standard should be stated in the report itself, together with the technical reasoning. Explaining a deviation only after being asked carries visibly less weight. Where the harmonised standards list status matters, confirm it before submission, because it affects whether you can claim presumption of conformity directly; the official list currently published is what governs.
Powered products add a further layer: whole-device electrical safety and electromagnetic compatibility evidence has to cover the actual conditions of use, including the charger and battery combinations shipped with the product. Where components are supplied separately or several battery options exist, expect questions about which combinations the verification covered and on what basis the remaining ones are considered no more onerous. For how testing is organised across different product lines, see powered wheelchair testing and manual wheelchair testing.
(Notified Body Route) Small Communication Details That Get Overlooked
- Keep one point of contact. The notified body has a project manager and technical reviewers; you need one person who understands both the regulatory language and the engineering language. Information leaks with every extra hand-off.
- Put it in writing. Understandings reached by phone or in a meeting should be restated by email afterwards and confirmed by the other side. When a disagreement surfaces late in the process, those emails are your record.
- Do not paraphrase the questions. Give the notified body's original wording straight to the R&D and testing teams. An extra layer of interpretation in the middle is a reliable way to answer the wrong question.
- Report changes proactively. Design changes, manufacturing site changes and key supplier changes during the certificate validity period generally require prior notification. Judging on your own that "this change is small" carries real risk.
Run Your Own Pre-Review Before You Submit
Whichever route you are on, asking the external questions internally first is one of the highest-value ways to compress the schedule. A workable order: is the classification record complete and reasoned - is the model family and representative configuration selection clearly written - does every applicable requirement have matching evidence - is every non-applicable item individually justified - do the risk management file and test reports cross-reference each other - are the instructions, labelling and technical file consistent - is the post-market plan executable. On the notified body route, add two more: is the mapping table between system documents and regulatory requirements ready, and has the body's designated scope been verified. Anywhere you cannot answer, fix it internally before submitting. That is cheaper than fixing it during a clock stop.
Where We Can Help With Testing and Documentation
SUNGO Mobility Testing Lab focuses on wheelchairs, powered wheelchairs, mobility scooters, walkers and crutches. We organise whole-device testing to EN 12183, EN 12184 and the ISO 7176 series, and we work alongside your ISO 14971 risk management file to map test evidence onto risk control measures. On self-declaration projects we help package test evidence into a form the technical documentation can cite directly; where a notified body is genuinely required, we help assemble the test evidence portion of the submission. The laboratory is accredited by CNAS, CMA and IAS (USA), with laboratories in Shanghai and Hefei. To be clear: an accreditation mark only demonstrates that the laboratory holds the corresponding technical competence within its accredited scope; it is not a commitment regarding market access outcomes. The classification conclusion is determined by the manufacturer against the regulations in force, and the conformity assessment conclusion is made by the notified body and the competent authority.
For the range of work we can take on, see the testing services overview. If you already have a specific model and target market, call +86 132 4819 8029 with your product configuration and the route you plan to take, and we will come back with a proposed test scope and schedule. You can also request a quote online.