Every club has the same Saturday morning. You booked the airplane on Tuesday. You drive forty minutes to the field. You pull up the weather in the pilot's lounge and the ceiling is 900 overcast, and you drive home.
Nobody's fault. The booking system did its job. It just had no opinion about the sky.
That gap is what the briefing emails are for. If you booked an airplane, we already know when you're flying, where you're going, and what your own limits are. Sending you a weather brief without being asked is the obvious next move, and it's strange that club software doesn't do it.
What actually shows up in your inbox
Four emails per booked flight: seven days out, three days out, one day out, and the morning of departure.
They are not the same email four times. Seven and three days out, no TAF exists yet, because TAFs only reach about 30 hours ahead. Pretending otherwise would be the worst thing this feature could do. So the early ones are explicitly framed as outlook: here's the pattern to watch, here's today's advisories as a signal, here's what the NOTAMs say about your field. Planning information, labeled as planning information.
The one-day and morning-of emails are the real brief. Those are the ones that change whether you get in the car.
The whole thing follows the FAA's own briefing taxonomy from AIM 7-1-5. A standard briefing inside six hours of departure, an outlook briefing further out, an abbreviated briefing when you're updating one you already had. That's not decoration. It's what a Flight Service briefer would give you, in the order they'd give it.
It forecasts the window, not the moment the email was sent
This one took us a while to get right and it matters more than it sounds.
A briefing sent at 6am that scores conditions at 6am is worse than useless if you fly at 2pm. A gust at send time reads NO-GO for a flight that's fine. Calm at send time reads GO for a departure that has 25 knots forecast.
So the score, your personal-minimums checks, and the crosswind math on the favored runway all run against the forecast for your departure and arrival window. Current conditions still appear, labeled as a right-now reference. When no forecast reaches your flight time, the brief says so plainly and falls back to current conditions rather than inventing confidence it doesn't have.
Your minimums, not somebody's average
Every member sets four numbers: minimum ceiling, minimum visibility, maximum wind, maximum crosswind. The brief checks the forecast against YOUR numbers.
A 400-hour instrument pilot and a 60-hour student get different verdicts off identical weather, which is the entire point. A single club-wide threshold would be wrong for everyone.
Worth saying plainly, because a club treasurer will ask: those four numbers live in their own table and only the member can read them. Not officers. Not admins. Not us. A pilot's honest limits are only honest if nobody is looking over their shoulder when they set them.
What's in the brief
Plain-language narrative first, raw data underneath. METARs and TAFs live from NOAA, never cached into staleness. NOTAMs for departure and destination. Winds aloft. PIREPs. AIRMETs and SIGMETs, scored for whether they actually touch your route and your altitude rather than just existing somewhere in the region.
Present weather gets decoded rather than printed. "BR" becomes mist. "-RA BR" becomes light rain and mist. "+TSRA" becomes heavy thunderstorm with rain. If you've been flying thirty years you don't need that, and you can read the raw group sitting right there. If you soloed in March, you do need it, and having to go look up a two-letter code is exactly the friction that makes people skip the brief.
Convective SIGMETs get the most work, because they're the advisory pilots most want a real answer on. Not "there is convective activity in your region" but where the cell is relative to your route, when it clears, and which side to deviate.
FAA airport diagrams are built in, so an unfamiliar field doesn't mean a separate tab and a PDF hunt.
The part that surprised us
None of this uses AI. It's deterministic templating. Same inputs, same brief, every time, instantly, with no API call and no model deciding what a pilot ought to hear about the weather.
That was a deliberate call and I'd make it again. A briefing is a safety document. It needs to be reproducible, explainable, and identical for the same conditions whether you open it Tuesday or Saturday. "Mostly right, usually" is not a standard that belongs anywhere near a go/no-go call.
What it is not
It's advisory. Every brief says so, and the final authority is the pilot in command, exactly as it has always been.
It doesn't file anything, it doesn't replace your official source, and it isn't trying to. What it does is put a real brief in front of every member of your club before every flight, without anyone having to remember to go get one. Most pilots who skip the weather aren't being reckless. They're busy, and the brief was three clicks away instead of zero.
We moved it to zero.
Why this lives in club software at all
Because the club is the only place that knows all three things at once: that you have an airplane booked, when you're flying it, and what your limits are. A weather app knows the sky. A scheduler knows the calendar. Only the club system knows both, and it's the only thing that can send you the brief before you've thought to ask.
Hope this all makes sense. If you want to see one, here's a 90-second look at the briefing email, or come take a look at the whole thing.