Which Wheelchair Information Must Be Permanently Marked

Every test passed, and the file still gets stopped by a rating plate

There is one type of nonconformity in wheelchair projects that deserves attention: every bench test passes -- strength, stability, braking and electrical data all clean -- and the submitted file still comes back for correction, on the grounds that product information disclosure is incomplete. This happens often enough in practice, and the rework often costs more than repeating a test: changing one sentence in the instructions can mean re-laying out the document, re-translating it, re-printing the rating plate, and sometimes unpacking finished goods to re-label them.

ISO 7176-15 is the part that governs this. It is the odd one out in the ISO 7176 series: no test method, no fixture, no acceptance curve. What it specifies is which information the manufacturer should disclose, in what form, what must appear on the product itself, and what may sit in the accompanying documents. Put another way, the other parts of the series produce the data and this one makes the data intelligible. It is the outlet for the whole technical file. The specific requirements and how they are assessed are governed by the current valid version of the standard text.

First, correct a common misreading: disclosure is not the same as meeting a threshold

Companies meeting this part for the first time often assume it sets thresholds for certain indicators, and so blur or simply omit the items whose numbers do not look flattering. That is precisely the classic route to a nonconformity. What the part asks for is that information be given truthfully, accessibly and intelligibly -- write down what was measured. Deliberately leaving out a piece of information that should be disclosed carries far more risk than disclosing an unremarkable result.

By the same logic, writing the instructions as marketing copy creates problems. If the promotional wording does not match the conditions in the test report, the contradiction shows up the moment a reviewer compares them. Our usual advice on projects: every sentence in the instructions that touches performance or use limitations should trace back to a source in some test record. A sentence with no traceable source should either be deleted or rewritten so that it makes no performance claim. Doing this before submission is much less work than doing it after a correction notice.

Which information has to go on the product

There is only so much usable area on a product; you cannot mark everything. Deciding whether a given piece of information should be a permanent marking reduces to three questions. Does the user or carer need it at the point of use? Is it directly safety-related? Does it still have to be visible after the packaging has been thrown away and the instructions lost? If the answer to any one of them is yes, treat that information as a candidate for permanent marking on the product rather than putting it only in the accompanying documents.

Following that logic, product identification, the user mass limit, and use limitations tied directly to safety boundaries normally end up on the product itself, while configuration combinations, maintenance intervals and troubleshooting -- all of which need room to explain -- belong in the accompanying documents. Wheelchairs have a further peculiarity: they frequently change users during their service life, and second-hand circulation and reallocation within institutions are both common, so whether the information is still there once the product leaves its original packaging matters more here than for most other home-use products.

The permanent in permanent marking is a materials problem

The standard requires markings to remain legible under the expected conditions of use; the wiping method, the media used and the acceptance requirement are governed by the current valid version of the standard text. From an engineering point of view, though, the routes to marking failure can be reasoned out. The following is analysis based on materials and loading, not a statistical statement about failure rates.

First, peeling on curved surfaces. Wheelchair frames are mostly round tube, and powder coating leaves a low-energy surface. A self-adhesive label wrapped on a round tube has to hold against the bending recovery stress of the substrate; that stress concentrates at the label edge, so the edge lifts first, then collects dirt, then the whole label comes away.

Second, chemical softening. Care and institutional settings clean frequently, and alcohol- or chlorine-based disinfectants soften pressure-sensitive adhesive and bleach surface inks, so the text blurs before it disappears.

Third, heat and UV. On scooters used outdoors, the surface layer and the substrate have different coefficients of thermal expansion; repeated thermal cycling combined with UV ageing makes the surface layer brittle and chalks the printing.

Choosing the position is therefore often more effective than choosing the material: prefer flat areas or areas of large radius, avoid gripping surfaces that hands touch constantly, avoid high-frequency cleaning zones, and avoid places that will be covered long-term by the cushion, the footrests or the battery box. Folding products need one more check -- in the folded state the marking must not be trapped and rubbed between two structural members. For customers doing powered wheelchair testing and mobility scooter testing, we suggest fixing the rating plate position at the design stage alongside the sample plan, rather than discovering after the prototype is built that there is nowhere to put it.

The accompanying documents address several very different readers

This is where accompanying documents most often go wrong: everything gets stirred into one pot. In reality there are at least four audiences, each wanting something different.

Users want to know how to use it, when not to use it, and what to check before sitting down. Carers and attendants want to know about their own safety and the key operating points when pushing, going up and down slopes, transferring, and folding the product for transport. Service and repair staff want disassembly sequences, replaceable parts, adjustment ranges and tool requirements. Prescribers, purchasers and rehabilitation assessors want fitting ranges, configuration options and performance data, so they can judge whether the product suits a particular user.

If these four bodies of content are not separated into blocks, a reviewer can readily conclude that the information is not accessible -- it is in the file, but the intended reader cannot find it. The safe approach is to structure the document by audience, or at minimum to state at the head of each section who it is written for. Fitting and adjustment instructions for manual products are especially prone to being cut short; while you are arranging manual wheelchair testing, it is worth going through that section as well.

One table to sort out where information belongs

The table below does one job: it sorts information categories into permanent marking on the product, accompanying documents, or both, so you can run through your own file quickly. The placement judgement uses the three questions above; it reflects our engineering habit when doing pre-reviews, and is not a restatement of the standard's clauses.

The individual entries are governed by the current version of the standard text. This table gives an approach to placement, not a complete list of the information to be disclosed; when you actually prepare the file, still work through the standard text item by item and layer in the requirements of your local submission route.

Running a file against this table, a few mistakes turn up with unusual regularity and are worth listing on their own. Product identification printed only on the coloured carton, so traceability disappears when the box is thrown out. User-related safety boundaries written only into the instructions, with nothing on the product itself. Configuration descriptions written for the generic model only, with differences between configurations in one series waved through as depending on the specific configuration. Wording of use limitations that does not match the actual setup conditions during testing. Suitability for particular situations left unaddressed -- and avoidance is generally treated as missing information, which carries more risk than plainly writing that the product is not suitable. Matching information for charging and associated components appearing only once in the instructions, when the user typically has only the accessory itself in hand at the moment they need it. Disposal and recycling content present in the original-language version and dropped from the translation. None of these needs specialist judgement to catch, yet every one of them has genuinely caused corrections.

Graphical symbols save words, not explanation

Replacing text with graphical symbols is the standard way to relieve pressure on marking area. But symbols cannot stand alone: the accompanying documents must explain them, and the explanation must match the artwork actually printed on the product. A common project problem is that the design team revises an icon style while the explanation artwork in the instructions is still the old one, so the two do not agree. Invented symbols also need care -- whether users can understand them is the substantive question this part is concerned with, not a formality. The graphic conventions for symbols themselves are governed by dedicated symbol standards; which set to use, and whether the source has to be cited in the file, should be confirmed against your target market's submission requirements and the current valid version of the standard text, not copied from how a previous project was done.

Consistency across language versions is an underrated hazard

Export projects usually need several language versions, and those versions are almost always produced by different people at different times. Typical problems we have seen: the configuration description updated in one language and not in another; the same model written inconsistently across versions; data tables shifted out of line during translation; a warning rendered in one language as a suggestion, weakening its force.

A practical suggestion: extract every sentence in the instructions that touches model, configuration, performance or warnings into a single controlled list, run any change through that list, and let the list drive updates to all language versions. It sounds laborious, but it is far more reliable than comparing versions side by side. The list has a side benefit too -- it is effectively a half-built version of the data cross-reference table described below, so the two jobs can be done together.

Information requirements diverge once the same product faces different markets

For domestic submission the GB/T 18029 series applies, and the corresponding information and marking requirements are where that route lands. For export to the European Union, powered wheelchairs and scooters usually involve the parts of EN 12184 dealing with information for use; but that standard defines its own scope of applicable products, and whether yours falls inside it -- and what has to be satisfied in parallel if it does -- needs to be confirmed against the actual form of your product and the current valid version of the standard text, not assumed.

On the United States route there is a point that frequently gets written up incorrectly: whether this kind of product needs a 510(k) submission should be confirmed by looking up the specific product code in the FDA classification database to establish its classification and whether an exemption applies. Do not insist, on the strength of an impression of similar products, that a submission is mandatory, and do not insist that an exemption applies -- the database search result governs. Note also that even where an exemption applies, labelling and accompanying information requirements still apply; what is exempted is the premarket submission route, not the obligation to disclose information. Work through how the different markets relate on the testing standards page first, then decide how many versions of the file you need.

What to prepare for submission

Information items involve no bench testing, but preparing for submission is not light work. In our experience, having the following ready noticeably reduces the back-and-forth during pre-review.

The final instructions for use -- not a draft, and not a version where the content is roughly there but the layout is pending. Drawings of the rating plate and every marking, annotated with material, printing process and position on the product. Physical marking samples, preferably produced by the same process as production. Packaging label artwork. Model naming rules and the configuration matrix, showing which configurations in a series share one set of instructions and which need their own. And a cross-reference table linking the test data from each part to the instructions, pointing every performance statement in the instructions at its data source.

Many companies think that last table is busywork, but it is exactly the cheap way to expose contradictions early. In actual pre-review, mismatches between the use limitations described in the instructions and the actual test setup conditions are a concentrated source of problems in this class of item; pull the table together and the contradictions announce themselves.

Do your self-check in reverse order

Most teams check from the instructions downwards, which makes it easy to be carried along by their own text. A more effective order is the reverse: start with the raw data and test conditions in the test report, then check whether the accompanying documents present those data truthfully, then check whether the markings on the product agree with the accompanying documents, and finally check the packaging and the foreign-language versions. Data sits furthest upstream; working downstream, each layer does one job only -- compare, do not judge.

One more habit worth building: keep the last correction notice on file and go through it before submitting the next model. Wheelchair companies usually iterate variants off the same platform, and problems tend to recur with them.

What we can do

SUNGO Mobility Testing Lab regularly takes on testing and technical documentation pre-review for wheelchairs, powered wheelchairs, mobility scooters, walkers and crutches. Before formal submission we can go through marking layout, accompanying document structure, consistency across language versions and the data cross-reference table, to cut down correction rework. 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 has the corresponding technical capability within its accredited scope; it is not a commitment regarding market access in any target market.

If you have a specific model to schedule, or a correction notice in hand and no obvious place to start, call us on +86 132 4819 8029, or request a quote online -- we will look at the documentation before proposing a plan.