Planning framework
01Start with the organizer, not the forecast
Open the event's current official page before relying on a weather app. Look for the exact wording: cancelled, postponed, held in rain, partially changed, ticket-only change or still undecided. Each organizer can use a different rule, so do not apply one festival's rain policy to another event.
02Use JMA for safety signals, not event status
JMA warnings, advisories, bulletins and emergency warnings are safety information. They help you decide whether travel and outdoor waiting are appropriate, but they do not by themselves prove that a specific event has been cancelled. Pair JMA information with the event organizer's own update.
03Read the update time and affected area
Before leaving, check when the organizer last updated the notice, which date or program it covers, whether only one venue side is affected and whether tickets, seats or refunds are mentioned. If the current page does not answer a point, keep it unknown instead of filling the gap from past years.
04Choose between go, wait and fallback
Use three separate decisions. First, is there an official safety warning or transport issue that changes your risk level? Second, has the organizer confirmed the event operation? Third, is the experience still worth the rain, standing time and exit crowd for your group? If any answer is unclear, wait for a newer official update or switch to a nearby fallback.
05Keep the fallback near the original route
A useful rain plan is close enough to use without crossing the whole city. For Tokyo, Kyoto or Osaka, choose an indoor or sheltered option near the original event area, then remove optional stops before you change the anchor. Treat the fallback as your own planning choice, not an official substitute for the event.
06Protect the return route
Major events may publish road restrictions, one-way pedestrian controls, station guidance or post-event crowd cautions. Save an official access page and an operator status page before entering the crowd. Do not assume the nearest station, fastest route or normal timetable will be the best exit after heavy rain or a large event.
Decision checklist
Keep official facts, safety signals and personal comfort decisions separate before changing plans.
Organizer update
Have you checked the current official event page or announcement, including the update time?
Exact rain wording
Does the source say cancelled, postponed, held in rain, partly changed or still undecided?
JMA safety signal
Are JMA warnings, advisories, bulletins or emergency warnings affecting your event area or travel route?
Transport page
Have you checked the relevant railway, subway, bus or event access page rather than assuming the normal route?
Ticket or refund dependency
Does your plan depend on a ticket, reserved seat, refund, exchange or timed entry that the official source actually confirms?
Nearby fallback
Is there a nearby indoor or sheltered fallback that keeps you in the same city area if the event becomes uncomfortable or unclear?
Common planning scenarios
Fireworks with severe-weather wording
Check the organizer's cancellation or postponement rule first. Itabashi 2026 is a useful example because the official site states severe-weather cancellation with no postponement, while its access pages also define viewing-area and station constraints.
Procession or street festival with a morning decision
For an outdoor procession, look for whether rain postponement exists and when the decision is made. Kyoto's Jidai Matsuri page states rain postponement with an early-morning same-day judgment, so visitors should avoid treating the procession as fixed before that update.
Crowded riverside event
For fireworks or riverside festivals, cancellation wording is only one part of the decision. Sumida's official pages also warn about no place-saving, pedestrian one-way controls, walking-style viewing and very heavy post-event crowds.
Indoor event with outdoor transfer risk
A ticketed indoor event may still run while rain or transport changes make access harder. Separate the ticket condition, queue or program update and transport status before deciding whether to continue.