How to Allocate Quota Across Territories

Most quota allocation is arithmetic. Take the company number, add a buffer, divide by rep count, adjust for a few loud complaints. The result is a plan where a third of the roster is structurally unable to attain and another third clears quota by February.

The allocation should follow potential, and potential should be modeled from data you already have.

What should quota allocation actually be based on?

Allocate quota in proportion to modeled territory potential, adjusted for pipeline already in place and for rep ramp status. Rep count, historical quota, and last year's actuals are all worse bases.

Historical quota compounds past errors. If a territory was over-assigned last year and missed, growing that number by 15 percent bakes the error in permanently. Last year's actuals reward under-assignment, since a rep who cleared 140 percent of an easy quota gets a bigger number and one who missed a hard quota gets relief.

Modeled potential breaks that loop. It answers what this specific set of accounts can realistically produce this year, independent of who owned it before.

How do you model territory potential?

Score each account for expected revenue, sum the scores by territory, then apply segment conversion rates. The inputs are already in your CRM. The age adjustment is the step most models skip. ORM sees 10 percent or more of a typical pipeline untouched for twelve months, and only about 20 percent of the value carrying in-quarter close dates on day one of a quarter actually closes in that quarter. A territory whose potential score is driven by aged pipeline will be assigned a quota against revenue that is not coming.

Use closed-won average deal size in the model rather than pipeline average deal size. The gap is routinely large. A pipeline averaging $80,000 against $40,000 closed-won deals is the shape of the problem. Allocating quota off the pipeline figure doubles every territory's assignment against reality.

How much should total assigned quota exceed the company target?

Enough to cover the gap between the plan and what the roster actually delivers. That buffer covers attrition, ramping reps who fall short, and territories that underperform their model.

Set the buffer from your own attainment distribution rather than from a rule of thumb. If 70 percent of your reps hit quota in a typical year and the average attainment across the roster is 85 percent, the buffer needs to cover the 15-point gap plus expected mid-year departures.

Over-assignment has a cost that does not show up in the model. Reps compare notes. When the sum of individual quotas visibly exceeds the company number by a wide margin, the plan reads as padding, and reps discount their own targets accordingly. The buffer stops working the moment nobody believes it.

How do you handle territories at different maturity stages?

Phase the quota across quarters to match when the territory can actually produce, rather than splitting the annual number evenly. Even quarterly splits are the most common source of predictable first-half misses.

Three cases that need phasing:

1. New territory, no pipeline. A rep starting with an empty book needs a full sales cycle before the first close. Set Q1 quota near zero, step up through the year, and load the annual number into the back half. 2. Ramping rep on a developed territory. The book can produce, the rep cannot yet. Use a ramped quota that steps with the ramp curve. 3. Mature territory with concentrated pipeline. Where a small number of large deals carry the number, phase quota to match the expected close timing rather than spreading it evenly. Otherwise a single deal slipping one quarter creates a miss and an overachievement in adjacent periods, which tells you nothing about performance.

Seasonality belongs in the phasing too. Across ORM's customer base, Q2 and Q4 run stronger than Q1 and Q3, and the third month of a quarter runs stronger than the first two. A flat quarterly split fights that pattern in both directions.

How do you validate the allocation before locking it?

Convert every territory quota into a required pipeline number and check whether that pipeline can exist. A quota that requires more pipeline than the territory can generate is a scheduled miss.

The check:

Required pipeline = territory quota x coverage ratio

ORM's benchmark range for pipeline coverage runs 3x to 5x, with most customers near 3.5x and outliers as low as 1.4x. Use your own historical ratio at the point where the team last hit plan.

Then compare against supply. Current qualified pipeline in the territory, plus what marketing has committed to deliver into it, plus what the rep can self-source at their historical rate. Any territory where the required number exceeds the supply by a wide margin needs one of three fixes: lower the quota, redirect demand generation, or move accounts into the territory.

Run this check per territory rather than in aggregate. A company at 3.5x overall can easily hold four territories at 1.5x, and those four reps will miss no matter what the company dashboard says. Coverage in aggregate hides composition, which is the argument in why the 3x pipeline coverage rule is wrong.

What should you do when a territory quota is clearly wrong mid-year?

Fix it if the error is structural, and hold it if the gap is execution. Distinguishing the two requires looking at the book, not at the rep.

Structural errors have a signature. The territory's actual conversion rates match the company average, activity volume is normal, and the book simply does not contain enough addressable revenue to reach the number. That is a planning mistake and leaving it in place teaches the team that the plan is arbitrary.

Execution gaps look different. Comparable territory potential, below-average activity, longer stage durations, a win rate beneath the segment norm. Adjusting quota there removes the signal that management needs.

Handle structural fixes through relief on the individual quota while holding the company number, funded from the over-assignment buffer. That is what the buffer exists for. Consult sales forecasting best practices for how the adjustment should flow into the forward forecast rather than being absorbed silently.