Picture a small deep-tech team in Pune. They have spent eighteen months developing a novel water purification cartridge, filed a complete specification, paid their fees, and settled into the long wait for examination. Then the First Examination Report arrives, and buried among the routine formal objections is one line that stops everyone in the room: "the specification does not sufficiently and clearly describe the invention so as to enable it to be performed by a person skilled in the art."

Nobody on the team is quite sure what that sentence means in practice, whether it is fatal, whether it is fixable, or whether it means their drafting was sloppy. This article walks through exactly what happens when that objection lands, at every stage it can appear, using that team's journey as a thread to keep the legal detail grounded in something concrete.

Act One: Understanding What "Sufficiency" Actually Demands

Before the Pune team can respond to anything, they need to understand what the law actually requires of them. Indian patent law is built on a bargain. In exchange for up to twenty years of exclusivity, the inventor must teach the public how the invention actually works, well enough that the teaching still has value once the patent expires.

That bargain is written into Section 10(4) of the Patents Act, 1970. Every complete specification must fully and particularly describe the invention, its operation or use, and the method by which it is performed, and it must disclose the best method of performing the invention that is known to the applicant at the time of filing. Two obligations sit inside that one subsection, and they are often treated as separate issues by examiners and opponents:

• A general enablement obligation: the invention must be described well enough that someone else, with ordinary skill in the field, could actually build and use it.
• A specific best-method obligation: whatever the applicant's own preferred way of doing it is, that has to be in the document too, not held back.

The team's cartridge patent had described the general filtration mechanism clearly, but the FER objection turned out to hinge on the second obligation. Their lab had actually settled on a specific pore-size and flow-rate combination that outperformed everything else they tested, and that detail had been left out of the specification in favour of a broader, safer-sounding range. That omission is precisely the kind of gap Section 10(4) is designed to catch.

Act Two: The Test Examiners and Courts Actually Apply

Insufficiency objections can sound abstract, almost philosophical, when they first appear on paper. In practice, Controllers, Opposition Boards, and courts collapse the whole inquiry into one working question:

Could a person skilled in the relevant art, reading only the specification and drawing on common general knowledge of the field, practise the invention without undue experimentation?

This "skilled person" is a legal fiction, not a real employee. They are assumed to be competent and diligent, familiar with the standard textbooks, tools, and techniques of the field as they stood on the filing date, but not a genius and not a mind reader. If the specification leaves a gap that this skilled person could fill in through routine trial and error using known techniques, the disclosure usually survives. If filling the gap would require genuine inventive effort, guesswork, or information the specification simply never provides, the disclosure fails.

For the cartridge team, the question became concrete rather quickly. Yes, a skilled process engineer could probably identify a workable pore size through routine testing. But could they identify the specific best-performing combination the team had actually found, the one their own data showed outperformed the alternatives, without that data being disclosed? No. That gap was not routine experimentation; it was withheld knowledge, and that is a best-method problem, not merely an enablement problem.

Act Three: Where This Objection Can Actually Land You

One of the more unsettling things the Pune team learned is that an insufficiency objection is not a single event they could simply get past and forget. It is a recurring risk that can resurface at four distinct points across the life of a patent, each with its own procedure and its own cast of characters.

Stage 1: The First Examination Report

This is usually the earliest point of contact. The Controller reviews the complete specification against the statutory requirements, including Section 10(4), and raises objections in writing. Delhi High Court decisions have made clear that these objections cannot simply assert "the invention is not enabled" in the abstract; the Controller is expected to identify what, specifically, is missing, so that the applicant has something concrete to fix or argue against. A vague objection is itself challengeable.

Stage 2: Pre-Grant Opposition

After the application publishes but before it is granted, any person, not just a competitor with a direct commercial stake, can file a representation opposing the grant. This is done on Form 7A, accompanied by a statement of case and supporting evidence. The governing procedure is Rule 55 of the Patent Rules, and since the 2024 amendments, the Controller must now issue a reasoned prima facie order on the representation, which has made this stage considerably more structured than it used to be. Insufficiency sits alongside novelty and inventive step as one of the standard grounds raised here.

Stage 3: Post-Grant Opposition

Once the patent is granted, the door does not close. Within one year of the publication of the grant, a "person interested," typically someone with a genuine commercial or research interest in the field, can file a post-grant opposition. This goes to an Opposition Board constituted under Rule 56, which examines the evidence and recommends a course of action to the Controller, who then decides.

Stage 4: Revocation in Court

After the one-year post-grant window closes, the challenge does not disappear; it simply changes venue. An interested person can seek revocation of the granted patent under Section 64, which lists insufficiency of disclosure, and separately, failure to disclose the best method, as independent statutory grounds. This is now a full court proceeding, with all the evidentiary weight that implies.

The team's takeaway from mapping this out was simple but sobering: surviving the FER objection would not make the issue disappear permanently. It would only close the earliest and cheapest door. A competitor could still raise the same argument years later, with a very different set of resources behind it.

Act Four: The Five Recurring Fault Lines

Working through published orders and known decisions with their patent agent, the Pune team noticed the same five weaknesses coming up again and again in insufficiency disputes, regardless of the technology involved.

1. Enablement gaps disguised as narrative. 

A specification can read smoothly and still fail to enable. If the actual operative steps, the specific reagents, the working ranges, or the essential apparatus are missing or vague, polished prose around them does not rescue the document.

2. The best method quietly left out. 

This is often not deliberate concealment; it is drafting caution. Teams sometimes describe a safer, more general version of their process instead of the exact configuration they actually use, worried that specificity narrows their claims. But Section 10(4)(b) does not ask for the safest description; it asks for the best one you actually know.

3. Broad claims resting on narrow examples. 

If the claims sweep across a whole family of variants, materials, or configurations, but the specification only illustrates one narrow point within that family, opponents will argue the disclosure does not support the breadth being claimed. This shows up constantly in chemistry, pharmaceuticals, and biotechnology, where a claim can cover thousands of theoretical compounds while the specification tests only a handful.

4. Claim clarity problems that compound the sufficiency argument. 

Section 64(1)(i) separately allows revocation where claims are not sufficiently and clearly defined. Loosely bounded words like "about," "substantially," or "optimised," used without any measurable anchor, invite both a clarity objection and a sufficiency objection at the same time, from the same sentence.

5. Information scattered rather than stated. 

If a critical parameter only appears in a drawing, or is implied by reference to an external paper or datasheet rather than written into the specification itself, the disclosure can be treated as incomplete even though the information technically exists somewhere in the file history.

The cartridge team recognised themselves in fault line two almost immediately. Their engineers had the best-method data in their lab notebooks; it had simply never made it into the drafted specification.

Act Five: Responding, Stage by Stage

If it happens at the FER stage

The response is a written submission, filed within the prescribed period, addressing the objection point by point. If the objection itself was vague, the applicant can push the Controller for specificity rather than guessing at what is actually being asked. Where the gap is genuinely one of explanation rather than missing substance, an expert affidavit explaining how a skilled person would fill the gap using common general knowledge can be persuasive. Where the gap is a real, substantive omission, such as the cartridge team's missing pore-size data, the fix usually has to come through permitted amendment.

If it happens at pre-grant opposition

The applicant files a detailed reply to the opponent's statement of case, again supported by technical argument and, where useful, expert evidence. Because the 2024 amendments require a reasoned prima facie order from the Controller, both sides now get a clearer, earlier signal of how the objection is likely to be viewed, before the matter proceeds to a full hearing if one is requested.

If it happens at post-grant opposition

This is a more formal, adversarial process, run through the Opposition Board. The evidentiary record matters enormously here: affidavits, cross-examination in some cases, and technical submissions from both sides. The Board's recommendation carries real weight with the Controller's final decision.

If it happens at revocation

By this stage, the matter is in court, and the standards of evidence and argument rise accordingly. The original prosecution history, including everything said in earlier FER responses or opposition proceedings, becomes part of the record that both sides will comb through for inconsistencies or admissions.

The one constant limit across every stage: Sections 57 and 59

At every single stage, there is one boundary that cannot be crossed. Amendments to the specification or claims, whether by way of correction, explanation, or disclaimer, are permitted under Sections 57 and 59, but only if they do not introduce new subject matter and do not enlarge the scope of the claims. This means an applicant can clarify, narrow, or better align claim language with what the description already supports. It does not mean an applicant can add the missing best-method data after the fact, if that data was never in the specification as filed. For the cartridge team, this was the hardest lesson: their actual best-performing pore size, sitting in a lab notebook, could not simply be inserted into the specification at this late stage without risking a new-matter objection, because it had never been disclosed on the filing date.

Act Six: What the Team Could Actually Do

Facing this, the team had three realistic paths, and they are the same three paths most applicants in this position have.

Path one: argue enablement without the missing data. 

If the missing detail is something a skilled person could plausibly work out through routine testing, even without knowing the team's specific best result, the response focuses on demonstrating that routine path, often with an expert declaration explaining the reasoning a skilled formulator or engineer would follow.

Path two: narrow the claims to what is genuinely supported. 

If the broader claim scope cannot be defended, a disclaimer amendment under Section 59 can pull the claims back to the range that the specification does support, sacrificing some breadth to preserve validity.

Path three: accept the exposure and manage it commercially. 

In some cases, particularly where the missing detail is minor and the claims are otherwise well supported, the team may decide the risk of a future opposition is manageable and proceed, keeping better records for next time and drafting future filings differently.

The cartridge team ultimately combined paths one and two: they filed expert evidence showing that a skilled engineer could reasonably arrive within a workable range of their actual result through standard optimisation testing, while also narrowing one claim slightly to track the disclosed range more closely. The application proceeded to grant roughly four months later.

Act Seven: Building a Specification That Does Not Have This Problem Later

The most useful output of the whole episode, for the team, was not the successful response itself but the checklist they built afterward for every future filing.

• Before drafting begins, list every parameter, material, and step that the internal team actually relies on to make the invention work well, not just the version that sounds defensible on paper.
• Include the best-performing configuration explicitly, even if it feels like giving away a competitive detail. The statute requires it, and withholding it creates a liability that can surface years later, at a much less convenient moment, such as during litigation.
• For any claim that spans a range or family of variants, add at least one worked example near each meaningful boundary of that range, not only at the comfortable centre.
• Avoid vague qualifiers such as "about," "substantially," or "optimised" unless they are anchored to a measurable definition somewhere in the specification.
• Keep dated internal records of test data and development notes. They will not change your priority date or your disclosure obligations, but they make it far easier to prove, later, exactly what was known and when, which matters both for best-method arguments and for any future wrongful-obtaining dispute.
• Treat the specification as though an opponent's patent agent is already reading it, looking for exactly the kind of gap that turned into the FER objection in this story.

Frequently Asked Questions

Does a insufficiency objection mean my invention itself is flawed? 

No. It is a drafting and disclosure issue, not a judgment on whether the invention works or is valuable. Plenty of genuinely strong inventions get insufficiency objections purely because the specification did not translate the team's actual knowledge onto paper.

Can I add the missing information later if I simply forgot to include it? 

Only within the strict limits of Sections 57 and 59. You can clarify or narrow what is already disclosed. You generally cannot add genuinely new technical content that was absent in substance on the filing date, even if you knew it internally at the time.

Is it worse to face this objection before or after grant? 

Both carry real consequences, but a post-grant or revocation-stage insufficiency finding is generally more damaging, because it can invalidate a right you have already been relying on commercially, possibly after you have licensed it, litigated on it, or built a business around it.

Does filing a provisional specification first change the sufficiency analysis? 

The sufficiency requirement applies to the complete specification, since that is the document from which claims and grant flow. However, if your complete specification simply mirrors a thin provisional without adding proper detail, you inherit whatever gaps existed at the provisional stage.

Can a well-funded opponent simply keep raising this objection at every stage to wear an applicant down? 

In principle, different opponents can raise the same ground at different stages, since surviving one stage does not bind a different party at a later stage. This is precisely why a specification built to withstand scrutiny from the outset is worth more than any single successful rebuttal.

Does this apply the same way to software and AI-related inventions? 

Yes, though the specific gaps look different. Instead of missing reagents or ranges, the common issue is claims framed entirely around a desired outcome or result, without disclosing the actual architecture, algorithmic steps, or technical implementation that achieves it. The same skilled-person test applies, just translated into a computer science context.

Closing

An insufficiency challenge, wherever it lands in the life of a patent, tends to reward one thing above all else: whether the specification, as filed, actually told the truth about how the invention works, completely and specifically, rather than in outline. The Pune team's cartridge patent survived because the gap was narrow enough to argue around and the rest of the disclosure was strong. Not every applicant is that fortunate. The lesson worth carrying forward is not really about how to win an insufficiency fight after it starts. It is about drafting so carefully, and so honestly, on the day of filing that the fight rarely needs to happen at all.

This article is for general informational purposes and reflects the author's understanding of the Indian Patents Act, 1970, the Patent Rules, and related judicial trends. The scenario used here is illustrative and does not describe any real client or matter. This is not a substitute for specific legal advice on your own specification or prosecution strategy.