hardScenarioDesignMidSeniorStaff
A relative telephones to tell you a customer has died. Walk me through everything your systems have to do from that call onwards.
6 min readUpdated 2026-08-15Target archetype: Enterprise Captive
Answer
Short answer
Death is a change to the person, not an instruction on one account, so it has to be recorded once and propagate to every product, mandate and communication. The hard parts are acting on an unverified notification, separating authority to inform from authority to distribute, and stopping outbound contact at once.
Was this answer helpful?
Likely follow-ups
- The notification turns out to be wrong and the customer is alive. What does reversing it involve?
- A joint account holder dies. What changes on that account and what deliberately does not?
- How would you handle an estate where one product is in credit and another is in arrears?
- Where does an attorney's authority end and an executor's begin, and how does your system enforce the gap?
Related questions
- You are moving a bank's existing accounts onto a new core platform. How do you cut over so there is never a moment when a customer's true balance is unknown?hardAlso on mandates6 min
- Events for a daily revenue table arrive up to three days late. How do you design the pipeline and the backfill?hardSame kind of round: design4 min
- You serve millions of prompts an hour and the LLM bill doubled. Where does the money go, and what do you cut?hardSame kind of round: scenario5 min
- Your RAG assistant cites the wrong document, and sounds completely sure of itself. How do you find which stage failed?hardSame kind of round: scenario5 min