Birthday and Holiday Client Touches
Builds guide sites for a livingPublished July 22, 2026Last updated July 26, 202634 min read
- 45 CFR 164.514(b)(2)(i)(C) puts birth date on the eighteen-item identifier list alongside social security numbers, biometric identifiers and full face photographs, because a date resolves to one person.
- Collect month and day rather than a full date unless an operational requirement genuinely needs the year, since the year is what turns a birthday into a birth date.
- 5 CFR 2635.204(a) allows gifts of $20 or less per source per occasion and $50 per person per calendar year, and excludes cash and investment interests entirely.
- That exclusion is the argument against gift cards: a thing is a gift and an amount of money is a transaction, and a card against your own trips reads as a discount.
- The message must contain something only the two of you know, which requires a one-line note written on the drive home, not remembered a year later.
- Pick the anniversary of their first trip or their season opening rather than December, where the message competes with forty others.
Federal health privacy rules list eighteen things that have to be stripped out of a record before it stops counting as identifiable. Social security numbers are on it. Biometric identifiers are on it. Full face photographs are on it. So is birth date.
None of which reaches a fishing guide, and all of which is worth knowing before you build a birthday email. The regulation is not saying birth dates are secret; it is saying they are strong enough to point at one person, which is exactly why a birthday message lands and exactly why it goes wrong when handled carelessly. The same body of federal rules also puts a published number on when a gift stops reading as a courtesy. Both are borrowed below as standards of judgment, not as obligations. Nothing here is legal advice. The related material is indexed on the running the business hub.
| A touch | A campaign |
|---|---|
| Sent by you, from your address, to one person | Sent by a tool, to a segment |
| Contains something only you would know | Contains a merge field |
| Asks for nothing | Ends in a call to action |
| Impossible at four hundred names | Trivial at four hundred names |
Why is a birth date treated as an identifier?
Because it points at a person, in combination with very little else.
Section 164.514(b)(2)(i) of Title 45 lists the identifiers that must be removed before health information can be treated as not individually identifiable, and item (C) covers all elements of dates except year for dates directly related to an individual, including birth date.
It sits in the same enumeration as telephone numbers, social security numbers, biometric identifiers including finger and voice prints, and full face photographic images and any comparable images.
The point of the list is not secrecy but resolving power: these are the fields that, alone or combined with what is readily available, narrow a record to one human being.
Which is a useful thing to hold in mind when a booking form asks for a date of birth, because the answer to why are we collecting this had better be better than for the birthday email.
Section 164.514 is carried on the eCFR.
What the intake form should and should not ask is set out in the intake form piece.
Should a guide collect birth dates at all?
Only where there is a real reason, and there sometimes is.
Some licensing regimes price differently by age, some vessels carry age-related requirements, and a minor aboard changes what the paperwork has to say.
Those are real reasons and they justify collecting the date, which then sits in your records with everything else and is subject to whatever your state's law says about it.
What does not justify it is the marketing use, because the marketing use is served completely by month and day, and month and day is a materially weaker identifier than a full date.
Which is the practical translation of the regulation's own logic: the year is what turns a birthday into a birth date.
So the working rule is to ask for the full date only where an operational requirement demands it, and otherwise to record the two fields you will actually use.
Requirements vary by state and by fishery, and this is not legal advice; confirm the current rules with your own state agency before changing what you collect.
Where the record itself should live is dealt with by the spreadsheet CRM piece.
Why this scales badly on purpose. Sixty clients, one birthday message each, at three minutes to write something specific is three hours a year spread across twelve months, or fifteen minutes a month. At four hundred clients the same standard is twenty hours, which nobody does, so the message becomes a merge field and stops being a touch at all. The honest threshold is roughly where you can still remember the day without reading the record: past it, send nothing rather than sending a template. Those figures are stated assumptions about your own time, not a measured result.
What does a birthday message actually say?
One specific thing about their day on the water, and no offer.
The generic version, meaning any message that would work equally well for anybody, is worse than nothing because it announces that a system sent it.
What makes it land is a detail only the two of you have: the fish in the riffle above the bridge, the weather that turned, the thing their son said.
Which is possible only if the trip record holds a note field and you fill it in on the drive home, and impossible otherwise.
Two sentences is the correct length, it asks for nothing, and it does not mention booking, dates, availability or the season.
Adding an offer converts the whole thing into a campaign with a birthday-shaped wrapper, and people can tell instantly.
The exception worth allowing is a photograph from their trip attached with no words about it, which does more than any sentence.
Why the note field is the load-bearing part is covered by the client database piece.
Neither regulation binds you. 45 CFR 164.514 governs covered entities under federal health privacy rules and has no application to a guiding business. 5 CFR 2635.204 governs the acceptance of gifts by executive branch employees and imposes nothing on anyone else. Both are used here as published standards of judgment. State law on the collection and retention of personal data varies considerably and does apply to businesses; confirm the current position in your state with a lawyer before changing what you collect or how long you keep it. Nothing on this page is legal advice.
Is there a number for what a gift should cost?
There is a published one, and it is smaller than most people guess.
The executive branch standards of ethical conduct permit an employee to accept unsolicited gifts having an aggregate market value of twenty dollars or less per source per occasion, provided the aggregate market value of gifts from any one person under that authority does not exceed fifty dollars in a calendar year.
Those numbers exist because somebody had to decide where a courtesy stops and an inducement starts, and twenty per occasion with a fifty annual ceiling is the answer that survived.
The same paragraph excludes gifts of cash, and of investment interests such as stock, bonds or certificates of deposit, from the exception entirely.
Which is the most transferable part of it: a thing is a gift and an amount of money is a transaction, and the regulation refuses to treat the second as the first at any value.
Section 2635.204 is carried on the eCFR.
What a discount does to your rate instead is worked through in the raising rates piece.
So what should a holiday gift be?
Something small, specific, and not redeemable.
The twenty-dollar figure is a useful anchor even though it binds nobody here, because it describes the value at which a gift reads as a courtesy rather than as a claim on the recipient.
A box of the flies that worked on their water last season, a spool of tippet, a decent hat: all under that number, all specific to the relationship, none of them convertible to money.
What fails is the gift card, precisely for the reason the regulation names, since a card redeemable against your own trips is a discount wearing a bow and is read that way.
The other failure is the branded object nobody wants, which is advertising sent at your expense and stored in a drawer.
The test is whether the recipient would have bought it, and a client who fishes will use tippet and will not use a logo keyring.
Postage on sixty small parcels is not trivial, which is the real constraint, and it is an argument for gifts to a shorter list rather than cheaper gifts to a longer one.
Which clients justify it is answered by the repeat rate piece.
What about the framing sentence?
It is the best line in either regulation.
Section 2635.204 opens by noting that even where acceptance is permitted by an exception, it is never inappropriate and frequently prudent for an employee to decline a gift if acceptance would cause a reasonable person to question the employee's integrity or impartiality.
Which is a standard written for the receiving side, and it inverts usefully: before sending anything, ask whether a reasonable person seeing it would think worse of the relationship.
A hat, no. A birthday email with a booking link, yes, because the reasonable observer reads it as a sales contact dressed as a courtesy.
That test is faster and more reliable than any rule about content, and it survives situations no rule anticipated.
It is also the reason to keep gifts to past clients rather than prospects, since a gift to somebody deciding whether to book you is doing something different from a gift to somebody who already did.
The equivalent test applied to messaging is set out in the text scripts piece.
Which holiday, and when?
One in the year, and not December.
A December card arrives with forty others and is looked at for two seconds, which is a poor return on the only annual gesture most guides make.
The alternatives that work are the anniversary of their first trip, which nobody else marks and which the records already know, and the week their usual season opens, which is genuinely relevant.
Either lands in an empty inbox and neither competes with anything, which is most of why they outperform.
Picking one and doing it consistently matters more than which one, because the value accrues over years rather than within a single send.
Where December is right is for a client who is also a friend, in which case send the card and do not think about it as marketing at all.
What the winter mail programme covers instead is set out in the winter email piece.
Does any of it need to be a card?
Physical mail is the strongest channel available and the least used.
A handwritten card is now unusual enough that it is kept, and the entire mechanism is that almost nobody sends one.
Which means the advantage is temporary in principle and durable in practice, since the reason nobody sends them is that they take time and that has not changed.
Three lines in your own handwriting, referencing their actual day, posted in an envelope with a real stamp, outperforms anything you can send electronically by a distance.
The cost is a stamp and four minutes, and the constraint is again the list size, since sixty is possible and four hundred is not.
Addresses are the practical obstacle, because most guides never collect them and asking for one at booking is easy and asking later is awkward.
Adding a mailing address field to the intake form costs nothing and is the enabling step for this whole channel.
What else the intake should capture is set out in the intake form piece.
What should the note field on a trip record contain?
One line, written the same day, about the person rather than the fishing.
The whole birthday practice depends on having something specific to say a year later, and a year later you will remember nothing, which means the note is the practice and the message is just the delivery.
What goes in it is not the fish count, because the fish count is already elsewhere and is not what a person wants recalled.
It is the thing that made the day theirs: that they had just retired, that the son was learning, that they drove eleven hours, that they lost a fish at the net and laughed about it.
One line, written on the drive home or in the truck at the ramp, takes about twenty seconds and is the difference between a message that works and one that does not.
The discipline is that it happens before you get home, because every guide who has promised themselves they will do it in the evening has stopped doing it within a fortnight.
What it must never be is anything you would be uncomfortable with the client reading, since a record you would not want seen is a record you should not be keeping.
That last rule is worth applying literally: write it as though they will one day read it, because occasionally somebody does.
Does any of this work on a client who fished once?
Less than people think, and the effort is better spent elsewhere.
A single-trip client from three years ago receiving a handwritten birthday card is more likely to find it odd than touching, because the gesture is out of proportion to the relationship it refers to.
Proportion is the thing people get wrong here, and it runs in both directions: too little for a client on their ninth season reads as neglect, and too much for a one-off reads as a sales technique.
The workable rule is that the gesture escalates with the relationship, so a one-off gets nothing or at most an email, a returning client gets the card, and a client on their fifth year gets the card and the flies.
Which also solves the list-size problem arithmetically, since the expensive gestures are automatically limited to the small group that has earned them.
The one exception worth making is the client who fished once and clearly wanted to come back but could not, which the record will usually tell you, and who is worth keeping warm.
Everybody else is better served by the winter mail programme, which is designed for exactly that population.
What about a client who had a bad day?
Send it anyway, and say nothing about the day.
The instinct is to skip the person whose trip went badly, on the grounds that a message would reopen it, and the instinct is wrong.
A bad day on the water is usually the weather or the water, both of which the client understood at the time, and silence afterwards is what converts a disappointing trip into a permanent conclusion about you.
What the message must not do is relitigate: no reference to conditions, no explanation, and above all no offer of a discounted return, which reads as an admission and cheapens the gesture.
Two sentences about something good that did happen, because something usually did, is the correct content.
Where the day went badly for a reason that was actually yours, that conversation belongs at the time and not folded into a birthday message a year later.
The separation matters: a courtesy is a courtesy and an apology is an apology, and combining them makes both worse.
How long should any of this be kept?
As long as the relationship is live, and not indefinitely.
A birth date, a home address and a note about somebody's family sitting in a spreadsheet six years after they last fished with you is a liability with no corresponding benefit.
The de-identification logic is instructive here too: what makes the record risky is the combination, and a name with an address and a birth date and a photograph is a substantially different thing from any one of them.
So the practical rule is that when a client comes off the mailing list, the personal detail comes off with them, leaving the trip record with the commercial facts.
Trip records themselves have their own retention needs, driven by tax and by insurance, and those are a separate question from whether you keep somebody's birthday.
State law governs a good deal of this and varies; confirm the current requirements in your state with a lawyer rather than adopting a rule of thumb from anywhere.
How the two sets of records separate is set out in the spreadsheet CRM piece.
Where do these gestures usually go wrong?
Six ways, and the merge field is the first.
Sending a templated birthday message, which announces that a system produced it and is read as worse than silence.
Attaching an offer, which converts a courtesy into a sales contact and fails the reasonable-observer test instantly.
Sending a gift card, which the ethics regulation refuses to treat as a gift at any value and which a client reads as a discount.
Sending branded merchandise, which is advertising posted at your own expense.
Choosing December, where the message competes with forty others for two seconds of attention.
And collecting a full date of birth with no operational reason to hold one, when month and day serve the purpose.
The photograph consent question that sits next to this is dealt with in the photo permission piece.
What is the working practice?
One gesture a year, by hand, asking for nothing.
Collect month and day rather than a full birth date unless an operational requirement demands the year.
Write two sentences containing something only the two of you know, drawn from the note you made on the drive home.
Keep any physical gift small, specific and not redeemable, and use the twenty-dollar anchor as the point where a courtesy starts reading as a claim.
Pick the anniversary of their first trip or their season opening rather than December, and do the same one every year.
Cap the list at the number you can genuinely handle by hand, and send nothing to the rest rather than sending a template.
The statute behind the gift standards is 5 U.S.C. 7353, and the privacy rule is mirrored on govinfo.
How the whole retention picture fits together is set out in the win-back piece.
How this was checked. The treatment of birth date as an identifier comes from 45 CFR 164.514(b)(2)(i)(C), which requires, for the safe harbor method of de-identification, the removal of all elements of dates except year for dates directly related to an individual, including birth date, admission date, discharge date and date of death, together with all ages over 89 and all elements of dates including year indicative of such age, except that such ages may be aggregated into a single category of age 90 or older. The other identifiers named in the same enumeration, including names, geographic subdivisions smaller than a State, telephone numbers, electronic mail addresses, social security numbers, account numbers, biometric identifiers including finger and voice prints, and full face photographic images and any comparable images, come from the surrounding subparagraphs of 164.514(b)(2)(i). Section 164.514 governs covered entities under the federal health privacy rules and has no application to a guiding business. The twenty dollar per source per occasion figure, the fifty dollar aggregate calendar year ceiling, and the exclusion of gifts of cash and of investment interests such as stock, bonds or certificates of deposit, come from 5 CFR 2635.204(a). The observation that even where acceptance is permitted by an exception it is never inappropriate and frequently prudent for an employee to decline a gift if acceptance would cause a reasonable person to question the employee's integrity or impartiality comes from the opening text of 2635.204. Part 2635 sets standards of ethical conduct for employees of the executive branch and imposes nothing on a private business. Both sections were read on the Electronic Code of Federal Regulations on 26 July 2026. State law on the collection, use and retention of personal data does apply to businesses, varies considerably, and was not analysed for this page. Nothing here is legal advice. No response rate, retention lift or benchmark for birthday or holiday client contact is asserted, because no consulted source publishes one for this trade; the time and list-size figures used above 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 previewWhether to collect a birth date at all, what a gift should cost, and why December is the wrong month
Why does a privacy rule matter to a birthday email?
Because it tells you what you are holding. 45 CFR 164.514(b)(2)(i)(C) requires removal of all elements of dates except year for dates directly related to an individual, including birth date, before health information counts as de-identified. It sits in the same list as telephone numbers, social security numbers, biometric identifiers and full face photographic images. The rule binds covered entities and not you; what it supplies is a calibration of how strongly a birth date points at one person.
Should a guide collect birth dates?
Only where there is an operational reason, and there sometimes is: age-priced licences, vessel requirements, or a minor aboard changing the paperwork. The marketing use is served completely by month and day, and month and day is a materially weaker identifier than a full date. Requirements vary by state and fishery; confirm the current rules with your own state agency, since nothing here is legal advice.
What should a birthday message say?
Two sentences containing something only the two of you know, drawn from a note you wrote the same day. The fish in the riffle above the bridge, the weather that turned, what their son said. It asks for nothing and mentions no dates, availability or season. A generic version is worse than silence, because it announces that a system produced it. A photograph from their trip attached without comment does more than any sentence.
How much should a holiday gift cost?
The federal ethics anchor is twenty dollars per source per occasion with a fifty dollar annual ceiling per person. It binds executive branch employees and nobody else, but it describes the value at which a gift reads as a courtesy rather than a claim on the recipient. Flies that worked on their water, tippet, a decent hat. The postage on sixty parcels is the real constraint, and it argues for a shorter list rather than cheaper gifts.
Why not a gift card?
For the reason the regulation itself gives: the exception excludes gifts of cash and of investment interests entirely, at any value, because an amount of money is a transaction rather than a gift. A card redeemable against your own trips is a discount with a bow on it, and clients read it exactly that way. Branded merchandise fails differently, being advertising posted at your own expense and stored in a drawer.
Which occasion works best?
The anniversary of their first trip, or the week their usual season opens. Both land in an empty inbox and neither competes with anything, which is most of why they outperform a December card arriving with forty others. Consistency matters more than the choice, since the value accrues across years. December is right for a client who is also a friend, in which case send the card and stop thinking of it as marketing.
What about a client whose trip went badly?
Send it anyway and say nothing about the day. Silence after a disappointing trip is what turns it into a permanent conclusion about you. The message must not relitigate conditions, explain anything, or offer a discounted return, which reads as an admission and cheapens the gesture. Two sentences about something good that did happen. Where the fault was genuinely yours, that conversation belonged at the time, not folded into a courtesy a year later.
Sources & methods
- 45 CFR 164.514 on the Electronic Code of Federal Regulations, read for the implementation specifications governing de-identification of protected health information, and specifically for the safe harbor method at paragraph (b)(2)(i), which requires the removal of enumerated identifiers of the individual or of relatives, employers or household members, including names, all geographic subdivisions smaller than a State, all elements of dates except year for dates directly related to an individual including birth date, admission date, discharge date and date of death, telephone numbers, fax numbers, electronic mail addresses, social security numbers, medical record numbers, health plan beneficiary numbers, account numbers, certificate or license numbers, vehicle and device identifiers and serial numbers, web addresses, internet protocol addresses, biometric identifiers including finger and voice prints, full face photographic images and any comparable images, and any other unique identifying number, characteristic or code. The section governs covered entities under the federal health privacy rules and has no application to a guiding business.
- 5 CFR 2635.204 on the Electronic Code of Federal Regulations, read for the exception at paragraph (a) permitting an employee to accept unsolicited gifts having an aggregate market value of $20 or less per source per occasion, provided the aggregate market value of individual gifts received from any one person under that authority does not exceed $50 in a calendar year; for the express exclusion of gifts of cash and of investment interests such as stock, bonds or certificates of deposit from that exception; for the rule that an employee may not pay the excess over $20 in order to accept a portion of a larger gift; and for the opening statement that even where acceptance is permitted by an exception it is never inappropriate and frequently prudent for an employee to decline a gift if acceptance would cause a reasonable person to question the employee's integrity or impartiality. Part 2635 sets standards of ethical conduct for employees of the executive branch and imposes nothing on a private business.
- 5 U.S.C. 7353 at the Office of the Law Revision Counsel, cited as the statutory basis for the gift standards in part 2635, together with the 2024 annual edition of 45 CFR 164.514 published on govinfo as an independent copy of the privacy provisions relied on above. State law on the collection, use and retention of personal data does apply to businesses, varies considerably, and was not analysed for this page.
- The 2024 annual edition of 45 CFR 164.514 published on govinfo, used as an independent copy of the de-identification provisions quoted above. No response rate, retention lift or benchmark for birthday or holiday client contact is asserted, because no consulted source publishes one for this trade.
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
Sixty names you can do this for. Not four hundred.
I'm Evan. Handwritten cards keep the clients you have. I build guides the booking site and run the ads that find the next ones. Free preview before you pay a cent.