A territory review is the quarterly check that keeps a working plan from drifting into an unfair one. It is not a redesign. The goal is to confirm the carves still match reality, catch the handful of territories where pipeline, tenure, or TAM has shifted, and make the smallest set of changes that fix the imbalance without reopening the whole plan. Done well, it takes a week of RevOps time and buys the next ninety days of rep trust.
Time: 5-7 business days
A review is not a redesign, and the first ten minutes decide which one you are about to run. Write down what is in scope (balance drift, named-account moves, rep load, coverage gaps) and what is explicitly out of scope (carve dimension changes, quota resets, comp plan edits). Share the one-pager with the sponsoring sales leader before kickoff. If leadership wants to revisit the dimension or the quota math, that is a redesign project, not a quarterly review, and it belongs on a different timeline. Scope creep is the single biggest reason reviews run four weeks instead of one.
Every territory review runs off the same four data cuts, and getting them right on day one saves a week of rework later. Pull pipeline distribution (open ARR, stage, age) by territory, trailing bookings (closed-won, closed-lost, average deal size) for the last four quarters, rep tenure and ramp status, and the TAM refresh (new accounts, dead accounts, segment reclassifications). Normalize them to the same account-ownership snapshot so a rep who switched territories in Q2 does not get credited twice. The output of this step is a single working dataset the rest of the review runs on. If the data is messy, the conclusions will be too.
Rerun the three balance metrics from the original plan: weighted potential, account count, and active load. Compare each territory to the plan baseline and the current team average. Flag any territory that is more than fifteen to twenty percent off on any metric. Drift is normal, drift is the whole reason you review, but the review's job is to separate the drift that is explained (a rep churned, a Tier 1 account acquired a competitor, a market segment collapsed) from the drift that is unexplained (silent shifts in pipeline that nobody flagged). Only the second kind triggers action. Explained drift gets documented and left alone.
Numbers in the carve are only half the picture. Overlay rep performance (attainment, pipeline coverage ratio, win rate) and tenure (months in role, months in territory, ramp status) on the drift table. The patterns that matter: a strong rep in a territory that cannot pay quota, a ramping rep in a territory sized for a top performer, a tenured rep whose book has eroded because the market shifted under them, and a rep about to depart whose territory needs a bridge plan. Review each flagged territory with this overlay before you suggest a move. The reassignment conversation is far easier when the data shows both the territory problem and the person affected.
With the drift table and rep overlay in hand, draft the smallest set of changes that fixes the imbalance. There are only three real moves: reassign accounts between adjacent territories, split a territory that has grown too large or too complex for one rep, or merge two territories that have both eroded. Prefer reassignment first because it is the least disruptive. Only split when the account load genuinely requires two reps and only merge when both territories have fallen below viable size. Document the before and after balance metrics for every proposed move so leadership can see the surgery, not just the result. If you cannot explain a move in one sentence, it is not the right move.
Walk the proposed changes through each sales manager before anyone talks to a rep. Managers see the deal-level context the data cannot: an active opportunity that would stall if the account moved, a relationship that justifies holding a Tier 1 account where the carve says it does not belong, a rep who is about to resign and should not be handed a bigger book. Capture each ask and the decision in a change log. Accept the ones with real evidence, reject the ones that are just preference, and surface the hard trade-offs to the sales leader for the final call. The decision log is what keeps the review from turning into a lobbying contest.
Changes that reps hear about through gossip are changes that get fought. Give every affected rep a short, direct conversation with their manager that covers what is moving, why, what is staying, and what the new quota math looks like. In parallel, push the new carve rules into the CRM so account ownership flips on the effective date without manual edits. The CRM is the source of truth for crediting disputes, and a plan that lives in a spreadsheet while the CRM still routes old accounts to the old owners is a plan that will blow up inside a week.
Close the review by scheduling the next one and updating the exceptions log. The exceptions log tracks every off-cycle change request that came in since the last review (a rep ask, a manager escalation, a Tier 1 acquisition) so the next review starts with a running list of pressure points, not a blank page. Also update the plan artifact itself so the carve rules, named accounts, and quotas on record match what the CRM now enforces. If you skip this step, the plan on paper and the plan in production will drift apart and the next review will start by reconciling them instead of running the actual analysis.
Quarterly is the standard cadence for most B2B sales teams. Volatile markets or heavy new-hire ramps can justify a monthly lightweight check on balance metrics, but the full review with manager walk-throughs and CRM updates belongs on a quarterly rhythm so reps are not constantly recalibrating their books.
A review assumes the plan is mostly right and makes small corrective moves (reassignments, splits, merges) inside the existing carve dimension and quota structure. A redesign changes the dimension, the scoring model, the quota math, or the headcount plan. Reviews run in a week; redesigns run in two to four weeks and happen once a year on the fiscal planning cycle.
Cap total account movement at ten to fifteen percent of the book per quarterly cycle. Beyond that, reps lose working context on their pipeline, forecasts get noisy, and the next quarter stalls. If the data says more needs to move, that is a signal to run a full redesign, not a bigger review.
RevOps owns the analysis and the artifact, sales leadership owns the final decisions on reassignments, and sales managers own the rep-level conversations. If any of the three try to own all three roles, the review either stalls or turns into a political negotiation. Separate the roles explicitly in the scope note.
Most teams use a fifteen to twenty percent band around the plan baseline or team average on weighted potential. Below that, drift is noise. Above that, the territory is no longer running on the same comp math as the rest of the team, which is where fairness complaints and attrition risk start to show up.
A pending or recent departure is one of the few off-cycle events that justify an immediate reassignment outside the review window. For the quarterly review itself, treat the departing rep's territory as an interim-coverage decision: split the book across the two adjacent territories, hold a few named accounts for the backfill, and avoid loading up any one rep with the full orphaned list.
Strkr keeps ownership, pipeline, and territory rules in one system so RevOps can run the quarterly review off a live dataset instead of a stale spreadsheet, and lock changes straight into the CRM when the decisions are made.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
