Crowd Crush Hazard Calculator
What the crowd-crush screening score measures
A crowd crush can develop when too many people are compressed into too little usable space and exits or walking routes cannot relieve that pressure quickly enough. This calculator is a rapid screening model for that type of venue situation. It does not simulate individual people or reproduce a site-specific evacuation study. Instead, it combines planning inputs that can be estimated early: people present, usable area, movement intensity, exit count, clear exit width, and the time available to clear the space. The result is a probability-like hazard percentage and a plain-language risk band.
This crowd-pressure screen can help with early layout decisions, tabletop exercises, and comparisons between operational scenarios. It can reveal whether peak occupancy, constrained egress, or an aggressive clearing target is driving the result. It is not a legal sign-off, an occupancy approval, or a substitute for a qualified crowd-management review. Treat it as a warning signal that prompts more careful questions before an event, rather than as a promise that a venue is safe.
Crush hazard is rarely determined by one measurement alone. A given density may be more manageable when movement is orderly, sightlines are clear, and egress has margin. The same density can become much more hazardous when a surge begins, opposing flows meet, or the area must clear too quickly. The sections below connect the calculator's inputs to those crowd-management concerns.
Crowd and egress inputs used in the hazard model
Crowd size is the number of people who may occupy the usable area at once. For crowd-crush planning, use the realistic peak in the zone being assessed, rather than total event attendance unless everyone can occupy that same space. For a forecourt, queue pen, stair landing, or fan zone, enter the people who could actually be present together. Underestimating this number can make the screening result falsely reassuring.
Usable area is space that people can genuinely occupy and move through during the scenario. It is not the gross venue footprint. Exclude stages, barriers, furniture, concession islands, planter boxes, camera platforms, closed corners, and no-standing areas. A wide space upstream does not eliminate a local narrowing or choke point. Because the calculator accepts one area figure, it is most useful when that figure reflects effective crowd space rather than architectural area.
Average crowd speed represents movement intensity in this model. A higher value is not automatically evidence of a comfortable or efficient crowd as it might be on an open walkway. In constrained conditions, compressed groups can display stop-start motion and surges while becoming less controllable. The calculation therefore treats speed as a contributor to the hazard score, not as a measure of crowd comfort.
Number of exits affects total egress width, but count alone is incomplete. Several narrow or obstructed exits are not equivalent to generous, visible routes. This simplified model treats the exits as broadly comparable. If one exit is substantially less useful than the others, use an effective arrangement that reflects the actual operating condition rather than an ideal architectural count.
Exit width is particularly important because the script multiplies the number of exits by the width value to estimate total exit capacity. Enter the average clear width of one exit, not the total width across every exit. If you know only the combined clear width, divide it by the number of exits before using this field. That interpretation prevents the model from double-counting capacity.
Desired evacuation time is the target number of minutes available to clear the crowd. A shorter target requires more people to pass through the exits each minute, increasing required flow and normally increasing the hazard score. Use the operational time you are assessing, not an optimistic result from an empty drill. Delays, hesitation, counterflow, and individual variation can make an optimistic clearing time unrealistic during a live event.
The starting values in the form are only a test scenario. They are not occupancy limits, design recommendations, or emergency-planning guidance. Replace them with assumptions for the crowd and space you are reviewing.
The crowd-density and exit-flow calculation
The crowd-crush model converts the inputs into density, total exit width, estimated exit capacity, and required evacuation flow. Density is people per usable square meter. Exit capacity is estimated from total clear exit width, while required flow is the number of people per minute needed to meet the selected evacuation time. Those components form a score, and a logistic curve maps that score to a value between 0 and 1 for display as a probability-like hazard percentage.
These are the relationships implemented by the calculator script.
In crowd-safety terms, the score rises when people are packed more tightly, when the exits must process a larger share of the crowd per minute, or when movement intensity is higher. The 82 people-per-minute-per-meter figure is a built-in capacity assumption, not a site-specific guarantee. Turns, steps, poor visibility, screening, hesitation, or opposing flows can lower actual discharge performance. Crowd composition, weather, and management also affect what can happen in practice.
The score is deliberately transparent: density is scaled by 5 people per square meter, required flow is compared directly with estimated exit capacity, and speed is scaled by 1.5 meters per second. Check that a change in an input moves the result in a physically sensible direction. For example, increasing usable space should lower density, while reducing evacuation time should increase the flow demanded of the exits.
Worked crowd-crush scenario from the starting values
Consider a fenced fan zone with 2,500 people, 500 square meters of usable area, an average crowd speed of 0.85 meters per second, 4 exits, an average clear width of 1.8 meters per exit, and an 8-minute target evacuation time.
Its crowd density is 2,500 divided by 500, or 5.0 people per square meter. That leaves limited room for people to adjust position and is an important warning condition in this simplified model.
Total clear exit width is 4 multiplied by 1.8, giving 7.2 meters. At the model's 82 people-per-minute-per-meter assumption, estimated exit capacity is 590.4 people per minute.
Clearing 2,500 people in 8 minutes requires 312.5 people per minute. Required flow divided by estimated exit capacity is approximately 0.529, showing the proportion of the modelled exit capacity needed to meet the chosen target.
The three score terms are 5.0 ÷ 5 = 1.0 for density, about 0.529 for required flow, and 0.85 ÷ 1.5 ≈ 0.567 for speed. Their sum is about 2.096. The logistic conversion displays this as an estimated hazard probability of about 64.5%, which is High under the calculator's thresholds.
Do not read that percentage as a literal prediction that a crush will or will not occur. It indicates that this set of assumptions deserves redesign or stronger operational controls. Lower peak occupancy, more effective space, more viable exit width, and a longer credible clearing time all reduce terms in the model. Comparing those options can help identify where the scenario has the least margin.
Comparing crowd-pressure changes
The same crowd scenario can be compared by changing one operational or physical assumption at a time.
| Scenario | Changed assumption | Approximate probability | What it indicates |
|---|---|---|---|
| Baseline | 2,500 people in 500 m², 4 exits at 1.8 m each, 8 minutes | 64.5% | High density and a demanding clearing target produce substantial modelled pressure. |
| More space | Increase usable area to 700 m² | 57.7% | Lower density reduces the score while exit capacity and evacuation timing remain unchanged. |
| Wider exits | Increase each exit to 2.3 m clear width | 61.8% | Additional clear width reduces the share of exit capacity required by the target flow. |
| More time | Allow 12 minutes instead of 8 | 60.3% | A longer target reduces required people-per-minute discharge flow. |
| Lower attendance and more time | Reduce crowd size to 1,500 and allow 12 minutes | 47.0% | Both density and evacuation-flow demand improve, bringing the displayed band to Moderate. |
The direction of the changes is more useful than false precision in the percentages. Stronger crowd-safety plans commonly improve more than one condition: adding usable capacity while managing arrivals, increasing credible egress while avoiding severe density, or staging departures rather than relying on a single rapid release. The calculator makes those tradeoffs visible but cannot identify every bottleneck in a real layout.
Reading a crowd-crush hazard result responsibly
The result box displays an estimated hazard probability and one of four bands: Low, Moderate, High, or Extreme. For this crowd-crush screen, treat the bands as planning urgency rather than legal classifications. High or Extreme indicates that density, evacuation-flow demand, movement intensity, or a combination of them is producing a larger score. Low or Moderate indicates more margin within this limited model, not a guarantee of safe conditions.
When the crowd-hazard result is surprising, verify three things first: whether usable area excludes inaccessible space and obstructions, whether width is entered per exit rather than as combined width, and whether the evacuation time is achievable for the actual audience and event. These assumptions often have more influence than minor arithmetic differences.
A useful crowd-planning workflow is to calculate a baseline, then a credible worse case such as higher occupancy or reduced usable area, followed by an improvement case based on a change that can really be delivered. Opening gates earlier, separating queues, staging departures, reducing occupancy in a constrained zone, or removing an obstruction may be more meaningful than a theoretical adjustment. If the result improves only with unrealistic assumptions, the venue plan may require more substantial review.
Pair the displayed score with local knowledge. Steep steps, downhill movement, alcohol, concealed queue bends, converging barriers, transport unloading, and crowd psychology can all matter. Where those conditions are significant, use a concerning result as a reason to slow down and assess the site more carefully, not as a numerical permission to ignore field conditions.
Limits of this crowd-crush screening model
This crowd-crush calculator intentionally uses a small number of inputs. That keeps it quick and transparent, but its result is approximate. It uses average conditions rather than detailed geometry and does not model individual bottlenecks, stairs, door swing, temporary obstructions, slope, disability access needs, security screening, or the rapid capacity loss that panic and conflicting movement can cause. It captures broad pressure, not every local failure mode.
The calculation also assumes that the stated exit count and clear widths are genuinely available and familiar to the crowd. An exit blocked by merchandise, hidden around a turn, poorly signed, or avoided by attendees is not equivalent to a visible unobstructed route. Likewise, an area total can mislead if people are compressed into one corner while another part of the zone is nominally empty. Where a critical choke point is known, assess that smaller problem area rather than relying only on the full venue footprint.
Crowd safety is operational as well as geometric. Stewarding, communications, queue separation, timed release, barrier layout, and transport coordination can change risk even when these six inputs do not. Use the calculator to surface concerns, compare options, and explain why operational margin is needed. High-stakes decisions should also involve site inspection, emergency planning, and appropriate professional review.
Crowd-crush calculator questions
Does a lower crowd-hazard result mean the venue is safe?
No. A lower result means this simplified screen finds less pressure from the entered density, flow, and movement inputs. Actual safety still depends on layout details, stewarding, signage, weather, crowd mood, queue discipline, transport timing, and whether a surge can form unexpectedly. Use a lower score as evidence that the scenario may have more margin, not as a guarantee.
Why can more exits still leave crowd-crush hazard high?
Additional exits address only the exit-capacity term. If crowd density remains very high or the evacuation target still demands rapid discharge, the score can remain high after capacity improves. The calculator is useful because it shows when one intervention does not address the full crowd-pressure picture.
Why is exit width entered as an average per exit?
The script multiplies exit count by exit width, so the width field must represent one typical exit. Entering combined width in that field would multiply capacity twice and understate the displayed hazard. If the exits vary substantially, use a reasonable average or calculate an equivalent clear width before entering it.
When does a crowd scenario need more detailed review?
Seek more detailed review when the result is High or Extreme, the layout is complex, crowd behaviour may be volatile, or the decision has serious life-safety implications. Detailed crowd-dynamics review, emergency planning, and on-site operational rehearsal are appropriate when failure could have severe consequences.
Crowd pressure relief mini-game
This optional crowd-pressure game turns the calculator's topic into a fast decision challenge. Each square on the venue map is a density zone, blue gates at the top are exits, and red zones are building pressure. Tap or click a hotspot to open a temporary relief corridor and pull people toward the exits before a zone remains overcrowded. The aim is to keep density under the crush threshold for the session. It is not part of the calculator's math, but it illustrates the relationship between local density and discharge capacity.
Why this crowd-pressure game fits the topic: when one corner stays crowded, safety falls rapidly even if the rest of the map looks clear. That mirrors crowd management, where local hotspots and bottlenecks can matter more than the venue-wide average.