CRI explained: this guide covers what it means, who it applies to, the step-by-step process, documents required, fees, due dates and penalties in India — so you can stay compliant with confidence and avoid costly mistakes.
Paragraph 4.4 of the CRI Guidelines 2025 is the drafting paragraph. It tells applicants how much the specification of a computer related invention must disclose, how the Office reads claims in any form, and when a "means for" claim is accepted. The common thread is that the specification must show the implementation, not only the idea.
For a CRI, the sufficiency requirement is treated as met when the specification answers a "What" question (the invention described fully and particularly) and a "How" question (the implementation shown with illustrations) (para 4.4). Claims are judged on substance, not form (4.4.1, 4.4.2). A means plus function claim is not allowed unless the specification discloses the structure behind each means (4.4.3). The Guidelines are the Patent Office's guidance and do not have the force of law; the Patents Act, 1970 and the Patents Rules, 2003 as now in force prevail.
The Office revises its guidelines, so check the current version on ipindia.gov.in. Section 10(4) is the statutory source; our posts on section 10, claims, abstract and biological material explain it, and the Manual's practice is in our article on sufficiency and unity. The aim here is to show what the CRI Guidelines add. For a specification built to meet these points from the start, see patent drafting and filing.
Why disclosure comes first
The Guidelines describe the grant of a patent as an exchange for disclosure. The specification must be clear and informative enough for a person skilled in the field to understand, replicate and practically apply the invention. They say that a specification should enable that person to work the invention without the patentee's help or undue experimentation, and that the description must be unambiguous, correct and accurate and must not mislead.
For CRIs the Guidelines then narrow the test: sufficiency is considered fulfilled if the specification addresses the "What" and "How" requirements.
The "What" requirement: fully and particularly
| Kind of invention | What the specification should contain |
|---|---|
| Apparatus, system or device (hardware-based) | Every feature described, with suitable drawings |
| Method | The necessary sequence of steps described clearly enough to distinguish the invention from the prior art, with flowcharts and other information required, including the implementing mechanism |
| Both | How the components work together and how they are connected; the desired output or outcome; any intermediate components or steps |
The effect of this is that a bare flowchart is not enough. The examiner looks for an implementing mechanism: what runs where, on what, and how data moves between the parts.
The "How" requirement: the most suitable method of performing the invention
Section 10(4)(b) requires the applicant to disclose the method of performing the invention that the applicant considers most suitable. For CRIs, the Guidelines say the description should not stay at the level of functionality; it should specifically and clearly describe the implementation, with suitable illustrations.
The Guidelines add a warning about a problem they call peculiar to this field. A problem statement or a prospective use case may be presented as if it were the solution. Because of that, the part that is claimed as the novel and inventive solution must be disclosed fully and particularly. In practice, an examiner who sees a specification that describes only what the system should achieve is likely to raise a sufficiency objection. The remedy is to describe the architecture, data structures, sequence and, where relevant, hardware interaction by which the result is reached.
Claims (paragraph 4.4.1)
The Guidelines list three points.
- Claims should define the scope clearly and meet the unity requirement of section 10(5).
- Claims should be clear and succinct and fairly based on the matter disclosed.
- In CRIs, claims are to be construed for their substance, without relying wholly on their forms and types.
Our article on claims in the Manual covers the general drafting rules.
Form and substance (paragraph 4.4.2)
The Office says judging mathematical and business methods is comparatively easier; the careful attention goes to computer programme per se and algorithm claims. Programmes are often claimed as methods or systems with "means" standing for flowchart functions. An algorithm claim can be even wider than a programme, because one algorithm can be implemented by different programmes in different languages.
The key sentence for applicants is that a claim in any form (method or process, apparatus, system or device, computer program product or computer readable medium) which in substance belongs to an excluded category is not patentable. The Guidelines add that the exclusion should not be avoided by changing the wording of a claim.
Two practical lessons follow.
- Do not draft a "system comprising a processor and memory storing instructions" claim and expect it to escape section 3(k) if the real contribution is the instruction set alone. The substance test applies.
- Do not assume you must choose only method or only system claims. Paragraph 4.4.2 says section 3(k) does not limit a CRI application to one type; if the specification supports both, both may be allowed even as independent claims. Annexure I carries a non-exhaustive list of allowable and non-allowable examples; our later articles in this series summarise them.
Means plus function claims (paragraph 4.4.3)
CRI claims often say "means for" performing a function. The Guidelines set four conditions.
| Condition | What it means for the draft |
|---|---|
| The means must be clearly defined by structural features and reference numerals | Tie each "means" to a numbered element in the drawings |
| The claim is not allowed if the structure of the means is not disclosed | Describe the hardware, firmware or software module that does the job |
| The means is limited to what the specification discloses | Do not expect the claim to cover every possible way of performing the function |
| The specification must disclose the corresponding structure, which may be hardware, firmware or a software module shown in the specification and drawings | A named module with its inputs, outputs and steps counts; a function label alone does not |
A worked example (invented)
Anvesha Labs files a claim to "means for predicting machine failure". The specification says only that the means "analyses sensor data and outputs a prediction". The examiner objects under paragraph 4.4.3 that no corresponding structure is disclosed. Anvesha amends the description to identify a sensor interface, a feature extraction module and a classifier module, each shown in a numbered drawing with its input and output, and ties the claim language to those references. The objection is met by pointing to the description and drawings that disclose the structure, not by arguing that the function is novel.
Common lapses
- Describing results but not the implementing mechanism.
- Using "means" with no numbered structure in the drawings.
- Presenting the use case as the solution.
- Drafting claims in several forms that all rest on the same abstract instruction set.
- Treating the Guidelines' "What" and "How" as a substitute for section 10; they are an application of it.
Need help with the specification or the claims?
If your invention is software-heavy, the description and the claim set need to be drafted together so that the structure behind every functional term is on the page. Our team can review a draft against paragraph 4.4 before filing or reply to a sufficiency objection after it. See patent drafting and filing and the next steps in paragraph 4.5.1 on mathematical methods.
Key takeaways
- For a CRI, sufficiency is met by answering "What" and "How".
- Show the implementing mechanism, not only the function.
- Claims are judged on substance in every form, including computer readable medium claims.
- Means plus function claims need disclosed corresponding structure.
- Both method and system claims can be allowed if supported.
Read next
- CRI Guidelines 2025, paragraphs 4.1 to 4.3: novelty, inventive step and industrial applicability
- CRI Guidelines 2025, paragraph 4.5.4: computer programme per se
- Manual Chapter 5: claims, unity, clarity and scope
- Manual Chapter 9: sufficiency of disclosure and unity
Disclaimer: Based on the manuals and guidelines published by the Office of the Controller General of Patents, Designs and Trade Marks that are named in the article, as consulted on 4 October 2026. They are guidance and do not have the force of law; the Patents Act, 1970 and the Patents Rules, 2003 as amended (including the 2024 amendment rules) prevail, and the current versions on ipindia.gov.in should be checked. This article is general information, not legal advice; check the official text before acting.