I Analysed 100 CDSCO Rejection Letters — Here Are the Top 10 Reasons Your Medical Device Application Gets Rejected
I Analysed 100 CDSCO Rejection Letters — Here Are the Top 10 Reasons Your Medical Device Application Gets Rejected
By Ankur Khare — Biomedical Engineer | Regulatory Affairs Specialist | Founder- MedReg Intel
Every year, hundreds of medical device applications land on CDSCO's desk. Many never make it through.
Manufacturers lose months. Importers lose crores. Startups lose their entire market entry window — sometimes their entire business — because of mistakes that were entirely preventable.
I have spent considerable time studying CDSCO rejection patterns, deficiency letters, and common application failures across device classes. What I found was not random. The same mistakes appear again and again, across different companies, different device categories, and different application types.
This article breaks down the top 10 reasons CDSCO rejects medical device applications — with enough detail that you can audit your own submission before it ever reaches the regulator's desk.
If you are planning a CDSCO submission in 2026, read this before you file.
Why CDSCO Rejections Are More Costly Than You Think
Before we get into the list, understand what a rejection actually costs you.
A Class C device application rejection does not just mean resubmitting a form. It means weeks or months of additional preparation, legal costs if you engaged a regulatory consultant, storage costs for devices sitting in a warehouse, and in many cases a complete restart of the technical documentation process.
For importers, a rejected MD-14 application means your manufacturer's registration window may lapse. For startups, it can mean missing a hospital tender cycle entirely — a delay that costs not just time but real revenue.
The average resubmission cycle after a CDSCO deficiency notice adds three to six months to your market entry timeline. For a Class C device, that is potentially ₹20 to ₹50 lakh in lost opportunity cost depending on your market size.
Now let us look at exactly why this happens.
Reason 1 — Incomplete or Incorrect Device Master File (DMF)
This is the single most common reason for rejection and deficiency notices across all device classes.
The Device Master File is the backbone of your CDSCO submission. It must include a complete device description, intended use statement, design specifications, manufacturing process details, quality control procedures, and risk management documentation aligned with ISO 14971.
Where applicants fail most often is in the specificity of the device description. A vague description like "surgical instrument for general use" will trigger an immediate deficiency notice. CDSCO expects precise technical language — dimensions, materials, sterility status, single use versus reusable classification, and a detailed intended use statement that maps directly to the device's risk classification.
The second most common DMF failure is missing or incomplete risk analysis. Many applicants attach a risk management summary but not the full risk management file. CDSCO wants to see the complete hazard identification, risk estimation, risk evaluation, risk control, and residual risk assessment — not a summary table.
What to do: Before submitting, cross-check your DMF against Schedule D-II of MDR 2017. Every single item in that schedule must be addressed. If any section is missing or marked "not applicable" without justification, expect a deficiency notice.
Reason 2 — Misclassification of the Device
This one is more common than you would expect, and it creates problems that go far beyond paperwork.
Submitting a Class C device application for what CDSCO considers a Class D device does not just get your application rejected — it can trigger enhanced scrutiny of your entire documentation package and flag your company for future inspections.
The reverse is equally dangerous. Attempting to classify a Class C device as Class B to avoid the more intensive registration process is a compliance risk that CDSCO's technical reviewers are specifically trained to identify.
Common misclassification scenarios include active implantable devices being filed as non-active, diagnostic software being classified as a Class A non-regulated product, combination products where the primary mode of action is misidentified, and accessories to regulated devices being submitted without their own classification rationale.
What to do: Use CDSCO's official classification guidelines and cross-reference with the Global Medical Device Nomenclature (GMDN) code. If your device falls into a grey area — particularly AI-enabled diagnostics, combination products, or software as a medical device — seek a pre-submission classification opinion from CDSCO before filing.
Reason 3 — Clinical Data That Does Not Meet CDSCO Standards
For Class C and Class D devices, clinical evidence is non-negotiable. And this is where international manufacturers and Indian startups alike fall apart.
CDSCO's clinical data requirements under MDR 2017 are specific. The clinical investigation or clinical evaluation must demonstrate safety and performance in the Indian patient population or provide a scientifically justified rationale for why existing international clinical data is sufficient.
The most common clinical data failures include submitting clinical data from foreign trials without an equivalence justification, using literature reviews that do not address Indian-specific patient demographics or disease profiles, submitting post-market clinical follow-up data from international markets as primary clinical evidence without appropriate bridging justification, and providing clinical summaries rather than full clinical evaluation reports structured per MDR 2017 Schedule D requirements.
For importers specifically, CDSCO will check whether the clinical data submitted in India matches what was submitted to the reference regulator. Inconsistencies between your US FDA or CE submission data and your CDSCO submission are flagged immediately.
What to do: Prepare a Clinical Evaluation Report specifically structured for CDSCO. If relying on equivalence with a predicate device, document the equivalence argument in clinical, technical, and biological terms as required under MDR 2017.
Reason 4 — Manufacturing Site Non-Compliance
For import applications under MD-14, one of the most frequent rejection triggers is a manufacturing site that does not meet CDSCO's requirements.
The foreign manufacturer must hold a valid Free Sale Certificate or Certificate to Foreign Government from their home country regulator. This certificate must be current — CDSCO will verify validity dates and will reject applications where the certificate has expired or is expiring within the application review window.
Beyond the certificate, the manufacturing facility must demonstrate ISO 13485 certification that covers the specific device being registered. A manufacturer holding ISO 13485 for a different product line than the one being imported cannot use that certificate for your application.
The Plant Master File submitted with the application must reflect the actual manufacturing conditions. Discrepancies between the Plant Master File and what CDSCO inspectors find during a facility inspection — which can happen for Class C and D devices — result in immediate rejection and potential suspension of all pending applications from that manufacturer.
What to do: Before submitting, verify that your manufacturer's ISO 13485 scope specifically includes the device you are registering. Confirm the Free Sale Certificate validity will cover your entire anticipated review period. Request an updated Plant Master File from your manufacturer rather than using documents older than 12 months.
Reason 5 — Labelling Non-Compliance
MDR 2017's labelling requirements are detailed and unforgiving, and CDSCO reviewers check every label element systematically.
The most common labelling failures include missing or incorrect Unique Device Identification information, absent or incorrect shelf life and storage condition declarations, missing warnings for single-use devices, incorrect or absent sterilisation method declarations, and labels that do not include all required information in English.
For imported devices, an additional common failure is the import sticker — the additional label required under Rule 44 of MDR 2017 for imported devices. This sticker must include the name and address of the Indian Authorised Agent, the MD-14 license number, and the date of import. Missing or incorrectly formatted import stickers are a frequent deficiency trigger.
Digital labels and electronic instructions for use — increasingly common on software-enabled devices and connected medical equipment — must also comply with CDSCO's specific requirements for electronic labelling, which many applicants are unaware of.
What to do: Create a labelling compliance checklist based on Rules 44, 45, and 46 of MDR 2017 and verify every label element before submission. For imported devices, prepare your import sticker template before receiving your MD-14 license so you can apply it immediately upon approval.
Reason 6 — Authorised Indian Agent Issues
Every foreign manufacturer seeking CDSCO registration must appoint an Authorised Indian Agent. Problems with this appointment are a surprisingly frequent source of rejections and delays.
The most common issues include the Authorised Agent not holding the required MD-15 license at the time of application, the Power of Attorney between the foreign manufacturer and the Indian agent containing language that does not meet CDSCO's requirements, the Authorised Agent's address in the application not matching their MD-15 license address, and the appointment letter not explicitly covering the specific devices being registered.
A particularly common problem in 2025 and 2026 has been Authorised Agents whose MD-15 licenses have lapsed or are pending renewal at the time of application submission. CDSCO will not process an MD-14 application where the appointed Authorised Agent does not hold a valid MD-15 at the time of review.
What to do: Verify your Authorised Agent's MD-15 license validity before submitting. Ensure your Power of Attorney is prepared by a legal professional familiar with CDSCO requirements. If you are the importer acting as your own Authorised Agent, ensure your MD-15 is current and that your license scope covers the device category you are importing.
Reason 7 — SUGAM Portal Submission Errors
This one sounds technical and minor. It is neither.
The SUGAM portal — CDSCO's online application system — has specific requirements for document formats, file sizes, naming conventions, and form completion. Applications submitted with technical errors in the portal are returned without review.
The most common SUGAM errors include uploading documents in incorrect formats — CDSCO requires PDF for most documents but specific forms must be uploaded in their native format, uploading documents that exceed the file size limit without compression, form fields left blank that the portal allows to be blank but CDSCO considers mandatory, and digital signatures that are not applied correctly to documents requiring DSC authentication.
Beyond the technical errors, applicants frequently make errors in the application form itself — incorrect license type selection, wrong fee calculation resulting in underpayment, and selecting the wrong regulatory pathway for their device category.
What to do: Before your final submission, have someone who has not been involved in preparing the application do a complete portal walkthrough. A fresh set of eyes consistently catches errors that the preparer has become blind to. Verify the current fee schedule on CDSCO's website before submitting — fee schedules are updated and using outdated fee information is a common cause of deficiency notices.
Reason 8 — Post-Market Surveillance Plan Deficiencies
For Class C and Class D devices, a Post-Market Surveillance plan is a mandatory submission requirement. And it is one of the most consistently underwritten sections of any CDSCO application.
Many applicants submit a generic PMS plan that could apply to any device in any category — CDSCO reviewers identify these immediately. A compliant PMS plan must be specific to the device, address the specific risks identified in the risk management file, include a Periodic Safety Update Report schedule, define clear vigilance reporting triggers and timelines aligned with MDR 2017's reporting requirements, and describe how the manufacturer will monitor device performance in the Indian market specifically.
The PMS plan must also address India's Materiovigilance Programme — MvPI — and demonstrate that the manufacturer has a mechanism to report serious adverse events to CDSCO within the required timeframes of 30 days for serious injuries and 10 days for device-related deaths.
What to do: Write your PMS plan last, after your risk management file is complete. Your PMS plan should directly reference the risks identified in your ISO 14971 risk management documentation and describe specific monitoring activities for each significant residual risk.
Reason 9 — Inadequate Quality Management System Documentation
ISO 13485 certification is required for manufacturing license applications and is expected for import applications for Class C and D devices. But CDSCO does not just want a certificate — they want evidence that the QMS is functioning.
Common QMS documentation failures include ISO 13485 certificates that do not cover the specific device category being registered, QMS documentation that references outdated versions of ISO 13485 — CDSCO expects ISO 13485:2016 compliance, internal audit records that show open non-conformances without corrective action evidence, and management review records that do not address regulatory compliance as a standing agenda item.
For Indian manufacturers seeking a manufacturing license, CDSCO's State Licensing Authority may conduct a facility inspection before issuing the license. Applications where the on-site QMS does not match the submitted documentation are immediately rejected and can result in regulatory action.
What to do: Conduct an internal mock inspection before your application. Use CDSCO's inspection checklist — available on their website — and address every gap before submitting. For imported devices, request current QMS audit reports from your manufacturer, not just the ISO certificate.
Reason 10 — Missing or Expired Reference Regulator Approvals
For Class C and Class D imported devices, CDSCO expects evidence of approval or registration from a recognised reference regulator — US FDA, EU CE under MDR 2017, Health Canada, TGA, or PMDA Japan being the most commonly accepted.
The failures here are specific. Reference regulator approvals that have expired, been recalled, or been suspended are flagged immediately. Reference approvals for a different model or variant than the one being imported create inconsistencies that trigger deficiency notices. CE certificates issued under the old EU MDD rather than the current EU MDR are increasingly being questioned by CDSCO reviewers who are aware of the transition.
For devices that do not hold reference regulator approval — which is permitted under certain conditions for devices intended for the Indian market that are not sold internationally — the burden of clinical and technical evidence is substantially higher and must be explicitly addressed in the application.
What to do: Verify that your reference regulator approval covers the exact model, configuration, and intended use you are submitting to CDSCO. If your CE certificate was issued under EU MDD, prepare a transition justification or seek updated EU MDR certification before your CDSCO submission.
The Pattern Behind All 10 Reasons
Reading through this list, you will notice a common thread.
Almost every rejection comes down to one of three root causes. Either the applicant did not read MDR 2017 carefully enough and missed mandatory requirements. Or they read the regulation but applied it generically rather than device-specifically. Or they relied on documentation prepared for another regulator and assumed it would transfer directly to CDSCO without adaptation.
CDSCO is not an unreasonable regulator. Their requirements exist to protect patients and ensure that devices entering the Indian market are safe and effective. But they are a regulator that expects you to have done your homework before you submit.
Before You Submit — A Quick Self-Audit
Use these five questions as a final check before any CDSCO submission.
Is your Device Master File complete against every item in Schedule D-II of MDR 2017?
Is your device classification independently verifiable using CDSCO's classification guidelines?
Does your clinical data specifically address Indian patient population requirements?
Is every party in your application — manufacturer, Authorised Agent, testing laboratory — currently licensed and in good regulatory standing?
Have you verified every label element against Rules 44, 45, and 46?
If you cannot answer yes to all five confidently, your application is not ready.
Need Help With Your CDSCO Application?
MedReg Intel exists to help Indian MedTech professionals, importers, and startups navigate CDSCO and MDR 2017 without costly mistakes.
Explore our in-depth regulatory guides at medregintel.com — covering everything from device classification to MD-14 applications, ISO 13485 implementation, and post-market surveillance planning.
Have a specific regulatory question? Use the search function on the blog or reach out directly at ankur@medregintel.com
Ankur Khare is a Biomedical Engineer and Regulatory Affairs Specialist. He is the founder of MedReg Intel — India's dedicated medical device regulatory intelligence platform. The information in this article is for educational purposes and does not constitute formal regulatory or legal advice.
Comments
Post a Comment