Executive contact record standards for relationship continuity

Relationship data

Key takeaways

• Capture name, organization, role, owner, last interaction, open promise, next action, and source date.
• Apply this control: search duplicates, compare conflicts, retain attributable history, and restrict sensitive notes.
• Escalate if records identify different owners or a merge would erase a commitment.

Operating data

Playbook

A useful executive contact record preserves relationship continuity without becoming an unbounded personal dossier. Keep name, organization, role, relationship owner, last substantive interaction, open promise, next action, and source date. Include only context that serves a legitimate business workflow, and separate verified facts from notes that may be outdated or interpretive.

Search before creating a record and compare email, organization, and prior activity before merging. HubSpot's duplicate-record guidance explains duplicate management capabilities; human review remains necessary when similar names represent different people or when two records contain distinct commitments that must survive consolidation.

Stop a merge when records identify different owners, conflicting employers, or promises that cannot be attributed safely. Route the conflict to the relationship owner. Restrict sensitive notes and remove material that lacks a defensible purpose. An assistant should not infer personal preferences, health information, or relationship strength from casual correspondence and then present that inference as settled data.

Audit duplicates resolved, stale actions, missing owners, removed notes, and records verified after a role change. The standard succeeds when a backup can continue an authorized follow-up without guessing. Operations follow-through can own next actions, while the stakeholder cadence guide explains how trustworthy records inform respectful outreach rather than automated noise.