Stale records fail quietly
Nobody notices a record going out of date. It's noticed later — when a statement goes to an old address, when a renewal reaches a dead mailbox, when a regulator asks when the details were last verified and the honest answer is that nobody knows.
The work required to prevent this is trivial per customer and intractable across all of them. Ask, wait, check, apply. Multiply by the customer list and by a review cycle, and it becomes a project nobody has time to run.
Confirmation isn't the same as no response
The failure mode worth naming: treating silence as confirmation.
When a review is run as a mass email — "let us know if anything has changed" — the absence of a reply gets recorded as an up-to-date record. It isn't. It's an unanswered question, and the distinction matters enormously the first time it's audited.
What Nuncily owns
- It asks each customer specifically about the details you hold, rather than sending an undifferentiated request.
- It reads what comes back and checks it for completeness and for obvious inconsistencies against what you already have.
- It queries anything that doesn't look right in the same conversation.
- It follows up with people who haven't responded — and keeps non-response distinct from confirmation.
- Once an answer checks out, it applies the change to the system of record, with a trail of what changed and on whose word.
What you end up with
A record set where every entry is either confirmed, changed with an audit trail, or explicitly flagged as unconfirmed. Three honest categories rather than one optimistic one.