RevOpsRevOps Analystadvanced 45 min saved

Account and Territory Assignment Audit

Audit account ownership, territory coverage, capacity, and assignment changes against supplied rules.

Customise & copy

Add the context you have. The prompt updates as you work.

Current account ownership dataset *

Paste the current account ownership records as CSV, JSON, or a clearly labeled table.

Territory assignment rules *

Include region, industry, revenue thresholds, precedence rules, exclusions, and effective dates.

Sales capacity limits and coverage maps *

List each owner or territory, capacity limit, current coverage, and any geographic or segment boundaries.

Historical assignment change log *

Provide dated assignment changes, previous and new owners or territories, and stated reasons where available.

Live prompt

4 fields

Audit the account and territory assignment data below against the stated rules. Use only the supplied information. Do not use external lookups or invent missing values. Infer what can be determined without asking follow-up questions, and label any undeterminable item as "Not determinable from supplied data" with the missing basis stated.

SOURCE DATA
Current account ownership dataset:
{{account_ownership_dataset}}

Territory assignment rules:
{{territory_assignment_rules}}

Sales team capacity limits and coverage maps:
{{capacity_and_coverage_maps}}

Historical assignment change log:
{{assignment_change_log}}

Apply all stated region, industry, revenue, capacity, coverage, effective-date, and ownership rules. Check each account for valid ownership, uncovered territory or account coverage, multiple active owners, capacity breaches, and inconsistent application of the rules. Use the change log to identify recent or recurring assignment logic issues. Calculate percentages from the supplied records only; state the denominator used. Suggested resolutions must be evidence-based and must not create owners, territories, or assignments that are absent from the supplied data.

Return exactly the following structure and headings. Keep tables compact and use "None identified" when a section has no findings.

# Account and Territory Assignment Audit

## 1. Audit summary
- Audit scope:
- Total accounts audited:
- Accounts with valid ownership:
- Uncovered accounts:
- Coverage percentage:
- Accounts with ownership conflicts:
- Accounts with duplicate coverage:
- Rule violations or logic inconsistencies:
- Capacity breaches:
- Key data limitations:

## 2. Ownership conflicts and recommended resolution
| Account | Current owner(s) | Conflict type | Rule or evidence | Recommended resolution | Confidence |
|---|---|---|---|---|---|

## 3. Uncovered accounts and recommended owner
| Account | Region | Industry | Revenue | Coverage gap | Eligible owner or territory | Recommendation | Confidence |
|---|---|---|---:|---|---|---|---|

## 4. Duplicate coverage report
| Account | Affected owner(s) or territories | Duplicate condition | Likely cause | Recommended resolution |
|---|---|---|---|---|

## 5. Rule violations and logic inconsistencies
| Account, segment, or rule | Finding | Expected logic | Observed logic | Evidence | Recommended correction |
|---|---|---|---|---|---|

## 6. Capacity and coverage risks
| Owner or territory | Assigned accounts | Capacity limit | Variance | Coverage-map issue | Recommended action |
|---|---:|---:|---:|---|---|

## 7. Assignment change-log observations
| Date or change reference | Account or territory | Observed change | Related audit finding | Risk or implication |
|---|---|---|---|---|

## 8. Prioritized actions
1. [High] Action — rationale and affected records.
2. [Medium] Action — rationale and affected records.
3. [Low] Action — rationale and affected records.

Do not add sections, omit required sections, include external facts, or present assumptions as confirmed data.

Proof before you use it

A real example

Tested on gpt-5.6-luna on 2026-09-09

{
"assignment_change_log": "2025-08-12,H-203,Daniel Brooks,Daniel Brooks;Grace Chen,Temporary commercial overlay added for device procurement project,No approval reference or expiration recorded\n2025-07-01,H-204,Lena Ortiz,,Representative left the company,Effective 2025-07-01\n2025-06-20,H-206,Daniel Brooks,Daniel Brooks,Health-system segmentation review,Effective 2025-06-20",
"account_ownership_dataset": "Account ID,Account Name,Region,Industry,Annual Revenue,Owner,Territory,Status\nH-201,MetroCare Hospitals,US Mid-Atlantic,Healthcare,220000000,Daniel Brooks,MA-Health-System,Active\nH-202,Silverline Imaging,US Mid-Atlantic,Medical Devices,38000000,Aisha Khan,MA-Commercial,Active\nH-203,Coastal Diagnostics,US Southeast,Healthcare,67000000,Daniel Brooks,SE-Health-System,Active\nH-204,Evergreen Clinics,US Pacific Northwest,Healthcare,12000000,,PNW-Commercial,Active\nH-205,Union Medical Supply,US Southeast,Medical Devices,49000000,Grace Chen,SE-Commercial,Active\nH-206,Great Lakes Oncology,US Midwest,Healthcare,91000000,Daniel Brooks,MW-Health-System,Active",
"capacity_and_coverage_maps": "Daniel Brooks: capacity 3, covers Mid-Atlantic, Southeast, and Midwest Health Systems. Aisha Khan: capacity 6, covers Mid-Atlantic Commercial and Medical Devices. Grace Chen: capacity 6, covers Southeast Commercial and Medical Devices. Malik Johnson: capacity 5, covers Pacific Northwest Commercial and Medical Devices. Territory map: MA-Health-System, MA-Commercial, SE-Health-System, SE-Commercial, PNW-Commercial, and MW-Health-System.",
"territory_assignment_rules": "1. Hospital and health-system accounts with revenue above $75M require Health Systems coverage. 2. Medical-device accounts and healthcare accounts below $75M use Commercial coverage unless an approved exception exists. 3. Accounts are assigned by operating region, not headquarters parent company. 4. Every active account must have one accountable owner; overlays do not replace the accountable owner. 5. Health Systems representatives may manage no more than 3 active accounts. 6. Commercial representatives may manage no more than 6 active accounts. 7. Exceptions must include an approval reference and expiration date."
}

A small ritual that works

How to use it

01Paste the current account ownership dataset.
02Add the territory assignment rules, including thresholds, exclusions, precedence, and effective dates.
03Add capacity limits and coverage maps.
04Add the historical assignment change log.

Why it works

The prompt gives the audit a clear evidence boundary: it must use only the four supplied data sources, avoid external lookups, distinguish determinable from undeterminable items, and state the missing basis when information is insufficient. It also translates the business objective into explicit checks covering ownership, territory coverage, duplicate assignments, capacity, effective dates, rule consistency, and change history. The required headings and compact tables create a practical reporting format for both account-level findings and broader capacity or logic issues. Requiring denominators for percentages improves transparency, while confidence fields and evidence-based recommendations help separate documented conclusions from items that require confirmation.

Where it fails

The prompt cannot resolve ambiguity that remains inside the supplied records, such as conflicting rules, unclear effective dates, incomplete capacity definitions, or missing approval information. Its restriction against creating owners, territories, or assignments also limits recommendations when no eligible option is explicitly present in the data. Historical observations may indicate a timing or logic concern, but the prompt does not provide a separate mechanism for establishing intent beyond the recorded change details. The fixed structure may also be restrictive when an organization needs additional audit dimensions that are not represented by the required sections.

Customisation tips

Define the source fields and allowed values before using the prompt, including account status, owner identifiers, territory identifiers, revenue units, effective-date conventions, and approval markers. State rule precedence explicitly when multiple region, industry, revenue, or strategic criteria can apply. Add a clear policy for how to treat inactive accounts, shared coverage, overlays, temporary assignments, and accounts that change segment over time. For capacity analysis, specify whether limits are hard thresholds, planning targets, or role-specific constraints. If the report will feed another system, replace the prose tables with a defined machine-readable schema and specify permitted confidence labels, date formats, and null-value conventions.

Watch-outs

Percentage calculations depend on a clearly defined denominator; active, inactive, excluded, and undetermined accounts should not be mixed without explanation.
A missing owner, missing territory, and duplicate territory are different conditions and should remain separately represented in the source data.
Recommendations must remain within the owners and territories explicitly supplied; apparent gaps cannot be filled with assumed personnel or organizational structures.
Change-log dates and effective dates may describe different moments, so the prompt should not treat a recorded change date as proof of when an assignment became active.

Works in

Quarterly sales planningTerritory restructuresCRM data quality reviewsRevenue operations audits

Was this useful?

Submit your variation

If your version helps, it may be published with your name and a link back to you.

Want to make AI useful across your team? Explore Atul's training.