How should a fishing lodge or guide collect client dietary restrictions and medical conditions?

Collect them from the client directly, in writing, and store them somewhere the whole operation can read — not in a booking-form field nobody opens again. In Fishing Outfitter the angler fills in dietary restrictions, medical conditions, and an emergency contact in their own portal profile, in their own words. That removes the two places the information usually dies: the relay through a phone call, and the handwriting on a paper form.

Why do dietary restrictions get missed at fishing lodges?

Almost never because the client didn't say. The client usually tells someone at booking, months before the trip. It's the transmission that fails: the answer stays where it was written down, and the people who need it — the cook planning the week's menu, whoever's making the provisioning run, the guide spending ten hours in a boat with the client — are somewhere else. Every hop between the booking call and arrival day is a place to drop it.

Do clients have to re-enter their dietary and medical information every season?

Not in Fishing Outfitter. Health, emergency, and identification details are stored on the person rather than on a single booking, so a returning client's information is already there next season — and so is an angler's, if they book with a different operation that also runs on Fishing Outfitter. Each operation sees that client's profile plus their own booking, nothing else.

Does the lodge cook see client dietary restrictions?

Yes. The cook's dashboard leads with the headcount and the dietary restrictions for upcoming trips, and the per-trip meal plan shows the restrictions for that specific week — including non-fishing companions, since a spouse who came along still eats dinner. The shopping list flags your booked anglers' restrictions as well, so the provisioning run accounts for them before anyone is standing in an aisle guessing — companion restrictions live on the meal plan rather than the shopping list. The cook portal, the meal planner, and the client-facing menu page come with the Business plan; the shopping list is available on Solo and up.

Can guides see a client's medical information on the water with no cell service?

Yes. Guides see dietary and medical details on each booking, and the guide field-notes view carries the client's health block and emergency contact. Those field tools are built to work offline: pages the guide has already opened while in service are cached on the device, and the app warms the most current bookings ahead of time. So a guide who has loaded the day's bookings before losing signal still has the emergency contact on the water, rather than having to radio the lodge to ask who to call.

August 27, 2026

Fishing Client Dietary Restrictions: Does Your Cook Actually Know?

Picture the moment the information actually matters. It's not the phone call in February when a client mentions, almost in passing, that he's diabetic. It's five months later: your cook is planning meals for a full lodge, someone's making the provisioning run in town — the last town before the water — and one of the anglers stepping off the floatplane needs his meals timed and his sugar handled, a long boat ride from the nearest pharmacy.

Between February and July, that one sentence had to survive a phone call, a notebook, maybe a text to your cook, and a grocery run. Every hop is a place to drop it.

Most operations askthe right questions. Booking forms have had a “dietary restrictions / medical conditions” line forever. The problem was never asking — it's that the answer lives where it was written down, and the people who need it are somewhere else: the cook planning the week's menu, whoever's standing in the grocery aisle, the guide who's about to spend ten hours in a boat with this client.

Remote water doesn't have a plan B

In a restaurant, a missed allergy is an apology and a new plate. At a lodge or a remote camp, it's a different story. Dinner is what came in on the last supply run, and nobody's making a second one tonight. A shellfish allergy nobody told the cook about — at a fishing lodge, where shellfish is half the menu some weeks. A diabetic angler facing a table built on starch and sugar. A heart condition your guide learns about mid-river. These aren't service failures out there. They're safety problems, happening exactly where help is hours away by boat or floatplane.

And here's the thing: the client told you. Almost every time, the information existed somewhere in your operation. The failure is transmission, not collection.

Close the loop: enter it once, surface it everywhere

This is one of those problems software actually solves cleanly, because it's a plumbing problem. Here's how it works in Fishing Outfitter:

Your client enters it themselves. When an angler sets up their portal account, their profile asks for dietary restrictions, medical conditions, and an emergency contact — in their own words, typed by the person who knows best. No relay through a phone call, no deciphering handwriting on a faxed booking form. And it's saved to the person, not the paperwork — a returning client doesn't re-enter it next season, and neither does an angler who books with a different operation on Fishing Outfitter.

Then it shows up everywhere meals and safety get handled:

The shopping list flags every current client's restrictions right at the top — so the provisioning run accounts for the diabetic angler before anyone's standing in an aisle guessing.
The per-trip meal plan shows the restrictions for that week's guests — including non-fishing companions, because the spouse who came along for the lodge eats dinner too.
The cook's own view leads with headcount and restrictions for upcoming trips — one of the pieces that makes running a full lodge week survivable.
Your guides see it on each booking — dietary and medical — and their field view carries the client's health details and emergency contact with them, built to work where there's no cell service. If something goes wrong on the water, the guide isn't radioing the lodge to ask who to call.

And once you are planning camp menus, your client can see it too. The menu page in their portal shows the dietary restrictions you have on file — so the angler with the shellfish allergy knows, before he ever leaves home, that your kitchen got the message. That's not a small thing. It's one more moment where your operation feels handled instead of hoped-for.

Client profiles — including health and emergency info — are on every Fishing Outfitter plan. The shopping list is Solo and up; the meal planner, the cook portal, and your client's menu page come with Business.

It's also just good hosting

Not every case is an emergency. Sometimes it's a gluten-free client quietly eating around half of every meal for five days, going home fed but not taken care of — and taken care of is the entire product you sell. The lodges that get remembered, reviewed, and rebooked are the ones where the cook slid the right plate in front of the right angler without being asked twice.

Profile once. Surface everywhere. Nobody guessing in the grocery aisle, nobody surprised a hundred river miles from town.

That's what Fishing Outfitter's client profiles are built to do — and dietary and medical details are just one slice of them, alongside licenses, waivers, packing lists, and everything else a season runs on. Start free on the Starter plan and see what your clients can hand you before you ever load the boats.

Start free on the Starter plan — or try a paid plan free for 14 days.