The SUGAM Readiness Guide: What CDSCO Won't Tell You About Medical Device Registration
Navigating the SUGAM Portal for Medical Device Registration in India
What the Official Guidance Does Not Tell You
By Ankur Khare — Biomedical Engineer | Regulatory Affairs Specialist | Founder, MedReg Intel
Every year, hundreds of medical device applications filed on India's SUGAM portal get stuck — not because the devices are unsafe, not because the manufacturers are incompetent, but because of avoidable errors made before a single document was uploaded.
This article is not a summary of what SUGAM is. It is a practical guide to what actually happens when you use it — the decisions that matter, the errors that cost months, and the logic you need to understand to move through the system efficiently.
The Real Cost of Getting It Wrong
Before the guidance, two illustrative examples for your understanding is worth knowing:
Case 1: A Gujarat-based importer lost 4 months on a Class B device application because the company address on SUGAM read "Industrial Area" while the GST certificate read "Industrial Zone." Same location. One word different. Three deficiency rounds.
Case 2: A Delhi-based manufacturer filed MD-7 for a Class C device that had no prior notified equivalent. The correct form was MD-27. The error was identified at first review. Timeline impact: 9 months and a complete refiling with fresh fees.
Neither error was technical. Both were entirely avoidable.
Why SUGAM Trips Up Even Experienced Applicants
The SUGAM portal was built to centralise and digitise India's medical device regulatory submissions. Before it existed, applications were submitted physically to CDSCO offices. The shift to digital was the right direction.
But SUGAM is not intuitive. It was designed around regulatory process logic — not user experience logic. Applicants who approach it expecting a straightforward online form are routinely surprised by the specificity it demands, the interdependencies between sections, and the consequences of small inconsistencies that would seem minor but trigger formal deficiency notices.
The most important thing to understand about SUGAM is this: it is not a submission tool. It is a verification system.
Every field you fill, every document you upload, every declaration you make is cross-referenced — against your company registration, against your manufacturer's documents, against CDSCO's notified device list, and against each other. Inconsistencies anywhere in that web create deficiencies.
The Foundation — Getting Your Company Profile Right
Before you touch an application form, your company profile on SUGAM must be complete and accurate. This sounds obvious. It is routinely ignored.
Your company legal name on SUGAM must match your Certificate of Incorporation exactly — not approximately, not with minor variations, exactly. Your registered address must match your GST registration exactly. Your authorised signatory must have a current, properly executed authorisation letter.
These seem like administrative details. They are not. They are the foundation against which every application you file will be verified. A name discrepancy between your SUGAM profile and your incorporation documents will generate a deficiency notice on every application you file until it is corrected. Many applicants discover this on their second or third application, having spent months wondering why routine queries keep coming back.
Set the foundation correctly once and it works for every application thereafter. Set it incorrectly and you pay the cost repeatedly.
The Most Consequential Decision — Choosing the Right Form
SUGAM offers multiple application forms for medical device submissions. Choosing the wrong form does not just cause a minor delay — it means filing an entirely new application after the error is identified, which can add three to six months to your timeline.
The decision logic is straightforward but requires two prior determinations. First, is your device already notified under MDR 2017? Second, are you importing or manufacturing?
If your device appears on CDSCO's notified device list and you are importing, you file MD-14 for Class B, C and D devices or MD-15 for Class A. If your device is not on the notified list — meaning it is a new medical device for which no regulatory pathway has been established in India — you file MD-26 for import or MD-27 for manufacture.
This distinction matters enormously. MD-14 follows a relatively established review pathway. MD-26 involves a more complex assessment because CDSCO is evaluating a device category it has not previously regulated. Timelines, documentation requirements and scrutiny levels differ significantly between the two.
Many applicants file MD-14 for devices that should be MD-26 because they assume their device must be on the notified list. The assumption is wrong often enough to make verification essential. Check cdsco.gov.in before you choose your form.
For manufacturers, the equivalent decision is between MD-3 and MD-5 for Class A and B devices under State Licensing Authority, and MD-7 and MD-9 for Class C and D devices under Central Licensing Authority. MD-3 and MD-7 are for fresh licenses. MD-5 and MD-9 are for retention of existing licenses. Filing a retention form when a fresh license is required — or vice versa — is another avoidable error that causes significant delays.
The Document Preparation Phase — Where the Real Work Happens
The SUGAM portal is the last step of a documentation process that should begin weeks or months before you log in. Applicants who treat portal submission as the beginning of the process rather than the end consistently produce incomplete or inconsistent applications.
For an MD-14 import license the core documentation requirement is the Device Master File and the Plant Master File. These are the two documents that carry the most weight in CDSCO's review and the two where deficiencies are most commonly raised.
The Device Master File must tell a coherent, complete story about your device — what it is, what it does clinically, why it is classified the way it is, what standards it meets, what risks it presents and how those risks are controlled, and what evidence supports its safety and performance. Every section of the DMF must be internally consistent and must be consistent with every other document in the application.
The Plant Master File or equivalent evidence of the manufacturing facility must describe the manufacturer's quality system, manufacturing processes, and facility capabilities in a way that supports confidence in the device's consistent manufacture. The manufacturing site address in the PMF must match the address on the manufacturer's ISO 13485 certificate exactly. A difference of even one word — Road versus Rd, for example — generates a deficiency.
The intended use statement deserves special attention because it drives classification and therefore determines the entire regulatory pathway. The intended use must be clinically precise, free of marketing language, and consistent with the risk class you have declared. Intended use statements that are too broad invite reclassification queries. Statements that contain performance claims rather than clinical descriptions invite scrutiny of the evidence base. Write the intended use statement as a regulator would write it — describing what the device does and for whom, not what it achieves or promises.
Intended Use Statement: This drives classification and therefore determines the entire regulatory pathway.
Wrong: "Provides accurate, reliable blood glucose monitoring with clinically superior results for better diabetes management."
Correct: "Intended for in vitro quantitative measurement of blood glucose concentration in capillary whole blood, for use by persons with diabetes for self-monitoring."
Write it as a regulator would. Describe what the device does and for whom — not what it achieves or promises.
Classification Justification — The Document Most Applicants Skip
Most SUGAM applications declare a device classification without providing any written justification for it. This works for obvious cases. It creates problems for anything where the classification is not immediately clear from the device description.
A written classification justification document — even a single page — that references the relevant MDR 2017 schedule, walks through the risk criteria systematically, and arrives at the declared class with reasoned analysis does two things. It demonstrates regulatory competence to the reviewer. And it preempts the classification query that would otherwise arrive as the first item on your deficiency notice.
For devices with software components this is especially important. Software that influences clinical decisions or drives therapeutic actions may independently affect device classification. The classification justification must address the software component specifically and explain why the overall device classification appropriately reflects the risk introduced by the software.
The Upload Phase — Small Errors With Large Consequences
SUGAM accepts PDF documents with a maximum size of 5MB per file. Every document must be uploaded in the correct section of the application. Documents uploaded in the wrong section are treated as missing from the correct section.
Name your files descriptively. DMF_DeviceName_Version1.pdf tells a reviewer immediately what they are looking at. Scan001.pdf does not. This seems minor. In a high volume review environment where reviewers are processing multiple applications simultaneously, clear document naming reduces friction and creates a marginally better review experience. Marginal improvements compound.
The most damaging upload errors are expired certificates and documents with mismatched information. Before uploading every document, check three things: the document is current and valid, the company name matches your SUGAM profile exactly, and the addresses match your other documents exactly.
Responding to Deficiency Notices — Where Applications Are Won or Lost
Most SUGAM applications receive at least one deficiency notice. The deficiency response is where many applicants lose weeks or months they did not need to lose.
CDSCO raises deficiency notices as numbered lists of specific queries or requests for additional information. The correct response addresses every item on the list, in order, explicitly. A response that provides the requested information but does not clearly identify which deficiency item it addresses forces the reviewer to infer the connection — and creates the possibility of a second deficiency notice asking for the same information again.
Write your deficiency response as a formal letter that mirrors the structure of the deficiency notice itself. Item 1 of the notice gets Item 1 of the response. The response for each item should state what was queried, what the response is, and which uploaded document provides the supporting evidence.
Never respond to a deficiency by resubmitting the same documents that generated the query without change. If the document was sufficient, the query would not have been raised. The response must either correct the document, provide an additional document, or explain why the original document is correct with specific regulatory justification.
The response timeline is typically 30 days. Applications where the deadline passes without response are closed. Closed applications must be refiled as new applications with new fees. Track your deficiency notice dates and respond with adequate time to spare.
What Realistic Timelines Look Like
Timeline expectations for SUGAM applications are a persistent source of frustration because applicants routinely underestimate them. Understanding what drives timelines helps set realistic expectations.
Clean, complete Class A and B applications with no deficiencies typically resolve in three to six months. Clean Class C and D applications typically take six to eighteen months. Applications for new medical devices under MD-26 or MD-27 routinely take twelve to twenty-four months because they involve more complex assessment.
Each deficiency round adds approximately three to six months to these baseline timelines. An application that generates two deficiency rounds on a Class C device can easily run to two years or more. This is why documentation quality at the point of initial submission is not just an efficiency consideration — it is a business-critical decision that affects product launch timelines, cash flow, and competitive positioning.
The single most reliable way to reduce timelines is to submit complete, consistent, well-prepared documentation the first time.
A Framework for SUGAM Readiness
Before logging into SUGAM to start any application, work through this sequence.
Verify your company profile is accurate and current.
Confirm your device's notified status and select the correct application form.
Prepare and internally review all required documents with specific attention to consistency across documents.
Write your classification justification.
Draft your intended use statement carefully.
Check every certificate for current validity.
Name your documents clearly.
Only when this preparation is complete should you open the application form.
The companies that move efficiently through CDSCO's regulatory process are not the ones with the most regulatory experience. They are the ones that treat preparation as the work and submission as the conclusion.
Final Thought
The SUGAM portal reflects the state of India's medical device regulatory infrastructure — ambitious in intent, improving steadily, and still demanding patience and precision from applicants who use it.
Understanding its logic does not make the process fast. But it makes the process manageable and eliminates the avoidable delays that trap applications in deficiency cycles for months longer than necessary.
Regulatory approval is not won at the portal. It is won in the weeks of preparation that precede it.
MedReg Intel publishes practical regulatory intelligence for Indian medical device manufacturers, importers and startups. Visit medregintel.com for the complete library.
For regulatory strategy support contact ankur@medregintel.com
This article is for educational purposes and does not constitute formal regulatory or legal advice.
Comments
Post a Comment