An executive address book collects years of introductions, conference badges, and forwarded messages. People change roles, companies rename themselves, and phone numbers are reassigned. The record that was accurate at the introduction slowly becomes a source of bounced email and awkward greetings. The decay is invisible until someone needs the contact urgently.
The cost is not only a failed message. A stale contact can cause a misdirected confidential note or a missed follow-up with an important partner. The desk often discovers the problem while preparing for a meeting, which is the worst time to fix it. A routine maintenance pass keeps the book reliable without turning it into a data project.
Define the fields that matter
Decide which fields the desk actually uses: name, role, organisation, email, phone, time zone, and the relationship owner. Add a field for the last verified date so the team knows when the record was checked. Keep free-text notes short and factual. A small set of reliable fields beats a long form full of guesses.
Separate personal contact details from business details and restrict access to the personal fields. Record how the person prefers to be contacted and whether an assistant handles their calendar. Those details prevent the desk from sending a meeting request to the wrong channel. The field list should match how the office actually works.
Assign one owner for the address book
Give one person responsibility for the address book's structure and quality. That person does not have to enter every contact, but they should own the standards and the review cycle. A named owner stops the book from becoming everyone's side project. The owner also decides when a duplicate can be merged.
Give the owner a backup who understands the merge rules and the access restrictions. Document the rules in a short page so the backup can act during an absence. If the address book is connected to a CRM, the owner coordinates with the CRM administrator. One owner does not mean one person does all the work.
Run a monthly duplicate pass
Set a monthly review for duplicate records, starting with the contacts who appear most often in meetings. Match on email address and phone number first, then on name and organisation. Merge carefully and keep the richer history rather than the newer record by default. A duplicate pass should reduce confusion, not erase context.
Before merging, check whether two records represent two people with the same name. A parent and child, or two partners at the same firm, can look like a duplicate. Review the interaction history and the relationship owner before combining. Record the merge so a later reader can see what happened.
Record the merge history rather than deleting the older record outright. A later question about a prior conversation may depend on the history attached to the old entry. Most systems allow a merge that preserves the interaction log. If the system does not, archive the older record and link it to the surviving entry.
Not every contact needs the same scrutiny. Prioritise the people who receive confidential material, approve payments, or represent a key relationship. Verify their role, organisation, and contact details directly rather than relying on an old email signature. Mark the verification date and the source.
Use a short verification message that explains why the desk is checking. Keep it polite and specific, such as confirming the best address for board papers. If a contact does not respond, mark the record as unverified rather than deleting it. The next review can try again.
Retire records with a clear rule
Write a rule for when a contact should be archived or deleted. A bounced address with no replacement, a person who has left the industry, or a relationship that has ended may qualify. Keep the rule simple and apply it consistently. The address book should reflect current relationships, not every introduction ever made.
Archive rather than delete when there is any chance the history matters. Remove personal details that are no longer needed, especially if the relationship has ended. Record the reason and the date. A clear retirement rule protects privacy and keeps the book searchable.
Check whether the address book feeds any mailing list or distribution group. A stale contact in a group can send a confidential note to the wrong person. Review the membership of sensitive groups separately from the general book. The cleanup is only complete when the downstream lists reflect the same decisions.
Connect the address book to the systems that use it
The address book is only one copy of the contact data. Check how it syncs with email, the calendar, the CRM, and any mailing tool. A change in one system should not create a contradiction in another. Name the system of record for each field. Without that rule, every cleanup is undone by the next sync.
Test the sync after a merge or a verification pass to confirm the change propagated. If a field cannot be synced, document where the authoritative value lives. A sync that silently drops a change is worse than no sync at all. For more productivity guidance, see our article on task management for executive assistants and our executive support services.
Key takeaways
- Keep a small set of reliable contact fields with a last-verified date.
- Name one owner and a backup for standards, merges, and access rules.
- Run a monthly duplicate pass and check for same-name different-person cases.
- Verify high-risk contacts directly and mark unverified records honestly.
- Write a retirement rule and name the system of record for each field.