No single count applies to every Seattle event. The City's restroom guidance sets out the principles, and the operator works out the count from the expected headcount, the length of the event and whether food and alcohol are served. The count is shown on the site map that the Special Events Committee reviews, with its reasons written beside it.
Key takeaways
- No single count applies to every Seattle event, and this page sets no ratio.
- The operator sets the count from peak headcount, event length, food and alcohol.
- The count is shown on the site map that goes into the permit application.
- The units are kept away from business entrances and high-traffic paths.
- Food workers' toilets count only with a handwashing sink beside them, within 200 feet of the serving location.
- Plan extra servicing for a long or hot day, not only extra units.
Why is there no set number?
The City's guidance gives principles and an approach, and the count is worked out for each event from its own facts.
Events differ widely. A street festival with food and beer, a stadium-side approach and a short walk on a Saturday morning are three different problems, and a single figure would be wrong for at least two of them.
This page sets no ratio because none can be stated as a fixed rule for Seattle in the sources it relies on. The count is reached by reasoning and then recorded on the plan.
What inputs set the count?
Four things set the count in practice: the expected peak headcount, the hours, food on site and alcohol. The table shows how each moves the figure.
The peak matters more than the total attendance. A crowd of several thousand over a full day does not all arrive at once, so the count is set for the busiest hour at each cluster.
Hours matter because use accumulates. A four-hour event and a twelve-hour event with the same peak need different servicing, and the longer one usually needs more units.
| Input | Effect on the count |
|---|---|
| Expected peak headcount | Sets the busiest cluster's units |
| Event length | Sets the servicing visits and any spare units |
| Food on site | Raises use and brings the handwashing rule |
| Alcohol served | Raises use and an extra visit |
| Cool or wet weather | Changes the use pattern and the pad |
How should the units be split across the grounds?
In clusters at each main gathering point, sized to the people who stop there, and kept away from business entrances and the high-traffic path.
A single cluster at the gate leaves the far end of the grounds without a unit close by. Each stage, food area and gathering point gets a cluster sized for its crowd.
The business-entrance and high-traffic rules keep the clusters off the doors and the main path, so they sit on the side routes with a short walk.
- One cluster at each main gate
- One cluster beside each stage or viewing area
- One cluster at each food area, with a handwashing sink
- Clusters on side routes, off the main path
- Accessible units spread across the grounds
How does a long or hot day change the count?
It needs more frequent servicing and sometimes spare units. Adding units alone does not fix a slow schedule.
Warm days speed the filling of units. The plan sets an extra visit for the hottest part of the day, and the provider is told the expected conditions.
A long evening event needs the units lit and checked before dark, and the visit before the evening crowd is the one most often missed.
How is the count checked afterwards?
Compare the servicing log with the plan, and record where units ran short or stood empty.
The check looks at the times units were full, the late visits and the clusters with the most use. A cluster that ran short is the clearest lesson for the next event.
A short written note goes into the event file, which helps the next organizer and answers questions if the event is held again.
What goes in the file?
The count and its reasons, the site map, the accessible units, the servicing plan and, for food areas, the handwashing sinks.
The Special Events Committee reviews the site map as part of the application. The map shows the units, the accessible routes and the handwashing, with the count per cluster.
The provider supplies the unit details, and the organizer includes them in the filed plan.
How do you handle a crowd that is hard to predict?
Plan a range rather than one number, set the count for the upper end at the busiest cluster, and agree a fast way to add units during the event.
Past attendance, the venue's capacity and the time of year are the best starting points. Where none is known, the plan says so and shows how the count would change if the crowd is larger.
A standby arrangement with the provider, with a call-out for extra units or an extra visit, is a practical answer to an uncertain crowd, and it is written into the plan.
What if the event spans more than one space?
Each space is counted on its own, with its own clusters and accessible units, and the total is the sum of the spaces. Each space's permit route is checked against the plan.
A festival that uses a park, a closed street and a plaza has three counts and three routes. The plan shows each and keeps them distinct.
A crowd that moves between the spaces is planned for the walk between them, so no cluster is left without a nearby alternative.
How is the count checked after the event?
Compare the servicing log with the planned count, and record where units ran short or stood empty, with the reasons.
The check looks at the times units were full, the late visits and the clusters with the most use. A cluster that ran short is the clearest lesson for the next event.
A short written note goes into the event file, which helps the next organizer and answers questions if the event is held again.
How do you set the count for a first-time event?
A first-time event has no past log, so the count is set from comparable events, the organizer's written estimate and a range that is checked during the first hours of the event.
Comparable events in the city give a starting pattern. The organizer's estimate is recorded with its basis, and the count is set for the upper end of the range at the busiest cluster.
During the first hours the stewards count the queues and report them, and the provider adds units or a visit if the queues are longer than the plan allows. The first hours are the test of the count.
Why is the peak count used and not the average?
A cluster sized for the average is empty for much of the day and overwhelmed for an hour, which is the worst result for the people who arrive in that hour.
The peak is when a queue forms and a person waits, so the count is set for it at each cluster. The average says little about the experience of the people in the queue.
The average is still useful, since it sets the servicing schedule between peaks, showing how often the units need emptying.
How do you count the units for a route event?
A route event counts its clusters at each stop, with the stop's expected crowd and the time the crowd waits, and the total is the sum of the stops.
A stop where the crowd waits for an hour needs more units than a stop people pass through. The organizer writes the expected crowd beside each stop.
The finish area is the busiest point, and it usually needs the largest cluster on the route, sized for the runners as well as the spectators.
Frequently asked questions
Does Seattle set a units-per-guest ratio?
No ratio is set as a fixed rule in the sources this page relies on, so none is stated here. The count is set for each event.
What is the most important input?
The expected peak headcount, because the busiest hour sets the cluster size.
Should I add spare units?
A spare count is reasonable for a large event, and extra visits often do more than extra units.
Where must the units appear?
On the site map in the permit application, which the Special Events Committee reviews.
What if the crowd is bigger than planned?
Call the provider to add units or a visit, and report any change to the approved layout.
Who decides the count?
The organizer, with the provider, and the committee checks it against the plan.
Sources
- City of Seattle, Special Events Office, Restroom Facilities guidance
- City of Seattle, Special Events Office, Food Service guidance
- City of Seattle, Seattle Parks and Recreation
This guide is general information for King County homeowners, not a substitute for an on-site inspection. Prices are estimates. See our disclaimer.