The short answer
Section 132 of the Bharatiya Nyaya Sanhita, 2023 punishes assaulting or using criminal force against a public servant, with imprisonment of either description up to two years, or fine, or both. S1
The single most important thing about this section is procedural. Section 131, the general offence one section earlier, is non-cognizable and bailable and can be compounded without the leave of the court. Section 132 is cognizable, non-bailable, and not compoundable at all. S4; S6
So the same physical act - a shove, a raised fist - sits in an entirely different procedural world depending on who is on the receiving end. Against a private individual it is a minor, settleable matter. Against a public servant in the execution of his duty it is an arrestable, non-bailable offence carrying eight times the custodial maximum. S1; S4; S6
Two further points of note. The fine is left unquantified, so section 8(1) of the Sanhita governs its amount - the opposite of section 131, which expresses a ceiling. S1; S6 And a Maharashtra amendment had raised the Penal Code predecessor's maximum to five years, which has consequences discussed below. S2
The three limbs - the section is wider than it first appears
The provision is usually described as being about attacking a public servant on duty. It is in fact three alternatives, and only the first requires the officer to be on duty at the time. S1
"Whoever assaults or uses criminal force to any person being a public servant— (i) in the execution of his duty as such public servant, or (ii) with intent to prevent or deter that person from discharging his duty as such public servant, or (iii) in consequence of anything done or attempted to be done by such person in the lawful discharge of his duty as such public servant, shall be punished with imprisonment of either description for a term which may extend to two years, or with fine, or with both."
Limb (i) is the obvious case - force used against an officer while he is performing his duty.
Limb (ii) does not require the officer to be on duty at all. It requires an intent to prevent or deter him from discharging it. S1
Limb (iii) is retrospective in its orientation: force used because of something the officer has already done, or tried to do, in the lawful discharge of his duty. This is the limb that covers reprisals after the event. Note that limb (iii) alone carries the word "lawful". S1
Any one of the three suffices. Section 132 has no Explanation and no Illustrations. S1
"Public servant" is not defined here
The term takes its meaning from the definition in section 2(28) of the Sanhita. That definition has not been analysed in this article, and no comparison of it against section 21 of the Penal Code has been carried out anywhere in this collection - a gap that matters, because whether a particular office-holder is a "public servant" is logically the first question under section 132. S1
Against IPC section 353
The penalty is identical: two years, or fine, or both, with imprisonment of either description. The three limbs are reproduced. The fine is left unquantified in both. S1; S2
One word changed - and it looks like a correction
The India Code text of IPC section 353 reads that the force must be used "in consequence of anything done or attempted to be done by such person to the lawful discharge of his duty". Section 132 reads "in the lawful discharge of his duty". S1; S2
"In" is the grammatically correct form, and "to" makes little sense in context. This appears to be the correction of a long-standing textual oddity rather than a change of substance. But that cannot be stated as fact here. The original 1860 Gazette has never been retrieved for this collection, so whether "to" was in the Penal Code as enacted or is an artefact of how the India Code renders it is unverified. Either way, nothing of substance turns on the preposition. S1; S2
The fine position is unchanged - and this one had to be tested
Section 132 says simply "or with fine". Because no ceiling is expressed, section 8(1) of the Sanhita supplies the limit: the amount is not unlimited, but it is not fixed by the section either. S1
It would have been easy to assume this was a change. It is not. IPC section 353 also left the fine unquantified, so the position under the Penal Code was the same, section 63 of that Code performing the function section 8(1) now performs. S1; S2
That matters because the collection has found provisions where the Sanhita introduced a fine ceiling, which has the counter-intuitive effect of reducing maximum exposure. Nothing of that kind happened here, and nothing was removed either. The fine position is simply untouched. S1; S2
The contrast with the neighbouring section is still instructive: section 131 expresses a ceiling of one thousand rupees, so section 8(1) is displaced there; section 132 does not, so section 8(1) operates. The Sanhita alternates between the two styles within adjacent sections. S1; S6
The Maharashtra amendment - and what happened to it
The India Code record of IPC section 353 carries a State amendment: S2
"Maharashtra.—Amendment of section 353 of 45 of 1860.—In section 353 of the said Code, for the words 'two years' the words 'five years' shall be substituted. [Vide Maharashtra Act 40 of 2018, sec. 3]"
So in Maharashtra the predecessor offence carried a maximum of five years, not two. S2
Section 132 of the Sanhita carries two years. The Penal Code has been repealed. S1
The apparent consequence is that in Maharashtra the maximum sentence for this offence has fallen - conduct before 1 July 2024 attracted up to five years under the amended Penal Code provision, and conduct on or after that date attracts two years under section 132, unless and until Maharashtra legislates again. S1; S2
Several things about this are not established here, and they matter. Maharashtra Act 40 of 2018 was not itself retrieved - the amendment is reported from the India Code note to section 353. Whether Maharashtra has since made a corresponding amendment to the Sanhita has not been researched, and if it has, the position in that State will differ from what this article describes. The general question of what becomes of a State amendment to a repealed central Act is a question of law not addressed here. Anyone concerned with Maharashtra must check the current State position directly. S1; S2
This is the first State amendment examined anywhere in this collection, and it is a reminder that a central provision's stated maximum may not be the operative maximum in every State. S2
Classification, forum and compounding
The First Schedule entry
| Column | Section 132 | Section 131, for comparison |
|---|---|---|
| Punishment | "Imprisonment for 2 years, or fine, or both" | 3 months, or fine of 1,000 rupees, or both |
| Cognizable? | Cognizable | Non-cognizable |
| Bailable? | Non-bailable | Bailable |
| Triable by | Any Magistrate | Any Magistrate |
The shift on both of the middle two columns is the practical heart of this section. Because the offence is cognizable, the police may register and investigate it without a Magistrate's order. Because it is non-bailable, bail is not available as of right. Neither was true of section 131. S4; S6
Not compoundable
Section 132 appears in neither Table to section 359 of the Bharatiya Nagarik Suraksha Sanhita. Both were checked separately: zero entries in the Table to section 359(1), which lists offences compoundable without the court's permission, and zero in the Table to section 359(2), which lists those compoundable with it. S4
So the offence cannot be compounded. This is a sharp contrast with section 131, which appears in the section 359(1) Table and may be compounded by the person assaulted without any need to approach the court. A complainant who is a public servant cannot settle a section 132 case. S4; S6
The forum, and a gap between trial and sentence
The Schedule says "Any Magistrate". Section 23 of the Bharatiya Nagarik Suraksha Sanhita provides: S5
- section 23(1) - a Chief Judicial Magistrate may pass any sentence except death, life imprisonment, or imprisonment exceeding seven years;
- section 23(2) - a Magistrate of the first class, up to three years, or a fine up to fifty thousand rupees, or both, or community service;
- section 23(3) - a Magistrate of the second class, up to one year, or a fine up to ten thousand rupees, or both, or community service.
Section 132 carries a maximum of two years. A first class Magistrate can impose that in full. A second class Magistrate, whose ceiling is one year, cannot - though the Schedule's "Any Magistrate" makes the offence triable before him. S1; S4; S5
The distinction worth holding onto is between competence to try and power to sentence. A second class Magistrate is competent to try the offence; he simply cannot award more than one year of the available two. The Sanhita contains machinery for a Magistrate who considers his sentencing powers inadequate, which is not examined in this article. S4; S5
This is the seventh instance in this Chapter of a gap between the Schedule's forum entry and the sentencing power available there. It cannot be said that the Sanhita created this one. IPC section 353 also carried two years, and the First Schedule to the Code of Criminal Procedure, 1973 has never been retrieved for this collection, so the predecessor position is unverified. S1; S2; S4
Community service is a new option
Section 23(2) and (3) both now list community service among the sentences a Magistrate may pass, and section 23 carries an Explanation defining it. Whether and how that option is used for a section 132 offence is not addressed here; no authority on it was read. S5
How the courts have applied IPC section 353
Because section 132 reproduces IPC section 353 with no change of substance, decisions on the Penal Code provision bear on it directly. S1; S2
The Supreme Court: the ingredients, and a charge that failed
Manik Taneja and Another v. State of Karnataka and Another, Supreme Court of India, V. Gopala Gowda and R. Banumathi JJ, 20 January 2015, reported (2015) 7 SCC 423. S9
The appellants, aggrieved at their treatment by a Police Inspector, posted comments on the Bangalore Traffic Police Facebook page accusing him of misbehaviour and sent an email complaining of harassment. An FIR followed under IPC sections 353 and 506, and the High Court declined to quash it as premature. S9
The Court set out section 353 and said at paragraph 12: S9
"A reading of the above provision shows that the essential ingredients of the offence under Section 353 IPC are that the person accused of the offence should have assaulted the public servant or used criminal force with the intention to prevent or deter the public servant from discharging his duty as such public servant. By perusing the materials available on record, it appears that no force was used by the appellants to commit such an offence. There is absolutely nothing on record to show that the appellants either assaulted the respondents or used criminal force to prevent the second respondent from discharging his official duty. Taking the uncontroverted allegations, in our view, that the ingredients of the offence under Section 353 IPC are not made out."
The appeal was allowed. S9
Two points should be taken from this, and the second is a caution.
First, and most practically: the offence requires assault or criminal force, and nothing else will do. Posting comments online and sending an email - however critical of the officer - supplied neither, and the charge collapsed. Words are not criminal force, and under section 130's Explanation mere words are not an assault either. S7; S8; S9
Second, the Court's summary of the ingredients does not reproduce all three limbs. It describes assault or criminal force used "with the intention to prevent or deter" - which is limb (ii). It does not mention limb (i), force used against an officer in the execution of his duty without any such intention, or limb (iii), force used in consequence of what the officer had done. On the facts the Court did not need to, because no force of any kind was established. The passage should therefore be read as sufficient to dispose of that case rather than as an exhaustive statement of the section's reach, and that reading is this article's own. S1; S9
A conviction set aside because the officer was not on duty
In Harendrajeet Singh v. State of Madhya Pradesh (Madhya Pradesh High Court, Sanjay Dwivedi J, 11 April 2023) the appellant had been convicted under IPC section 353 by a Special Judge. S10
The Court set out the definitions of force, criminal force and assault together, reasoning that to establish whether the appellant "assaulted the complainant or used any criminal force upon him, it is necessary to examine" all three. S10
On the facts, the complainant himself admitted in his evidence that at the time of the incident he was not performing any official duty, and that nobody had restrained him from discharging it or assaulted him. The Court also criticised the prosecution for recording witness statements three to four years after the incident, holding that a witness deposing contrary to the complainant after such a delay could not be regarded as trustworthy. S10
It held that the prosecution had failed to establish the material ingredients of section 353, allowed the appeal, set aside the conviction and sentence, and acquitted the appellant. S10
This is the most useful authority on limb (i). The officer's actually being in the execution of his duty is not a formality to be assumed from his office - it is a matter to be proved, and a complainant's own admission that he was off duty was fatal to the charge. S1; S10
A caution about a third decision
Kailash Vijayvargiya and Others v. State of West Bengal and Another (Calcutta High Court, Appellate Side, Criminal Revisional Jurisdiction, Shampa Dutt (Paul) J, 20 November 2024) is a further section 353 decision which sets out the same definitions and cites Manik Taneja. S11
It is a High Court decision, not a Supreme Court one, notwithstanding a case name that invites the opposite assumption; the court was verified from the judgment itself. And its analytical paragraphs are textually identical to those in Harendrajeet Singh. Nothing is suggested about how that came about, but a reader who treated the two as independent authorities for the same proposition would be double-counting a single piece of reasoning. This article relies on the earlier decision. S10; S11
Practical distinctions and common misconceptions
The procedural consequences are the real difference from section 131 - cognizable, non-bailable, and not compoundable, against non-cognizable, bailable and compoundable without leave. S4; S6
The offence cannot be settled. It appears in neither compounding Table, so even a willing complainant cannot compound it. S4
The officer need not be on duty for limbs (ii) and (iii). Only limb (i) requires it. S1
But where limb (i) is relied on, duty must be proved. On Harendrajeet Singh, the complainant's admission that he was not on official duty defeated the charge. S10
Only limb (iii) uses the word "lawful". S1
Assault or criminal force is indispensable. On Manik Taneja, online comments and an email supplied neither and the charge was quashed. S9
Words alone will not do, since mere words are not an assault under section 130 and are not force under section 129. S7; S8
The fine has no ceiling in the section, so section 8(1) governs it - unlike section 131. S1; S6
A second class Magistrate can try it but cannot impose the full two years. S4; S5
In Maharashtra, check the position separately. The predecessor carried five years there by State amendment, and the current State position has not been researched. S1; S2
Worked examples
Example 1. A shoves a police officer who is directing traffic, to make him stop. Section 132, limb (i) and limb (ii) - cognizable and non-bailable, up to two years. S1; S4
Example 2. A shoves a private individual in the same way. Section 131 - non-cognizable, bailable, three months, and compoundable by the person shoved. The act is the same; the consequences are not. S4; S6
Example 3. A posts comments on a police Facebook page accusing an officer of misbehaviour, and emails a complaint. On Manik Taneja, neither assault nor criminal force, and the ingredients of the offence are not made out. S9
Example 4. A, angry at a tax officer who sealed his shop last week, pushes him in the street. Limb (iii) - force in consequence of something done in the lawful discharge of duty - even though the officer was not then on duty. S1
Example 5. A pushes an officer who is off duty and out of uniform, in a private quarrel unconnected with his office. Limb (i) is not satisfied, and limbs (ii) and (iii) require the intent or the connection to duty. On Harendrajeet Singh the absence of official duty was fatal. Section 131 may still apply. S1; S6; S10
Example 6. A raises his fist at an officer serving a notice, intending him to believe he is about to be struck, but never touches him. That is an assault under section 130, and assault is enough for section 132 - no contact is required. S1; S7
Example 7. The officer wishes to drop the matter after an apology. The offence is not compoundable, so he cannot. S4
Example 8. A is tried by a second class Magistrate who considers two years warranted. He cannot impose it - his ceiling is one year under section 23(3). S5
Commencement and which law applies
Section 132 commenced on 1 July 2024, under Ministry of Home Affairs notification S.O. 850(E) dated 23 February 2024. S12
Outside Maharashtra the transition is immaterial in substance: IPC section 353 and section 132 carry the same penalty, the same three limbs and the same unquantified fine, the only textual difference being the preposition discussed above. For conduct before 1 July 2024 the applicable provision is IPC section 353; on or after it, section 132. S1; S2; S12
In Maharashtra the position may differ, because the predecessor carried a five-year maximum there by State amendment while section 132 carries two. The current State position has not been researched and should be checked directly. S1; S2
Related provisions worth reading alongside section 132
- Section 129 - criminal force, one of the two ways the offence may be committed. S8
- Section 130 - assault, the other, and the source of the rule that mere words will not do. S7
- Section 131 - the general offence, and the procedural contrast that defines section 132. S6
- Section 2(28) - the definition of "public servant", not analysed here. S1
Sources and honest limits
The statutory comparison was made by token-level comparison of the India Code text of section 132 against the India Code text of IPC section 353, with page-number artefacts removed from the Penal Code text first, and with the section text checked against the Gazette publication of the Sanhita. The First Schedule row and both Tables to section 359 were read from the Gazette text of the Bharatiya Nagarik Suraksha Sanhita, as was section 23. The texts of sections 129, 130 and 131 were read from the verified section inventory. S1; S2; S3; S4; S5; S6; S7; S8
What this article does not establish:
- "PUBLIC SERVANT" IS NOT ANALYSED. It takes its meaning from section 2(28) of the Sanhita, and no comparison of that definition against section 21 of the Penal Code has been made anywhere in this collection. Whether a given office-holder is a public servant is logically the first question under section 132, and this article does not answer it.
- THE MAHARASHTRA AMENDMENT IS REPORTED, NOT RESEARCHED. Maharashtra Act 40 of 2018 was not retrieved; the amendment is taken from the India Code note to IPC section 353. Whether Maharashtra has made a corresponding amendment to the Sanhita has not been researched. What becomes of a State amendment to a repealed central Act is a question of law not addressed here. Anyone concerned with Maharashtra must check the current State position directly.
- THE "TO" / "IN" CHANGE IS NOT TRACED TO SOURCE. The India Code text of IPC section 353 reads "to the lawful discharge" and section 132 reads "in". The original 1860 Gazette has never been retrieved for this collection, so whether "to" was in the Penal Code as enacted or is a rendering artefact is unverified. The article's reading, that this is the correction of a textual oddity rather than a change of substance, is its own.
- MANIK TANEJA'S STATEMENT OF THE INGREDIENTS DOES NOT COVER ALL THREE LIMBS. It describes limb (ii) only. The reading of that passage as sufficient to dispose of the case rather than as an exhaustive statement of the section's reach is this article's own, and no authority on limbs (i) and (iii) as such was read beyond Harendrajeet Singh on the duty requirement.
- Harendrajeet Singh is a single-Judge decision of one High Court and does not bind elsewhere. Its subsequent treatment was not checked, nor was Manik Taneja's, though the repository records the latter as cited by 159.
- KAILASH VIJAYVARGIYA IS A CALCUTTA HIGH COURT DECISION, NOT A SUPREME COURT ONE, and its analytical paragraphs are textually identical to those in Harendrajeet Singh. It is cited only to record those two facts and not as independent authority.
- A SEARCH ON THE DUTY ELEMENT RETURNED 225 HITS WHICH WERE NOT READ EXHAUSTIVELY. Several decisions that may bear on "in the execution of his duty" - including one from 2010 - were identified and not pursued. So this article does not state the law on when an officer is or is not in the execution of his duty, beyond what Harendrajeet Singh decided on its facts.
- NOTHING IS SAID ABOUT WHETHER THE OFFICER'S OWN ACT MUST BE LAWFUL under limbs (i) and (ii). Only limb (iii) uses the word "lawful", and the significance of that asymmetry was not researched.
- THE SEVENTH FORUM GAP IS REPORTED WITHOUT ATTRIBUTING CAUSE. IPC section 353 also carried two years, and the First Schedule to the Code of Criminal Procedure, 1973 has never been retrieved, so it cannot be said whether the Sanhita created this gap or inherited it.
- The machinery for a Magistrate whose sentencing powers are inadequate is not examined, nor is the community service option now available under section 23.
- The procedural consequences of cognizability and non-bailability are stated but not worked through. What follows for arrest, investigation and bail applications is not set out.
- Criminal intimidation is not examined. Manik Taneja also concerned IPC section 506, and that provision and its Sanhita successor are not analysed.
- Private defence is not examined, though it is plainly capable of arising where force is used against an officer.
- Dates. Law checked as of the date in the article metadata. Later decisions, and any amendment to the Sanhita, are not reflected.
Section 132 is best understood by putting it beside section 131. The conduct element is identical - assault or criminal force, as defined in sections 130 and 129 - and the Sanhita changed neither the penalty nor the fine nor the three limbs it inherited from the Penal Code. What the section does is attach a sharply different procedural regime to the same act when the person on the receiving end is a public servant: cognizable instead of non-cognizable, non-bailable instead of bailable, and incapable of being compounded at all. The two decisions that matter both cut the other way, and are worth remembering: assault or criminal force must actually be established, and where the charge depends on the officer being in the execution of his duty, that too must be proved and not assumed. Verify the current text, and take advice on your own facts, before acting.