Product scope discussion

About product scope discussion

Clarify product identity, intended use and the applicant’s role before selecting a submission route.

CDSCO-related enquiries need an identified product, intended use and applicant role. For medical-device work, manufacturing, importing and other activities can involve different routes and authorities. A product’s commercial name alone does not establish its regulatory classification or the documents needed for a submission.

For product scope discussion, agree the product, activity, application or record involved and the working output. Focus the preparation on the information needed at this stage, with clear evidence references and an understandable handover for the person continuing the work.

When this support is useful

Businesses preparing a medical-device regulatory documentation enquiry can explore this support. The product category, intended use, applicant role and current Indian requirements must be established before the detailed submission scope is agreed.

This subservice can be discussed when the business has reached the relevant stage, received a request for information or identified a gap it cannot resolve from its existing records. Start with the actual request and explain what work has already been completed. That avoids both duplicating earlier preparation and overlooking an unresolved dependency.

Regulatory licensing, product testing and ISO 13485 management-system certification are distinct. An application acknowledgement is not a granted licence. The competent authority determines the applicable regulatory outcome.

The starting information for this work

The task-specific inputs are: Product description, models, intended use and manufacturer information.

Identify the current version of each input and the person who can confirm it. Keep the original requirement alongside any summary. Where an input has not yet been verified, mark that point clearly so the preparation does not convert an assumption into an application statement.

• Product description, intended use and model information
• Applicant, manufacturer and site details
• Relevant quality-system and manufacturing information
• Available technical reports and product specifications
• Labels, instructions and other requested product information
• Existing licences, applications and authority correspondence

How the work is organised

1. Separate product variants.

   Begin with the relevant source record and the scope agreed with the applicant. Record the fact being checked and identify what would establish it, rather than relying only on a title or a previous file name.

2. Identify activity.

   Compare the related information as a connected set. A change to one attachment can affect a product description, application field or evidence reference elsewhere, so keep those relationships visible.

3. Record classification questions for competent review.

   Retain the reviewed result and any question that remains open. Identify the next owner and the evidence needed before the applicant treats the work as ready for the next stage.

The steps should be agreed with the business and adapted to the actual record or product. Where a question requires a technical, regulatory or other professional conclusion, the preparation should identify the appropriate reviewer. Administrative organisation and professional assessment remain different responsibilities.

Evidence and consistency checks

Use this wider service context to check whether the task-specific records remain coherent. For example, names, models, locations and reporting periods should be understandable across related files. If they differ for a valid reason, explain the relationship with the applicant and keep the source evidence accessible.

The working output and its handover

A regulatory-scope enquiry brief.

A useful handover identifies what was reviewed, the version or date, the evidence references and the outstanding questions. It should also identify the next responsible person. That allows another team member or an external reviewer to continue the work without reconstructing the preparation history from scattered messages.

An organised output is not a substitute for the relevant external decision. Where the next step is a submission, test, assessment or professional review, agree who authorises it and which reviewed information will be used. Keep the acknowledgement or response with the same record.

Why careful preparation matters

• An identified product and applicant scope before document preparation.
• A coherent technical-file structure with clear evidence references.
• Better visibility of missing information and specialist-review tasks.
• An organised history of application questions and responses.

For this subservice, judge the preparation by how clearly it resolves the task and supports the next decision. An output that still contains unexplained identity or scope differences can create avoidable questions later, even if the folder appears complete. The practical aim is a record that the business can understand and stand behind.

An illustrative working example

An importer proposes a family of devices with different intended uses. The team separates the models, records the manufacturer and identifies which technical documents apply to each. It asks the classification and route questions before assuming that a certificate from another market establishes Indian approval.

At the product scope discussion stage, the team would focus on this question: Are intended use and organisational role consistent across the proposed range? The evidence for the answer should be recorded in the working output, with any unresolved point assigned to a person rather than silently treated as settled.

Common issues and the final review

• Using a similar product’s classification without a product-specific review.
• Treating an overseas certificate as automatic permission for the Indian market.
• Submitting conflicting model or intended-use information across documents.

The task-specific review question is: Are intended use and organisational role consistent across the proposed range?

Separate a missing document from an unsupported claim and from a technical question. These need different actions. Obtaining a file may resolve the first; correcting the statement or obtaining competent review may be necessary for the others. Keep those actions visible until the responsible person has reviewed the result.

After this stage is completed

Keep the granted scope, product details and conditions accessible. Review proposed design, manufacturing, applicant or labelling changes through the applicable route before assuming continued coverage.

Retain the task output with the source information, reviewed version and relevant correspondence. If the underlying business facts change before the next submission or assessment, check the effect on the prepared material rather than assuming the earlier result still applies.

Discuss your requirement with TenderCert

Start with the outcome you need and the evidence you already hold. Bring the exact buyer clause, authority request or assessment enquiry where available, together with a short description of the product, activity or site. This makes the conversation more useful than asking for an unspecified certificate.

TenderCert’s consultancy scope can then identify the preparation and coordination tasks to discuss, the person responsible for each input and the questions for the relevant decision-maker. The applicant should review information and declarations before any external submission. Keep the final reviewed version and the acknowledgement together so later follow-up begins from the same record.

Common questions