A company record is not one fact
Legal status, location, phone number, website ownership, technology signals and contact roles change on different schedules. A record-level timestamp hides that difference and encourages teams to treat every field as equally current.
Store freshness with the field
For each consequential value, retain the source, retrieval time, match method, confidence and next refresh date. A current registry status does not refresh a phone number, and a live website does not prove a specific person still holds a role.
Use honest states
Verified, uncertain, stale and blocked are more useful than a binary valid/invalid flag. They tell an operator what may proceed, what needs refresh and what should never be inferred. Uncertainty is not a failure when it is visible and actionable.
Design refresh around consequence
High-consequence fields should refresh before CRM progression or outreach. Lower-risk descriptive fields can refresh on a longer schedule. This keeps research cost focused on decisions that affect contact eligibility, opportunity priority and compliance.
The practical outcome
Teams stop asking whether an entire record is current and start asking whether the evidence required for the next action is current enough. That is a smaller, clearer and auditable question.