Client Contracts Beyond the Waiver

A waiver handles injury. It does almost nothing about the six other ways a trip goes wrong, and most guides have no document that does.

Somebody cancels four days out. A party of six shrinks to three on the morning. A client damages a rod. Two anglers turn up drunk. A corporate booking wants an invoice and thirty day terms. Somebody objects to a photograph appearing on your site. None of those is a liability event and none of them is what a release was written for, yet every one of them costs money and every one of them is resolved by whatever you happen to say at the time. The document set that handles them is short, unglamorous and almost entirely absent from this trade. Tools that collect and record any of this are compared at the booking software topic page.

Why does the waiver not cover this?

Because it was written to do one job and this is a different one.

A release addresses claims arising from harm. Booking terms address what each of you owes the other commercially, which is an entirely separate relationship between the same two people.

Guides conflate them because both are paperwork signed before a trip, and because the waiver is the only document anybody told them to have.

The practical result is that the commercial side of every booking runs on custom and goodwill, and works perfectly until the one occasion it does not.

That occasion is not usually a dispute. It is a conversation at six in the morning where you have to decide something on the spot with somebody who is already unhappy.

Having decided it in advance is the entire value, and the document is just the place the decision is written down.

Boneafide, FL

Fish 409, TX

What do booking terms need to say?

Six things, and most guides can draft the substance in an afternoon.

What the deposit is, when it is due, and whether it is refundable, stated as a date rather than as a vague window.

What happens when the client cancels, with a cutoff, so that late and early cancellations are treated differently and everybody knows which is which.

What happens when you cancel for weather, because a policy that only covers the customer cancelling reads as one-sided and creates a worse conversation.

What happens when a party changes size, since a boat cleared for six and boarded by three is a commercial question rather than a logistical one.

What is included in the price and what is not, which prevents the most common minor dispute in this trade entirely.

And when the balance is due and how, since that single sentence removes the awkward moment at the end of a day.

Where should the terms actually live?

At the point of booking, visible, not linked from a footer.

Terms nobody read are terms that produce an argument, and a link at the bottom of a page is a link nobody follows.

The version that works is short enough to sit on the booking page itself, in plain language, with a tick box that records agreement. Published booking tools from about $39.95 a month handle that natively, and Checkfront publishes a monthly figure plus a charge on each reservation, so what it costs to record agreement can be worked out in advance.

That records the agreement and, more usefully, means most people actually see it, which is where the practical protection comes from.

Most people who cancel late genuinely did not register that timing carried a consequence, and a visible sentence at checkout prevents a real share of it.

Where a booking page should be and what else it must do is set out in the website piece.

What about damage to your equipment?

Worth a sentence, and worth being generous about in practice.

Rods get stood on, reels go overboard, and somebody eventually closes a hatch on something expensive.

A term establishing that a client is responsible for loss or damage to equipment caused by their own conduct gives you a position, which is different from always using it.

Most guides will write off most breakages, and having the term does not oblige you to charge, it simply means that the one time you do it is not a negotiation from nothing.

The version that reads well distinguishes ordinary wear and accidents inherent to fishing from carelessness, because charging for a snapped tip on a good fish would cost you the customer.

What that gear actually costs to run, and how quickly it depreciates, is set out in the wader fleet piece.

Do you need conditions of carriage?

A short version, and it exists mainly to make one conversation possible.

Every guide eventually meets a party who arrive intoxicated, refuse a lifejacket, or behave in a way that makes the day unsafe.

Settle your response before it happens and you can deliver it evenly, instead of constructing a position mid-argument on a cold morning.

A short statement that you may end a trip for behaviour that compromises safety, and what happens to the money if you do, is the whole of it.

Most operators never invoke it and the ones who have all say the same thing: having it written made the conversation shorter.

Handling the safety conversation early enough that none of this arises is the subject of the briefing piece.

What about photographs?

A consent line, and it protects the thing your marketing depends on.

Photographs of real clients holding real fish are the most valuable marketing asset a guide produces, and most are used without any recorded permission.

A single line at booking asking whether images from the trip may be used promotionally, with an easy no, settles it before anybody is on the water.

Almost everybody says yes, and the ones who do not are usually people with a specific reason you would have wanted to know about anyway.

Asking afterwards works and produces worse results, because somebody enjoying a good day says yes readily and the same person by email a fortnight later does not reply.

Why your own photographs matter more than any other visual asset is set out in the photographs piece.

What changes for a corporate booking?

Nearly everything about the commercial arrangement, and it needs its own document.

A company booking several trips wants an invoice, a purchase order reference, payment terms and somebody's name on an agreement, none of which your ordinary booking flow produces.

They may also want liability wording their own people have looked at, and a cancellation position negotiated rather than imposed. Platforms are no help here: even one publishing its full fee structure describes deposits and refunds rather than negotiated terms.

That is genuinely a different transaction, and treating it like a larger version of a normal booking is how guides end up unpaid sixty days after a trip.

The practical minimum is a written scope, a payment schedule with dates, a cancellation position, and clarity about who signs waivers and when.

What those arrangements should contain is set out in the group contracts piece.

What about a subcontracted guide?

A separate agreement again, and it is between you and them rather than the client.

Everything above concerns the relationship with a customer. The moment somebody else runs a trip under your name, a second relationship exists and it needs its own terms.

Who holds the insurance, who collects the money, what happens if they cancel, whose waiver applies and who the client belongs to afterwards are all live questions.

None of them is difficult to settle in advance and all of them are unpleasant to settle after a season of assumptions.

The classification question sitting underneath it, and its consequences beyond paperwork, belongs with an accountant before the first payment.

Everything belonging in that document is itemised in the subguide agreements piece.

Does any of this interact with permits?

Indirectly, and one federal scheme reaches your records.

Agencies authorising commercial operations on public land can require access to permit records, and the public land scheme states this broadly.

It provides that records may be examined whether held by you, your employees, your business affiliates or your agents, and that requests may come up to three years after a permit expires.

That reaches booking records and agreements sitting inside a platform or with a bookkeeper, which is worth knowing before assuming a document is somebody else's problem.

What each agency asks for differs, and the rules move quietly. Pull the exact current requirements from whoever administers the ground you work rather than trusting a summary of any kind.

The public land permits piece goes through that scheme properly.

What does a cancellation cutoff actually need?

A date, a consequence, and a reason the customer can see.

Most cancellation policies fail because they state a rule without explaining it, and a rule without a reason reads as arbitrary at exactly the moment somebody is unhappy.

One sentence explaining that a day released inside a week cannot usually be refilled turns a policy into a fact about the business, which people accept far more readily.

The cutoff itself should reflect how long it actually takes you to resell a date, which differs enormously between a destination fishery and a busy inshore market.

Setting it by copying another operator is the common approach and produces a number unrelated to your own ability to refill.

Work out how many days notice you genuinely need, then set the cutoff there and say why.

What that deposit should be to make the policy bite is set out in the deposit sizing piece.

What happens when you are the one cancelling?

The part of the policy that earns you goodwill, and most operators leave it out.

A booking policy covering only the customer's cancellation reads as one-sided, and customers notice, particularly the ones weighing you against another guide.

Stating plainly what happens when you call a day for weather, and being generous about it, costs you nothing on the days it does not happen and buys considerable trust on the days it does.

The version that works offers a straightforward choice: a full refund or a rescheduled date, decided by the customer rather than by you.

That also removes an argument, because the customer with a choice has nothing to negotiate and the conversation ends in a minute.

Weather is the single largest cause of a lost day in this trade, so this clause gets used more than any other in the set.

Salvaging value from a day you have just stood down is the subject of the recovery piece.

How do you handle party size changes?

By pricing the trip rather than the person wherever you can.

A per-angler price creates a live commercial question every time somebody drops out, and it produces the awkward morning conversation this whole page exists to avoid.

A trip priced as a trip, up to a stated maximum, removes the question entirely: four people or two, the day costs what it costs.

That is not always possible, and for genuinely per-seat operations the terms need a minimum charge stated at booking rather than negotiated later.

Either way, the decision belongs at booking rather than on the dock, since a party discovering the position at six in the morning has every incentive to argue about it.

Stating it plainly also tends to reduce shrinkage, because a group knowing the price is fixed has less reason to let somebody quietly drop out.

Where per-seat pricing genuinely matters, and how software handles it, is set out in the charter software piece.

Should the terms be short or thorough?

Two versions, because they are read by different people at different moments.

The short version exists to be seen at checkout by somebody who has already decided to book and is not going to read a page of conditions.

Six or seven lines covering the deposit, the cutoff, weather, party size, what is included and when the balance is due does the whole job at that moment.

The thorough version exists for the rare occasion something is disputed, and for a corporate client whose procurement people actually will read it.

Trying to make one document serve both produces something too long to be seen and too thin to rely on, which is the commonest failure in this whole area.

Link the long from the short, and treat the short one as the piece that does the practical work every day.

Nobody has ever lost a booking because the terms were clear, and plenty have lost a morning because they were absent.

What is the one term guides most often omit?

When the balance is due, and it costs more than any of the others.

A deposit is usually stated because a platform collects it. The balance is frequently left to custom, which means the awkward moment happens at the end of every trip rather than once.

Stating it plainly at booking, whether the balance is taken automatically beforehand, charged on the day or collected at the dock, removes that moment entirely.

It also removes the quiet leakage that comes from a guide who under-collects after a slow morning rather than have the conversation.

That leakage is invisible because it never appears as a dispute, and across a season it is frequently larger than the cancellations everybody worries about.

Whichever mechanism you choose, tell the customer in the confirmation as well as in the terms, because a charge somebody expects is a charge that does not fail.

How the payment side interacts with the trip itself is set out in the prepay versus deposit piece.

What would you actually do?

Write the substance yourself, then have somebody qualified look at it once.

Spend an afternoon writing, in your own words, what you would want to happen in each of the situations at the top of this page. That is the substance and nobody knows it better than you.

Then have counsel admitted where you operate turn that into wording you can rely on, which is a much smaller and cheaper job than asking them to invent your policy.

Put the short version on the booking page where people see it, and keep the longer version somewhere you can send.

Review it in the same annual sitting as the waiver and the insurance schedule, because the same changes to your operation affect all three.

And keep the deciding rule in mind throughout: these documents exist so that a decision is made calmly in advance rather than badly at six in the morning.