The five beats of a planned trip
Every trip Sedna is involved in moves through the same five beats. You will not always stop at every beat — sometimes you know exactly when and where you're going and skip straight to the briefing — but the structure is worth carrying in your head because it's what the portal is built around.
Most windows show up before you ask. Sedna watches the forecasts your vessel profile cares about — your range, your hull, your target species, your months active — and surfaces the windows that fit. The dashboard and the chat both carry these: "The SW wind shuts down after Thursday — Friday and Saturday both look clean, Saturday's major window is the better of the two." You didn't ask. She told you.
Window flags are a suggestion, not a booking. You still decide whether to fish the window. But the mental cost of noticing a good day existed just dropped to zero.
This is where chat earns its keep. Open Hey Sedna and give her the frame: "Saturday. Looking at the window you flagged. Running solo. Want to put a keeper bass in the box and be back by noon." Or: "Saturday. Bringing two clients, one of them has never been offshore. Canyons are too far. What inside run gives them a day they'll remember?"
The more context, the sharper the plan. She's reasoning against your vessel profile and this week's water regardless — the sentence you type is what tells her what "a good day" means for you, on this trip.
Sedna comes back with a plan: leave Snug at 5:30 — the flood turns at 7:14, you want to be on structure at the start — run the 14 nm straight to the SW Ledge, work the south edge for the first hour, reposition toward the bunker pods at 7:45 if the first drift doesn't produce. Gear: live eels if Wakefield has them Friday, bunker chunks as backup. Backup plan: if the Ledge doesn't fire by 8, the North Rip has been patchy but the fleet reported a push there Wednesday.
This is a plan, not a briefing. It's rough, it's conversational, it exists so you can push back on it.
Push back where you want to. "I'd rather fish the rip first — I was on the Ledge Wednesday and it was dead for me." She regenerates against your on-water experience, which now weighs against her fleet-intel-derived pick. "Fair — the rip on the start of the flood, Ledge as fallback at 8 if the rip doesn't light up." The plan tightens.
When the plan feels right, you commit to it by requesting an @Desk briefing for that trip. That moves you from conversation to document — from "let's run the rip" to "Saturday May 9, Snug Harbor departure 5:30, primary target SW Block Rip, keeper bass, backup SW Ledge."
Saturday happens. You run the plan (or don't — the fish have a vote). You come back to the dock, snap the @Dock photos, email them to Sedna. The catch log populates, the Angler Cards go out, and the Captain's Report lands in your inbox.
Here's the part most captains don't notice the first time: the trip you just ran is now input for the next trip you plan. Sedna has your Saturday logged against this week's water. The next time she flags a window in similar conditions, she's weighing Saturday's actual result in the plan — not just the fleet's, yours. A season of this and your briefings start knowing your water the way you know it.
Where the loop shows up in the portal
You won't find a single page called "Trip Planning." The loop lives across three places you already know:
- Hey Sedna chat is where beats 1 through 4 happen — window flag, plan request, iteration, commit.
- @Desk briefing is where beat 4 turns into a document you and your crew can share.
- My Trips / Catch Log / Reports is where beat 5 lives — the trip map, the photos, the Captain's Report, and the rolled-up season view.
The portal's sidebar surfaces each of those directly. The Trips page in particular is worth opening at the start of each season — it carries every trip you've run through the portal, with the briefing, the catch log, and the actual result linked to the same date. At a glance you can see what produced, what didn't, what window patterns your boat fished well, and what you want to try again this year.
The loop is also your trip history with each client.
Every trip you run with a given guest links the briefing, the Angler Cards, and the Captain's Report to that day. Repeat clients — and on a good charter program most of the year's revenue comes from repeat clients — effectively carry a file. When the same guests book again, you can open the prior trip in seconds: what they caught, what the water did, what the mate noted, what they liked about the day.
You walk into the next trip with "last August we got you on that 62-inch cow, water was 73 on the north wall, let's see if we can set you up on a better one this season" instead of "good to see you again, how've you been." Clients notice the difference. The ones who fished three charters with three different captains and one with you stop comparing you to the other three.
It is the single cheapest way to turn a one-trip client into a standing account.
When to skip beats
Not every trip is a planned trip. Sometimes you wake up at 4 a.m. on a Tuesday, the water looks good out the window, and you go. That's fishing — and the portal is not trying to replace it.
The working compromise: even on an unplanned run, send the @Dock photos when you get back. You skipped beats 1 through 4. Beat 5 still closes the loop — Sedna records the trip, the catch, and the conditions, and your next planned trip benefits from what happened today. The value of the loop doesn't require you to use every step; it requires you to close it somewhere.