Territory Management

Define sales territories by region and segment while keeping ownership and overlap visible. The screen connects Territories and Rules so sales teams can find the “Create territory” action while checking territories and coverage.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as US Enterprise · Maya and EMEA Mid-market · Jon, rather than an empty visual shell.

Territory Management
Use this template in Figr

Template facts

Screen

Workspace

Primary action

Create territory

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Sales teams need a clear “Create territory” action without losing sight of territories, coverage and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Create territory is clearly available where the task happens.
  • Main view: Territories keeps the starting point obvious.
  • Connected view: Rules supplies nearby context.
  • Metric: Territories is visible with a meaningful value.
  • Another signal: Coverage helps people judge what to do next.
  • Representative record: US Enterprise · Maya makes the example specific.
  • Second record: EMEA Mid-market · Jon shows the pattern works beyond one item.

States worth designing

  • First-use workspace; show what people can do instead of leaving a blank panel.
  • Loading territories without changing the layout unexpectedly.
  • Unavailable or restricted panel; explain the problem and preserve work.
  • Permission denied for rules; clarify who can continue.
  • Success after choosing Create territory; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Territories → Rules → Create territory → Review outcome

Patterns used

Workspace, Territories, Rules, Coverage, accessible states, contextual actions

Why these choices work

Keep the main job visible above supporting panels. Group related controls and surface exceptions where people act.

In this design, people should be able to compare US Enterprise · Maya with EMEA Mid-market · Jon. Make territories clear, then use coverage to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Create territory” action. The happy path alone is not enough.

Related UI examples: Sales Forecasting, Revenue Operations, Contact Import.

Start from this in Figr

Design a territory management screen for our existing software product. Use our real design-system tokens, components and product language. Show Territories and Rules, include believable records such as US Enterprise · Maya, and make create territory easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr