CDSCO medical device licensing in India requires ten core documents: covering letter and application form, Device Master File (DMF), Plant Master File (PMF), ISO 13485 QMS certificates, Clinical Evaluation Report (CER), device labelling, safety and performance test reports, regulatory authorization from the country of origin (imports only), post-market surveillance plan, and fee payment with undertaking. Preparation follows a 10-step process from regulatory mapping through final dossier assembly — all aligned with MDR 2017.
Sneha Kapoor had been working on her company's MD9 application for four months. The technical team had completed testing. ISO 13485 was certified. The facility was inspection-ready. When her regulatory consultant reviewed the draft submission dossier two weeks before filing, he found the same problem he finds in roughly half of first-time submissions: the Device Master File and the Clinical Evaluation Report were internally inconsistent. The risk analysis in the DMF identified six hazards that the CER's risk-benefit assessment did not address. The Essential Principles Checklist referenced a superseded version of a key standard.
Fixing the gaps took three additional weeks. The application was filed late. A CDSCO query round added another five weeks. Sneha's total timeline ran to nearly ten months — five of which were directly caused by documentation that had been assembled rather than prepared. The technical quality of the device was never in question. The documentation told a different story.
📑 Quick Navigation
Why Documentation Quality Determines Licensing Timelines
In India's medical device regulatory system, the quality of your documentation is the single variable most within your control. Device classification, facility readiness, and ISO 13485 certification are prerequisites — but once those are in place, the speed and outcome of your CDSCO application depends almost entirely on how well your dossier is prepared.
CDSCO's technical reviewers assess applications against a defined checklist for each license type. Every gap, inconsistency, or missing element generates a formal query. Each query round typically adds four to eight weeks to the overall timeline. Multiple query rounds compound. Manufacturers who treat documentation as a box-ticking exercise routinely spend twelve to eighteen months on applications that well-prepared competitors complete in five to seven months.
The 10 Core CDSCO Documentation Types
Every CDSCO medical device license application — whether for manufacturing (MD5 or MD9) or import (MD15) — draws from the same family of core documents. The specific set required varies by license type and device class, but understanding what each document must contain and why it matters to reviewers is the foundation of effective dossier preparation.
The covering letter establishes the application's purpose, identifies the applicant and device, and references the applicable rules and form number (MD3, MD7, or MD14). Every field on the form must be accurate and consistent with supporting documents — discrepancies in device names, applicant names, or addresses between the form and supporting documents are among the most common query triggers. The letter must be signed by the authorised signatory with the company seal.
The DMF is the technical heart of the application. It must describe the device completely — intended use, design specifications, materials, manufacturing process, performance characteristics, and essential principles compliance. The risk analysis section must align with ISO 14971 and must be traceable to production controls and post-market monitoring. A DMF that is technically accurate but internally inconsistent — where the risk analysis and the essential principles checklist reference different standards or different hazards — will generate queries even if the underlying device is sound.
The PMF describes the manufacturing facility from a regulatory compliance perspective — building layout with dimensioned drawings, equipment list with calibration status, utilities and environmental controls, cleanroom classifications where applicable, and personnel qualifications. It must demonstrate that the facility consistently meets GMP requirements. CDSCO inspectors cross-check the PMF against the actual facility during on-site inspections — any discrepancy between the document and physical reality generates an observation that must be resolved before license grant.
ISO 13485 certification is mandatory for all medical device manufacturing license applications. The certificate must be valid, issued by an accredited certification body, and in-scope for the specific device being licensed. Supporting QMS documentation — CAPA records, internal audit reports, management review summaries, and nonconformance records — strengthens the submission by demonstrating that the QMS is operational, not just certified. An ISO 13485 certificate with a scope that does not cover the device being licensed is one of the most common single causes of MD5 and MD9 application delays.
The CER demonstrates the device's clinical safety and performance through systematic review of literature, clinical investigation data, and post-market information where available. The risk-benefit analysis must be clearly articulated and must address the hazards identified in the DMF's ISO 14971 risk file — this cross-document traceability is what reviewers check first. The CER methodology must align with CDSCO and MDR 2017 requirements; CERs structured according to EU MDR Annex XIV methodology are generally acceptable as the methodological basis, with India-specific contextualisation where the CLA requires it.
Labels must comply with Schedule IV of MDR 2017. Required elements include the product name and model, intended use statement, manufacturer's name and address, batch number or lot number, manufacturing date and expiry date, storage conditions, instructions for use, and applicable warnings. For sterile devices, sterility method and sterility expiry must be clearly indicated. Instructions for use must be in English and, where applicable, in other Indian languages. Packaging must demonstrate tamper-evidence and, for sterile devices, must be validated for sterility maintenance under the intended storage and transport conditions.
Testing reports validate the device's compliance with applicable national and international standards for electrical safety, biocompatibility, mechanical performance, electromagnetic compatibility, and sterility as applicable to the device type. Tests must be conducted by accredited testing laboratories. Reports must contain the full test protocol, all results including any failures and the disposition of those failures, and the laboratory's conclusions on compliance. Reports referencing outdated editions of standards generate queries — verify that the standards cited in all test reports are the current editions before submission.
Required for all MD15 import license applications. The Free Sale Certificate issued by the National Regulatory Authority of the country of origin confirms that the device is approved for sale in its home market. The certificate must be apostilled or notarised depending on whether the country of origin is a Hague Convention signatory. The certificate must cover the specific device models and intended uses being imported — a Free Sale Certificate that covers a product family but not the specific model number in the Form MD14 will generate a query requiring a supplementary certificate or a written explanation from the overseas authority.
The PMS plan sets out how the manufacturer will monitor device performance after market authorisation. It must define the mechanisms for collecting and analysing post-market data, the adverse event reporting structure and timelines for reporting to CDSCO through SUGAM, the criteria for triggering a Field Safety Corrective Action, and the schedule for Periodic Safety Update Reports. A PMS plan that is generic — copied from a template without device-specific risk identification — is immediately identifiable and routinely generates clarification queries from CDSCO reviewers who expect device-specific monitoring criteria.
Proof of fee payment generated through the SUGAM portal must be attached. The undertaking confirms adherence to CDSCO's rules, acknowledges the applicant's readiness for inspections, and certifies the accuracy of all information submitted. It must be signed by the authorised person. Any false declaration in the undertaking can result in license cancellation and potential regulatory action against the organisation and responsible individuals. This is the final document in the dossier but carries significant legal weight — it should be reviewed by the authorised signatory, not delegated entirely to a document coordinator.
Document Requirements by License Type
While all ten document types are part of the CDSCO documentation family, the specific combination required varies by license type. Use this reference to confirm which documents apply to your application before you begin preparation.
| Document | MD5 Manufacturing (Class A/B) |
MD9 Manufacturing (Class C/D) |
MD15 Import (All classes) |
|---|---|---|---|
| Covering letter & application form | Required | Required | Required |
| Device Master File | Required | Required | Required |
| Plant Master File | Mfg only | Mfg only | Import: overseas PMF |
| ISO 13485 QMS certificate | Required | Required | Required (manufacturer's) |
| Clinical Evaluation Report | Performance data sufficient | Required | Required |
| Device labelling | Required | Required | Required |
| Safety & performance test reports | Required | Required | Required |
| Regulatory auth. / Free Sale Certificate | Not applicable | Not applicable | Import: mandatory |
| Post-market surveillance plan | Required | Required | Required |
| Fee payment & undertaking | Required | Required | Required |
10-Step Dossier Preparation Process
Having the right documents is necessary but not sufficient. A submission dossier is more than a collection of files — it is a structured, internally consistent, cross-referenced package that tells CDSCO a coherent regulatory story about your device. The ten steps below describe how to build that package systematically rather than assembling it under deadline pressure.
Before preparing a single document, identify your device class, the specific license required, the applicable application form, and every document required for that combination. Cross-reference against MDR 2017's latest amendments and CDSCO's current submission guidance. Note any India-specific requirements that differ from CE or FDA documentation standards — these differences, if missed, are invariably caught by reviewers. Regulatory mapping performed at the start eliminates the most common structural errors from the outset.
Create templates with consistent structure, numbering conventions, version control headers, and company identification across all documents before writing begins. Establish shared sections — company profile, facility overview, quality policy — that will appear in multiple documents and need to be identical across the dossier. Consistent templates reduce formatting errors during peer review and make cross-document traceability significantly easier to maintain as drafts evolve.
Gather technical specifications, test reports, clinical data, and certificates from R&D, quality assurance, and manufacturing teams using a formal document request tracker — not ad hoc email requests. For import applications, request Free Sale Certificates and overseas regulatory authorizations well in advance; apostille or notarisation processes typically take two to four weeks in the country of origin and are the most common cause of delayed dossier completion. Validate the authenticity and currency of every third-party document before including it.
Begin with a structural outline — headings, subheadings, and section references — before entering any content. Fill factual data first: numbers, test results, facility dimensions, personnel lists. Then add explanatory text, regulatory references, and supporting rationale. Insert diagrams, process flowcharts, and tables where they replace ambiguous prose. Layered drafting produces cleaner documents because structural logic is established before content density makes revision difficult.
This is the step that separates assembled dossiers from prepared ones. Every hazard identified in the DMF's risk file must appear in the CER's risk-benefit analysis. Every risk control measure in the ISO 14971 file must be traceable to a specific production control in the PMF or a specific monitoring activity in the PMS plan. Every essential principle claimed as met in the Essential Principles Checklist must reference a specific test report or clinical evidence. CDSCO reviewers follow these links explicitly — broken traceability chains are the most frequent source of substantive queries.
Higher-risk devices require deeper documentation at every level — more detailed DMF risk analysis, more extensive CER clinical evidence, more granular PMS plan monitoring criteria. Class D devices require implant-specific documentation: long-term biocompatibility data, accelerated ageing studies, patient implant record systems, and post-market clinical follow-up protocols. Applying the same documentation depth to a Class D pacemaker as to a Class B nebulizer is a fundamental calibration error that experienced reviewers identify quickly.
Before peer review, compare every document systematically against CDSCO's official submission checklists for your license type and device class. Tick off each mandatory section and supporting element. Maintain a compliance tracker spreadsheet that maps every checklist item to its location in the dossier. This review step should be treated as a formal quality gate, not a casual check — it is the last opportunity to identify structural gaps before human reviewers are involved.
Share complete drafts with regulatory, quality assurance, clinical, and technical teams. The goal is not just to check accuracy — it is to identify cross-departmental inconsistencies. The PMF describes a facility that the manufacturing team knows; the DMF describes a device that the engineering team knows; the CER draws on clinical evidence that the medical affairs team owns. Inconsistencies that arise between these domains are invisible to any single reviewer and only surface in cross-functional review. Document all review comments formally for audit trail purposes.
Apply consistent document formatting — fonts, heading styles, page numbering, headers, and footers — across all dossier documents before finalisation. Add required signatures, company seals, and notarisations. For import applications, confirm that all overseas documents have been apostilled or notarised correctly for the country of origin. Convert all documents to secure, searchable PDF format. Ensure file sizes are within SUGAM portal upload limits — oversized files are a common last-minute technical obstacle that delays submission.
Organise all documents in logical order — application forms, DMF, PMF, QMS certificates, CER, test reports, labelling, regulatory authorizations, PMS plan, and fee payment — with a comprehensive contents page and a numbered annexure list. Ensure every cross-reference in the main documents points to the correct annexure number. Prepare the number of dossier copies specified in SUGAM's requirements for your license type. A well-structured dossier reduces CDSCO's review time because reviewers can navigate directly to any referenced document without searching through unorganised files.
The Most Common Documentation Gaps in 2026
Based on patterns observed across CDSCO license applications, these are the documentation gaps that most frequently generate queries or cause application delays in 2026.
| Document | Most Common Gap | How to Prevent It |
|---|---|---|
| Device Master File | Risk analysis references ISO 14971:2007 instead of the current edition; hazards not linked to production controls | Verify all standards references to current editions; build explicit traceability from hazard to control measure |
| ISO 13485 Certificate | Certificate scope does not cover the specific device category being licensed | Read the certificate scope line by line against the device description before filing |
| Clinical Evaluation Report | Risk-benefit analysis does not address hazards identified in the DMF | Build the CER from the DMF risk file; every hazard must appear in both documents |
| Plant Master File | Building layout not dimensioned; environmental monitoring data absent | Use professional draftspeople for layout; include current environmental monitoring records |
| Test Reports | Standards referenced are superseded editions; reports from non-accredited labs | Verify current edition of every standard; use only NABL or internationally accredited laboratories |
| Post-Market Surveillance Plan | Generic template with no device-specific monitoring criteria or adverse event thresholds | Build the PMS plan from the device's specific residual risk register; define device-specific trigger criteria |
| Free Sale Certificate (imports) | Certificate covers product family, not the specific model number in Form MD14 | Match model numbers on the FSC exactly to those in the application form |
Frequently Asked Questions
Is the Device Master File the same as the Technical File used for CE marking?
They serve similar purposes — both are comprehensive technical descriptions of the device — but they are structured differently. The CE Technical File follows EU MDR Annex II/III requirements, while CDSCO's DMF must address the specific sections and content requirements of MDR 2017 and CDSCO's submission guidance. Manufacturers with existing CE documentation can adapt their Technical File for India, but direct submission of a CE Technical File without India-specific adaptation will typically generate queries on sections that differ between the two frameworks.
Can documents in languages other than English be submitted to CDSCO?
No. All documents submitted to CDSCO must be in English or accompanied by a certified English translation. For import applications, overseas documents issued in other languages — manufacturing licenses, Free Sale Certificates, ISO 13485 certificates — must be accompanied by certified English translations that are notarised or apostilled together with the original document. Submitting documents in other languages without certified translations will generate an immediate query.
How long should the Clinical Evaluation Report be for a Class C device?
There is no prescribed length — the CER must be as comprehensive as the clinical evidence base and the device's risk profile require. A Class C device with substantial published clinical literature and multiple years of post-market data will typically have a longer and more evidence-rich CER than a Class C device entering the market for the first time. What CDSCO reviewers assess is the quality of the methodology, the completeness of the literature search, and the adequacy of the risk-benefit analysis — not the word count.
Does CDSCO accept documentation prepared by a regulatory affairs consultant?
Yes. CDSCO accepts documentation prepared by regulatory affairs consultants on behalf of the applicant. The applicant remains legally responsible for the accuracy and completeness of the submission — the authorised signatory's signature on the undertaking certifies this. Using experienced regulatory consultants who are familiar with CDSCO's current standards and query patterns is a legitimate and widely practised approach to improving documentation quality and accelerating licensing timelines.
✓ Key Takeaways
- CDSCO documentation quality is the single most controllable variable in your licensing timeline — poor documentation causes delays that technical quality cannot compensate for
- The ten core document types apply across MD5, MD9, and MD15 applications — specific combinations vary by license type and device class
- Cross-document traceability — particularly between the DMF risk file, CER, and PMS plan — is what CDSCO reviewers check first and what most commonly generates substantive queries
- ISO 13485 certificate scope must explicitly cover the device being licensed — this single gap delays more applications than any other documentation issue
- All standards references must be to current editions — superseded standard citations are caught immediately and generate corrective queries
- Post-market surveillance plans must be device-specific — generic templates with no device-specific monitoring criteria are immediately identifiable and routinely queried
- For import applications, Free Sale Certificates must match the exact model numbers in Form MD14 — product family certificates without specific model coverage are insufficient
- A pre-submission documentation review by a regulatory affairs specialist is the highest-return investment available to any applicant preparing a CDSCO dossier
Your Documentation Action Plan
The manufacturers and importers who navigate CDSCO licensing efficiently are not necessarily those with the most sophisticated devices or the largest regulatory teams. They are the ones who understand what CDSCO reviewers are looking for, build their documentation to address those requirements explicitly, and invest in cross-document consistency before they submit — not in response to queries after they submit.
Documentation preparation is not where you cut time in a licensing project. It is where you invest it. A dossier built with discipline, internal consistency, and explicit regulatory traceability does not just pass review more quickly — it reflects the quality culture of the organisation that built it. CDSCO's licensing process is designed to assess exactly that.
Start your regulatory mapping today. Build your traceability framework before you write a single document. The manufacturers who prepare their dossiers correctly the first time are the manufacturers whose products reach the Indian market on schedule.