Workflow & Monitoring
Change Log
A change log is a human-readable list of meaningful updates to a record over time (roles, AUM shifts, contacts, mandate changes).
Allocator relevance: Change logs create timing—lets users engage when something actually changed, not on a calendar guess.
Expanded Definition
Change logs are the user-facing expression of audit trails and change detection. Instead of raw field history, a change log summarizes important updates: “CIO changed,” “email verified,” “mandate updated,” “new co-invest activity.” For outreach and diligence, change logs are the difference between proactive timing and stale targeting.
Decision Authority & Governance
Governance defines what counts as “meaningful,” how to prevent spammy micro-changes, and how to tag changes by impact (routing-critical vs informational).
Common Misconceptions
- Every change should trigger a log entry.
- Change logs replace verification status.
- Change logs are only for product updates, not data updates.
Key Takeaways
- Change logs should summarize high-impact changes only.
- Pair with verification and freshness.
- Great change logs improve watchlist workflow.