Here's a scenario every commuter knows. You check the weather before leaving: partly cloudy, no rain. Twenty minutes into the drive, the sky opens up. Your app wasn't wrong — it just answered a different question. It told you the weather at your home, right now. Your trip happens somewhere else, later.
Weather is local and time-sensitive. A 40-minute commute can pass through two or three distinct weather cells, and the forecast for 8:00 AM at your origin says very little about 8:35 AM at your destination. If you bike, run, or walk part of the way, the difference between "dry when I left" and "soaked at kilometer six" is the whole game.
Why single-point forecasts fail for trips
A standard weather app gives you a point forecast: one location, one time series. Three things get lost:
1. Spatial variation. Rain bands, sea breezes, and elevation changes mean conditions shift over surprisingly short distances. Coastal-to-inland commutes and valley-to-hill routes routinely see different rain and wind within 20 km.
2. Time offset. You don't experience your destination's weather now — you experience it when you arrive. If a front is moving through, the difference between "now" and "in 45 minutes" can be a downpour.
3. Exposure. Ten minutes of drizzle is irrelevant in a car and miserable on a bike. The same forecast means different things depending on how you travel.
The manual method
You can absolutely do this by hand. Here's the routine:
- Break your route into checkpoints. Origin, midpoint(s), destination. For a multi-stop trip (school drop-off, then office), each stop is a checkpoint.
- Estimate your arrival time at each checkpoint. Leaving at 7:45, at school by 8:00, at the office by 8:40.
- Look up the hourly forecast for each checkpoint at its time. Most apps let you search other locations and scrub the hourly timeline.
- Check precipitation probability and amount. A 60% chance of 0.2 mm is a non-event; a 40% chance of 5 mm is a soaking risk.
- Glance at wind if you're on two wheels. A 25 km/h headwind changes a bike commute more than light rain does.
This works. It also takes five to ten minutes, involves two or three apps, and you have to remember to do it every single morning — including the mornings when the forecast changed overnight and yesterday's check is stale.
Rules of thumb while you're checking
- Radar beats forecast for the next hour. If you're leaving within 60 minutes, a live precipitation radar tells you more than an hourly forecast. Watch which way the cells move.
- The gap matters more than the average. Rain often comes in bands. If the radar shows a 30-minute dry gap, shifting departure by 15 minutes can mean arriving dry instead of drenched.
- Trust probability trends, not single values. If the rain probability for your window rose from 30% to 70% between last night and this morning, that trend is the signal.
The automated method
This is exactly the kind of chore software should do. Waycast was built around this one idea: you save a trip once — origin, stops, destination, travel mode, schedule — and it samples the forecast along your actual route at the times you'll be at each point. Before departure it sends you a short briefing: not a wall of numbers, but "Showers likely at drop-off around 8:05 — grab the umbrella" or "Dry window until 9 — leave on time and you'll beat it."
Because trips can recur ("every weekday at 7:45"), the checking happens automatically every day, and you only hear about it when the weather actually changes what you're about to do. If the forecast shifts meaningfully after your briefing, you get one heads-up — no spam.
The free plan covers up to three trips, which is enough for a commute, a school run, and a weekend ride. Set up your first trip — it takes about two minutes, and you can stop doing the five-app morning routine.