Territory Realignment Acceptance Checklist
Use this sheet in the meeting where a realignment is approved and again after it goes live. Each line names the evidence to ask for. Tick a box only when the evidence has been seen, not when someone says the work is done.
Territory or region reviewed: ........................................
Review date: .................... Reviewed by: ....................
Before the plan is approved
☐ Patches are compared on agreed measures of potential, workload and capacity, with the source and date of each estimate.
☐ The role hierarchy, territory coverage, record ownership and record access are documented as separate decisions.
☐ Each person type (rep, manager, cross-team collaborator) has a written list of the objects and records they need to see.
☐ The rule for which territory an opportunity counts in is written down, with one worked example.
☐ Regional managers have confirmed the report levels and rollups they need.
☐ The fields and relationships behind each planning view are documented, and one district or patch has been reconciled to an independent account list.
☐ Imported assignment rules and associations were checked using a rule-matched account, a manually associated account, an unmatched account and a deliberate exception.
☐ The plan was rehearsed at representative data volume, with timings and errors kept.
☐ Any workaround was tested as the actual planner, not only as an admin.
☐ The previous associations and owners have been exported so the change can be reversed.
After the change is published
☐ The publish destination and what it was expected to change are recorded.
☐ Expected and actual account associations match for a sample of accounts, compared by Account ID.
☐ Account Owner changes match the approved handoff list.
☐ Accounts with no territory are listed, each with a named owner or a recorded exception.
☐ Accounts in more than one territory are labeled as an approved overlay or removed.
☐ Open opportunities with a blank or unexpected territory are listed and resolved.
☐ Changing a rule-driving field through the user interface, an import and each automation or integration route gives the expected result.
☐ Recent leads entering the territory reached a named salesperson, and queue time was reviewed.
☐ Access was tested while logged in as a rep, a manager and a collaborator.
☐ Unique-account and opportunity totals reconcile with territory and region reports.
☐ Job status, error messages and record counts were reviewed and explained.
Sign-off
Open items and owners: ........................................................
........................................................................................
Approved by: .................... Date: ....................