Skip to main content
About Us
About Us

Company profile, service system, quality philosophy and technical capabilities.

View all
Global Certification
Global Certification

Market-access routes covering testing, certification, registration and technical documentation.

View all
News & Insights
News & Insights

Regulatory updates, standards interpretation and practical product-compliance guides.

View all
Contact Us
Contact Us

Tell us the product, destination market and planned project to begin a technical review.

View all
SCS Testing service page banner

SCS Testing

News & Insights
Home > News & Insights > Quality Management

Before Report Issue: Match the Sample to the Technical-file Version

2026-08-13 SCS Testing Source: SCS Testing Technical Notes

Before Report Issue: Match the Sample to the Technical-file Version

Testing is complete, but engineering sends a new BOM, purchasing changes the adapter and the instructions still show the old ratings. Renaming a PDF “final” will not resolve those differences. First establish which configuration was tested, which version the results describe and which version will go into production.

Create a clear sample-configuration record

Use a record identifying the product model, sample number, PCB revision, critical-component list revision, adapter or battery model, firmware and test mode. Link the instructions, markings, construction drawings and circuit diagrams to that configuration through a document register. If the production version differs, list the differences explicitly rather than leaving them in a chat message.

A file name can be simple: “ModelA_CriticalComponents_R02_20261021”, for example. The useful information is the applicable model, revision and date. Assign one person to maintain the register so that engineering, quality, purchasing and the project contact work from the same status list.

Describe changes well enough to assess their effect

This is a hypothetical record, not a decision about whether a particular change requires retesting:

RecordExample entry
ChangeAdapter P1 replaced by P2 with the same nominal output ratings
Versions affectedBOM R02; sample A-03; affected orders to be confirmed
Supporting informationSpecifications, markings, relevant reports and connection details for both adapters
StatusSubmitted for technical review; supplementary testing and document changes not yet agreed

Identical nominal ratings are not a substitute for reviewing the actual differences. Keep the originator, date, affected models, final decision and its basis in the record. Mark an unfinished assessment as pending; do not apply an old conclusion to the new configuration before the review is resolved.

Cross-check the sample and documents before issue

  • Do the models, ratings and key accessories match the sample photographs, markings and application?
  • Were the cited drawings, components, firmware and modes used for the relevant tests?
  • Are modifications, replacement parts and repeat tests linked to the final configuration?
  • Do the standard editions, test items and deliverables match the agreed scope?
  • Have open points been resolved, or do the documents need to state a limitation?

The testing organisation retains its original test records under its own management requirements. The manufacturer should retain its product-configuration and delivery records. Request revisions to an issued report or certificate from the issuer, keeping the relationship and status of old and new files. Do not edit an issued document yourself.

Keep earlier versions identifiable

Section 4.3 of the 2022 Blue Guide explains that technical documentation should reflect the versions, changes and associated assessments where a product has been redesigned and reassessed. In practice, retain read-only copies and identify their applicable model, batch or other product identifier.

For EU technical documentation, use the applicable product legislation to establish content and retention requirements; the official EU preparation guide provides an overview. A document-retention period is different from a universal validity period for test reports. It does not remove the need to assess product changes or applicable requirements.

To discuss whether an existing report can support a new configuration, send the earlier documents through SCS market-access project enquiries, change list, current BOM and sample photographs, together with the destination market and requested deliverables. These inputs help identify evidence that may remain relevant, gaps to resolve and any supplementary testing or document revisions to consider.

Public sources checked: 21 October 2026. The proposed register and record format are working suggestions. EU references apply only where the relevant product legislation is applicable.