A Device Master File (DMF) is the technical "recipe" for a medical device — it describes the device's design, specifications, materials, manufacturing process, testing, and validation. Under CDSCO's Medical Devices Rules, 2017, the DMF is a mandatory document for every manufacturing or import license application, alongside the Plant Master File (PMF), which describes the facility rather than the product. CDSCO reviewers check that the DMF, the PMF, and the physical facility are all consistent with one another. Because a DMF contains many interrelated documents that change over time, manufacturers who rely on shared drives, spreadsheets, and email-based reviews often find their DMF becomes outdated or inconsistent — which is precisely what triggers CDSCO queries and audit observations. A structured document control process keeps the DMF accurate, current, and ready for submission or audit at any time.
Of all the documents in a CDSCO medical device license application, the Device Master File is the one that tells reviewers what your product actually is. The cover letter, the constitution proof, the facility layout — these establish who you are and where you operate. The Device Master File establishes what you have built, how you built it, and how you know it works. It is, in effect, the technical biography of your device, and it is the document CDSCO reviewers return to again and again throughout the review and audit process.
Despite its importance, the DMF is also the document most likely to drift out of date, become internally inconsistent, or arrive at submission missing a section that a different team assumed someone else had completed. This guide explains what a Device Master File needs to contain for a CDSCO application, how it relates to the Plant Master File, and why the way you manage your documents — not just what's in them — determines whether your DMF holds up under review.
📑 Quick Navigation
What Is a Device Master File?
A Device Master File is the consolidated technical record that describes how a medical device is designed, built, tested, labelled, and supported throughout its life. If the Plant Master File answers the question "is this facility capable of making medical devices?", the Device Master File answers a different question: "is this specific device, as designed and manufactured, safe and effective for its intended use?"
For CDSCO applications under the Medical Devices Rules, 2017, the DMF is a mandatory submission for manufacturing licenses (MD5 for Class A/B devices, MD9 for Class C/D devices) and for import licenses (MD15). Whatever the device — a thermometer, an IVD kit, or a cardiac implant — the underlying expectation is the same: the DMF should contain, or clearly reference the location of, everything a competent reviewer would need to understand how the device is built and how its safety and performance have been demonstrated.
Device Master File vs Plant Master File: What's the Difference?
It is easy to conflate the Device Master File with the Plant Master File, since both are mandatory CDSCO documents and both are often prepared around the same time, by overlapping teams. But they answer fundamentally different questions, and CDSCO reviewers treat them as complementary rather than interchangeable.
Device Master File (DMF)
- Describes the device — its design, specifications, and intended use
- Contains the bill of materials, drawings, and component specifications
- Documents the manufacturing process for the product itself
- Contains risk management, testing, and validation data for the device
- Includes labelling, instructions for use, and the declaration of conformity
Plant Master File (PMF)
- Describes the facility — layout, infrastructure, and environment
- Contains equipment lists and qualification records
- Documents the quality management system at the site
- Contains personnel records and organisational structure
- Describes GMP controls applicable across all products made at the site
What CDSCO Expects to Find in the DMF
While CDSCO's guidance does not prescribe a single rigid template for the Device Master File, the underlying expectation — consistent across MD5, MD9, and MD15 applications — is that the DMF should contain, or clearly reference the location of, information covering five broad areas of the device and how it is produced.
Drawings, composition, formulation, component specifications, and — where applicable — software specifications that fully describe the device as designed.
The equipment used, the production methods and procedures followed, and the production environment specifications required to manufacture the device consistently.
Acceptance criteria for incoming materials, in-process checks, and finished devices, along with the quality assurance equipment used to verify them.
The methods and processes used for packaging and labelling, including the content and layout of labels and instructions for use.
A fifth area — installation, maintenance, and servicing procedures — applies where the device requires these activities after it reaches the end user, and should be included in the DMF wherever relevant to the device category.
Typical Contents of a CDSCO Device Master File
In practical terms, a Device Master File assembled for a CDSCO application typically draws together the following documents and records. Not every item applies to every device category, but the list below reflects the breadth of material reviewers expect to be able to locate, either within the DMF itself or by reference to where it is held.
- Declaration of conformity — A statement confirming the device meets the applicable essential principles of safety and performance.
- Intended use statement — A clear description of the device's intended purpose, which must match the wording used in the application form.
- Requirements and specifications — The design inputs and outputs that define what the device must do and how it is built.
- Product specifications and drawings — Detailed drawings and specifications sufficient to describe the device as manufactured.
- Risk management documentation — Risk analysis and risk control records prepared in line with ISO 14971.
- Product and process testing data — Results demonstrating the device and its manufacturing process meet defined acceptance criteria.
- Sterility testing data — Where the device is supplied sterile, validation and routine testing records for the sterilisation process.
- Shelf-life and stability data — Evidence supporting the claimed shelf life of the device, where applicable.
- Bill of materials (BOM) — A complete listing of components and materials used in the device.
- Quality control instructions and forms — The procedures and recording formats used to verify quality during manufacture.
- Component information — Specifications and supplier information for key components and materials.
- Labelling and instructions for use — Final approved labelling artwork and instructions provided with the device.
- Clinical evidence files — Clinical data or literature supporting the device's safety and performance, where required by its classification.
- Change request records — A history of design or process changes made to the device, with their justification and approval.
- Complaint and CAPA history — Records of complaints received and corrective or preventive actions taken in response.
Anyone reviewing this set of documents should come away with everything needed to understand how the device is built, how it is checked, and how issues with it are managed — while also being able to see, at a glance, how each document came to be in its current, approved form.
How to Prepare the CDSCO Plant Master File in 2026 — Complete Guide
The companion document to the DMF. This guide covers the sections CDSCO expects in the Plant Master File, how it is used during facility audits, and how to keep it consistent with your Device Master File.
Why Spreadsheet and Folder-Based DMFs Fall Short
Looking at the list of contents above, it should be clear that a Device Master File is not a single static document — it is a living collection of interrelated records, many of which are also referenced from your Plant Master File, your quality management system, and your post-market surveillance records. Trying to hold all of this together using shared drive folders, spreadsheets, and email-based reviews tends to work for a while — and then quietly stops working at exactly the wrong moment.
Three structural problems tend to recur in manually managed DMFs:
Specifications, drawings, and the bill of materials are iterated by different people in quick succession, moving from draft to approved status through multiple corrections. Without controls, documents are easily misfiled, overwritten, or simply lost between teams.
Spreadsheets and standard file-sharing tools have no native process for routing, authorising, and recording changes. Manual change requests by email take time, create bottlenecks, and increase the risk that a change is implemented in one document but never reflected in the others that depend on it.
The same test data, drawing, or specification is often referenced from multiple places in the DMF and PMF. Folder-based systems have no way to keep these references linked, so updates made in one place do not propagate to the others.
Why Structured Document Control Matters
The practical fix for all three problems above is the same: manage the Device Master File using a structured document control approach from the outset, rather than retrofitting order onto a folder of files once a submission deadline is close. A well-run document control process defines the structure of the DMF at the start of development, so that approved documents populate the right sections automatically as the design progresses, rather than being assembled retrospectively.
This matters most at two moments: when CDSCO raises a query and you need to locate the exact current version of a specific document quickly, and when an auditor asks to see the change history behind a particular design decision or test result. A DMF maintained under proper document control answers both questions in minutes. A DMF spread across shared drives and spreadsheets often cannot answer either with confidence — and that uncertainty, more than any single missing document, is what turns a routine review into a prolonged one.
Frequently Asked Questions
Is the Device Master File the same for every CDSCO license type?
The underlying expectation — that the DMF describes the device's specifications, manufacturing process, quality controls, packaging and labelling, and (where relevant) installation and servicing — applies across MD5, MD9, and MD15 applications. The depth of detail expected, particularly around risk management, biocompatibility, and clinical evidence, increases with the device's risk classification, so a Class C or D implant's DMF will typically be considerably more extensive than that of a Class A or B device.
Who is responsible for maintaining the DMF after the license is granted?
The license holder is responsible for keeping the DMF current throughout the product's life. Any material change to the device's design, materials, manufacturing process, or testing should be reflected in the DMF through a documented change control process, and the updated DMF should remain consistent with the Plant Master File and with what CDSCO has approved.
Can the DMF simply reference other documents instead of containing them directly?
Yes — CDSCO's expectation is that the DMF should contain the relevant information or refer to the location of it. In practice, this means a DMF can reference controlled documents held elsewhere in your quality management system, provided those documents are clearly identified, current, and readily retrievable if requested during review or audit.
What is the most common reason a DMF generates CDSCO queries?
Inconsistency is the most common trigger — between the DMF and the application form (most often the intended use statement), between the DMF and the Plant Master File (most often around equipment or process steps), or within the DMF itself (most often outdated versions of specifications or test reports that contradict more recent ones).
✓ Key Takeaways
- The Device Master File is the technical record of how a medical device is designed, manufactured, tested, and supported — it is mandatory for MD5, MD9, and MD15 CDSCO applications
- The DMF describes the product; the Plant Master File describes the facility — CDSCO reviewers check that the two are consistent with each other and with reality
- A complete DMF covers device specifications, production process specifications, quality assurance procedures, packaging and labelling, and — where relevant — installation and servicing
- Typical DMF contents include the declaration of conformity, intended use, specifications and drawings, risk management documentation, testing data, BOM, labelling, clinical files, and change/complaint/CAPA history
- Spreadsheet and shared-drive approaches tend to produce broken links, outdated copies, and duplicated effort as documents move between teams and revisions
- Structured document control with change management keeps the DMF accurate, consistent, and audit-ready at all times — not just at submission
- A DMF maintained under proper document control allows quick, confident responses to CDSCO queries and audit questions about specific documents and their history
Your Next Step
A Device Master File is only as useful as its weakest link — if one section is out of date or inconsistent with the rest, that is the section a reviewer or auditor will find. Manufacturers who treat the DMF as a structured, continuously maintained record from the start of development consistently move through CDSCO review and audit with fewer queries and fewer surprises than those who assemble it retrospectively from scattered files.
If you are preparing a Device Master File for a new CDSCO application, restructuring an existing DMF that has become inconsistent, or need help resolving queries that point to gaps in your documentation, Rego Services' regulatory team can help — from structuring your DMF around CDSCO's expectations through to setting up the document control discipline that keeps it audit-ready throughout your product's life.
Speak to a Rego Services regulatory consultant today to review your Device Master File structure and identify what needs to be in place before your next CDSCO submission or audit.