The Pre-Trip Confirmation Workflow
Builds guide sites for a livingPublished July 23, 2026Last updated July 26, 202635 min read
- 46 CFR 185.504 requires a written passenger count communicated ashore before departure and available to the Coast Guard on request; 185.503 imposes the same architecture on a voyage plan.
- 14 CFR 91.103 requires a pilot to become familiar with all available information before a flight, expressly including alternatives available if the planned flight cannot be completed.
- Name the alternative in the two-day message, because it is the only part of the day the client cannot work out for themselves.
- End the two-day confirmation with an explicit request for a one-word reply; no reply by the next morning is a phone call, not another message.
- Restate the headcount and ask for correction, since groups change between booking and trip and nobody says so unprompted.
- Send the same three facts to the same person ashore every morning: put-in, take-out, expected time off the water.
The Coast Guard's rules for small passenger vessels put three verbs on the information that has to exist before a boat leaves. Prepared prior to departing. Communicated ashore. Available on request. Nothing about the trip itself, only about what somebody on land knows before you go.
Aviation asks for something adjacent and broader: before beginning a flight, the pilot in command must become familiar with all available information concerning that flight, including the alternatives available if the planned flight cannot be completed. Neither regime governs a guide running a drift boat on a river, and both describe the same discipline, which is that the day is decided before it starts. What follows is that discipline turned into a confirmation workflow. Nothing here is legal advice, and the requirements that do apply to your operation depend on your vessel, your waters and your licence. The rest of the operations material lives at the ops playbooks hub.
| When | What moves |
|---|---|
| At booking | Deposit, dates, headcount, the licence question |
| Seven days out | Meeting point, time, what to bring, the conditions read |
| Two days out | The confirmation reply, and the plan B if there is one |
| The night before | Nothing new, one line only |
What do the vessel rules actually require?
That somebody ashore knows who is aboard, before you leave.
Section 185.504 of Title 46 requires the master of a vessel to keep a correct, written count of all passengers that embark on and disembark, and provides that prior to departing on a voyage the count must be communicated verbally or in writing and available ashore at the vessel's normal berthing location or with a representative of the owner or managing operator.
Section 185.503 requires a voyage plan for certain vessels, prepared prior to departing and communicated verbally or in writing ashore in the same way.
Section 185.502 requires, for certain other voyages, a correct list of the names of all persons that embark and disembark, prepared before departure and communicated ashore.
The three share one architecture: the information exists before you go, it leaves the boat, and it can be produced on request.
Part 185 is carried on the eCFR.
Whether any of it reaches your operation is a licensing question, taken up in the captain's licence piece.
What does the aviation rule add?
The plan B, as a requirement rather than a courtesy.
Section 91.103 of Title 14 requires each pilot in command, before beginning a flight, to become familiar with all available information concerning that flight.
The enumerated minimum for a flight not in the vicinity of an airport includes weather reports and forecasts, fuel requirements, alternatives available if the planned flight cannot be completed, and any known traffic delays.
That third item is the one worth stealing outright, because it makes the alternative part of the preparation rather than something improvised at the ramp.
The rest of the section deals with runway lengths and with performance under expected values of elevation, slope, weight, wind and temperature, which is a way of saying that the conditions you expect are part of the plan and not a surprise.
Section 91.103 is carried on the eCFR.
The conditions call itself is dealt with in the contingency piece.
What a bad confirmation costs. One client turning up at the wrong ramp, forty minutes away, costs you the first hour of a nine-hour day, which is about eleven per cent of the trip. On a $700 day that is $78 of delivered value handed back, plus a client who starts the morning flustered. Across a hundred-day season, three such mornings is $234 and three trips that started badly. The seven-day message that prevents them takes four minutes to send. Every figure here is a stated assumption.
What goes in the seven-day message?
Everything they need to arrive correctly, and nothing else.
The meeting point, written as a place a person can find rather than as a name only locals use, with a link to a map pin.
The time, stated as the time you want them standing at the truck rather than the time the boat goes in.
What to bring, as a short list rather than a paragraph, and what you are providing so they do not duplicate it.
The licence position, meaning whether they need one, where it is bought, and whether it can be bought at the ramp.
And a two-line read of conditions, which is the part that makes the message feel like it came from a person on that water rather than from a system.
The licence question in detail is covered by the licence requirements piece.
Neither regime necessarily applies to you. 46 CFR part 185 applies to small passenger vessels subject to subchapter T, and whether your vessel and operation fall within it depends on facts this page does not know. 14 CFR 91.103 governs aircraft operations and has no application to a boat. Both are quoted as models of preparation, not as compliance guidance. Federal, state and local requirements for guided fishing vary a great deal. Confirm your own obligations with the Coast Guard and your state agency, and nothing here is legal advice.
Why does the plan B belong in writing?
Because it is the only part the client cannot supply themselves.
A client can find a ramp and buy a licence; what they cannot do is know what happens if the river is unfishable on Thursday.
The aviation formulation is the right one: the alternative is prepared in advance, not discovered on the morning.
Which in practice means the two-day message states the alternative explicitly, being the other stretch, the later start, or the different fishery.
Naming it in writing removes an entire class of dispute, since a client who was told on Tuesday that high water means the tailwater instead has agreed to something rather than been diverted.
It also prevents the worst version of the conversation, which is the one held at six in the morning at the ramp with everybody's gear already out.
Where the alternative does not exist, saying so is better than implying one does.
How to decide the call is set out in the contingency piece.
Should the confirmation require a reply?
Yes, once, and it is the whole point of the two-day message.
An unacknowledged confirmation is not a confirmation, it is a message you sent, and the difference shows up at the ramp.
The two-day message therefore ends with a request for a one-word answer, and the request is explicit rather than implied.
Confirming the meeting point and time, reply yes and I will not bother you again, works because it tells them exactly what is wanted and promises an end to it.
No reply by the following morning is a phone call, not another message, because two unanswered texts is a no-show forming.
Recording the reply against the booking is what makes the whole workflow auditable later, which matters exactly once and matters enormously then.
Where those records live is set out in the spreadsheet CRM piece.
What about the headcount?
Confirm the number and the names, and do it in writing.
The vessel rules require a correct count and, for some voyages, a list of names, both communicated ashore before departure, and the reason is not administrative.
A count that is wrong is a count that fails at the only moment it matters, and the moment it matters is the one nobody plans for.
Applied to a guide's day, the workable version is that the two-day message states the number aboard and asks for correction, rather than assuming the booking is still accurate.
Groups change constantly between booking and trip, and the change is almost never communicated unprompted.
Where the headcount affects the boat, the licence count or the food, the two-day confirmation is the last moment it can be fixed cheaply.
What the boat can actually carry is covered by the capacity piece.
What does the booking message have to settle?
Everything that would be expensive to change later.
The confirmation workflow only works if the booking message did its job, and the test of that is whether anything in the seven-day message could still come as a surprise.
Four things belong there and nowhere else: what the day costs and what that covers, what happens if either side cancels, how many people are coming, and whether they need a licence.
Each of those is cheap to settle in October and expensive to settle in June, which is the entire argument for front-loading them.
The one most often skipped is what the price covers, and it is the one that generates the most friction at the takeout, because a client who assumed lunch was included and paid separately for it feels charged twice.
Writing it as a short list of what is included and what is not takes four lines and it is the single most useful paragraph in the whole sequence.
Where the operation runs multiple trip types, that list differs per type, which means the template has variants rather than one general version.
A general version that covers everything covers nothing, since the client has to work out which parts apply to them.
What about a client who has fished with you before?
Shorter, but not shorter by leaving things out.
The temptation with a returning client is to skip the workflow, on the reasonable ground that they know where the ramp is and what to bring.
What they do not know is this year's conditions, this year's meeting time, and whether anything about the water has changed since they were last there.
So the seven-day message shrinks to the conditions read and the time, and the two-day confirmation stays exactly as it is, because the acknowledgement is the part that has nothing to do with familiarity.
Assuming a returning client will turn up correctly is how experienced clients end up at last year's ramp, which happens more often than anybody admits.
Where something genuinely has changed, the message says so plainly rather than assuming they will notice: we are putting in at the lower ramp this year.
The returning client's version can also carry something the new client's cannot, being a reference to their last trip, which costs one line and does more than the rest of the message.
How should the bring list be written?
As objects, in order of what happens if they are missing.
A bring list written as a paragraph gets skimmed and a bring list written as ten bullets gets ignored, so five items is the working ceiling.
The ordering that works is by consequence: the thing that ends the trip if forgotten goes first, and the thing that makes the day slightly less pleasant goes last.
For most operations that means a licence or a pair of boots at the top and sunglasses somewhere near the bottom, which is the reverse of how most lists are written.
Naming what you provide is as important as naming what they bring, because a client who packs a rod you were going to supply has carried it four hours for nothing and will mention it.
Specificity beats completeness throughout: rain jacket, not appropriate outerwear, because the second is advice and the first is an instruction.
Where a client asks a question the list should have answered, the list gets edited that evening rather than answered ad hoc, which is how a template stops accumulating gaps.
Who ashore should know?
One named person, every day, with the same three facts.
The regulations are specific that the information goes to a person or place ashore rather than staying with the vessel, and for a solo guide there is usually nobody performing that role at all.
The workable substitute is a standing arrangement with one person, being a partner, a shuttle driver or another guide, who receives the same message every morning.
Three facts: put-in, take-out, and expected time off the water, with the number aboard.
A text takes fifteen seconds and it is the single cheapest safety measure available to a one-boat operation.
What makes it work is that it is the same person and the same format daily, because an irregular message is one nobody notices the absence of.
The absence being noticed is the entire function, and it is why the arrangement has to be boring.
The wider safety picture is set out in the safety briefing piece.
When is the night-before message right?
Only as one line, and only with nothing new in it.
A message the night before is reassurance rather than information, and it works precisely because it contains nothing the client has to act on.
See you at six at the Bridge Street ramp, forecast looks fine, is the entire message and it should not be longer.
What ruins it is introducing a change at that hour, since a client who learns at nine in the evening that the meeting point moved will arrive stressed if they arrive at all.
Where something genuinely changed, that is a phone call rather than a text, and it happens as soon as you know rather than at bedtime.
The value of the routine one-liner is that it makes the exceptional call recognisable as exceptional.
How the morning-of contact should run is dealt with in the morning-of piece.
How much of this can be automated?
The scaffolding, not the conditions line.
Meeting point, time, what to bring and the licence position are identical for every client on that water and belong in a saved template.
The conditions read is the part that cannot be, because it is the only sentence that proves a human looked at the river this week.
Which is also the sentence clients quote back to you, and the one that separates a confirmation from an automated reminder.
Two minutes a message, four messages a trip, is under ten minutes per booking and it is the highest-return administrative time in the business.
Where a booking system sends its own reminders, they run alongside rather than instead, because a system reminder proves nothing about the water.
What booking software actually handles is examined in the booking software piece.
What should never be in a confirmation?
An upsell, a policy change, or a question you should have answered.
An offer attached to a confirmation converts an operational message into a sales one and gets it read as such, which means the operational content stops landing.
A policy restated at the two-day mark reads as a warning and it should have been agreed at booking, where it belonged.
And a question of the form let me know what you would prefer puts a decision on somebody who booked you to make it.
The confirmation is a statement of what will happen, with one request for acknowledgement, and that is its whole job.
Anything else belongs in a different message on a different day.
The booking terms this rests on are set out in the deposit piece.
Where does the workflow usually break?
Six ways, and the unacknowledged message is the first.
Sending a confirmation that asks for no reply, so nobody knows whether it was read until the ramp.
Leaving the alternative undecided, so the weather call happens at six in the morning with gear already out.
Assuming the headcount from the booking, when groups change and nobody thinks to say so.
Naming a meeting point the way locals do, which is unfindable to somebody who has driven four hours.
Introducing a change the night before, when the client has stopped being able to absorb one.
And telling nobody ashore, so the one thing the vessel rules insist on is the one thing missing.
What happens when a client is late anyway is covered by the late client piece.
What is the working workflow?
Four messages, one reply, one person ashore.
At booking, the deposit, the dates, the headcount and the licence answer, every one of them in writing.
Seven days out, the meeting point with a map pin, the standing-at-the-truck time, the bring list, and two lines on conditions.
Two days out, the confirmation with the headcount restated, the alternative named if there is one, and an explicit request for a one-word reply.
No reply by the next morning is a phone call rather than another message.
The night before, one line with nothing new in it.
Every morning, the same three facts to the same person ashore.
The statutory basis for vessel inspection standards is 46 U.S.C. 3306, and part 185 is mirrored on govinfo.
The checklist this hangs off is built in the daily checklist piece.
How this was checked. The passenger count requirement comes from 46 CFR 185.504, which requires the master of a vessel, except a vessel listed in 185.502(a), to keep a correct written count of all passengers that embark on and disembark from the vessel, and provides that prior to departing on a voyage the passenger count must be communicated verbally or in writing and available ashore at the vessel's normal berthing location or with a representative of the owner or managing operator, and shall be available to the Coast Guard upon request. The voyage plan requirement comes from 46 CFR 185.503, which requires the master of vessels making an oceans or coastwise voyage, a voyage of more than 300 miles on the Great Lakes with a stated exception, an overnight voyage with overnight accommodations for passengers, or a voyage arriving from a foreign port with a stated exception, to prepare a voyage plan prior to departing and communicate it verbally or in writing ashore in the same manner. The crew and passenger list requirement comes from 46 CFR 185.502, which requires a correct list of the names of all persons that embark and disembark for the voyages it enumerates, prepared prior to departing and communicated ashore. Part 185 applies to small passenger vessels under subchapter T, and whether a particular vessel and operation fall within it depends on facts not known to this page. The preflight requirement comes from 14 CFR 91.103, which requires each pilot in command, before beginning a flight, to become familiar with all available information concerning that flight, and which enumerates for a flight not in the vicinity of an airport weather reports and forecasts, fuel requirements, alternatives available if the planned flight cannot be completed, and any known traffic delays of which the pilot has been advised by air traffic control, together with runway lengths at airports of intended use and takeoff and landing distance information including, for aircraft without an approved flight manual containing such data, other reliable information relating to performance under expected values of airport elevation and runway slope, aircraft gross weight, and wind and temperature. Section 91.103 governs aircraft operations and has no application to a boat. Both sections were read on the Electronic Code of Federal Regulations on 26 July 2026 and are quoted as models of preparation rather than as compliance guidance. Federal, state and local requirements for guided fishing vary considerably and were not researched for this page. Nothing here is legal advice. No industry no-show rate, late-arrival rate or benchmark is asserted, because no consulted source publishes one; the figures in the arithmetic panel are stated illustrative assumptions.
If your booking calendar has more open weeks than you’d like, I’ll build you a free preview of your booking site before you pay a cent.
Get a free website previewWhat goes in each message, why the plan B belongs in writing, and who ashore should know
What do the vessel rules require?
46 CFR 185.504 requires the master to keep a correct written count of all passengers embarking and disembarking, and requires that count to be communicated verbally or in writing and available ashore at the vessel's normal berthing location before departure, and available to the Coast Guard on request. 185.503 requires a voyage plan for certain voyages on the same terms, and 185.502 a list of names for others. All three share one architecture: prepared before departure, communicated ashore, retrievable. Part 185 applies to subchapter T small passenger vessels, and whether it reaches your operation depends on facts this page does not know.
What does the aviation rule add?
14 CFR 91.103 requires each pilot in command, before beginning a flight, to become familiar with all available information concerning that flight, and enumerates for a flight not in the vicinity of an airport weather reports and forecasts, fuel requirements, alternatives available if the planned flight cannot be completed, and any known traffic delays. The third item is the one worth stealing: the alternative is part of the preparation rather than something worked out at the ramp.
What goes in the seven-day message?
The meeting point written as a place a stranger can find, with a map pin. The time, stated as when you want them standing at the truck rather than when the boat goes in. A bring list of about five items, ordered by what happens if each is missing, plus what you are providing. The licence position. And two lines on conditions, which is the part that proves a person looked at the water this week.
Why does the confirmation need a reply?
Because an unacknowledged confirmation is just a message you sent, and the difference shows up at the ramp. End the two-day message with an explicit request: confirming the meeting point and time, reply yes and I will not bother you again. That tells them exactly what is wanted and promises an end to it. No reply by the following morning is a phone call, because two unanswered texts is a no-show forming.
Who ashore should know?
One named person, every day, receiving the same three facts: put-in, take-out and expected time off the water, with the number aboard. The regulations are specific that the information leaves the vessel, and for a solo guide nobody is performing that role at all. A text takes fifteen seconds and is the cheapest safety measure a one-boat operation has. It has to be the same person and the same format daily, because the absence being noticed is the entire function.
Is the night-before message worth sending?
As one line with nothing new in it. See you at six at the Bridge Street ramp, forecast looks fine. It is reassurance rather than information and works because there is nothing to act on. Introducing a change at that hour is how a client arrives stressed or not at all; where something genuinely changed, that is a phone call made as soon as you know it. The routine one-liner is also what makes the exceptional call recognisable.
How much can be automated?
The scaffolding but not the conditions line. Meeting point, time, bring list and licence position are identical for every client on that water and belong in a template. The conditions read cannot be, because it is the only sentence proving a human looked at the river this week, and it is the sentence clients quote back. Where a booking system sends its own reminders they run alongside, since a system reminder proves nothing about the water.
Sources & methods
- 46 CFR part 185 on the Electronic Code of Federal Regulations, read for section 185.504, requiring the master of a vessel except one listed in 185.502(a) to keep a correct written count of all passengers that embark on and disembark from the vessel and, prior to departing on a voyage, to communicate that count verbally or in writing and make it available ashore at the vessel's normal berthing location or with a representative of the owner or managing operator, with the count available to the Coast Guard upon request; for section 185.503, requiring the master of vessels making an oceans or coastwise voyage, a voyage of more than 300 miles on the Great Lakes with a stated exception, an overnight voyage with overnight accommodations for passengers, or a voyage arriving from a foreign port with a stated exception, to prepare a voyage plan prior to departing and communicate it ashore in the same manner; and for section 185.502, requiring a correct list of the names of all persons that embark and disembark for the enumerated voyages, prepared prior to departure and communicated ashore. Part 185 applies to small passenger vessels under subchapter T, and whether a given vessel and operation fall within it depends on facts not known here.
- 14 CFR 91.103 on the Electronic Code of Federal Regulations, read for the requirement that each pilot in command, before beginning a flight, become familiar with all available information concerning that flight, and for the enumerated minimum, which for a flight under instrument flight rules or not in the vicinity of an airport includes weather reports and forecasts, fuel requirements, alternatives available if the planned flight cannot be completed, and any known traffic delays of which the pilot in command has been advised by air traffic control, and which for any flight includes runway lengths at airports of intended use together with takeoff and landing distance data or, for aircraft without an approved flight manual containing such data, other reliable information relating to performance under expected values of airport elevation and runway slope, aircraft gross weight, and wind and temperature. The section governs aircraft operations and has no application to a boat.
- 46 U.S.C. 3306 at the Office of the Law Revision Counsel, cited as the statutory basis for the vessel inspection regulations quoted above, together with the 2024 annual edition of 46 CFR part 185 published on govinfo as an independent copy. Federal, state and local requirements for guided fishing vary considerably and were not researched for this page. Nothing here is legal advice, and no no-show or late-arrival benchmark is asserted because no consulted source publishes one.
- The 2024 annual edition of 46 CFR part 185 published on govinfo, used as an independent copy of the vessel provisions relied on above.
Every figure here is traced to a named public source and checked against it. Licensing, tax, and fee rules change. Verify your state’s current rules with the agency directly before you count on any number here.
Evan Knox
I build booking websites and run the ads and search for owner-run fishing guides, one operation per stretch of water. My first guide client, Bowman Fly Fishing, grew its revenue 4x in a year from that work. Field Notes is where I put the straight numbers on the business of guiding.
More field notes
A confirmed trip is worth more than a booked one.
I'm Evan. Workflow keeps the days you sold. I build guides the booking site and run the ads that sell them. Free preview before you pay a cent.