Morning-Of Client Communication

The motor carrier rules contain a sentence that answers the hardest question a guide faces at five in the morning. If conditions become sufficiently dangerous, the operation shall be discontinued and shall not be resumed until it can be safely conducted.

Not reduced, not managed, not attempted carefully. Discontinued. The rule governs commercial motor vehicles and reaches no drift boat anywhere, and the aviation rules supply the other half of the same answer by making the person in command directly responsible for and the final authority as to the operation. Together they describe a morning that most guides run backwards, in which the client's expectation decides and the guide narrates. What follows is the morning-of communication built the other way round. Nothing here is legal advice. Everything adjacent sits under the ops playbooks hub.

What does the hazardous conditions rule say?

Three sentences, and the second one is the standard.

Section 392.14 of Title 49 requires extreme caution in the operation of a commercial motor vehicle when hazardous conditions, such as those caused by snow, ice, sleet, fog, mist, rain, dust or smoke, adversely affect visibility or traction, and requires speed to be reduced when such conditions exist.

It then states that if conditions become sufficiently dangerous, the operation shall be discontinued and shall not be resumed until the vehicle can be safely operated.

And it closes with a proportionality clause: where compliance would increase the hazard to passengers, the vehicle may be operated to the nearest point at which the safety of passengers is assured.

Which is a complete decision structure, being a graduated response, a stopping rule and an exception for the situation where stopping is itself the danger.

Section 392.14 is carried on the eCFR.

The planning that should have happened days earlier is covered by the contingency piece.

Rio Anglers, TX

Who makes the call?

You do, alone, and the rule says so in nine words.

Section 91.3(a) of Title 14 provides that the pilot in command of an aircraft is directly responsible for, and is the final authority as to, the operation of that aircraft.

Directly responsible and final authority are separate ideas and both matter, since responsibility without authority is the position most guides put themselves in.

Paragraph (b) goes further, permitting deviation from any rule in the part to the extent required to meet an in-flight emergency, and (c) requires a written report of that deviation on request.

Which is a structure worth noticing: the authority is broad, and it comes attached to an obligation to account for how it was used.

The transferable version is that the morning call is yours, that the client's travel and expectation do not enter the calculation, and that you should be able to say afterwards what you looked at and why you decided as you did.

Section 91.3 is carried on the eCFR.

How that decision gets recorded is dealt with in the debrief piece.

Cajun Paradise, LA

When is the call actually made?

The moment you have the information, not the moment you feel ready.

The gap between knowing and telling is where the whole failure lives, and it is almost never about information.

It is about not wanting to have the conversation, which produces a decision made at five and delivered at six-fifteen when the client is already twenty minutes away.

The rule to hold yourself to is that the message goes out inside five minutes of the decision, and that the decision is made as soon as the data exists rather than as late as it can be left.

Where the data genuinely will not exist until dawn, saying that in advance is the honest move: I will look at the gauge at half five and message you either way by six.

Either way is the load-bearing phrase, because it converts silence from ambiguous into alarming, which is what silence should be.

The evening message that sets this up is covered in the confirmation workflow piece.

What does the cancellation message say?

The decision first, the reason second, the remedy third.

Most cancellation messages are written in the reverse order, opening with an apology and a paragraph about the weather, which leaves the client reading for the sentence that matters.

The working shape is: we are not going today. The river came up nine hundred overnight and it is unfishable. Your deposit goes back this morning, or I can hold it for a date, whichever you prefer.

Three sentences, no hedging, and a decision already taken rather than a situation described.

What must not appear is any construction that invites the client to weigh in, since asking what they would like to do hands them a judgment they are not equipped to make and did not ask for.

The reason belongs in it because a client who knows why accepts it, and a client told only that conditions were poor suspects a better-paying booking.

A number in the reason does most of that work, since nine hundred cubic feet per second is checkable and bad conditions is not.

What happens to the money is set out in the rollover piece.

What about the marginal morning?

Name the two outcomes and let them choose the risk, not the safety.

Plenty of mornings are not dangerous and not good, and those are the ones that go wrong, because the guide splits the difference and says nothing.

The honest message states the position and both branches: the water is high and off colour, we will probably catch fewer fish and it will be a working day, we can go or we can move it, tell me which.

Which is a legitimate client decision, unlike the safety one, because the thing being traded is their day and their expectation rather than anybody's wellbeing.

Sending it costs you a booking sometimes, and it prevents the worse outcome, which is a client who fished a poor day believing they were sold a good one.

What makes it work is that the message is unhedged: not it might be tough, but we will probably catch fewer fish.

Softening the description is the same failure as delaying the call, and it produces a client who feels misled by a message that was technically accurate.

The playbook for the day itself is set out in the no-fish day piece.

Should the client be able to overrule you?

On comfort, yes. On safety, never, and say it plainly.

A client who has driven six hours will push, and the push is completely understandable and entirely irrelevant to the decision.

The final authority formulation is useful here because it is not a matter of confidence: the responsibility does not move to the client when they insist, so neither does the authority.

Saying that out loud, once, ends the conversation faster than any amount of explanation: I understand, and it is my call and the answer is no.

What makes it survivable commercially is that the same person who is angry at six in the morning is, a fortnight later, telling people you turned down a day's money rather than put them on bad water.

Guides who bend on this once find the conversation harder the next time, because the client has learned that pushing works.

The one legitimate flexibility is on the alternative, where the client's preference genuinely governs.

The protocol for a client who becomes a problem is set out in the difficult clients piece.

What about a client who is late?

One call at the stated time, then the day starts.

The morning has a shape and a late client bends it, which affects the water you can reach and the light you have.

The workable rule is a call at the meeting time, a second at fifteen minutes, and a decision at thirty that was stated at booking.

Sending texts to somebody driving achieves nothing, which is why this is a call rather than a message.

Where they are close, the honest thing is to say what the delay costs: we can still go, we will lose the top stretch, that is fine if it is fine with you.

Which keeps the client informed and stops the loss being discovered at the takeout as a disappointment.

The stated policy behind it is set out in the late client piece.

What data actually decides it?

Three sources, looked at in the same order every morning.

The gauge first, because a number is a number and it is the only input that is not a forecast.

Radar second, since it tells you what is arriving in the next six hours, which is the window that matters and the one a daily forecast averages away.

The forecast third and last, because it is the least specific input and the one most likely to be wrong about a river valley.

Doing them in that order matters more than it sounds, since starting with the forecast anchors you to somebody else's summary before you have looked at the actual water.

What you are looking for is a threshold decided in advance rather than a judgment formed in the moment: this stretch is off above a stated flow, that one is fine.

Thresholds written down in the autumn are worth ten mornings of deliberation, because a number decided when nobody is waiting is a better number than one decided at five with a client driving.

Where a stretch has no threshold yet, the morning it first blows out is the morning to write one down.

How should the message be sent?

By text, then by phone if it cancels the day.

A text arrives silently and is read on waking, which is exactly right for a message that says the trip is on.

A cancellation is different, because it needs to reach somebody who may already be driving, and a text to a driver may sit unread for two hours.

So the pattern is: text always, and follow with a call when the message changes their morning.

The call does not need to be answered to have worked, since a missed call from you at five-forty is itself information and produces a callback at the next stop.

Email is wrong for all of this and it is still what a surprising number of booking systems default to, which is worth checking before the season starts.

Where a client gave a landline or an unfamiliar number, the morning of the trip is not when you want to find out, which is another argument for the two-day acknowledgement.

What should be said to a group?

Everything to the organiser, and one line to everybody else.

A group message thread at five in the morning produces four opinions and no decision, which is the opposite of what the morning needs.

The workable form is the full message to the organiser, with the decision and the reason, and a single short line to the group so that nobody is waiting on a relayed rumour.

Where the group is travelling separately, the short line matters more than the long one, since the person forty minutes behind is the one who needs to turn around.

Asking the organiser to relay is the common approach and it fails predictably, because they are also driving and also processing the news.

Having every participant's number is what makes this possible, which is a booking-time task rather than a morning-of one.

Collecting them takes one line on the intake form and it pays for itself the first time weather cancels a group day.

Does any of this get written down?

One line per cancelled day, and it takes twenty seconds.

The date, the reading that drove the decision, and what was offered.

Which matters for three reasons that only show up later: it builds a record of what your water actually does, it settles any dispute about what was offered, and it stops you second-guessing a call you already made correctly.

Three seasons of those lines is a better guide to your own thresholds than any amount of recollection, because memory over-weights the days that went badly.

The record also answers the question an insurer or a lawyer might one day ask, which is what you looked at and when you decided, and that is precisely what the aviation rule's reporting requirement is designed to produce.

Keeping it with the trip records rather than in a separate log is what makes it survive, since a separate weather log is a thing nobody maintains past March.

What is said at the ramp?

Nothing that could have been said earlier.

The ramp is for greeting, gear and the safety briefing, and every operational fact introduced there lands badly because everybody is busy.

A client learning at the ramp that they needed a licence, or that the day ends at two rather than four, has been failed by the confirmation rather than informed at the ramp.

Which is a useful audit: anything you find yourself explaining at the truck belongs in the seven-day message, and it goes in that template that evening.

The exception is the conditions read, which is genuinely new information and is worth thirty seconds of framing before anybody gets in the boat.

Setting the expectation at the ramp rather than on the water is worth doing because the client is still calibrating, and after the first hour they are not.

What the briefing itself should contain is set out in the safety briefing piece.

Does the discontinue rule have a version for mid-trip?

It does, and it is the proportionality clause.

Section 392.14 permits operation to the nearest point at which the safety of passengers is assured where stopping would itself increase the hazard.

Which is exactly the situation a guide faces when weather arrives on a float, since the boat cannot simply stop and the correct answer is the nearest safe take-out rather than the planned one.

Knowing where those points are on every stretch you run is preparation rather than judgment, and it is the sort of thing that gets worked out once and used rarely.

The communication half is telling the clients what is happening in one sentence as it starts rather than after it is resolved.

People tolerate a curtailed day they understood and resent one that simply ended, and the difference is a sentence said at the right moment.

What the shortened day owes them afterwards is a policy question that should already be answered.

Where it gets answered is in the deposit piece.

Where do mornings usually go wrong?

Six ways, and the delayed call is the expensive one.

Making the decision at five and sending it at six, by which point the client is on the road and the refund no longer covers what they lost.

Describing conditions instead of stating a decision, so the client has to work out whether the trip is on.

Asking the client what they would like to do about a safety question, which hands them a judgment that is not theirs.

Softening a marginal forecast, which produces a client who fished a hard day believing they were sold an easy one.

Texting a client who is driving, when the situation needs a phone call.

And introducing operational facts at the ramp that belonged in the confirmation a week earlier.

What the day's record should capture afterwards is set out in the debrief piece.

What is the working morning?

Decide on data, message inside five minutes, no negotiation on safety.

Look at the gauge, the radar and the forecast before anything else, and make the call there.

Send the message immediately, leading with the decision, then the reason with a number in it, then the remedy.

Where the morning is marginal rather than dangerous, state both branches unhedged and let the client choose, since that trade is genuinely theirs.

Where it is a safety question, say once that it is your call, and do not revisit it.

Call rather than text a late client, and know the nearest safe take-out on every stretch you run before you need it.

The statutory basis for the motor carrier rules is 49 U.S.C. 31136, with section 392.14 mirrored on govinfo.

The evening before is handled in the confirmation workflow piece.