Occasion calendar
The work is remembering, and then making the remembering cheap to act on. A reminder that
arrives on the day is a reminder that arrives too late: gifts ship, cards need signing,
and a message sent the morning after says exactly what it looks like.
The one rule that governs everything
The gift is specific or it is not a gift. A mug, a generic card, a gift voucher, and
anything with the company logo on it all say the same thing, which is "you are an obligation
that was discharged". Specific means it comes from something the person actually said — a
trip they mentioned three times, a broken thing they keep complaining about, an author they
quoted, a hobby they gave up and miss.
So the calendar is only half the skill. The other half is a running note per person of the
things they said, because you cannot invent specificity on the day.
Procedure
- Build the person list with the dates you can verify. Birthdays, work anniversaries,
and anything they have flagged themselves. Never guess a date: a wrong birthday
celebrated is worse than none, because it proves the record is fiction.
- Keep a two-line note per person, appended whenever they mention something. What they
are into, what they complained about, what they are saving for, what they already have.
This is the only input that makes step 5 possible.
- Work backwards from the date, not forwards from today. Lead times below. The
deadline is "in their hands on the day", so a physical gift's real deadline is the order
date, and that is the date to surface.
- Surface the occasion at the lead time, once, with a concrete proposal rather than a
question. "Dave's ten years is on the 14th, here is the thing, ordered Monday, card
written, you just sign" is actionable. "Dave's anniversary is coming up, any thoughts?"
hands the work back.
- Pick the gift from the note, not from a category. If the note is empty, say the note
is empty and propose the least-generic thing available — consumable and good beats
durable and neutral, and an experience beats an object when you know nothing.
- Draft the card, always. Specific, short, one detail only they would know, signed by
the human. A card is the part that is remembered and it costs nothing but the drafting.
- Log what was given and when. The second-best gift is one they already have, and the
worst is the same gift twice.
- Send the thank-you the same week or not at all. A late thank-you draws attention to
the lateness. Same-week is the whole standard.
Lead times
- Physical gift, needs ordering: surface 10-14 days out; order 5-7 days out.
- Handwritten card only: 4-5 days out.
- Work anniversary requiring anyone else's sign-off (a gift budget, a group card):
3 weeks out. Group involvement is the slowest dependency, every time.
- Flowers or food: 2-3 days out, delivery date named explicitly.
- Condolence: immediately, same day. Nothing about this waits for a good draft, and a
plain sentence sent today beats a considered one sent next week.
- Thank-you: within 3 days of the thing being thanked for.
- A milestone with travel or a booking involved: 6+ weeks.
Registers, which are not interchangeable
- Birthday: warm, light, specific. Never a group email with a list of names.
- Work anniversary: specific about the work. "Five years" is a number; "five years and
you are still the only person who understands the billing exports" is a gift.
- Condolence: short, no advice, no silver lining, no "everything happens for a reason",
no request for a reply. Name the person who died if you knew them. Offer one concrete
thing rather than "let me know if you need anything" — a delivered meal, a covered shift.
- Thank-you: name the specific thing and its effect. Never combine a thank-you with a
new request; that converts the thank-you into a preamble.
- Get well: low-key, no prognosis talk, no expectation of a reply.
- Congratulations on something private (engagement, pregnancy, a diagnosis resolved):
only if they announced it. Second-hand news is not yours to acknowledge.
Hard rules
- Never guess a date and never round one. Unknown is a state you can report.
- Never fabricate a shared memory or a detail in a card. If the note is empty, write
something plain and true rather than something warm and invented.
- Never buy on someone else's behalf without their say on the amount. Money is theirs;
the calendar and the draft are yours.
- Never surface a sensitive occasion in a shared channel. Illness, bereavement, divorce,
and anything about a family member goes privately, always.
- Ask before a public celebration. Plenty of people do not want their birthday
announced, and a surprise is not consent. Record the preference once and honour it.
- Never treat a date as a marketing opportunity. A branded gift on a personal occasion
reads as a transaction, because it is one.
- Do not moralise about a missed date. Say what can still be done today.
Worked example
Note file, accumulated over months from things Dave actually said:
dave — mentioned the alaska fishing trip 3x (may, june, july). complains his flask
"leaks in the truck". drinks coffee black. has enough branded jackets, said so.
10-year work anniversary: 2026-09-14 (confirmed, from HR, not guessed).
gave last year: bookshop voucher (generic — he never mentioned it again).
Surfaced on Sep 1, 13 days out, as a proposal rather than a question:
Dave's ten years is the 14th. Not a mug and not another jacket, he has said so.
He has mentioned that Alaska trip in three separate calls and complains his flask
leaks in the truck: the good insulated flask, engraved, ordered Monday so it is
here by Wednesday. £48 — say yes or say a number.
Card is written, you just sign:
"Ten years, Dave. You are still the only person here who can read the billing
exports without swearing, and you have never once made anyone feel stupid for
asking. Enjoy Alaska — the flask should survive the truck this time."
Three things that make it work: the gift comes from a complaint he voiced rather than a
category, the card names something only a colleague would know, and the decision left for
the human is one word plus a number. Compare "Dave's anniversary is coming up, any ideas?",
which is the same information and none of the work.
Missed-date variant, same day it is noticed:
Dave's anniversary was Monday and we missed it. Do not send a late "happy
anniversary" — send this instead, today, and it lands better than on-time would have:
the flask, plus "Ten years last Monday and I only clocked it on Wednesday, which
tells you how little you make of it. Alaska-proof this time."
Handoff
Return: the occasion, the date, the lead-time deadline that actually matters (order date,
not event date), the specific gift with its reason drawn from the note, the drafted card,
and the one decision left for the human. For a calendar build, return the person list with
verified dates, the unknowns named as unknowns, and the next three occasions with their
lead-time dates already computed.
1---2name: occasion-calendar3description: Keep the human calendar nobody else keeps — birthdays, work anniversaries, condolences and thank-yous — and put a specific gift and a written card in front of someone before it is late. Use this for "when is X's birthday", "what should I get X", "I need a gift for X", "draft a thank-you note", "someone's parent died, what do I send", "who on my team has a work anniversary coming up", or setting up the calendar in the first place. Also use when a date has already been missed and the question is how to handle it.4---56# Occasion calendar78The work is remembering, and then making the remembering cheap to act on. A reminder that9arrives on the day is a reminder that arrives too late: gifts ship, cards need signing,10and a message sent the morning after says exactly what it looks like.1112## The one rule that governs everything1314**The gift is specific or it is not a gift.** A mug, a generic card, a gift voucher, and15anything with the company logo on it all say the same thing, which is "you are an obligation16that was discharged". Specific means it comes from something the person actually said — a17trip they mentioned three times, a broken thing they keep complaining about, an author they18quoted, a hobby they gave up and miss.1920So the calendar is only half the skill. The other half is a running note per person of the21things they said, because you cannot invent specificity on the day.2223## Procedure24251. **Build the person list with the dates you can verify.** Birthdays, work anniversaries,26 and anything they have flagged themselves. Never guess a date: a wrong birthday27 celebrated is worse than none, because it proves the record is fiction.282. **Keep a two-line note per person**, appended whenever they mention something. What they29 are into, what they complained about, what they are saving for, what they already have.30 This is the only input that makes step 5 possible.313. **Work backwards from the date, not forwards from today.** Lead times below. The32 deadline is "in their hands on the day", so a physical gift's real deadline is the order33 date, and that is the date to surface.344. **Surface the occasion at the lead time**, once, with a concrete proposal rather than a35 question. "Dave's ten years is on the 14th, here is the thing, ordered Monday, card36 written, you just sign" is actionable. "Dave's anniversary is coming up, any thoughts?"37 hands the work back.385. **Pick the gift from the note**, not from a category. If the note is empty, say the note39 is empty and propose the least-generic thing available — consumable and good beats40 durable and neutral, and an experience beats an object when you know nothing.416. **Draft the card**, always. Specific, short, one detail only they would know, signed by42 the human. A card is the part that is remembered and it costs nothing but the drafting.437. **Log what was given and when.** The second-best gift is one they already have, and the44 worst is the same gift twice.458. **Send the thank-you the same week or not at all.** A late thank-you draws attention to46 the lateness. Same-week is the whole standard.4748## Lead times4950- **Physical gift, needs ordering:** surface 10-14 days out; order 5-7 days out.51- **Handwritten card only:** 4-5 days out.52- **Work anniversary requiring anyone else's sign-off** (a gift budget, a group card):53 3 weeks out. Group involvement is the slowest dependency, every time.54- **Flowers or food:** 2-3 days out, delivery date named explicitly.55- **Condolence:** immediately, same day. Nothing about this waits for a good draft, and a56 plain sentence sent today beats a considered one sent next week.57- **Thank-you:** within 3 days of the thing being thanked for.58- **A milestone with travel or a booking involved:** 6+ weeks.5960## Registers, which are not interchangeable6162- **Birthday:** warm, light, specific. Never a group email with a list of names.63- **Work anniversary:** specific about the work. "Five years" is a number; "five years and64 you are still the only person who understands the billing exports" is a gift.65- **Condolence:** short, no advice, no silver lining, no "everything happens for a reason",66 no request for a reply. Name the person who died if you knew them. Offer one concrete67 thing rather than "let me know if you need anything" — a delivered meal, a covered shift.68- **Thank-you:** name the specific thing and its effect. Never combine a thank-you with a69 new request; that converts the thank-you into a preamble.70- **Get well:** low-key, no prognosis talk, no expectation of a reply.71- **Congratulations on something private** (engagement, pregnancy, a diagnosis resolved):72 only if they announced it. Second-hand news is not yours to acknowledge.7374## Hard rules7576- **Never guess a date and never round one.** Unknown is a state you can report.77- **Never fabricate a shared memory or a detail** in a card. If the note is empty, write78 something plain and true rather than something warm and invented.79- **Never buy on someone else's behalf without their say** on the amount. Money is theirs;80 the calendar and the draft are yours.81- **Never surface a sensitive occasion in a shared channel.** Illness, bereavement, divorce,82 and anything about a family member goes privately, always.83- **Ask before a public celebration.** Plenty of people do not want their birthday84 announced, and a surprise is not consent. Record the preference once and honour it.85- **Never treat a date as a marketing opportunity.** A branded gift on a personal occasion86 reads as a transaction, because it is one.87- **Do not moralise about a missed date.** Say what can still be done today.8889## Worked example9091Note file, accumulated over months from things Dave actually said:9293```94dave — mentioned the alaska fishing trip 3x (may, june, july). complains his flask95"leaks in the truck". drinks coffee black. has enough branded jackets, said so.9610-year work anniversary: 2026-09-14 (confirmed, from HR, not guessed).97gave last year: bookshop voucher (generic — he never mentioned it again).98```99100Surfaced on Sep 1, 13 days out, as a proposal rather than a question:101102```103Dave's ten years is the 14th. Not a mug and not another jacket, he has said so.104105He has mentioned that Alaska trip in three separate calls and complains his flask106leaks in the truck: the good insulated flask, engraved, ordered Monday so it is107here by Wednesday. £48 — say yes or say a number.108109Card is written, you just sign:110111 "Ten years, Dave. You are still the only person here who can read the billing112 exports without swearing, and you have never once made anyone feel stupid for113 asking. Enjoy Alaska — the flask should survive the truck this time."114```115116Three things that make it work: the gift comes from a complaint he voiced rather than a117category, the card names something only a colleague would know, and the decision left for118the human is one word plus a number. Compare "Dave's anniversary is coming up, any ideas?",119which is the same information and none of the work.120121Missed-date variant, same day it is noticed:122123```124Dave's anniversary was Monday and we missed it. Do not send a late "happy125anniversary" — send this instead, today, and it lands better than on-time would have:126the flask, plus "Ten years last Monday and I only clocked it on Wednesday, which127tells you how little you make of it. Alaska-proof this time."128```129130## Handoff131132Return: the occasion, the date, the lead-time deadline that actually matters (order date,133not event date), the specific gift with its reason drawn from the note, the drafted card,134and the one decision left for the human. For a calendar build, return the person list with135verified dates, the unknowns named as unknowns, and the next three occasions with their136lead-time dates already computed.