An unplanned disruption is a live, unexpected traffic event that has a major impact on traffic flow and lasts for an extended period. As a Waze partner, you can inform drivers of unplanned disruptions by adding them as traffic events in the Waze Map Editor (WME). Explore our short course to learn more about adding road closures and events in Waze.
Before adding an unplanned disruption, make sure it meets the following criteria:
- It's an out-of-the-ordinary, unplanned traffic disruption happening in real time
- It's expected to affect at least 100,000 drivers on impacted or nearby roads
- The resulting traffic impact from the disruption is expected to last longer than 3 hours
Add an unplanned disruption in the WME
-
Create the event
- Log in to the Waze Map Editor
- In the search bar, enter the location of the event
- In the left-side panel, click Events. The panel will expand.
- Click Create event
- In the "Event category" field, select Unplanned disruption
- In the "Impacted area" field, define the affected area. You can do this in 2 ways:
- Option 1: Draw a polygon
- Select "Specific area (recommended)"
- Click Draw on map
- With your mouse pointer, click on the map to start drawing the polygon around the affected area
- Double-click to close the polygon
Note: If the polygon-based event doesn't have closures, once it's submitted, you can't delete the polygon you drew. To edit a polygon's area, click it and adjust the points. Repeat for each adjustment.
- Option 2: Enter coordinates
- Select “Specific area (recommended)”
- Click Insert area coordinates
- Paste the GeoJSON, KML, or WKT polygon string
- Click Create polygon
Note: Defining a polygon is optional if you intend to only associate road closures with the event. For combined events with both known road closures and an overall affected area, it's recommended to map both.
- Option 1: Draw a polygon
- In the "Start of traffic" field, select the current time you're creating the event, even if the event began earlier
- In the "End of traffic" field, enter the predicted end time for when traffic is expected to clear. You can extend or shorten this time later based on real-time changes.
- In the "Event name" field, enter the name for your event in English. Use this format: [Enter location] [Enter type of event]. See detailed guidelines, including examples, here.
- In the "Event description" field, enter a short description of the event. Use this format: [What happened + specific location] [Immediate impact] [What drivers should do] [Other relevant information, if available]. See detailed guidelines, including examples, here.
- If relevant, in the "Translations" field, select the relevant language
- In the "Event name" field, enter the event name in the local language
- In the "Event description" field, enter the event description in the local language
- If available, in the “Event website” field, add a link to official information about the unplanned disruption
- In the top-right corner, click Save
Note: If your unplanned disruption event doesn't involve specific road closures, proceed to step 3: "Submit the event."
-
Associate closures with the unplanned disruption (Optional)
If your unplanned disruption event involves specific road closures, you can associate them with the event. This is especially useful for combined closure and polygon-based events.
- Find the closure’s location. You can either:
- Pan around and find it on the map
- In the search bar, enter the closure's coordinates (recommended)
- Click the relevant segment
- Click the Road Closures tab
- Click Add closure
- In the “Description” field, enter the event name
- In the “Direction” field, select the direction from which the road is closed
- Enter the "Start" and "End" dates and times for the closure
Tip: For closures that are expected to last all day, set the closure times to 00:00 - 23:59 for that specific day. - In the "Event" field, select the unplanned disruption you previously created
- Select or clear the "HOV/Service Road adjacent" option
Tip: If this option is selected, Waze ignores all detected live traffic and won't monitor the closure for real-time changes. Select this option only if the closure is next to an HOV/Service lane where GPS readings may be misunderstood as activity on the closed road. - In the “Closure nodes” field, close or open closure nodes. Closing a node prevents traffic from passing through it in any direction, including cross streets.
Tip: Use this feature sparingly as closing all nodes can lead to blocking valid turn options, preventing Waze from routing drivers through open intersections. - In the “Provided by” field, select your organization
- In the top-right corner, click Save
- Repeat the steps in this section for each closure
- Find the closure’s location. You can either:
-
Submit the event
- Click Events
- Click your event to view the details
- Verify the event details are correct
- Click the Road Closures tab
- Verify the road closures are associated with the event
- Click the General tab
- Click Submit. A pop-up window will appear.
- Click OK
- In the top-right corner, click Save
Submitting the event will create an event webpage, visible at waze.com/events, and will appear in the WME’s event list with a “Ready” status.
Got questions?
What are some examples of unplanned disruptions?
Any type of incident that impacts traffic and falls within the established criteria can be submitted as an unplanned disruption. Here are some examples:
- A collapsed bridge on a major highway
- A large sinkhole opening up on a key arterial road
- An overturned truck or a chemical spill that closes multiple lanes on a highway for several hours
- Widespread flooding in tunnels
What are the general guidelines for naming and describing unplanned disruptions?
When naming and describing unplanned disruptions, please follow these guidelines:
- Be clear and concise: Drivers need to understand the situation quickly, so be as clear as possible
- Use neutral language: Stick to the facts that you want to convey. Avoid any personal opinions, political views, or offensive language.
- Be helpful: Provide information that helps drivers make informed decisions about their routes and drives
- Do: Highway 17 chemical spill
- Don't: Urgent incident on Highway 101 (too vague)
The event description backs up the title. It tells people what happened, where exactly, how it affects traffic, and what they should do.
Best practices for descriptions:
-
Be concise: Provide all necessary information without redundant words or overly complex phrasing
-
Do: Large brush fire near Highway 50 has reduced visibility and created hazardous driving conditions.
-
Don't: There appears to be a substantial vegetation fire in the vicinity of State Route 50, which is currently causing decreased atmospheric clarity and potentially dangerous operational circumstances for motor vehicles.
-
-
Be specific: Always use exact details like street names, exit numbers, or directions when possible
-
Do: Flooding has closed Main St from Oak to Pine.
-
Don't: Flooding has closed Main St.
-
-
Write directly: Use strong, active sentences where the cause of the event is clear. Say who or what is doing the action.
-
Do: The bridge collapsed, closing all lanes.
-
Don't: All lanes were closed due to a bridge collapse.
-
-
Keep it factual: Stick to what's known and observable. Avoid opinions, speculation, or emotional language. Avoid advocating for any particular viewpoint or agenda.
-
Do: Overturned truck on I-5.
-
Don't: Another terrible accident on I-5.
-
Good examples of unplanned disruption descriptions:
-
Example 1:
-
Title: Highway 1 chemical spill
-
Description: A major chemical spill has closed all lanes of Highway 1 southbound near Exit 25. Significant delays expected for at least 4 hours. Avoid the area and seek alternate routes.
-
-
Example 2:
-
Title: Downtown water break
-
Description: A large water main break has flooded several streets in the Manchester city center, causing significant traffic disruptions. Expect delays and road closures in the downtown area. Visit the city website for updates.
-
What happens if I don't add a description?
What should I do if the estimated duration of the disruption changes?
What types of events should not be reported as unplanned disruptions?
Here are some examples of events that should not be reported as unplanned disruptions:
- Minor or common crashes that are expected to clear within 1-2 hours (unless they're blocking a major artery)
- General weather-related driving conditions like fog or heavy rain
- Routine road work or planned maintenance
How are unplanned disruptions different from crisis events?
- Natural disasters such as earthquakes, hurricanes, or major flooding
- Incidents that require large-scale evacuations or sheltering