Blog / Sales operations

Build a territory list review that catches stale accounts for the quarter-start review

A quarter-start territory review that gives every account one owner, one recent touch, and one written keep-or-release decision.

Sales Development Rep Editorial Team · Published · 8 min read

Build a territory list review that catches stale accounts for the quarter-start review article cover

The control this territory list review needs

A territory list review control earns its place when a new reviewer can apply it without reopening a chat thread. The first design question is which decision the territory review exists to support on a normal Tuesday. The territory queue should make the next decision obvious rather than collect another activity row.

Good territory list review controls reduce the number of times the same question gets a different answer. A short rule is easier to defend than a policy that only appears during onboarding. Start with the owner, because an unsigned territory review cannot be escalated cleanly across a shift.

A control that survives staff turnover is worth more than a longer form nobody finishes. The territory queue works when the newest reviewer can pick up an item and name the next owner. Keep the scope narrow enough that one person can own the territory queue without a second tracker.

What the territory review record must show

The note should say what was checked, not just that a check happened. Write the source version beside the decision so a later change stays visible. A dated observation is worth more than a current screenshot that cannot show what the note said earlier.

Two fields usually settle a territory review: whether the origin matches the system and whether the named approver still holds authority. A short note with four specific fields usually beats a long narrative with one buried fact. The record is complete when the reviewer can tell what would have counted as a different answer.

A cross-reference to the source entry saves the next reviewer a search through old threads. Missing, unavailable, and confirmed negative values belong in separate fields. Every territory review needs an observation time, because a later reader cannot infer it from context.

Where the SDR’s work stops

For this step, the written action is to record the account, owner, last touch, and reason for keeping it. When the boundary moves, tell the SDR on the same day the rule changes. The note should show that an escalation happened and who received it.

Escalation is a normal step, not a failure of the territory review process. Write the boundary in the same place the work is assigned and reviewed. A prepared packet is a question waiting for an answer, not an approval in itself.

An SDR who guesses at territory list review turns a small gap into an escalation. Keep the scope narrow enough that one person can actually own the weekly decision. The queue should name the manager who decides account reassignment and any change to quota coverage, not just the department.

Use the related specialist service as a starting point for scope and evidence.

The daily territory list review routine

The routine should make the next reviewer faster rather than merely busier. Small habits carry the territory list review routine: date the origin, initial the check, state the next action, and never copy a familiar value. End each shift with a dated note naming what moved, what stalled, and who checks next.

For this step, the written action is to confirm the account still fits the territory rule. The daily routine is short: open the list, confirm the origin, log the exception, and leave a named next action. Start with the oldest unresolved item, because age turns a small gap into an escalation.

A consistent daily start time makes the queue easier to trust across shifts. The SDR should leave each territory review with a date and a next step. Judgment stays with the sales manager; the SDR records only what was checked and when.

Exceptions that should stop the case

The SDR should never invent a resolution to keep the territory queue moving. The queue should show the reason an item stopped, not just that it stopped. The safest exception rule is the one a new hire can apply on day one.

If an exception has no owner, it will sit until it becomes urgent. A stop condition that is not written down is discovered only after something goes wrong. For this step, the written action is to record the account, owner, last touch, and reason for keeping it.

The next shift should be able to act on the entry without calling the SDR who prepared it. The note should say who was notified and when, even when the answer was no. Exceptions deserve a shorter path to the decision maker, not a longer form.

U.S. Small Business Administration provides public guidance that can help test workflow assumptions.

How to confirm and close

The resolution rule should stay stable across the quarter-start window. For founders and revenue leaders, a defensible resolution is worth more than a fast one. The resolution note should say what was confirmed and by whom.

Reopened accounts are a useful signal about where the routine is weak. Keep the resolution rule fixed for the review window so the comparison means something. The note should distinguish a confirmed resolution from an assumed one.

Close the territory review only after the destination note shows the approved change. A second pair of eyes is worth the time on any territory list review exception. For this step, the written action is to confirm the account still fits the territory rule.

Common questions

How old is too old for a territory account?

Use a written window, such as two touch cycles, and apply it to every account in the review.

Who decides whether an account stays?

The sales manager keeps the reassignment decision; the SDR supplies the dated touch history.

Turn the guidance into a controlled role

Bring the workflow, systems, current owner, and known exceptions. We will help shape a focused first handoff.

Plan a consultation

Related field notes

Continue building the system.

Set a lead response standard the team can measure for the following cycle

A response standard that names the start event, the window, the channel, and the exception Revisit the rule with one current example before the following cycle.

Write a discovery note that names the next step for the following cycle

A discovery note that records the buyer's words, the need, the next step, and the owner Revisit the rule with one current example before the following cycle.

Build a handoff from SDR to account executive for the following cycle

A handoff that records the qualification, the buyer's words, the next step, and the AE's acceptance Revisit the rule with one current example before the following cycle.