top of page
Search

Karnataka's Crowd Control Bill 2025: What India's First Crowd Safety Law Means for Event Organisers

Writer: nitin virat
nitin virat
3 days ago
16 min read

Published by: Crowd Management India


Last updated: October 2026


Reading time: Approximately 12 minutes


Key facts

  • The Karnataka Crowd Control (Managing Crowd at Events and Place of Gathering) Bill, 2025 (LA Bill No. 63 of 2025) is India's first dedicated crowd safety legislation at the state level

  • The Bill was introduced in the Karnataka Legislative Assembly in August 2025 and referred to an 11-member Select Committee in September 2025 — legislative status should be verified at karnataka.gov.in before citing as enacted law

  • The Bill requires permission for any event expecting 5,000 or more attendees, with tiered approval thresholds based on crowd size

  • Penalties under the Bill include three to seven years imprisonment for negligence causing harm, escalating to life imprisonment where negligence results in fatalities

  • Fines of up to ₹1 crore are prescribed for violations; organisers are also held financially liable for compensation to victims

  • The Bill was triggered directly by the Bengaluru M. Chinnaswamy Stadium crowd crush of 4 June 2025, which killed 11 people during RCB's IPL victory celebration

  • Private family events such as weddings are explicitly exempted from the Bill's provisions

A note on legislative status

Before proceeding, one clarification is essential for professional accuracy.

Multiple news sources — including The Logical Indian — have reported that the Karnataka Crowd Control Bill "passed" the Assembly. The more authoritative PRS India legislative brief, which analyses the Bill text directly (Bill No. 63 of 2025, sourced from the Karnataka Legislative Assembly), confirms that the Bill was introduced in August 2025 and referred to an 11-member Select Committee chaired by Home Minister G. Parameshwara in September 2025 for detailed scrutiny.

A bill referred to a Select Committee has not yet been enacted as law. It remains under legislative examination.

This platform will update this post when the Bill's final status — whether passed, amended, or lapsed — is confirmed through the Karnataka Gazette or the official Karnataka Legislature records at karnataka.gov.in.

For the purpose of this analysis, the Bill's provisions as introduced are discussed in full, as they represent the most significant legislative development in Indian crowd safety in decades — regardless of their final form.

Introduction

On 4 June 2025, approximately 200,000 people gathered outside M. Chinnaswamy Stadium in Bengaluru to celebrate Royal Challengers Bangalore's maiden IPL title. The stadium holds 35,000. The event was not planned, had no crowd management infrastructure, and had no standard operating procedure. Eleven people died. The Karnataka government acknowledged this in the Karnataka High Court.

Two months later, the Karnataka Cabinet introduced the Karnataka Crowd Control (Managing Crowd at Events and Place of Gathering) Bill, 2025 — India's first standalone legislation specifically designed to assign legal liability for crowd safety to event organisers. It is the most significant regulatory development in Indian crowd safety since NDMA issued its crowd management framework.

Whether this Bill becomes law in its current form, is amended by the Select Committee, or serves as the template for similar legislation in other states, its provisions define what a crowd safety legal framework for India should look like. Every event organiser, venue manager, government official, and architect working in India should understand it.

What triggered the Bill: the Chinnaswamy Stadium crowd crush

The Bill's Statement of Objects and Reasons is explicit: it was brought in response to the Bengaluru crowd crush of 4 June 2025.

The facts of the incident, as acknowledged in Karnataka High Court proceedings: approximately 200,000 people gathered for an unplanned public celebration outside a stadium designed for 35,000. No crowd management plan existed. No standard operating procedure governed the event. Eleven people were killed and 33 to 56 people were injured — figures vary across sources, with 11 deaths consistently confirmed and the Karnataka High Court acknowledging the government's own statement that the event was conducted without an SOP.

Home Minister G. Parameshwara, piloting the Bill in the Assembly, described the Chinnaswamy crush as a "wake-up call." The legislative objective was to close the accountability gap that the incident exposed: the absence of any law that required, before the event, a crowd management plan — and assigned criminal liability to the organiser if that gap contributed to deaths.

The Bill's key provisions: what it requires

Who needs permission

The Bill defines a "crowd" as a group of 5,000 or more people gathered for a common purpose. Any person or organisation intending to hold an event that will attract 5,000 or more attendees must obtain permission from the relevant police authority before the event takes place.

The permission application must be submitted at least 10 days before the event. Events arranged at short notice — without the 10-day advance window — will not be granted permission.

Tiered approval authority

The Bill establishes a tiered system of approval authority based on expected crowd size:

Expected attendance

Approving authority

Below 7,000

Officer-in-charge of the local Police Station

7,000 to 50,000

District Superintendent of Police or Deputy Commissioner of Police

Above 50,000

Commissioner of Police or Inspector General of Police

This tiered architecture is significant. It recognises that larger gatherings carry proportionally greater risk and require proportionally higher-level oversight. It also creates a bureaucratic escalation path that distributes accountability for crowd safety assessment across multiple levels of the police hierarchy.

What organisers must provide

The Bill requires organisers to provide detailed safety and crowd management plans as part of the permission application. Organisers are responsible for:

  • Ensuring smooth movement of the crowd inside and outside the event

  • Ensuring compliance with the crowd management (bandobast) scheme

  • Providing for adequate crowd dispersal at the conclusion of the event

  • Not barring or restricting police and administrative officials from carrying out their duties at the venue

This last provision directly addresses the Hathras pattern — where organising committee members actively prevented police and administrative officials from exercising oversight.

Powers of authorities during the event

Police authorities under the Bill are empowered to:

  • Monitor compliance with the crowd management plan in real time

  • Cancel, postpone, or modify events if risks to public safety increase

  • Issue on-the-spot instructions to organisers and volunteers

  • Take any measures to control the crowd or mass gathering that the authority deems fit

Failure to comply with on-the-spot police instructions is itself a punishable offence under the Bill.


The indemnity bond

For events where more than 50,000 people are expected, organisers must furnish an indemnity bond. The quantum of the bond is not specified in the publicly available bill text as a fixed figure — the ₹1 crore figure widely reported in media derives from earlier drafts and media coverage of Cabinet deliberations. The PRS India analysis confirms an indemnity bond requirement but does not specify the amount as fixed in the tabled Bill text.


Compensation liability

The Bill holds organisers financially liable for compensation to victims or their families in the event of crowd disasters. If organisers fail to pay compensation, the government is empowered to recover the amount as land revenue dues — including by auctioning the organiser's property if necessary.

This is the most significant departure from prior Indian practice in crowd safety liability. It creates a civil liability mechanism that operates independently of criminal proceedings. An event organiser faces not only potential imprisonment but also mandatory financial compensation obligations — recoverable through the same mechanisms used to collect government dues.


Penalties

The Bill's penal provisions are graduated by severity:

For disobeying police orders or violating the Act's general provisions: Up to three years' imprisonment, a fine of ₹5,000, or both.

For organising unpermitted events: Imprisonment of three to seven years, a fine of up to ₹1 crore, or both.

For negligence resulting in harm: Three to seven years' imprisonment.

For negligence resulting in fatalities: Life imprisonment.

The life imprisonment provision is the headline figure and it is what distinguishes this legislation from any prior Indian crowd safety regulation. It signals that the state legislature views crowd safety negligence resulting in deaths as a category of offence comparable in severity to culpable homicide — not an administrative oversight subject to a nominal fine.


Offences related to misinformation

The Bill also creates offences for spreading false information in the context of crowd management — recognising that rumour-triggered surges (as at Naina Devi 2008 and Ratangarh 2013) are a documented mechanism of crowd disaster causation. This provision has no precedent in Indian event regulation.

What is exempted

Private family events — weddings and similar functions conducted within private premises — are explicitly exempted from the Bill's provisions. The exemption applies to events held within private places, not to large-scale events at private venues open to ticketed attendees.


What the Bill gets right

From a crowd management professional perspective, several aspects of the Bill reflect sound understanding of how crowd disasters occur and what legal architecture can prevent them.

Placing liability with the organiser

The most important structural feature of the Bill is that it places crowd safety liability where it belongs: with the person or organisation that decided to hold the event, set the attendance expectation, applied for permission, and controlled the operations on the day.

Prior to this Bill, the Indian legal framework offered no clear mechanism to hold an event organiser specifically liable for crowd safety failures. The Hathras crush — where the principal organiser received a clean chit from both the SIT and the Judicial Commission — illustrated how the accountability gap operated in practice under general criminal law.

The Karnataka Bill closes this gap directly. The organiser is now the named party with specific obligations, specific liabilities, and specific penalties.

The 10-day advance requirement

The 10-day advance application period is a crowd management planning requirement disguised as an administrative timeline. It creates a mandatory window during which the crowd management plan must exist on paper before the event takes place — making it impossible for an organiser to claim, after a disaster, that there was insufficient time to plan.

It also creates an administrative record: the application, the plan, and the permission or refusal. This record is the evidentiary foundation for any subsequent accountability proceeding.

The no-SOP prohibition on police barring

The explicit prohibition on organisers preventing police and administrative officials from exercising oversight addresses a documented pattern in Indian crowd disasters. At Hathras, the organising committee actively kept police away from event operations. At multiple other events, the presence of police has been treated as an intrusion rather than a safety function. The Bill makes this exclusion itself a criminal act.

The compensation recovery mechanism

The ability to recover compensation as land revenue dues — bypassing the often-lengthy process of civil litigation — gives the compensation obligation practical enforceability. An organiser who faces bankruptcy as a consequence of compensation liability has a structural incentive that no fine or imprisonment threat alone provides.

What the Bill leaves unresolved

A crowd management professional reading the Bill identifies several gaps that the Select Committee review should address.

No technical standard for what a "crowd management plan" must contain

The Bill requires a crowd management plan. It does not specify what a qualifying crowd management plan must contain, who is qualified to prepare one, or what technical standards it must meet.

A document titled "crowd management plan" that consists of a head count and a list of security personnel is not the same as a plan that includes pedestrian flow simulation, occupancy load analysis, Level of Service assessment, egress capacity calculation, and emergency evacuation scenario modelling. The Bill, as introduced, cannot distinguish between the two.

This is the most significant technical gap in the legislation. Without a prescribed technical standard, the permission process will evaluate crowd management plans on the basis of their existence — not their quality. A plan can be submitted, a disaster can follow, and the organiser can argue that a plan was provided and approved. The accountability intended by the Bill cannot function without a technical benchmark against which plans are assessed.

The permission thresholds are headcount triggers, not density standards

The tiered permission thresholds (below 7,000, 7,000 to 50,000, above 50,000) are based on the number of expected attendees — not on the density conditions that number will create in the specific venue.

A crowd of 7,000 people in a purpose-built stadium with wide concourses and multiple egress routes is fundamentally different from 7,000 people channelled through a 3-metre temple approach path. The density — and therefore the risk — is entirely different. Headcount thresholds without corresponding spatial assessment create a regulatory architecture that can approve genuinely dangerous events while declining low-risk ones, based on the accident of the venue's capacity.

The international best practice is to tie permission requirements to the ratio of attendance to effective pedestrian area — the density assessment — rather than to absolute headcount.

No requirement for venue inspection before permission

The Hathras Judicial Commission found that permission was granted without any physical inspection of the venue. The Karnataka Bill, as introduced, does not explicitly require a physical inspection of the event venue as a condition of permission. The Select Committee review should consider whether a site inspection by the approving authority — or by a qualified crowd safety professional on their behalf — should be mandatory for events above a specified size threshold.

What this means for event organisers in Karnataka

If the Bill is enacted in its current or similar form, the practical implications for event organisers in Karnataka are direct:

For any event expecting 5,000 or more attendees:

  • You need police permission — apply at least 10 days in advance

  • You need a crowd management plan as part of the application

  • You cannot bar police or administrative officials from the event

  • You are financially liable for compensation to any victims of a crowd disaster at your event

For events expecting more than 50,000 attendees:

  • Permission must come from the Commissioner of Police or Inspector General

  • An indemnity bond is required

  • The bar for negligence is explicit: if people die at your event due to your negligence, you face life imprisonment

For all commercial event organisers: The calculation of event viability in Karnataka now includes crowd safety liability as a direct cost. Insurance underwriting for events will need to account for this liability. Organisers who have not previously engaged crowd management professionals will need to do so — not because they want to, but because a crowd management plan is now a prerequisite for permission.

What this means for other Indian states

Karnataka's Bill is the first. It will not be the last.

The Bengaluru crush, the Hathras crush, the New Delhi Railway Station crush, and the Maha Kumbh Mela crush all occurred within a 12-month period in 2024–25. The political and public pressure for regulatory action at the state level is real and is being felt across multiple state governments.

The Karnataka Bill provides a legislative template. States that follow will have a draft to work from. The Select Committee process may produce a refined version that becomes the model for national-level legislation.

The question for event organisers, venue managers, and government officials in every other state is not whether crowd safety legislation is coming to their jurisdiction — it is when, and whether they will be compliant when it arrives.

The NDMA guidelines (March 2025) and the BPR&D guidelines (June 2025) are national-level frameworks. They are advisory, not statutory. They describe what good crowd management practice looks like. The Karnataka Bill describes what the legal consequences of ignoring it are. As state-level legislation develops, the advisory and the statutory will converge.

International context: how Karnataka's approach compares

Karnataka's Bill is broadly consistent with the legislative architecture of crowd safety laws in jurisdictions that have enacted them — though it goes further in some respects.

United Kingdom: The Health and Safety at Work etc. Act 1974 and associated regulations create general duties on event organisers for the safety of persons at events. The Safety of Sports Grounds Act 1975 and the Fire Safety and Safety of Places of Sport Act 1987 create specific requirements for designated venues. The UK framework is general safety law applied to events — not dedicated crowd safety legislation.

Germany: German states regulate crowd safety through general assembly law (Versammlungsgesetz) and building regulations. There is no dedicated federal crowd safety statute.

India — Karnataka Bill: By creating a dedicated statute with specific crowd management obligations, tiered permission architecture, and explicit criminal penalties including life imprisonment for fatal negligence, the Karnataka Bill is more specific and more prescriptive than most comparable international frameworks in its stated scope.

The gap between Karnataka's stated legislative ambition and the practical implementation — which depends on having qualified crowd safety reviewers to assess the plans that will be submitted — is where the challenge lies.

Key takeaways

  • The Karnataka Crowd Control Bill 2025 is India's first dedicated crowd safety legislation. Its status should be verified at karnataka.gov.in — as of this writing it was under Select Committee review.

  • The Bill's most significant features are: mandatory permission for events of 5,000 or more, 10-day advance application, organiser liability for compensation, and life imprisonment for fatal negligence.

  • The Bill places crowd safety liability where it belongs — with the event organiser — and creates a financial compensation mechanism recoverable as land revenue dues.

  • The Bill's most significant technical gap is the absence of a prescribed technical standard for what a qualifying crowd management plan must contain. Without this, the accountability it intends cannot fully function.

  • Event organisers in Karnataka should engage crowd management professionals now — not only to comply with the Bill's permission requirements, but to demonstrate the quality of planning that distinguishes a defensible plan from a paper exercise.

  • Every state government in India should treat the Karnataka Bill as the opening of a legislative conversation that will reach them. The question is when, not if.

Frequently asked questions

What is the Karnataka Crowd Control Bill 2025? The Karnataka Crowd Control (Managing Crowd at Events and Place of Gathering) Bill, 2025 (LA Bill No. 63 of 2025) is a legislative proposal introduced in the Karnataka Assembly in August 2025. It is India's first dedicated crowd safety legislation at the state level. It requires permission for events expecting 5,000 or more attendees, mandates crowd management plans, assigns civil and criminal liability to event organisers for crowd safety failures, and prescribes penalties including life imprisonment for negligence resulting in fatalities. As of October 2026, verify its current legislative status at karnataka.gov.in.

What triggered the Karnataka Crowd Control Bill? The Bill was directly triggered by the crowd crush outside M. Chinnaswamy Stadium in Bengaluru on 4 June 2025, in which 11 people were killed during an unplanned public celebration of RCB's IPL title win. The Karnataka government acknowledged in the Karnataka High Court that the event was conducted without any standard operating procedure. Home Minister G. Parameshwara described the incident as a "wake-up call" when introducing the Bill.

Who needs permission under the Karnataka Crowd Control Bill? Any person or organisation intending to hold an event that will attract 5,000 or more attendees needs permission from the relevant police authority. Permission must be applied for at least 10 days before the event. The approving authority is tiered by crowd size: local police for below 7,000, District SP or DCP for 7,000 to 50,000, and Commissioner or IGP for above 50,000.

What are the penalties under the Karnataka Crowd Control Bill? Penalties are graduated by severity. Disobeying police orders or violating general provisions carries up to three years' imprisonment and/or a fine. Organising an unpermitted event carries three to seven years' imprisonment and/or a fine of up to ₹1 crore. Negligence resulting in harm carries three to seven years. Negligence resulting in fatalities carries life imprisonment. Organisers are also financially liable for compensation to victims, recoverable as land revenue dues.

Does the Karnataka Crowd Control Bill apply across India? No. The Bill is a state-level piece of legislation applicable only within Karnataka. No equivalent national law or comparable state law exists in any other Indian state as of October 2026. NDMA's crowd management guidelines (March 2025) and BPR&D's guidelines (June 2025) apply nationally but are advisory, not statutory.

Are weddings and private events covered by the Karnataka Crowd Control Bill? No. The Bill explicitly exempts private family functions — such as weddings — conducted within private premises. The Bill applies to public events and commercial gatherings expecting 5,000 or more attendees.

What should event organisers outside Karnataka do in response to this Bill? Track the Bill's progress through the Select Committee and its eventual enactment or amendment — this is the legislative template that other states will follow. Begin developing the internal processes required for compliance: crowd management plan preparation, venue capacity assessment, and engagement with crowd safety professionals. An event organiser who has never prepared a crowd management plan will find it significantly harder to do so under legislative time pressure than to develop that capability proactively.

What is missing from the Karnataka Crowd Control Bill? The most significant gap is the absence of a technical standard specifying what a qualifying crowd management plan must contain. Without this, the Bill requires the existence of a plan but cannot enforce its quality. A second gap is that the permission thresholds are based on headcount rather than the density conditions that headcount creates in the specific venue. The Select Committee review provides an opportunity to address both gaps.

Sources and references

  1. PRS India — "The Karnataka Crowd Control (Managing Crowd at Events and Place of Gathering) Bill, 2025" — legislative brief and Bill analysis — prsindia.org — primary source for Bill provisions

  2. Karnataka Legislative Assembly — LA Bill No. 63 of 2025 — Bill text PDF — prsindia.org/files/bills_acts/bills_states/karnataka/2025/Bill63of2025KA.pdf

  3. The Week / PTI (21 August 2025). "Karnataka Assembly Crowd Control Bill referred to house committee for scrutiny." — theweek.in

  4. The Week / PTI (23 September 2025). "Speaker constitutes 11-member committee of MLAs to scrutinise crowd control Bill." — theweek.in

  5. The Logical Indian (August 2025). "Karnataka Passes India's First Crowd Control Bill, Months After Bengaluru Stampede That Killed 11." — thelogicalindian.com — note: headline uses "passed"; PRS confirms Select Committee referral

  6. Bar and Bench (June 2025). Karnataka Crowd Control Bill — earlier draft (Cabinet version, June 2025) — barandbench.com

  7. BoomLive (June 2025). "3 Years Jail, Rs 5 Lakh Fine: Karnataka's Crowd Control Bill After Bengaluru Stampede." — boomlive.in

  8. NDMA (March 2025). Managing Crowds: Guidelines for Events and Venues of Mass Gathering. ndma.gov.in

  9. BPR&D (June 2025). Comprehensive Guidelines on Crowd Control and Mass Gathering Management. bprd.nic.in

  10. Crowd Management India — "Crowd Disasters in India: A Complete History (1954–2025)" — for Chinnaswamy Stadium incident context

Legislative status note: The provisions described in this article reflect the Bill as introduced (LA Bill No. 63 of 2025) and publicly available Select Committee information. The Bill may have been amended or enacted since this article was last updated. Always verify current status at karnataka.gov.in or through the PRS India legislative tracker at prsindia.org before citing this legislation in professional or legal contexts. Last updated October 2026.

Published articles on Crowd Management India:

  • Crowd Disasters in India: A Complete History (1954–2025)

  • The Hathras Crowd Crush 2024: What the Official Inquiry Reveals

  • What Is Crowd Management? A Complete Guide

  • Crowd Density and Level of Service: The Science Behind Safe Crowd Management

  • What Causes a Crowd Crush? The Science That Explains Why People Die Standing Still

Content

Crowd management India Alright, as you are aware, I am a people movement consultant with an expertise in advising about space planning, and evacuation planning with a special focus on people, movement and people comfort. Crowd management is also a part of people movement, or I can say people moveme

pasted

Step 2 — Add the first module Just like before — click the + button, search for Anthropic Claude, select it, choose Create a Message (Prompt), and select your existing CMI-Claude connection. No need to create a new connection — it is already saved. Do not fill in any settings yet — just click OK t

I'll research current, verifiable information before drafting. Let me run searches across several relevant topics simultaneously. I now have sufficient verified information to draft the post. I'll focus on the Regulatory and Legal Landscape pillar — the most timely given Karnataka's landmark le

pasted

Get a Document.

Press Enter in the browser. You should see Accepted.

5. Press Enter — it should say Accepted this time

Now approve

The Poster agent checks every 15 minutes automatically.

Karnataka's Crowd Control (Managing Crowd at Events and Venues of Mass Gathering) Act, 2025 is India's first standalone legislation placing legal liability for crowd safety directly on event organisers. It took 11 deaths outside Chinnaswamy Stadium on 4 June 2025 to produce it. The Act establis

pasted

When you receive the approval email, the Google Doc contains a detailed Visual Brief. Open Adobe Express, open your CMI template, apply the brief — it takes 5–8 minutes. Download as PNG.

Also fix the same issue in your Writer Agent — go to that Claude module and check the User message field. If it also has a hardcoded date, replace it with the same formula:

Go into your LinkedIn Image Post module and change the action — delete this module and replace it with the original Create a Company Text Post module temporarily. This tells us whether the issue is with the image or with LinkedIn itself.

last run → Operation 1 →

Then in the LinkedIn module, change the Text field to map from Text Parser 6 → $1

[POST] 𝗥𝗮𝘁𝗵 𝗬𝗮𝘁𝗿𝗮 𝟮𝟬𝟮𝟲 is seven weeks away. Up to two million devotees. One 2.5-kilometre road. A crowd that, during chariot pulling, routinely exceeds the surveyed capacity of Bada Danda by a factor of two. This is not a security problem. It is a pedestrian flow problem — and the d

pasted

Step 3 — Add the incident table: This is the most important part. In Wix, click Add Elements → search for Table or look under Interactive → Table. Add a table with 6 columns: Year | Incident | Location | Deaths | Primary Cause | Source Confidence Then add these rows one by one from your content d

 
 
 

Recent Posts

See All

Comments


+91 99534 73011

Crowd Management India
crowdmanagementindia.com
crowdmanagementindia@gmail.com

Munirka Enclave, New Delhi, 110067

bottom of page