Indonesia Technical Evidence Package: CSDT Dossier Assembly and Evidence Traceability

1. Key takeaways

The technical evidence package is the entire substantive argument that sits outside the administrative documents. Administrative documents (letter of authorization, certificate of free sale, quality system certificate) answer who is entitled to file; technical evidence answers why the product should be approved. Indonesian reviewers read a submission along the ASEAN CSDT structure, so the way technical evidence is organised is not a manufacturer’s free choice but the fixed entry point of the review process. Assemble the dossier in the wrong order and even sufficient evidence is downgraded within the first minute of reading.

GRZAN compresses the judgement into one sentence: the quality of technical evidence depends not on the thickness of the documentation but on whether every conclusion can be traced back to a specific report within 30 seconds. That sentence decides three things: the evidence list is drawn up at project start by classification tier rather than assembled after the reports are finished; every block is written as conclusion plus evidence pointer; and the Indonesian labelling and terminology consistency check is performed once, at the end of dossier assembly, as the final gate before submission.

2. Legal basis

3. Expert insights

Insight one: the CSDT is a reading map, not a document list.

The order of the eight blocks mirrors the reviewer’s reading order: the executive summary first to form an overall judgement, then the essential principles checklist item by item, then device description and design verification and validation. A manufacturer that assembles the dossier around its own document architecture (placing risk management in the final volume, for example) forces the reviewer to jump between files to reconstruct a single chain of reasoning. Deficiencies arise not because evidence is insufficient but because evidence cannot be found. This also explains why the same CE technical file can attract noticeably more deficiency rounds in Indonesia than in Europe.

Insight two: classification sets the depth of evidence, and the review clock in turn constrains how it is organised.

Permenkes No. 5/2026 sets the review clock at 21 working days for class A, 36 for class B/C and 55 for class D. Class D has the longest clock precisely because it demands the most evidence. Class A, with only 21 working days, works the other way: a reviewer will not keep questioning a poorly indexed low-risk file, he will simply return it. The value of a low-risk submission therefore lies not in writing less but in writing so that the reviewer has nothing to ask.

Insight three: administrative documents come first so that technical evidence is never interrupted by procedural issues.

The letter of authorization, the certificate of free sale and the ISO 13485 certificate are administrative requirements under Annex II A and Annex 3 of Permenkes No. 11/2025. When they are missing, review stops at the formal examination stage and the technical evidence is never read at all. Treating administrative documents as a precondition rather than a parallel workstream is the first scheduling discipline for an Indonesian project. The Hague Apostille has applied to Indonesia since June 4, 2022, which makes the authentication chain for a CFS more controllable than in the consular legalisation era, but notarisation and translation still need to be scheduled.

Insight four: the technical file may be in English, user documents must be in Indonesian.

This is the most frequently misread rule. Permission to file in English applies only to the technical file itself; labels, instructions for use and packaging face the user and must be in Indonesian. The cost of misreading is not a single deficiency round but rework of the whole user documentation, which in turn triggers a consistency review of labels against the risk file, because label warnings are how risk control measures are implemented and any change of language changes the correspondence the risk file has to document.

4. Practical recommendations

1. Draw up the evidence list at project start. Work back from the target classification (A/B/C/D) to the minimum evidence set for each CSDT block and build a four-column table of block, report name, owning department and completion date, drafting it alongside each topic rather than assembling after all reports exist.
2. Write the executive summary separately and finalise it last. Cover the four items in full: marketing history, intended use, approvals in other countries, and important safety or performance information. It is the first text the reviewer reads and the only text that will be read in full.
3. State how each essential principle is met and which evidence proves it. Copying the template is the most common loss of marks, because it pushes the judgement back onto the reviewer.
4. Give design verification and validation a conclusion summary and an evidence-strength judgement. Attaching reports without a summary leaves the reviewer unable to judge whether the evidence supports the intended use.
5. Build a correspondence table between the risk file and label warnings. Mark where each ISO 14971 control measure lands on the label and re-check it once the Indonesian wording is final.
6. Align Regalkes attachment naming and indexing. The file name is the retrieval path: number attachments to match CSDT block numbers to reduce cannot-find deficiencies.
7. Give software products their own volume. UU No. 17/2023 already brings software within the device definition, so software description, cybersecurity and version change policy should be separate chapters rather than mixed into hardware design verification.

5. Verification checklist

• □ All eight CSDT blocks are present and in template order
• □ The executive summary covers all four items (marketing history, intended use, other-country approvals, safety and performance points)
• □ Each essential principles checklist line states how the principle is met and which evidence proves it
• □ Design verification and validation carry a conclusion summary and an evidence-strength judgement
• □ Administrative documents (letter of authorization, CFS, ISO 13485 certificate) are complete before technical evidence
• □ A line-by-line correspondence table links the risk file to Indonesian label warnings
• □ Technical file in English, user documents in Indonesian, with consistent terminology across both
• □ Regalkes attachment names match CSDT block numbers and the index is searchable
• □ Evidence depth matches the target class and is scheduled against 21 / 36 / 55 working days

Regulatory information verified as of October 26, 2026.

GRZAN supports manufacturers, importers and authorised representatives with Indonesian registration dossiers, including CSDT assembly, evidence indexing for Regalkes, risk file and labelling consistency review, and deficiency response. For a product-specific feasibility assessment or dossier review for the Indonesian market, contact the GRZAN regulatory team at info@grzanglobal.com.