download dots

🔄 Plan for Someone Leaving or Retiring

Run a book of business without letting a renewal slip. These prompts build what an agent or broker actually needs: every policy with its renewal date, commission you can check, claims tracked from notification to settlement, and a client portal that answers the routine questions. The renewal date does the work, because it is a reminder that repeats every year on its own.
  • Tested prompts
  • Edit for your use case
  • Works across models
  • Save in Taskade
Plan for Someone Leaving or Retiring

Copy

If one of my senior people left tomorrow I would lose clients, because everything is in their head. Build me a continuity app. For each client record the primary relationship owner, any secondary contact who also knows them, and a relationship depth rating showing whether the client would stay if the owner left. Capture the things that are not written down anywhere, such as the client preferences, their history, why cover is arranged a particular way, and who really makes the decisions, as notes against the client. Show me every client where only one person holds the relationship and no secondary contact exists, prioritized by premium. Maintain a handover plan per team member listing their clients, their in-flight work and anything only they know. Add an AI agent that reviews the agency and names the specific single-point dependencies, quantifies the premium at risk behind each, and suggests where to introduce a second contact first. Automate two things: a scheduled annual continuity review, and a prompt to update a handover plan whenever a client is reassigned. Two logins: a team member who maintains their own client notes and plan, and an owner who sees the whole risk picture.

STATUS · LIVE
v1

01 / Spark - intelligence awakens

Plan for Someone Leaving or Retiring

Record relationship depth and undocumented knowledge per client, and prepare handover plans before anyone leaves.

// the spark catches · intelligence awakens · the answer unfolds

In a small agency the relationships live in individuals. This records what only one person knows, so a departure or retirement does not take the book with it.

What's Included

  • Relationship depth per client not just who owns the file.
  • Undocumented knowledge captured which is the real risk.
  • A handover plan per person prepared before it is needed.
  • An assistant that names the single-point dependencies.

How To Use

  1. Record what only one person knows. That is the actual exposure.
  2. Introduce a second contact on key clients well before you need to.
  3. Write the handover plan while the person is still there.
  4. Review it annually. Relationships and people both change.

Use the ownership map from the workload manager, and prioritize with segmentation.