The module defines territories along any combination of dimensions the business sells across: postal geography, sales region, country and continent, named-account lists, industry vertical, account size band, product family and channel. Each territory is a precise, non-overlapping definition, and every account, lead and opportunity resolves to exactly one owning territory through the rules engine rather than through manual tagging. Assignment rules evaluate account attributes in a defined order of precedence, so that a strategic named account routed to a global account team always outranks the geographic rule that would otherwise place it in a regional patch.

Around this core sit the operational disciplines that make territories usable. Balancing analysis measures the load carried by each territory against configurable fairness metrics: account count, addressable revenue, active pipeline, historical bookings and travel density, then proposes reallocations that even out the distribution. Quota allocation takes a target set at any level of the hierarchy and distributes it downward using weighted drivers such as installed base, market potential and prior attainment, with the ability to override any node and have the remainder redistribute automatically. Coverage analysis surfaces white space: accounts with no owner, segments that are thinly staffed, and overlaps where two definitions inadvertently claim the same account. Effective-dated changes let the organisation restructure for a new fiscal period while the current structure stays live until the switchover date.

At the heart of the module is the idea of a territory: a defined slice of the market with a single accountable owner. A territory is not merely a shape on a map but a rule-bound claim over a population of customers and prospects, expressed through the criteria that qualify an account into it. Territories nest into a hierarchy that mirrors the sales organisation, so that a seller's patch belongs to a district, the district to a region, and the region to a division, and any figure defined at one level, coverage, pipeline or attainment, aggregates cleanly up the branches above it.

Ownership is the second organising concept. Each territory carries a primary owner and may carry supporting roles: overlay specialists, technical resources and managers who inherit visibility down their branch. Because assignment is governed by rules rather than by hand, the relationship between an account and its owner is always explained by a traceable reason, and when an account's attributes change, its territory is re-evaluated and, where warranted, reassigned. The third concept is the quota: a commitment attached to a territory for a period, connected to the owner responsible for it and to the target above it from which it was apportioned. Every quota knows its parent, so the organisation can always demonstrate that the parts sum to the whole. Around these run the temporal records that make the structure auditable: who owned what, under which rule, carrying which number, during which period, so history is never lost when the map is redrawn.

The recurring cycle is the periodic territory plan. An operations lead opens a new planning version as a working copy of the live structure, revises boundaries and rules, runs balancing and coverage analysis against the proposal, and reviews the projected impact on every affected owner before anything takes effect. The plan moves through review and sign-off, then activates on its effective date, at which point account ownership, quota and reporting lines all cut over together and the prior version is retained as history.

Alongside the planning cycle sit the continuous, in-flight workflows. When a new account enters the suite, the rules engine assigns it immediately and notifies the owner. When an account is disputed, a structured reassignment request routes to the relevant managers for adjudication, with the decision and its rationale recorded. When a seller joins, leaves or moves, their book of business is transferred in a controlled hand-over that preserves opportunity continuity and credit. Quota setting runs as its own guided workflow: a target is entered at the top, allocated down the hierarchy, negotiated and adjusted node by node, and locked once every branch reconciles. Each of these workflows is permission-aware, so managers act only within their branch of the hierarchy and every change leaves an audit trail.

The precision of the module lives in how it resolves contention and reconciles numbers. The assignment engine applies strict precedence and mutual exclusivity, so an account can never fall into two territories at once. Named-account definitions override attribute-based rules, exception lists pin specific accounts to specific owners regardless of geography, and a full simulation mode lets a planner apply a proposed rule set to the live population and inspect exactly which accounts would move before committing. Every assignment carries its determining rule, so any owner can see why an account is theirs.

Quota mechanics are equally exacting. Allocation supports top-down distribution, bottom-up roll-up and blended methods, weighting each territory by drivers such as market potential, installed base, pipeline coverage ratio and prior-period attainment. Seasonality curves spread annual numbers across periods, ramp schedules discount the quota of newly hired sellers, and reconciliation controls guarantee that the sum of child quotas matches the parent to the currency unit, flagging any over or under allocation. Balancing is measured against explicit fairness thresholds, and the module reports a distribution index across territories so that inequity is quantified rather than felt. Multi-currency handling, effective-dated boundaries, overlay credit rules and a complete change history round out the controls, so the structure withstands audit and supports clean, defensible compensation downstream.

Territory Management is the organisational backbone that several other modules draw on. The CRM module consumes territory assignment directly: accounts, leads and opportunities inherit their owner and reporting line from the territory that claims them, so pipeline is always attributed correctly. Sales Forecasting aggregates opportunity along the same hierarchy the territories define, which means the forecast rolls up through exactly the structure quota was allocated down, and attainment is always comparable to target.

Quotas set here flow into Incentive Compensation, which pays against the territory owner and period the module records, so credit disputes are resolved by the same authoritative ownership history. The HR and workforce modules supply the people, roles and reporting lines that populate the hierarchy, and seller movements there trigger the hand-over workflows in Territory Management. Analytics reports coverage, balance and attainment across every dimension of the territory model, while Identity and Access uses the hierarchy to scope what each manager and seller can see and do. Because all of these read from one shared definition of who owns what, the whole revenue stack stays internally consistent.

AI Workers are first-class participants in Territory Management, holding their own credentials and acting within the same permission scopes as human colleagues. A manager can ask, in plain language, which accounts moved out of a region this quarter, which sellers are carrying pipeline above the fairness threshold, or how a proposed rule change would redistribute the named-account list, and the Worker answers by querying the live model and returning both the figures and the accounts behind them. Beyond query, Workers execute actions: they run balancing and coverage analyses, draft reallocation proposals, generate a quota distribution from a top-line target, and prepare the seller hand-over package when someone changes role.

Workers watch the structure continuously for anomalies and exceptions: unowned accounts, overlapping claims, territories drifting past their load thresholds, and quota branches that no longer reconcile, raising each as an alert with the context needed to act. They extract and normalise inbound data, mapping an uploaded account list or an external market file onto the territory dimensions so it can be assigned. They provide decision support during planning, modelling the coverage and balance consequences of a design before it is committed. And they participate directly in workflows as an approval or review node: a Worker can be configured to review every reassignment request against policy, approve routine hand-overs within defined tolerances, and escalate the genuinely contested cases to a human, so the routine volume clears itself while judgement calls still reach a person.