A contact data review keeps executive relationship records accurate, necessary, owned, and appropriately restricted. It checks both factual fields and the notes that can create privacy or relationship risk when they are stale, speculative, or excessive.
Define the systems in scope and name the relationship owner and data steward for each record set. Do not export everything into a new spreadsheet merely to make the review easier.
Verify useful fields
Check names, roles, organizations, approved channels, assistant contacts, time zones, pronunciation, and material meeting constraints against reliable sources. Mark uncertainty instead of replacing an old detail with an unverified one.
Use event-based checks before important outreach, travel, board work, or an ownership change. A periodic review cannot catch every role or preference change at the moment it happens.
Minimize sensitive notes
Keep only information needed for a legitimate relationship or operating purpose and allowed by policy. Avoid opinions, inferred personal traits, irrelevant family details, and copied conversation history.
The NIST Privacy Framework offers public resources for businesses. Internal privacy, legal, records, and security owners should define the organization's specific handling rules.
Resolve ownership and access
Assign unresolved duplicates, shared relationships, departed employees, and orphaned lists to a named owner. Restrict editing and viewing according to role, and remove temporary access that no longer has a purpose.
Bring ownership gaps into the office operating rhythm without exposing the sensitive record itself. Move corrections into the authoritative system rather than maintaining a competing clean copy.
Close the review
Record completed corrections, unresolved questions, approved removals, and the next trigger. Apply retention and hold rules before deleting information or an entire record.
Use the translation request workflow when contact preferences require another language or locale. Sample future outreach errors to learn whether the review changed real operating quality.
Define the review purpose and scope
Choose the systems, records, owners, and business purpose before opening a contact-data review. The goal may be preparing for a leadership transition, correcting outreach failures, removing stale event lists, or checking access to sensitive relationship notes. A broad instruction to clean the database can lead people to export data, delete governed records, or rewrite information without authority.
Name the relationship owner and the data steward for each set. The relationship owner understands why the contact matters, while the steward may control fields, duplicates, access, and integrations. When those roles differ, write the handoff.
The assistant can coordinate review tasks without becoming the permanent owner of every executive relationship record.
Verify identity, role, and organization
Check preferred name, formal name where needed, role, organization, assistant contact, approved channels, time zone, and current relationship owner against reliable sources. Mark a field unverified when evidence conflicts. Do not replace an old title with a guess based on a social profile or assume two people with similar names are the same contact.
Record the source and check date for material corrections when the system supports it. This is especially useful before board, investor, customer, candidate, or government outreach. Avoid copying entire public profiles into the record.
The office needs enough verified information to communicate responsibly, not a private archive of everything available online.
Resolve duplicates and fragmented records
Duplicates may reflect different organizations, past roles, personal and business addresses, or separate systems with distinct purposes. Compare identifiers and relationship history before merging. A careless merge can attach private notes or correspondence to the wrong person.
When uncertainty remains, flag the records for the steward instead of forcing a match.
After an approved merge, confirm which record survives, which fields prevail, how links and consent states transfer, and whether integrations will recreate the duplicate. Close old shortcuts and personal lists that no longer have a purpose. The authoritative system should become easier to trust without erasing valid historical context required by policy.
Review relationship notes for necessity
Keep notes that support a legitimate operating need, such as pronunciation, approved channel, meeting constraint, last commitment, or relevant professional context. Remove or correct unsupported opinions, inferred personality, irrelevant family detail, and stale speculation through the approved process. The test is usefulness and permission, not whether a detail is interesting.
Use neutral, attributable language. A note should distinguish what the stakeholder stated, what an authorized colleague confirmed, and what remains uncertain. Avoid labels that can bias future interactions.
If sensitive context belongs in a restricted legal, people, or security system, link the authorized owner rather than copying the detail into a general contact record.
Check channel and communication preferences
Confirm which email address, phone number, assistant, portal, or messaging route is approved for the relationship. A contact may use different channels for scheduling, formal notice, urgent travel changes, and personal communication. Record the distinction only when the stakeholder or relationship owner has established it.
Review subscription, consent, and do-not-contact states according to applicable policy and law. An executive's desire to reach someone does not override required communication controls. The assistant should route questions to privacy, legal, or marketing owners rather than edit consent fields based on an informal request.
Keep operational contact notes separate from promotional lists.
Review access, exports, and integrations
Identify who can view, edit, download, and share executive stakeholder data. Remove access linked to old projects, departed staff, temporary coverage, or roles that no longer need the information. A record can remain important while a former collaborator's access ends.
Use groups and system roles where possible instead of accumulating direct permissions.
Locate exports, local spreadsheets, phone sync, event tools, and integrations that copy contact data. Confirm their owner, purpose, security, and deletion route. Correcting the main system will not fix a stale personal file that still drives outreach.
Do not launch an uncontrolled search across devices; work with security and privacy owners on the approved discovery scope.
Prepare for relationship ownership transfer
When an executive, assistant, or leader changes role, name the new relationship owner and effective date. Prepare a concise handoff with current commitments, communication preferences, relevant professional context, and source links. Exclude private commentary that does not help the new owner act.
The stakeholder should receive a coordinated introduction when the relationship owner approves it.
Close the prior owner's tasks and adjust access without deleting governed history. Confirm who will maintain the record after the transition and how new information will enter the system. A one-time cleanup will decay quickly if the new operating owner remains unclear.
The handoff is complete only when both relationship and data stewardship have somewhere to land.
Maintain data quality after the review
Set event triggers for role changes, returned messages, important meetings, travel, board cycles, and owner transitions. Add a periodic review only where the change rate and sensitivity justify it. The assistant should correct information during normal work when a reliable source appears, rather than allowing a known error to wait for an annual campaign.
Track outreach failures, duplicate creation, stale permissions, and unowned corrections as signals. Avoid a single quality score that hides different risks. A wrong time zone, an unauthorized note, and an old job title need different remedies.
Assign each recurring problem to the intake, integration, training, or ownership change most likely to prevent it.
Keep the final review date and owner visible in the authoritative system.