The Late Client Policy

Wage law has a phrase for the guide standing at a ramp at twenty past six for a client who said six. The employee is unable to use the time effectively for his own purposes. It belongs to and is controlled by the employer.

Which is the whole argument in one sentence. Waiting is not the absence of work; it is work whenever the person waiting cannot do anything else with the time. The regulations distinguish being engaged to wait from waiting to be engaged, and a guide holding a ramp for a late client is squarely in the first category. None of this is a rule anybody can enforce on a client, and none of it is employment advice. What it supplies is the reason a late-arrival policy is legitimate rather than petty. The rest of this cluster is gathered at the ops playbooks hub.

What is the distinction?

Whether the time can be used for anything else.

Section 785.15 of Title 29 gives the examples: a stenographer reading a book while waiting for dictation, a messenger doing a crossword while awaiting assignments, a repair man waiting for a customer to get the premises in readiness.

All of them are working during those periods, and the regulation explains why: the periods are unpredictable, usually short, and in either event the person is unable to use the time effectively for their own purposes.

It adds the phrase that carries the whole idea, being that the time belongs to and is controlled by the employer.

Section 785.16(a) supplies the opposite case: periods during which somebody is completely relieved from duty and which are long enough to enable them to use the time effectively for their own purposes are not hours worked.

And it adds a condition that matters here, being that a person is not completely relieved unless they are definitely told in advance that they may leave and need not start until a specified hour.

Part 785 is carried on the eCFR.

Where the meeting time gets set in the first place is covered by the confirmation workflow piece.

Anglers Advantage, MO

Why does that matter for a late client?

Because it names what is actually being lost.

Guides framing a late-arrival policy usually reach for fairness to other clients, or for the fishing, and both are true and neither is the strongest argument.

The strongest argument is that the twenty minutes at the ramp is time the guide is unable to use effectively, which is the regulation's own test, and time already sold.

Which reframes the conversation from a complaint about punctuality into a statement about what the client purchased.

The day was bought as a block of your time, starting at a stated hour, and the block does not move because it cannot: the light, the water and the take-out shuttle are all fixed.

Stated that way, almost nobody argues, because it is plainly true and it is not about them personally.

Stated as a rule about lateness, it invites a debate about traffic.

The same reframing runs through the difficult clients piece.

Southern Tide, VA

What should the policy say?

Three sentences, and the third is the one that does the work.

The day starts at a stated time, meaning standing at the truck rather than arriving in the car park.

Where somebody is late, the day still ends when it was going to end, because the take-out and the shuttle are fixed.

And after a stated interval with no contact, the trip is treated as a no-show under the cancellation terms.

That third sentence is what converts an intention into a policy, and it is the one most operations leave out.

Thirty minutes is a defensible interval for most operations, and the specific number matters far less than having one written down.

All three belong on the confirmation rather than in the terms alone, because the terms are not what anybody reads.

Where those sentences go is set out by the confirmation workflow piece.

Does the day get shorter?

Yes, and saying so in advance is what makes it acceptable.

The temptation is to absorb the lost time by finishing later, which is generous, unsustainable and quietly ruinous across a season.

It also does not work, since the take-out is at a fixed place, the shuttle is arranged, and light runs out on its own schedule.

Which means the honest position is that the day ends when it was going to end, and the client who arrived late gets a shorter day.

Saying that at the ramp, once, without irritation, is enough: we are going to lose the top stretch, that is fine, but I wanted you to know.

What must not happen is discovering the loss at the take-out as a disappointment, which is how a late client becomes an unhappy one.

Where the operation genuinely can run later, doing so is a gift and it should be named as one rather than absorbed silently.

The morning-of communication this belongs to is described by the morning-of piece.

What about a group where one person is late?

The hardest case, and the answer is the group decides.

Three people standing at a ramp waiting for a fourth is the worst version, because the cost is being borne by people who did nothing wrong.

Which makes it their decision rather than yours: we can wait, or we can start and pick them up at the first access, tell me which.

Handing them the choice removes the resentment entirely, since whatever happens next was chosen by the people affected.

It also produces the right answer more often than a guide's judgment does, because groups know their own dynamics.

Where the late person is the organiser, the group will usually wait and should be allowed to without comment.

The one thing to avoid is deciding for them and then discovering that the wait cost the day.

The wider group handling is set out by the group contracts piece.

What does the first hour actually cost?

More than any other hour, on most water.

The reason lateness matters operationally rather than merely administratively is that the hour being lost is almost never an average hour.

On a great many rivers the first light is the best fishing of the day, and it is also the only period with nobody else on the water.

Which means a twenty-minute delay does not cost twenty minutes of a nine-hour day; it costs a disproportionate share of the day's actual value.

Saying that to a late client is worth doing, because it converts an abstract complaint about time into a specific statement about what they missed.

It also explains why the start time was what it was, which most clients have never considered and which makes them punctual next time.

Where the water is genuinely better later, the argument reverses and the start time should reflect that rather than tradition.

Checking which is true for your own water is a season of records rather than an assumption.

Should the policy differ by trip type?

Yes, and the difference is about what cannot be recovered.

A wade trip on accessible water can frequently absorb a late start with almost no consequence, since the plan can be reshaped on the spot.

A float with a booked shuttle and a fixed take-out cannot, because the geometry of the day is set before anybody arrives.

Which means the same operation may reasonably run a relaxed policy for one product and a firm one for another, provided both are stated.

Stating the reason alongside the rule is what stops the firm one reading as arbitrary: this is a float, the shuttle is booked, we have to be on the water by seven.

Clients accept constraints they can see and resent rules that appear to exist for the operator's convenience.

The distinction also helps at booking, since a client who knows one product is time-critical will choose accordingly.

Where a client is habitually late, steering them towards the forgiving product is a quiet solution nobody has to discuss.

What about the shuttle driver?

The invisible party in every late arrival, and they are being paid to wait too.

A shuttle arrangement is a third person's schedule, and a delayed launch pushes their whole day without anybody telling them.

Which is both a courtesy problem and a practical one, since a shuttle driver who has been messed about twice stops being available at short notice.

One message the moment a delay is known costs nothing and preserves a relationship that is far harder to replace than most guides assume.

The same applies to a second guide covering the other boat, who is now standing at a ramp for reasons that have nothing to do with them.

Building that message into the late-client sequence, rather than remembering it afterwards, is what makes it happen.

It belongs in the same two-minute window as the calls to the client.

Why that relationship is worth protecting is set out by the double-booking piece.

When does it become a no-show?

At a stated time, and only after you have called.

The interval is arbitrary and the calls are not: one at the meeting time, one at fifteen minutes, and a decision at whatever your policy says.

Calling rather than texting matters because the person is driving, and a text to a driver may sit unread for an hour.

Where they answer and are twenty minutes away, that is a shortened day rather than a no-show and the conversation is straightforward.

Where there is no answer at all by the stated time, the trip is a no-show and the terms apply, which is exactly why the terms had to exist.

Leaving is the difficult part and it is the correct one, because standing at a ramp for two hours helps nobody and the day is gone regardless.

Sending one message before leaving, saying what time you left and that you tried twice, is worth doing for the record.

How the no-show itself is handled is set out by the no-show piece.

Does the fee ever get charged?

Rarely, and it should exist anyway.

Most guides who write a late policy never invoke it, and conclude from that it was unnecessary, which reverses cause and effect.

A stated start time with a stated consequence produces punctual clients, and the absence of late arrivals is the policy working rather than evidence it was not needed.

Where somebody is genuinely delayed by something outside their control, waiving it costs nothing and is remembered.

Which is only possible if the policy exists, since you cannot waive something you never had.

The judgment worth applying is that a person who called ahead is in a different category from one who simply did not arrive.

Communication rather than punctuality is the thing actually being asked for, and saying so makes the policy easier to write and easier to keep.

What the deposit terms should already cover is set out by the deposit piece.

Is the guide ever the late one?

Occasionally, and the standard is higher.

A guide arriving twenty minutes late has done something categorically worse than a client doing the same, because the client cannot start without them and has no alternative.

Which means the response has to be proportionate and immediate: an explanation, an apology, and a concrete adjustment rather than an intention to make it up.

Extending the day where possible is the obvious remedy and should be offered rather than waited for.

Where it is not possible, a stated reduction is the honest move, and it is far better received than a full-price day that quietly lost an hour.

The reason this matters beyond fairness is credibility, since a guide who enforces a late policy and is themselves unreliable has no policy at all.

Building fifteen minutes of margin into your own arrival is the entire prevention and it costs a quarter of an hour.

The morning routine that buys that margin is built in the daily checklist piece.

What causes lateness?

Bad directions, more often than bad clients.

The largest single cause is a meeting point described the way locals describe it, which is unfindable to somebody who has driven four hours in the dark.

Which is a confirmation failure rather than a punctuality failure, and it is entirely within your control.

A map pin, a note about the last turning, and a warning about the stretch with no phone signal fix most of it.

The second cause is the difference between the time you meant and the time you said: arriving in the car park at six is not standing at the truck at six.

Stating the time as when you want them ready, and saying so explicitly, removes an entire category of twenty-minute delay.

The third is a client who genuinely did not know how far it was, which a drive-time note in the confirmation prevents.

All three are fixed in the same message, which is described by the confirmation workflow piece.

What about the client who is early?

A smaller problem and a real one.

A client arriving forty minutes early finds the guide rigging, unloading and not yet ready to be sociable, which is an awkward start to a day.

Which is worth pre-empting in the same sentence as the start time: there is nothing to do before six, so no need to be early.

Where they are early anyway, giving them something to do is better than either ignoring them or abandoning the preparation.

Carrying gear, sorting a rod or making coffee are all real jobs that read as inclusion rather than as being managed.

The alternative, which is standing about watching somebody work, makes the client feel in the way before the day has started.

None of this is a policy question and all of it is a small piece of the same discipline.

What the first hour should establish is set out by the safety briefing piece.

Where do late policies fail?

Six ways, and having no stated consequence is the first.

Writing a start time with nothing attached to it, so the time is read as a suggestion.

Absorbing the lost time by finishing later, which is unsustainable and teaches the client that the start time is soft.

Discovering the shortened day at the take-out, rather than naming it at the ramp.

Texting a driver instead of calling, so nobody knows anything until they arrive.

Deciding for a group whether to wait, when it is their day being spent.

And describing the meeting point the way a local would, which causes most of the lateness in the first place.

The prevention lives in the confirmation workflow piece.

What is the working policy?

A stated start, a fixed finish, thirty minutes, and two calls.

State the start as the time you want them standing at the truck, with a map pin and a drive-time note, in the confirmation rather than in the terms.

Say plainly that the day ends when it was going to end, because the take-out and the shuttle are fixed.

Set a stated interval after which the trip is a no-show, and put it in writing at booking.

Call at the meeting time and again at fifteen minutes, because the client is driving and will not read a text.

Name the shortened day at the ramp, once, without irritation, rather than letting it surface at the take-out.

Hand a waiting group the choice about whether to wait, since it is their day being spent.

Hold yourself to a higher standard than the policy, and build fifteen minutes of margin into your own arrival.

The statutory basis is 29 U.S.C. 207, with the regulations mirrored on govinfo.

The no-show end of it is handled by the no-show piece.