The Workflow Library

Library / Deal hygiene / deal-hygiene-047

Deal ownership validation on territory change

Deal hygieneDealSales Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. When a deal's territory changes but the current owner is not part of that territory's team, sales ops gets a flag and a task to review reassignment, so ownership stays aligned with territory instead of drifting after an account moves.

Workflow map Enrollment, branches and actions at a glance deal-hygiene-047
flowchart TD
    A[Territory changes] --> B{Owner belongs to the matching territory team?}
    B -->|no| C[Set Ownership Territory Mismatch Flag = true]
    C --> D[Create review task for sales ops]
    D --> E[Notify sales ops]
    B -->|yes| F[Exit, no mismatch]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when accounts (and their deals) can change territory, for example after a company updates its address, its size crosses a segmentation threshold, or a restructuring redraws territory lines.
  • UseUse it as a review-and-flag mechanism, this fiche checks alignment, the actual reassignment to a new owner is a separate action, either manual or built with the rotation pattern from the lead-routing category.
  • SkipDo not use it if territory almost never changes after a deal is created in your business, in that case the flagged volume will be near zero and the build is not worth the maintenance.
  • SkipDo not use it as a substitute for a proper round-robin reassignment workflow, this fiche tells you ownership is misaligned, it does not pick the new correct owner for you.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.4 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.3 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the deal hygiene pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.