
TSEK application records: connect the accepted criterion revision to real evidence
A TSEK file must identify the accepted criterion, actual product and manufacturing evidence. An older report needs a requirement-by-requirement relevance check, not a renamed cover.
Build a criterion-to-evidence register
Obtain the criterion reference and revision accepted for the actual application before assembling a file. Record the product use, models, configurations and manufacturing locations beside it. For each applicable requirement, identify the document, test or production-control record that supports it, its version and any unresolved gap. A document index lists files; this register explains why each file answers the requirement.
Keep genuine reports with the sample identity, method, conditions and result that the laboratory recorded. Connect drawings, material specifications and production records to that same configuration. Confirm current application attachments and submission instructions with TSE rather than treating a copied checklist from another product as the official list.
An old criterion revision is a question to resolve
Conditional example: the available report refers to an earlier criterion revision, while the proposed application uses a later revision. Compare the actual changed requirements and methods. Record which results remain relevant and which leave a gap; a different revision number alone neither proves that every test must be repeated nor that every old result is acceptable.
Ask TSE to confirm the programme’s treatment of the evidence and commission only the additional work required by that decision. Do not alter the report’s criterion reference or sample details to make it appear current. A corrected clerical mistake must come through the appropriate document issuer; a missing technical result needs genuine evidence.
Control the submitted and production versions
Give each evidence link an accountable owner and retain the version actually submitted. If a material, drawing or manufacturing location changes during preparation, identify the affected requirement and report before releasing the next file. Submission receipts show what was sent; they do not establish that TSE accepted the evidence or granted the certificate.
The applicant provides truthful records and operates the controls, the laboratory owns its report and TSE evaluates programme acceptance and certification. Kayra can organise the requirement register and coordinate agreed corrections. Close each gap with the real accepted evidence, keeping pending technical questions visible instead of marking the folder complete merely because every filename is present.
Related service guides
- ← Return to the main document guide
- 01TSEK Audit ProcessOpen guide →
- 02Is TSEK Mandatory? Requirements ExplainedOpen guide →
- 03Frequently Asked Questions About TSEKOpen guide →
- 04TSEK Scope and Key DifferencesOpen guide →
- 05How to Obtain TSEKOpen guide →
- 06Who Manages the TSEK Process?Open guide →
- 07TSEK Certification and Consultancy ProviderOpen guide →
- 08TSEK Cost and TimescaleOpen guide →
- 09TSEK Enquiry and ValidityOpen guide →
Tell us what you need and our specialists will contact you.
The exact records for TSEK Required Documents depend on the confirmed scope. Current, consistent and traceable information reduces avoidable revisions.