Choose milestones that matter to the relationship
A milestone register is not a birthday list. It records the moments that shape a professional relationship: a promotion, a new role, a retirement, a major publication, a long tenure, a shared project, or a public recognition. The test is whether acknowledging the moment would be appropriate and meaningful.
Ask the relationship owner which milestones the executive would want to know about. A board member’s new committee role may matter more than a personal anniversary. A customer’s product launch may matter more than a holiday.
The register should reflect the executive’s actual relationship strategy.
Keep the list short. Ten to twenty active relationships with a handful of meaningful milestones is more useful than a database of hundreds of dates that no one reviews. A smaller register is easier to keep accurate and less likely to contain information people did not intend to share.
Capture only what the person shared
Record a milestone only when the person shared it in a professional context or it is publicly announced. Do not infer a pregnancy, an illness, a divorce, or a religion from indirect signals. Sensitive personal events are not relationship data unless the person explicitly offered them.
Note the source and the date. “Mentioned at the March board dinner” is a useful provenance note; it tells the next assistant why the entry exists and whether it is still appropriate to reference. If the source is a public announcement, link to it.
Give the person a way to ask for removal. A short line in the relationship record or a note from the relationship owner is enough. The register should be easy to correct, and the correction should propagate to any reminder or briefing that used the entry.
Set a reminder rhythm, not a card factory
Not every milestone needs a card. Decide the appropriate gesture for each category: a brief note, a call, a mention in a meeting, a small gift within policy, or no action at all. The executive’s time and the relationship’s closeness should drive the choice.
Set reminders at a useful lead time. A retirement may need three weeks for a letter; a promotion may need a note within a week. Put the reminder in the executive’s calendar with the context and a draft, not just the date.
Avoid annual reminders that fire for every entry on the same day. A batch of generic messages is worse than a few thoughtful ones. Group the review by relationship owner so the executive can decide where to invest attention.
Assign recognition to the right owner
The relationship owner should decide whether and how to recognize a milestone. The assistant can draft, buy within policy, and track, but should not substitute for the executive’s judgment about the relationship. A message that is clearly from an assistant may be appropriate for a vendor and inappropriate for a board member.
Coordinate with the organization’s recognition or protocol function. A public award, a donation, or a gift to a public official may trigger policy or disclosure requirements. Check before acting, and record the approval.
If several executives know the same person, agree on one gesture. Three separate gifts from three offices look careless and can create a compliance question. The relationship owner should coordinate across the executive team.
Respect privacy and opt-outs
Keep the register in a restricted location with access limited to the executive and the support team. Do not sync it to a marketing list or a CRM without a lawful basis and a clear purpose. Personal milestones are not lead-scoring data.
Honor a request to stop receiving acknowledgments. Record the opt-out and remove the person from future reminders. If the relationship is professionally important, the executive can still maintain contact without the milestone program.
Review the register for outdated or sensitive entries. A milestone that was appropriate five years ago may now be intrusive, especially after a job change or a public dispute. Delete what no longer serves the relationship, and record the deletion date.
Coordinate with company recognition programs
Separate relationship milestones from employee service awards and customer loyalty programs. Those programs have their own eligibility rules, budgets, and communications. The executive register should not duplicate or override them.
When a milestone overlaps with a company program, let the program lead. The executive can add a personal note if appropriate, but the organization should speak with one voice. Duplicate recognition can embarrass the recipient and confuse the budget owner.
Share only the minimum information needed for coordination. The recognition team does not need the full relationship history. A name, the milestone, the date, and the approved gesture are enough.
Audit the register for staleness
Twice a year, review each entry for accuracy: Is the role current? Is the milestone still relevant? Is the relationship owner still in place?
Is the preferred contact channel still correct? Remove entries that cannot be verified.
Check the reminder history. If a milestone produced no action for two cycles, decide whether to keep it. A register full of ignored reminders trains everyone to ignore the next one.
Measure usefulness, not size. Ask the executive after a quarter which acknowledgments felt right and which felt obligatory. Use the answers to refine the categories and the lead times.
The register is a tool for attention, and attention is scarce.
Background sources consulted for this workflow: Privacy Framework; Governance Resources; Insights.