Resource
Published April 20, 2026 by BoogieBoard Bot Β· Updated April 20, 2026
A rep leaves. Every account needs a coverage answer.

A rep leaves. Every account needs a coverage answer.
That is the problem.
Most companies handle this reactively. RevOps pulls lists. Managers make judgment calls. Reps wonder whether accounts are being handed out fairly. Existing customers get nervous. Pipeline gets messy. Reporting gets harder to trust.
It should not work like that.
A rep departure should trigger a known operating plan. The team should already know how accounts will be covered right away, how they will be covered in the near term, and how long-term ownership will be decided. That is territory management.
When a rep leaves, you need to answer three questions fast:
That is the whole job.
Do not start with fairness debates. Do not start with spreadsheet shuffling. Start with coverage.
Not every account has the same risk.
Existing customers and live opportunities come first. They need the clearest answer and the fastest answer. These are the accounts where bad transitions do the most damage.
If you mishandle an existing customer, you create churn risk. If you mishandle a live deal, you create revenue risk. If you mishandle both, the team loses trust in the process.
So the first question is not, βWhat should move?β
The first question is, βWho should cover this account right now, and what is the best long-term answer for it?β
This is where teams get sloppy.
Immediate coverage is one decision. Long-term structure is another.
They are related. They are not the same.
This is the short-term answer.
Who is covering the account now so the customer is supported, the opportunity keeps moving, and the team is not guessing?
This is the bridge period.
Who is covering the account over the next few weeks or months while the company backfills, reshapes the patch, or decides what to do?
This is the durable answer.
Where should the account live once the company is no longer in reaction mode?
If you do not separate these three time horizons, teams make permanent decisions under temporary pressure.
Once coverage is stabilized, you need a clear way to decide the long-term answer.
That is where Balance Goals come in.
Balance Goals are the measurable criteria that define what a healthy Territory or book looks like. They replace gut feel with a shared standard. They tell you what βfairβ means in your business.
That might include:
The exact metrics will vary.
The point is simple: if you have not defined a healthy book in advance, your long-term reassignment decisions will feel arbitrary.
The policy should fit the model you already run.
The Territory stays stable. Coverage changes.
That makes this cleaner. You can assign temporary coverage right away, protect sensitive accounts first, and decide later whether the Territory should stay intact or be adjusted. The structure survives even though the rep changed.
The accounts are tied directly to the rep.
That makes the mechanics messier. Reassignment usually requires direct owner changes, which makes it easier to blur short-term coverage with long-term structure. That is why the policy needs to be even clearer.
But the logic is still the same:
cover the accounts now, protect the highest-risk accounts first, then make the durable decision using your definition of a healthy book.
Use this order every time a rep leaves.
Every account needs an answer right away.
These accounts get first attention because the downside is highest.
Make the short-term plan clear for the rest of the book.
Once coverage is stable, evaluate the long-term fit using your published criteria.
Keep the structure intact, redistribute some accounts, or rebalance more broadly if the departure exposed a real structural issue.
Preserve the old state, the temporary answer, and the final answer. If you do not, later analysis gets muddy.
Managers will always need judgment.
That is normal.
The problem is not discretion. The problem is hidden discretion.
The team should know where manager judgment applies. For example:
If the override logic is not visible, people will assume favoritism.
A rep leaves.
RevOps pulls a spreadsheet. Managers ask for specific accounts. Existing customers get reassigned with no clear logic. Live opportunities move inconsistently. Two weeks later nobody can explain what happened.
That is how trust gets lost.
A rep leaves.
Coverage is stabilized immediately. Existing customers and live deals are handled first. Temporary coverage is clear. Long-term decisions are made using a published definition of a healthy book. Manager discretion is visible. The changes are documented.
That is what good territory management looks like.
When a rep leaves, every account needs a coverage answer.
Some need an answer right now. Some need a different long-term home. All of them need a plan.
The operating model is simple:
If those rules are clear, a rep departure is manageable.
If they are not, every departure becomes a fairness fight.
Policy name: Rep Departure Coverage Policy Applies to: [Sales Team / AM Team / CSM Team / Segment] Coverage model: [Territory-Based / Owner-Centric] Owner: [RevOps / Sales Ops / Sales Leadership] Last updated: [Date]
This policy defines how accounts will be covered when a rep leaves the company.
It answers three questions:
The goal is to protect customers, protect pipeline, reduce unnecessary disruption, and maintain a healthy coverage model.
Use these principles in this order:
Use the following metrics to evaluate long-term fit:
Within [X hours/days] of a rep departure:
Review these accounts first:
For each of these accounts, answer:
Temporary coverage may be assigned in the following ways:
Temporary coverage should not last longer than [time period] without formal review.
Long-term account placement should be decided using:
Possible long-term outcomes:
Managers may override the standard process only for the following reasons:
All overrides must be documented in: [System / Doc / CRM Field / Notion Database]
For every rep departure:
Driver: [Role] Approver: [Role] Contributors: [Roles] Informed: [Roles]
Download or copy the markdown version of this template and paste it directly into Claude, ChatGPT, or your LLM of choice. Then add context about your org:
The LLM will use the template structure and your context to generate a customized version for your specific rep-departure scenario.
Part of BoogieBoard's Territory Planning Resource Library. More templates and guides at boogieboard.ai/resources.