Blog · Territory, capacity and quota planning · Sales teams
A sales territory planning dashboard compares coverage, workload, potential, and account movements across proposed plans. This worked example shows which totals must stay fixed, how to read the tradeoffs, and what changes when capacity increases.
A sales territory planning dashboard compares competing account assignments on coverage, workload, opportunity, and disruption. Keep the account universe and valuation assumptions fixed, then show what changes when ownership or capacity changes. A map can help explain geography, but the decision needs totals that reconcile and a visible list of relationships that move.
Suppose a US industrial distributor needs to relieve an overloaded territory before the next quarter. Its sales operations team has already prepared alternative assignments. The dashboard's job is to compare those supplied plans, with enough account detail to explain the tradeoff.
Use sales territory planning for constructing scenarios and checking assignments. Here, the question is narrower: does the proposed change improve service capacity enough to justify moving customer relationships?
Salesforce's territory-design guidance treats workload balance and coverage as planning considerations and describes using reports and dashboards to communicate assignments. Those are useful review questions regardless of where the scenario files were prepared. Covirage is not affiliated with Salesforce.
The distributor compares its current plan, A, with candidate B. Revenue is trailing annual revenue; potential is management's estimate of total attainable annual account spending, including current business. Potential is a separate measure, not an amount to add to revenue. Required hours cover the coming quarter and include the team's approved service and travel assumptions.
| Account | Annual revenue (USD) | Annual potential (USD) | Required hours | Territory A | Territory B |
|---|---|---|---|---|---|
| A | 120,000 | 240,000 | 60 | East | East |
| B | 100,000 | 180,000 | 50 | East | East |
| C | 80,000 | 120,000 | 40 | East | West |
| D | 90,000 | 160,000 | 40 | West | West |
| E | 60,000 | 100,000 | 30 | West | West |
| F | 50,000 | 80,000 | 20 | West | West |
| Total | 500,000 | 880,000 | 240 |
Each territory has one rep with 120 available service hours for the quarter. These are supplied planning inputs. The sales capacity calculation explains how to establish available time before comparing assignments.
Keep stable account IDs alongside the display names. Define whether an account means a parent company or a location: the Census Bureau's glossary distinguishes a single-location establishment from an enterprise that may contain several establishments. Mixing those units can double count opportunity even when every row has an owner.
Calculate three measures from the rows:
Workload utilization = Required territory hours / Available territory hours
Hours covered = Smaller of required hours and available hours, by territory
Company workload coverage = Sum of hours covered / Sum of required hours
This is a capacity measure. It assumes service work can be scheduled within each territory; it does not prove every account receives every planned visit. Actual account coverage needs account-level completion records.
| Plan | Territory | Accounts | Revenue (USD) | Potential (USD) | Required hours | Available hours | Utilization | Hours covered |
|---|---|---|---|---|---|---|---|---|
| A | East | 3 | 300,000 | 540,000 | 150 | 120 | 125.0% | 120 |
| A | West | 3 | 200,000 | 340,000 | 90 | 120 | 75.0% | 90 |
| B | East | 2 | 220,000 | 420,000 | 110 | 120 | 91.7% | 110 |
| B | West | 4 | 280,000 | 460,000 | 130 | 120 | 108.3% | 120 |
Plan A covers 120 + 90 = 210 of 240 required hours, or 87.5%. Plan B covers 110 + 120 = 230 hours, or 95.8%. Percentages are rounded to one decimal place after calculation; the improvement is 20 / 240 = 8.3 percentage points.
Both plans have 240 available hours. Dividing company capacity by company workload would show 100.0% for both and hide the territory constraint. East's unused hours in B do not automatically serve West's accounts.
The top comparison should include the account movement behind the coverage improvement.
| Review measure | Current A | Candidate B |
|---|---|---|
| Company accounts | 6 | 6 |
| Company revenue (USD) | 500,000 | 500,000 |
| Company potential (USD) | 880,000 | 880,000 |
| Required hours | 240 | 240 |
| Hours covered | 210 | 230 |
| Workload coverage | 87.5% | 95.8% |
| Accounts changing owner from A | 0 | 1 |
| Revenue associated with moved accounts (USD) | 0 | 80,000 |
Account C is the complete movement list. It represents 80,000 / 500,000 = 16.0% of current revenue. That does not mean revenue will be lost; it identifies the customer book exposed to a handoff.
Potential becomes more balanced: the territory difference falls from 540,000 - 340,000 = $200,000 to 460,000 - 420,000 = $40,000. Managers must still judge whether the new owner can serve C and whether West's remaining workload gap is acceptable. Record the transition owner and planned handoff date beside the account row.
Now retain every assignment in A and change only East's available hours from 120 to 160, using approved temporary support. Call this variation C.
| Territory | Required hours | Available hours | Hours covered | Utilization |
|---|---|---|---|---|
| East | 150 | 160 | 150 | 93.8% |
| West | 90 | 120 | 90 | 75.0% |
| Total | 240 | 280 | 240 | 85.7% |
Coverage is 240 / 240 = 100.0%, with no account moves. Company utilization is 240 / 280 = 85.7%, a different denominator. Compared with A, the variation adds 40 available hours and covers 30 additional required hours. Finance needs the supplied support cost before choosing between C and B; this dashboard does not assign a value to capacity that has not been priced.
For every plan, reconcile six assigned account IDs, $500,000 of revenue, $880,000 of potential, and 240 required hours to the frozen table. Check duplicates and missing IDs separately: a matching total can conceal an omitted account offset by a duplicate.
Keep the underlying assumptions beside the summary using the territory plan template. Review compensation effects separately in the sales commission dashboard, because moved revenue alone does not determine payout treatment.
Bring your account assignment file, capacity assumptions, and competing scenario exports to Covirage. Covirage maps the columns; its tools compute and check the comparisons, and the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data.
See territory planning with Covirage for the supporting planning context.
Show account counts, current revenue, estimated potential, required workload, available capacity, and account movements for each territory and scenario. Include company totals and a list of assignment exceptions so managers can verify that an apparent improvement comes from allocation rather than missing accounts.
Define the unit first. Workload coverage can mean required service hours that available territory capacity can accommodate, divided by total required hours. Account coverage instead needs a rule for which accounts receive their required service; the two percentages should have separate labels.
No. A plan can distribute opportunity and service work more evenly without changing demand or conversion. Review the account evidence, transition risks, and sales outcomes after implementation. Potential is an assumption about opportunity, while booked or recognized revenue measures actual business results.