Last Verified
Last verified is the timestamp indicating when a specific data field (e.g., role, email, mandate) was most recently confirmed as accurate.
Allocator relevance: A trust and actionability signal—recency determines whether outreach routing and decision-maker mapping is reliable.
Expanded Definition
In allocator datasets, many fields decay quickly: staff changes, emails change, mandates evolve, titles shift. “Last verified” is a core control that prevents users from treating stale data as current. It should ideally be field-level (not just profile-level) and tied to verification status and source confidence.
For Altss use cases, last verified is essential for compliance-minded outreach and for reducing reputational risk caused by mis-targeting.
How It Works in Practice
Systems attach verification timestamps to contacts, roles, mandates, and ownership structures. Change detection can trigger re-verification workflows. Users can filter by recency to prioritize high-confidence targets.
Decision Authority and Governance
Governance defines verification standards (what counts as verified), timestamp rules, and decay policies. Without governance, timestamps become meaningless or misleading.
Common Misconceptions
- A recently updated profile means all fields are current.
- Last verified equals last seen online.
- Recency matters only for emails.
Key Takeaways
- Field-level recency is a core quality metric.
- Users need last verified to manage outreach risk.
- Pair with verification status and source confidence for clarity.