Better territories begin with a better definition of work.
Medical device territory alignment assigns accounts, geography, and selling responsibilities across representatives so coverage demands fit the team’s capacity. It decides who owns an account and who supports it. Account prioritization decides what that person should work on next.
Those questions are connected, but a balanced map does not produce a useful call plan on its own. A representative needs enough time to cover the patch, relevant opportunities to investigate, and the context to start a credible conversation.
This guide proposes a practical planning framework for medical equipment and device teams. Adapt the assumptions to your product and sales motion. A capital-equipment rollout, a surgical-device territory, a diagnostics workflow, and a dental dealer patch should not inherit the same visit model.
01 · Diagnose the account mix before drawing boundaries.
Use one row per selling location and keep parent organizations separate. Record whether purchasing responsibility is local, shared, centralized, or still unknown. Do not assume a location’s public brand tells you who controls the purchase.
Separate existing customers, verified evaluations, researched prospects, and accounts excluded by contracting or coverage rules. A prospect whose product fit is uncertain should not carry the same weight as an active project with an agreed next step.
| Dimension | Record | Challenge |
|---|---|---|
| Ownership | Rep, support roles, parent relationship, exceptions | Who is accountable for the next action? |
| Workload | Expected visits, demonstrations, travel, service coordination | Does the rep recognize the estimate? |
| Opportunity | Verified projects and evidence-backed fit, separately | What is confirmed versus inferred? |
| Access | Known procurement, access, or contract constraints | Is a realistic path still open? |
| Continuity | Existing relationships and live evaluations | What would an account transfer disrupt? |
02 · Equal account counts can hide unequal workloads.
A patch of established customers may require more ongoing time than an equally large patch of prospects. The reverse can also be true when prospecting involves long travel or specialist demonstrations. Make the assumptions visible, then let the field team correct them.
The example below starts with 50 accounts per representative and an invented monthly time budget. Explore how transfers and service effort change the workload. This is a worksheet, not a territory optimizer or an industry benchmark.
Both reps have 50 accounts. A needs 80 hours; B needs 60. Move the sliders to compare a different alignment.
At the default assumptions, moving five customer accounts makes both workloads 70 hours. That is one possible comparison, not a recommendation to transfer those specific relationships. Account potential, access, skill, and continuity may justify keeping an uneven workload.
03 · Compare the baseline with one realistic alternative.
Keep the existing alignment intact while reviewing a proposal. List every moved account, the reason, the receiving owner, and any specialist responsibilities. Compare account hours, travel assumptions, known projects, and relationship disruption side by side.
Salesforce’s territory-planning documentation demonstrates scenario comparisons using account attributes and options for balance, continuity, and drive-time compactness. It is a useful implementation reference; it does not supply a universal objective for every device team. See the source.
For an imaging team, check whether a proposed boundary separates account development from an active site evaluation. For a surgical team, check how specialist support is shared. For a diagnostics team, distinguish a named facility from the organizational buying relationship. Treat these as review questions for the team, not facts discoverable from a map.
04 · Plan the handoff before moving the account.
Document the effective date, outgoing and incoming owner, open opportunity, last conversation, promised follow-up, support commitments, and relationship context. Resolve account-credit questions internally before the change reaches the customer.
Keep an exception register with an owner, reason, and review date. A useful exception is explicit and revisited; an invisible exception makes the model look cleaner than the field reality.
01 · Check coverage
02 · Challenge the proposal
05 · Give the new owner a reason to act.
After assigning responsibility, prioritize accounts using product relevance, recent changes, evidence quality, and a next question. A public expansion announcement can justify research. It does not establish an open equipment decision or purchasing intent.
Read our medical device buying-signals guide for that evidence-to-question workflow. The dental equipment territory guide provides a narrower product example.
Balance workload. Preserve relationships. Review the model with the people working the territory, keep uncertain inputs visible, and agree in advance how the new alignment will be evaluated.
What should a manager review after the change?
Choose a review window before activation. Compare the assumed coverage work with actual demands, inspect missed follow-ups and account conflicts, and ask reps which assignments created friction. Review accepted research findings and qualified next steps separately from raw activity counts.
A single universal visit cadence or account quota would hide too much variation. Record your own baseline and change one assumption at a time so the next iteration teaches you something.
Sources, assumptions, and product scope.
- Salesforce Trailhead: Create an Optimal Territory Alignment — primary documentation for account comparisons and selected optimization attributes.
- The worksheet, numerical example, and review method are Readout’s proposed planning framework. They are not measured medical-device benchmarks.
Readout is exploring medical device account-intelligence pilots, building on dental research. The public dental demo illustrates account research; it does not reassign CRM accounts, optimize routes, or publish territory boundaries.
Bring one market into focus.
Tell us the device category, territory, and account question you want to test.