Check specifications, BOMs, manuals and software versions before submitting samples to reduce communication and resubmission caused by inconsistent documentation.

Complete and consistent documentation is essential to an efficient testing project. Before formally submitting samples, GTG recommends that development staff and project managers jointly check the samples and define the models, configurations and target markets covered by the tests.

Basic documentation typically includes product specifications, circuit diagrams, critical component lists, labels, manuals and any necessary software operating instructions. If the product includes batteries, chargers or external accessories, explain how they are used together. Engineers confirm the actual document checklist and sample quantities for each project.

If samples are still being developed, maintain version records covering changes to hardware, firmware, construction and materials. Communicate any changes during testing promptly to avoid combining data from different versions. Clearer documentation improves project execution and issue tracking.