The short version: scope decides where a report can be used, not whether the product gets approved
When a third-party test report lands on your desk and you have to judge whether it is good enough, there are really only three things to look at: which legal entity issued the report; how far the capability scope behind the accreditation mark on that report actually reaches; and whether your sample and your test method fall squarely inside that reach. If all three line up, the report is technically credible. If any one of them does not, the report can come back at you during regulatory review, customer acceptance or a QMS audit with a request for clarification, and in the worst case the testing has to be redone.
One misconception is worth clearing up first, because it sits at the root of a lot of rework: an accreditation mark only demonstrates that the laboratory holds the corresponding technical competence within its accredited scope; it does not constitute a commitment regarding the market access outcome in the target market. It answers the question "can this lab measure this parameter by this method", not the question "will your product be approved". Treating the two as one and the same is where many projects quietly plant their rework risk at the planning stage.
A scope is locked down by four elements at once, and missing one means no coverage
Plenty of people check a scope by asking only "have they handled this kind of product before". That is not enough. Under ISO/IEC 17025 an accredited scope is a multi-dimensional combination, and coverage exists only when all four elements are hit at the same time.
| Element | What it constrains | Typical consequence of a mismatch |
|---|---|---|
| Field and product category | Which class of sample can be accepted, for example medical devices, rehabilitation aids, textiles and polymer materials | A sample in an out-of-scope category can only be reported as a non-accredited item |
| Test item or parameter | What is actually measured, for example a given mechanical property or a given electrical safety characteristic | Items with similar names but different substance get challenged in review as not being the same thing |
| Method standard applied | Which standard, and which part of it, is executed | A method standard outside the scope means method validation or a scope extension, and the timeline stretches |
| Limitations and remarks column | Parameter bands, sample forms, "specific test rig only" and other side conditions | Ignore the limitations and the data you generate sits outside the capability boundary |
The limitations and remarks column is the one most often skipped, and it is where the traps cluster. It frequently carries wording such as "applicable only to samples of a certain form", "excluding a certain type of special construction", or "parameter band restricted to one range". The moment your sample falls on the excluded side, the other three elements can all match and you still have no coverage.
Three steps to check a scope yourself
You do not have to wait for the lab to send over a credentials package. This can be finished on your own at the planning stage.
Step one. Take the accreditation certificate number and the full legal name of the holder from the cover of the specimen report or credential document you were given. The full legal name has to match the party that signs the contract. Groups with several legal entities behind one brand are common: company A signs the contract, company B holds the certificate, and the chain of legal responsibility for the report now has a break in it. That kind of break is almost always picked up in a QMS audit.
Step two. Go to the accreditation body's public search portal and pull up the capability annex by certificate number. The annex is the scope itself. A marketing page claiming "we have the capability to test X" carries no legal meaning. The annex is normally segmented by product category, with test items and the method standards they rely on listed under each segment.
Step three. Lay your test plan against it line by line. Compare as a package of three, item name plus method standard plus limitation remarks, instead of searching for a standard number on its own. A single standard number spans several parts and several parameters, and a laboratory is typically granted only a subset of them, so searching by standard number alone makes it very easy to arrive at a false conclusion of "covered".
Put the comparison result straight into the pre-contract technical communication record. We place this step ahead of quotation in the testing process precisely because at that point it costs nothing.
Four common mismatches, and what to do about each
| Situation | How to spot it | Workable handling | Cost |
|---|---|---|---|
| The lab is accredited, but your item is not in the scope | The item cannot be found in the annex, or the item name means something materially different | Report the item as non-accredited, or move it to a laboratory whose scope covers it | Whether non-accredited data is accepted depends on the receiving party, so there is a risk of rejection |
| The item is in the scope, but the method standard differs | The item matches, the standard or the part does not | Run the method validation route, or apply for a scope extension | Extra validation testing and internal review are needed, and the timeline stretches noticeably |
| The scope names a broad product family, your product is a sub-category | The family matches, but the remarks constrain construction or form | Submit a sample construction description in advance and let the lab decide whether it sits inside the capability boundary | If the decision goes against you, the slot already booked is wasted |
| Some items have to be subcontracted | The report carries a subcontracting indication or cites third-party data | Confirm the subcontractor's accreditation status and agree the subcontracting arrangement in writing before placing the order | Subcontracting that was not disclosed in advance can be treated by the receiving party as a defect in the report |
Subcontracting deserves a couple of extra sentences. Subcontracting is a perfectly compliant, routine arrangement, provided the client knows about it and agrees in advance and the report identifies it clearly. What actually causes trouble is invisible subcontracting: the client assumes everything was done under one roof, the report arrives and a few items turn out to have come from somewhere else, and that somewhere else does not have the scope either. Asking about subcontracting intentions before the order is placed, and writing it into the testing requirements checklist, is far more useful than assigning blame afterwards.
What that mark on the report proves, and what it does not
| Dimension | Report carrying an accreditation mark | Report without the mark (non-accredited item) |
|---|---|---|
| Evidence of technical competence | The item sits inside the accredited scope and the competence has been assessed by a third party | Competence has not been confirmed under that framework and rests with the laboratory itself |
| Traceability of the data | Traceability chain, method validation and uncertainty evaluation are all under controlled requirements | Depends on the laboratory's internal management level, and practice varies widely between organisations |
| Acceptance by the receiving party | Accepted directly in most situations | Needs to be discussed with the receiving party in advance and confirmed in writing |
| Relationship to market access | Not a commitment regarding market access | Not a commitment regarding market access |
The two columns are identical in the last row, and that is not a typesetting slip. An accreditation mark only demonstrates that the laboratory holds the corresponding technical competence within its accredited scope; it does not constitute a commitment regarding the market access outcome in the target market. Whether a product reaches the market depends on conformity with the technical requirements, on the completeness of the registration dossier and on the conclusion reached by the competent authority. The test report is one input among several. People who wave an accredited report at a customer and say "we are already certified" tend to find that, in front of a counterpart who knows the field, the sentence damages trust rather than building it.
As for how to read the data inside the report itself, how to check the traceability chain, what uncertainty actually means, and how the decision rule shapes the conclusion when a result sits close to a limit, that is a separate topic and can be picked up on its own in the knowledge section.
Seen from the manufacturer's QMS side: accreditation is objective evidence for supplier evaluation
If your company runs a quality management system built to ISO 13485, an external testing laboratory is an external provider inside that system. Two practical consequences follow.
First, choosing a laboratory is not a decision procurement makes alone. There have to be evaluation criteria and evaluation records. How well the accredited scope covers your plan is one of the heavier pieces of objective evidence in that record, and it stands up to audit questions far better than statements like "we have worked with them for years" or "they have a good reputation in the industry". What an auditor will genuinely chase is this: on what basis did you conclude that this laboratory is competent for this item, and where is the evidence.
Second, a scope is a moving target. Extensions, reductions and suspensions all happen, which means supplier evaluation is not a one-off exercise. Pulling the annex again before a project kicks off costs almost nothing, and it blocks the quite well-hidden case where the certificate is still valid but the specific item you need has dropped out of the scope. That case is completely invisible from the certificate cover; the only way to see it is to open the annex.
A schedule collapse you can avoid at the planning stage
We have seen this project shape more than once. The client places the order the way they always have, and the prototypes arrive on schedule and testing starts. Halfway through, the client's internal compliance review pulls the laboratory's annex and discovers that two of the items, while perfectly executable, are not inside the accredited scope, so they can only be marked as non-accredited in the report. The receiving party, however, has explicitly asked for those two items to carry the mark. The workflow then becomes: find another laboratory that holds the scope, queue again, prepare samples again, ship again, and keep the earlier data only as an internal reference.
The cost comparison is blunt. Spending a little time at the planning stage comparing against the annex means editing a test plan that has not been executed yet, at a cost close to zero. Making the same change after the prototypes have arrived means editing the schedule, the samples and the budget, and engineering prototypes are usually built in limited quantities, so producing another batch often takes longer than the testing itself. In rework of this kind the expensive part is never the retest fee; it is the project timeline that gets stretched.
A self-check list you can use as it stands
- Are the contracting entity, the report-issuing entity and the accreditation certificate holder one and the same legal person
- Can every line of your test plan be matched to an item name and a method standard in the annex
- Does the sample satisfy every constraint written in the limitations and remarks column
- Is there any subcontracting, does the subcontractor's scope cover it, and has it been disclosed and agreed in writing
- Are non-accredited items clearly identified in the report, and has the receiving party confirmed it can accept them
- Was the accreditation status re-checked before this particular order, rather than carried over from old paperwork
Running these six lines takes very little effort and heads off the large majority of rework caused by capability boundary issues. Credential checking is a textbook case of cheap up front and expensive later; the earlier you do it, the better the trade.
When you want someone to walk the scope with you
If you are holding a test plan and are not sure which items sit inside the accredited scope and which will need a scope extension or subcontracting, send over the item list and the sample construction description. We will compare it line by line using the three-part package described above and set out the coverage position, the method validations that would be needed and any likely subcontracting arrangements in one pass, before talking about schedule and cost. Coverage by category is outlined under testing services. Call +86 132 4819 8029, or request a quote.