Making the Annual Trip a Tradition

Federal privacy regulation contains a definition of when somebody stops being your customer. One trigger is that you have not communicated with them about the relationship for twelve consecutive months, and it says expressly that promotional material does not count as communicating.

Read that twice if you send a newsletter. The rule governs financial institutions and reaches no fishing guide anywhere, but the standard it sets is the one that matters for anybody trying to turn a client's trip into an annual event: a year of silence ends a relationship, and marketing is not the cure because marketing is not a communication about the relationship. The same section also defines what annual means, and the definition is about consistency rather than about the calendar. Both are borrowed below. Nothing here is legal advice. Everything adjacent to it sits under the running the business hub.

What does the regulation say about annual?

That you pick the period, and then you have to keep it.

Section 1016.5(a)(1) of Title 12 requires a notice not less than annually during the continuation of the customer relationship, and then defines the word: annually means at least once in any period of twelve consecutive months during which that relationship exists.

It continues with the part that transfers: you may define the twelve-consecutive-month period, but you must apply it to the customer on a consistent basis.

Which is the whole architecture of a tradition compressed into a sentence, since a tradition is not a frequency but a period applied consistently to one person.

The section's own example anchors to the customer rather than to the calendar, noting that where a customer opens an account on any day of year one, the notice is due by the end of year two.

Section 1016.5 is carried on the eCFR.

The measurement side of all this is worked through in the repeat rate piece.

Big Crappie, TX

When does somebody stop being a client?

Twelve months of silence, and promotional material does not count.

Paragraph (b) of the same section lists the events that turn a customer into a former customer, and among them is that you have not communicated with the customer about the relationship for a period of twelve consecutive months, other than to provide annual privacy notices or promotional material.

The carve-out is the important half, because it says plainly that sending somebody marketing is not the same as being in touch with them.

Which is a harder standard than most guides apply to themselves, since the newsletter going out four times a winter feels like contact and by this test is not.

What counts is communication about the relationship, meaning something addressed to that person about the thing you did together.

One message a year that meets that test, and the relationship persists; four broadcasts that do not, and by this measure it has ended.

A message that clears that bar is drafted in the text scripts piece.

Capt Steve Friedman, FL

What actually makes a trip annual?

A fixed anchor that is not you.

Clients do not maintain traditions with businesses; they maintain them with dates, seasons and people, and the guide's job is to attach the trip to one of those.

The strongest anchor available is a calendar date they already keep, meaning a birthday, an anniversary, the week they always take off, or the weekend a group already gathers.

The second strongest is a natural event, being a hatch, a run or an opening, which has the advantage of being genuinely interesting and the drawback of moving by three weeks in a bad year.

The weakest, and the one most guides rely on, is the client remembering that they enjoyed it, which is not an anchor at all.

Which anchor a given client has is usually discoverable by asking them once, in the boat, why they picked that week.

The answer goes in the record and it is the single most useful field you will ever fill in.

The column it belongs in is built in the spreadsheet CRM piece.

When should next year be booked?

At the takeout, and the reason is not sales pressure.

A date proposed at the end of a good day is accepted at a rate no later ask approaches, and the reason is that the value is present rather than remembered.

Three weeks later the same client is at a desk, the day has compressed into a photograph, and the decision is now abstract.

What makes the takeout ask work is that it names the same week next year rather than asking whether they would like to come back.

Same week next year, shall I pencil you in, is a question with two answers and no arithmetic in it.

Pencilled is the right word, because it commits nothing and creates a record, and a pencilled date confirmed in January is the mechanism by which a tradition actually happens.

The phrasing that works is set out in the end-of-trip ask piece.

What does the consistent basis requirement translate to?

Contacting each client on their own clock, not on yours.

The regulation lets the institution choose the twelve-month period and then requires it to apply that period to the customer on a consistent basis, which is a rule against drifting.

Applied here, it means a client who fishes in June hears from you on a June cycle and a client who fishes in October hears from you on an October cycle.

Running everybody on the same winter cycle is simpler and it is the reason the June client gets a January email about a season they were already going to book and nothing whatever in the month that matters.

The per-client version costs nothing extra once the trip dates are recorded, since the cycle is derivable from the record rather than maintained by hand.

Sorting the client list by anniversary month once and working down it is the whole implementation.

Which is also why the broadcast newsletter cannot do this job: a broadcast has one clock and traditions have as many clocks as there are clients.

What the broadcast is for instead is set out in the winter email piece.

Does the group version work differently?

Yes, and it is more durable and more fragile at once.

A group trip that has run four years has an internal momentum no individual booking has, because the participants hold each other to it and the organiser's reputation is attached.

It is also fragile in a way individual bookings are not, since it dies the year the organiser cannot make it work rather than the year the fishing is poor.

Which means the guide's job with a group is to reduce the organiser's workload rather than to sell to the group.

Holding the same weekend without being asked, proposing it in writing in October, and giving them a date to release it by, removes most of the work that kills these.

The other durable move is knowing a second name, because a group whose only link to you is one person ends when that person moves.

Asking who else should be on the confirmation is a small ask that buys the group's survival.

How group bookings should be papered is covered in the group contracts piece.

What about priority?

Give it, state it, and honour it without being asked.

A tradition needs the date to be available, and the date being available is entirely within your control.

Holding a returning client's usual week until a stated release date each year is the single strongest retention instrument available to a guide and almost nobody does it.

It costs nothing when they take it and costs one held week for a few weeks when they do not, which is a small price for the effect.

What makes it work is that it is told to them: your week is held until the fifteenth of December, no need to reply before then.

An unannounced hold does nothing, because the client cannot rely on something they do not know about.

The release date matters as much as the hold, since an indefinite hold is a week you cannot sell and cannot count on.

The mechanics of it are set out in the priority booking piece.

What happens when a year is missed?

Treat it as a gap, not an ending, and say so.

A client who misses a year has usually had something happen rather than decided anything, and the guide's response determines whether year three exists.

The failing response is silence, which by the standard at the top of this page is precisely what converts them into a former client.

The working response is a message in the usual month of the following year that treats the gap as unremarkable: your week is here again if the year is kinder.

No reference to the missed year, no note of regret, and nothing that requires them to explain themselves.

Which matters because the commonest reason for a missed year is something they would rather not discuss, and an invitation to explain is a reason not to reply.

A tradition survives one gap comfortably and rarely survives two, which is why the message in the gap year is the load-bearing one.

The broader version of this is dealt with in the win-back piece.

Should the trip stay the same?

Mostly, and the small variations are what stop it going stale.

The sameness is the point: the same week, the same water, the same shape of day is what makes it a tradition rather than a repeat purchase.

What should change is one element a year, usually a different stretch, a different technique or a different target, which gives the client something to have done this time.

Announcing that in advance is worth doing, since it converts the booking from another day on the river into this year we are going to do the upper section.

The risk on the other side is real: a client on their sixth identical day starts to wonder, and the wondering happens quietly and shows up as a year missed.

One deliberate change a year, chosen by you and told to them in the confirmation, is the whole treatment.

What the day itself should contain is set out in the trip inclusions piece.

How long does a tradition take to form?

Three bookings, and the second is the one at risk.

A first trip is a purchase, a second is a preference, and a third is a habit that will now run on its own until something breaks it.

Which means all the effort belongs between the first and the second, where almost nobody spends it, because the second booking is the one that has no momentum behind it at all.

After the third, the client's own expectation does most of the work and your job narrows to holding the week and not disappointing them.

Before the second, there is nothing operating except whatever you built at the takeout and whatever contact happened over the winter.

That asymmetry is worth acting on directly: a client who has fished once gets more attention than a client who has fished six times, which feels backwards and is correct.

The six-time client needs one message and a held week; the one-time client needs the anchor established and the second date proposed.

Does the price move?

Yes, and predictably, which is the part that protects the tradition.

Freezing a returning client's rate forever feels generous and quietly poisons the arrangement, because the gap widens every year until the day the correction has to happen all at once.

A correction of a hundred and fifty dollars arriving in year six reads as a betrayal in a way that twenty-five dollars a year never does.

What works is telling them the shape rather than the number: rates move a little most years, and your week stays your week.

Which is an honest description of a small annual increase and it removes the anxiety that a rate rise is aimed at them specifically.

The genuine concession worth making to a long-standing client is not a lower rate but a longer hold, better dates and first refusal, all of which cost you far less.

A client on their eighth year almost never leaves over money and quite often leaves over losing their week.

What should be remembered between years?

Three things, and none of them is the fishing.

Who came with them, what the occasion was, and one detail about the person that is not about angling.

A guide who opens the year with how did the knee turn out has done something no amount of marketing achieves, and it costs a line in a record.

The fishing detail matters less than people assume, partly because the client remembers it better than you do and partly because it is the part they can get anywhere.

What they cannot get anywhere is being known, and being known is the entire difference between an annual trip and an annual transaction.

The practical form is one line written the same day, kept with the trip record, and read for ninety seconds before any contact.

Reading it before you call is the step people skip, and skipping it wastes the whole practice of writing it down.

Where the record itself belongs is set out in the client database piece.

Where do traditions usually break?

Six ways, and the anchorless booking is the first.

Never attaching the trip to a date the client already keeps, so the only thing holding it up is their memory of enjoying it.

Asking at the wrong moment, weeks after the day, when the value has compressed into a photograph.

Running every client on one winter cycle, so the June client hears from you in January about a season they had already decided on.

Mistaking the newsletter for contact, when a broadcast is the one thing the standard at the top expressly excludes.

Not holding the week, so the tradition dies the year somebody else books it.

And going quiet after a missed year, which is the exact behaviour that converts a gap into an ending.

How the touches through the year should be handled is set out in the client touches piece.

What is the working practice?

One anchor, one hold, one message on their clock.

Ask in the boat why they chose that week, and record the answer, because it is the anchor everything else attaches to.

Propose the same week next year at the takeout and pencil it, then confirm it in January.

Hold each returning client's usual week until a stated release date, tell them you are doing it, and honour it without being asked.

Contact each client on their own twelve-month cycle rather than on a single winter one, which the trip records already make possible.

Change one element of the day each year and tell them what it is in advance.

Where a year is missed, send the usual message in the usual month and say nothing about the gap.

The statute behind the annual notice requirement is 15 U.S.C. 6803, with the regulation mirrored on govinfo.

What all of it is worth is calculated in the repeat rate piece.