The local trial waiver, and the case it actually has to make
The New Drugs and Clinical Trials Rules, 2019 allow the licensing authority to waive the requirement for a local clinical trial in specified circumstances, including for a new drug already approved in certain countries. That provision has changed the arithmetic for a lot of programmes, and it has also produced a lot of applications that read as though the waiver were automatic.
It is not automatic. It is discretionary, and the discretion is exercised by a Subject Expert Committee reading your dossier. What that committee is deciding is a scientific question, not an administrative one: whether the evidence you have generated elsewhere predicts what will happen to Indian patients.
The question behind the rule
Requiring local data was never about nationality. It was about a real phenomenon: the same dose of the same drug does not always produce the same exposure, the same effect, or the same safety profile across populations.
The mechanisms are well characterised. Polymorphisms in metabolising enzymes differ in frequency between populations, and for a drug cleared predominantly by one of them, that difference moves exposure directly. Body weight distributions differ, which matters for fixed-dose products. The background burden of comorbidity and concomitant medication differs, which changes both the safety picture and the interaction risk. Standard of care differs, which changes what the comparator arm means.
A waiver application is an argument that, for this specific molecule, none of these move the answer enough to matter. It is a molecule-specific argument, and it cannot be made generically.
Where applications are thin
The pattern we see most often is a dossier that establishes approval elsewhere thoroughly and stops there. Approval status is the eligibility condition. It is not the case.
Three things are usually missing.
An explicit pharmacokinetic bridging argument. If the pivotal studies enrolled few or no South Asian participants, that has to be addressed rather than left for the committee to notice. Where the drug's clearance pathway is known and the relevant enzyme frequencies are comparable, say so and cite it. Where they are not comparable, the honest position is that a small local pharmacokinetic study answers the question faster than an argument will.
A defensible account of the Indian patient population. Committees ask what the indication looks like in India, and the answer is frequently different from the trial population in ways that matter. Disease stage at presentation, prior treatment lines, and comorbidity load all shift the benefit and risk balance, and a dossier that has thought about this is immediately distinguishable from one that has not.
A post-marketing commitment that is specific. A general undertaking to conduct surveillance is worth little. A stated design, population size, duration, and the events being watched for is a proposal the committee can accept or amend, and it converts an open concern into a managed one.
The strongest waiver applications read as though the sponsor had already asked itself the committee's questions and answered them. The weakest read as though approval elsewhere ought to settle it.
Not every product is arguing the same thing
The nature of the case varies more than the framing suggests.
For a small molecule with a well-understood metabolic pathway and a wide therapeutic window, the pharmacokinetic argument is usually straightforward and the discussion moves to the safety database.
For a narrow therapeutic index drug, the same population differences that would be tolerable elsewhere become the central issue, because a modest shift in exposure has clinical consequence. Expect the committee to focus there, and prepare the exposure argument in detail.
For a biological, immunogenicity is the question that will be asked, and it is one where population data are genuinely less transferable. A waiver argument that does not engage with immunogenicity in the Indian population is not addressing the committee's actual concern.
For an orphan indication, the argument runs the other way and often runs well: the number of Indian patients available is small, a local trial may be impractical or unethical to run, and the unmet need is high. That is a strong case, and it is worth making explicitly rather than relying on the committee to infer it.
Sequence the meeting, not just the submission
A practical point that costs programmes months. The Subject Expert Committee meets on a schedule, and applications are taken up when they are complete. An application submitted with a known gap does not wait in a queue until the gap is filled; it is taken up, queried, and returns to the back of the process.
The difference between submitting complete and submitting nearly complete is often one committee cycle, and sometimes two. Where a piece of the argument is weak, it is almost always faster to spend four weeks strengthening it than to submit and respond to the query it will generate.
It is also worth being ready for the meeting itself. Committees ask questions, and having someone available who can answer on the science rather than on the paperwork changes how the discussion goes.
When to stop arguing and run the study
The last thing worth saying is the least commercial. Sometimes the right answer is a local study.
If the drug's clearance depends heavily on a polymorphic pathway with materially different frequencies, if the therapeutic index is narrow, if the pivotal programme enrolled essentially no comparable population, or if the Indian standard of care differs enough that the comparator arm would not have been accepted here, the waiver argument is weak and the committee will see that faster than the sponsor does.
In those cases a well-designed local study, agreed in advance, is frequently the shorter path to market than two rounds of queries followed by a requirement to run one anyway. Deciding that early is a commercial judgement as much as a regulatory one, and it is worth making deliberately rather than by default.