What’s a Fair Holdover Policy and How Do You Write One

A Territory changes. A rep wants to keep an account or opportunity that would otherwise move.

That is where Holdover Policies come in.

A Holdover Policy lets a rep keep an account or opportunity during a Territory change because it meets defined criteria. The goal is simple: reduce disruption without undermining the future-state Territory Model.

But here is the important disclaimer:

Not all holdovers are good.

In many companies, holdover opportunities have lower close rates than people expect. They often represent deals that already should have closed, or weak pipeline that someone wants to protect. The exception is longer sales cycles. That is why a fair Holdover Policy should be narrow, clear, and skeptical of opportunity quality.

Start with the right mindset

Less is usually more.

A Holdover Policy is not supposed to be a giant side door around your Territory Model. It is supposed to be a limited tool for protecting specific situations during change.

If too many accounts or opportunities get held over, your future-state model stops being real. Reps are technically moved, but the work is still sitting in the old structure. That creates confusion, slows adoption, and makes reporting messier.

Start with this rule:

Use holdovers sparingly. Prefer Account Locking when the account truly should not move.

What holdovers are actually good for

1. Protecting live deal continuity

If a real opportunity is far enough along, moving it immediately can be disruptive. A Holdover Policy can give the current rep a short period to finish what they started.

2. Protecting strategic situations

Some accounts or opportunities are too sensitive to move just to achieve balance. Strategic relationships, renewal timing, major support issues, or executive sponsorship may justify temporary protection. Often this is better handled with Account Locking Criteria, but holdovers can still play a role if timing matters.

3. Giving reps some agency

A clear Holdover Policy can give reps one defined vehicle for input instead of forcing all feedback into side conversations.

But it should not be the only vehicle.

Reps should already have input into Territory quality, target account logic, and Account Locking Criteria. Their only shot at being heard should not be “please let me keep this one.”

Be careful with opportunity holdovers

This is where teams get sloppy.

The existence of an open opportunity does not automatically mean it should be held over.

A fair policy should define real thresholds, such as:

• stage requirement
• minimum amount threshold
• required data completeness
• manager approval
• expiration date

That is the key distinction.

A weak policy says: any open opp stays.

A fair policy says: only clearly defined opps that meet real criteria stay, and only for a limited time.

Prefer time-boxed holdovers

If you allow holdovers, put a clock on them.

A good Holdover Policy answers:

• what qualifies
• who approves it
• how long it lasts
• what happens when the clock runs out

For example:

A rep may retain ownership of a qualified Stage 3+ opportunity above [$X] for up to 90 days after Territory go-live. After that, the account and opportunity transfer to the new owner unless an approved exception is documented.

Without a time box, holdovers linger. Then the Territory change is technically done but not really done.

Use Account Locking when the account truly should stay put

This is the simpler answer in many cases.

If an account really should not move, lock it.

If the account has an active renewal, a support issue, a meaningful executive relationship, or some other strong reason to stay with the current rep, Account Locking Criteria is usually cleaner than a temporary holdover. That preserves continuity without creating a second transition later.

That is why the default should usually be:

• lock the account if it should stay
• use a holdover only if a temporary bridge is truly needed

Make the policy painfully clear

A Holdover Policy should be published with ultra-clear rules.

Reps should know:

• what qualifies
• what does not qualify
• how many requests are allowed
• who approves them
• how long approved holdovers last
• when the holdover ends
• how the final transfer will happen

A good policy reduces politics. A vague one creates resentment.

The simplest test

A fair Holdover Policy should be small.

If the policy is so broad that large parts of the future-state model are suspended, it is too big.

A fair Holdover Policy is usually one of these:

• a small number of account requests per rep
• a strict opportunity threshold with manager review
• a short holdover window after go-live
• a narrow exception category for strategic situations

That is enough.

The takeaway

A fair Holdover Policy should do one thing well:

limit disruption without undermining the Territory Model.

That means:

• use holdovers sparingly
• be skeptical of opportunity quality
• prefer Account Locking when the account truly should stay
• use real qualification thresholds
• put a clear expiration date on every holdover
• give reps some agency, but not only through holdovers
• publish the rules with total clarity

If you do that well, holdovers stay practical.

If you do not, they become a mess.

---

Holdover Policy Template

Policy name: Holdover Policy Applies to: [Sales Team / AM Team / CSM Team / Segment] Owner: [RevOps / Sales Ops / Sales Leadership] Last updated: [Date]

1. Purpose

This policy defines when a rep may temporarily retain an account or opportunity that would otherwise move during Territory redesign or Territory change.

The goal is to reduce disruption without undermining the future-state Territory Model.

2. Decision principles

Use these principles in this order:

• holdovers should be rare
• Account Locking Criteria is preferred when the account truly should stay put
• opportunity-based holdovers must meet clear quality thresholds
• all holdovers must have an expiration date
• all holdovers must be documented and approved
• rep agency should exist elsewhere in the Territory Planning process, not only through holdovers

3. Account holdover rules

A rep may request an account holdover only if the account meets one or more of the following criteria:

• [Strategic relationship criterion]
• [Renewal timing criterion]
• [Support / escalation criterion]
• [Executive sponsorship criterion]
• [Other approved criterion]

Account holdovers last until: [date / duration]

At expiration, the account will:

4. Opportunity holdover rules

An opportunity may qualify for holdover only if it meets all required criteria below:

• minimum stage: [Stage]
• minimum amount: [$]
• required fields complete: [Yes / No]
• manager approval: [Required / Not Required]
• close date within: [X days / months]
• other criteria: [Add]

Opportunity holdovers last until: [date / duration]

At expiration, the opportunity will:

5. Rep request limits

To prevent overuse:

• each rep may request up to [X] account holdovers
• each rep may request up to [Y] opportunity holdovers
• exceptions require approval from [Role]

6. Approval workflow

1. Rep submits holdover request.
2. Manager reviews against policy criteria.
3. RevOps confirms qualification and documentation.
4. Final approver: [Role]
5. Approved holdovers are recorded in: [CRM / Notion / Report]

7. Expiration and transfer rules

All approved holdovers must include:

• holdover start date
• holdover end date
• future-state owner
• transfer process at expiration
• approving manager
• documented reason

8. Reporting requirements

Track:

• total number of holdovers approved
• total number of holdovers denied
• holdovers by rep
• holdovers by manager
• average holdover duration
• close rate of holdover opportunities
• number of expired holdovers that required extension

Use With AI

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:

• whether holdovers apply to accounts, opportunities, or both
• what criteria define a real strategic exception in your business
• how long your average sales cycle is
• what stage or amount thresholds should apply
• whether reps are allowed a fixed number of requests
• when a holdover should expire and transfer

The LLM will use the template structure and your context to generate a customized version for your specific Holdover Policy scenario.

Part of BoogieBoard's Territory Planning Resource Library. More templates and guides at boogieboard.ai/resources.