Mohun Nicholas D'Souza v. The Controller of Patents of Designs

In the world of patents, the word "obvious" gets thrown around a lot. But calling an invention obvious without actually proving it? That's not just lazy reasoning — it can be a fatal flaw that unravels an entire rejection. For one inventor with a tamper-evident security seal, a vague obviousness finding became the very reason he won his case against the patent authority.

Mohun Nicholas Dsouza, an independent inventor, filed a patent application titled "TAMPER EVIDENT TWIST SEAL WITH BREAKAWAY ANCHOR MECHANISM" — a specialized security device designed to reveal tampering through a unique mechanical design. The Patent Controller, however, refused to grant the patent, citing Section 25(1)(e) of the Patents Act. The ground? The invention allegedly lacked an inventive step, meaning it was considered "obvious" to a person skilled in the art given what already existed. Dsouza, convinced his invention brought something genuinely new to the table, challenged this refusal before the High Court.

Dsouza's core argument was straightforward but powerful: the Controller had rubber-stamped the rejection without doing the hard analytical work. He pointed out specific differences between his claimed invention and the prior art cited against him — differences that, if properly considered, would have shown his mechanism was not a mere variation of existing designs. On the other side, the Controller stood by the rejection, presumably arguing that the elements of the invention were already known and could be combined without any inventive leap. The legal friction centered on a critical question: did the Controller actually engage with the technical distinctions Dsouza raised, or did it simply declare the invention obvious without substantiating that conclusion?

The High Court sided with Dsouza. The court found that the Controller had failed to conduct a proper analysis of obviousness — specifically, the Controller neglected to consider the differences between the claimed invention and the prior art that the applicant had pointed out. This was not a minor procedural oversight; it struck at the heart of how an obviousness rejection must be reasoned. Drawing on established precedent, including the principles from F. Hoffmann-La Roche Ltd., the court reinforced that rejecting a patent for lack of inventive step requires a detailed, substantive discussion of how a person skilled in the art would move from existing knowledge to the subject invention. Without that analysis, the rejection could not stand. The outcome was favorable to the petitioner.

For founders, inventors, and IP professionals, this case delivers a sharp reminder: an obviousness rejection is not a conclusion — it's an argument that must be built. If you receive a rejection under Section 25(1)(e), scrutinize whether the patent office actually walked through the reasoning required by precedent. Did they identify the person skilled in the art? Did they map the prior art against your claims? Did they address the technical distinctions you raised? If the answer is no, that rejection may be vulnerable. Equally, when drafting or prosecuting a patent application, anticipate the obviousness challenge head-on by clearly articulating what makes your invention non-obvious — the specific technical effect, the unexpected result, or the combination that a skilled person would not naturally arrive at. In patent law, the difference between a granted patent and a refused one often comes down to whether someone did the thinking out loud.