Non-Revenue Balance Attributes: Definition and Use

A seller's guide to understanding non-revenue Balance Attributes, including what you should inspect in your accounts, workload, pipeline, quota, and customer relationships.

By Kevin Davis, Co-Founder & CEO

Your territory shapes your accounts, workload, pipeline, customer relationships, quota, earnings, and opportunity to advance. Revenue is the laziest balance metric. Workload, intent, and renewal timing often predict success better. This guide shows what you should check, what evidence to request, and which questions to bring to your manager. You can use them without becoming the territory designer yourself.

BoogieBoard treats non-revenue Balance Attributes as part of a governed change process. The model must connect market strategy with account-level evidence, productive capacity, explicit decision rights, and controlled activation. The objective is not to remove judgment. It is to make judgment visible and repeatable.

The central position is: Do not sum the account score; deconstruct it. The sections below turn that position into definitions, alternatives, procedures, examples, controls, and an operating decision.

Working Definitions

• Balance Attribute: an account characteristic used to measure or distribute a territory.
• Balance Goal: a measurable objective for healthy opportunity, quality, workload, or continuity.
• intent data: a defined input used when evaluating non-revenue balance attributes.
• workload: a defined input used when evaluating non-revenue balance attributes.
• technographics: a defined input used when evaluating non-revenue balance attributes.

BoogieBoard's observed prospect books range from 1 to 15 accounts for strategic AEs to roughly 250 to 1,000 for SMB AEs. Those ranges are context, not quotas: role, segment definition, service model, and account quality determine whether a book is workable. For non-revenue balance attributes, use that observation only for the claim and population it directly supports.

Independent evidence provides a separate check for non-revenue balance attributes: The World Bank defines the Gini index as a measure of the area between an observed distribution and a line of absolute equality.

A Practical Decision Lens: Non-Revenue Balance Attributes

Summing revenue, fit, intent, and workload into one score hides the very drivers sellers and managers need to understand. A practical test is to pick one surprising account and trace it end to end. Explain why it is in the segment, why it belongs in the territory, whether it is locked, which goals it affects, and what happens when the seller changes. If the answer requires several private spreadsheets, the model is not yet governed. In non-revenue Balance Attributes, test the choice against Balance Goal, then record any accepted exception in the decision log. You should be able to trace the result from your account roster to the published rule.

Use this module to make the hidden decision explicit. State the role, population, evidence, rule, exception path, and operating consequence. The objective is not a perfectly clean model; it is a model whose compromises are visible enough to approve, communicate, and improve. The non-revenue Balance Attributes review is complete only when intent data and the affected account roster tell the same story. If your territory is an outlier, ask whether the difference is intentional, temporary, or a data error.

Calculating and Testing Non-Revenue Balance Attributes

Two customer books each hold $5 million ARR. One has 18 renewals next quarter and six at-risk implementations; the other has four renewals and stable adoption. Revenue equality conceals workload inequality. Assume six comparable territories cover 900 serviceable accounts. A count-only split begins at 150 accounts each. The team then measures Balance Attribute, Balance Goal, and intent data; one territory holds 28% of high-potential accounts and another carries twice the near-term workload. The worked answer is not to force identical counts. It is to publish the priority, range, and tradeoff. The non-revenue Balance Attributes review is complete only when intent data and the affected account roster tell the same story. If your territory is an outlier, ask whether the difference is intentional, temporary, or a data error.

Create three scenarios. Scenario A minimizes movement, Scenario B minimizes variance on the primary goal, and Scenario C protects continuity while improving the two largest outliers. Compare complete territories after qualifying locks return. Select the scenario whose residual imbalance leadership is prepared to explain and operate. Use one current-state baseline to keep every non-revenue Balance Attributes scenario comparable. Your manager should be able to explain the tradeoff without relying on a private spreadsheet.

Balance Goal: The Decision Test

Additional attributes reveal the book but create competing objectives. Designate a small set of primary Balance Goals and keep the rest as diagnostics. A practical test is to pick one surprising account and trace it end to end. Explain why it is in the segment, why it belongs in the territory, whether it is locked, which goals it affects, and what happens when the seller changes. If the answer requires several private spreadsheets, the model is not yet governed. Use one current-state baseline to keep every non-revenue Balance Attributes scenario comparable. Your manager should be able to explain the tradeoff without relying on a private spreadsheet.

intent data: The Decision Test

Use this module to make the hidden decision explicit. State the role, population, evidence, rule, exception path, and operating consequence. The objective is not a perfectly clean model; it is a model whose compromises are visible enough to approve, communicate, and improve. For non-revenue Balance Attributes, name the approver, the permitted evidence, and the condition that would justify a departure from the rule. Check how the decision changes your workload, pipeline, customer continuity, and quota context.

Policy and Governance: Non-Revenue Balance Attributes

A practical test is to pick one surprising account and trace it end to end. Explain why it is in the segment, why it belongs in the territory, whether it is locked, which goals it affects, and what happens when the seller changes. If the answer requires several private spreadsheets, the model is not yet governed. Keep account-level results beside the non-revenue Balance Attributes summary so Balance Goal remains inspectable after approval. You need an account-level correction path when the source data does not match what you know.

Balance Attribute: The Decision Test

Measure the components before combining them. Report distributions for Balance Attribute, Balance Goal, and intent data, then show the spread, median, outliers, and acceptable range. A composite score can support comparison, but it should never hide the account attributes and assumptions that produced it. Give the non-revenue Balance Attributes decision a source date, an owner, and a condition that would trigger revision. Ask what evidence would cause leadership to revisit your territory after activation.

Balance Goal: The Decision Test: Review 7

Use both current-state and future-state views. Report account movement, locked accounts, unassigned records, family splits, vacancies, and quota differences beside Territory Health (the measured condition of the complete territory). Monitor outcomes later, but avoid claiming that attainment alone proves the design was correct; product, market, timing, execution, and quota also affect performance. Before activating non-revenue Balance Attributes, show managers the effect on intent data and every downstream rule that depends on it. Your review should focus on documented facts and rules, not a negotiation for preferred accounts.

Common Failure Modes: Non-Revenue Balance Attributes

A second failure is letting exceptions define the model. Define Balance Goals first, then Account Locking Criteria. Apply qualifying locks, model the remaining book, and evaluate the complete result. If the constraints make a goal unattainable, disclose the residual imbalance instead of changing the rule in private. In non-revenue Balance Attributes, test the choice against Balance Goal, then record any accepted exception in the decision log. You should be able to trace the result from your account roster to the published rule.

See Balance in the Planning Workflow

The relevant product workflow is Balance Hybrid Territories by Type. BoogieBoard Scenario Planning keeps the account-level assumptions, tradeoffs, and proposed assignments visible while the team completes that work.

Scenario Results show customer and prospect mix, prospect grade, quarterly ARR, account locks, and rep capacity in one review surface.

Balance Attribute: The Decision Test 2

Use this module to make the hidden decision explicit. State the role, population, evidence, rule, exception path, and operating consequence. The objective is not a perfectly clean model; it is a model whose compromises are visible enough to approve, communicate, and improve. The non-revenue Balance Attributes review is complete only when intent data and the affected account roster tell the same story. If your territory is an outlier, ask whether the difference is intentional, temporary, or a data error.

From the Non-Revenue Balance Attributes Result to Action

Select attributes with a business rationale and reliable source. Common choices include qualified intent, renewal timing, implementation stage, product usage, target persona presence, technology fit, and service complexity. Create three scenarios. Scenario A minimizes movement, Scenario B minimizes variance on the primary goal, and Scenario C protects continuity while improving the two largest outliers. Compare complete territories after qualifying locks return. Select the scenario whose residual imbalance leadership is prepared to explain and operate. Use one current-state baseline to keep every non-revenue Balance Attributes scenario comparable. Your manager should be able to explain the tradeoff without relying on a private spreadsheet.

Balance Goal: The Decision Test 2

Use this module to make the hidden decision explicit. State the role, population, evidence, rule, exception path, and operating consequence. The objective is not a perfectly clean model; it is a model whose compromises are visible enough to approve, communicate, and improve. For non-revenue Balance Attributes, name the approver, the permitted evidence, and the condition that would justify a departure from the rule. Check how the decision changes your workload, pipeline, customer continuity, and quota context.

intent data: The Decision Test 2

A practical test is to pick one surprising account and trace it end to end. Explain why it is in the segment, why it belongs in the territory, whether it is locked, which goals it affects, and what happens when the seller changes. If the answer requires several private spreadsheets, the model is not yet governed. Keep account-level results beside the non-revenue Balance Attributes summary so Balance Goal remains inspectable after approval. You need an account-level correction path when the source data does not match what you know.

How the Alternatives Differ: Non-Revenue Balance Attributes

Compare alternatives against the same population and definitions. One option may improve Balance Attribute, another may protect Balance Goal, and a third may reduce disruption. Do not let each option use a different denominator or source date; that turns scenario review into a presentation contest. Give the non-revenue Balance Attributes decision a source date, an owner, and a condition that would trigger revision. Ask what evidence would cause leadership to revisit your territory after activation.

Why the Decision Matters: Non-Revenue Balance Attributes

This decision affects more than visual symmetry. It changes market coverage, seller focus, quota credibility, customer continuity, performance interpretation, and the amount of manual administration required during the year. Poor design transfers work to managers and sellers, who then create informal rules to keep operating. For non-revenue Balance Attributes, document the effect on Balance Attribute before the model advances. For your book, ask which accounts move and which measure justifies the change.

Practical Implications

A non-revenue Balance Attribute is an account characteristic other than current revenue used to compare opportunity, workload, timing, specialization, or continuity across territories.

Decision Worksheet

Decision	Evidence to inspect	Control
Define the population	Balance Attribute and comparable roles	Named data owner
Measure the current state	Balance Goal and intent data	Source date and baseline
Choose the tradeoff	Scenario comparison and complete Territory Health	Recorded approver
Activate the result	Account roster, changes, quota, and transition rules	Effective date and correction path

What This Means for You

You do not need to rebuild the model to evaluate non-revenue balance attributes. Check whether your accounts match the published population, whether your workload and opportunity are measured with understandable inputs, whether locked accounts remain in the final comparison, and whether your quota reflects material territory differences. Bring account IDs and evidence when you find an error.

Questions to Ask Your Manager

1. What business objective drove this decision, and what tradeoff did leadership accept?
2. Which rules determine the accounts and customers in my territory?
3. Which Balance Goals were used, and what range is considered acceptable?
4. Which accounts were locked, and are they included in the final Territory Health result?
5. How does my quota account for potential, workload, capacity, and ramp?
6. Where do I submit a data correction or policy challenge, and when will I receive an answer?

Frequently Asked Questions

What can you balance territories on besides revenue?

A non-revenue Balance Attribute is an account characteristic other than current revenue used to compare opportunity, workload, timing, specialization, or continuity across territories. Additional attributes reveal the book but create competing objectives. Designate a small set of primary Balance Goals and keep the rest as diagnostics. Use the published definitions and complete-territory result instead of relying on one universal benchmark. Ask your manager to show how that standard applies to your book.

Which balance attributes matter most?

Select attributes with a business rationale and reliable source. Common choices include qualified intent, renewal timing, implementation stage, product usage, target persona presence, technology fit, and service complexity. Two customer books each hold $5 million ARR. One has 18 renewals next quarter and six at-risk implementations; the other has four renewals and stable adoption. Revenue equality conceals workload inequality. Publish the assumptions so another reviewer can reproduce the answer. You should be able to reproduce the answer from your roster and the stated inputs.

What data is required for non-revenue balance attributes?

For non-revenue balance attributes, assemble governed account data, current assignments, role capacity, and decision evidence for Balance Attribute, Balance Goal, and intent data. Date the sources and publish the definitions so another reviewer can reproduce the result and separate a factual correction from a policy exception. Request the source date when the underlying account facts look stale.

How often should non-revenue balance attributes be reviewed?

Review non-revenue balance attributes on the formal planning cadence and whenever the inputs behind Balance Attribute, Balance Goal, and intent data change materially. Keep customer and pipeline ownership stable between reviews; reopen the model when strategy or new evidence changes the decision, not merely because a manager prefers a different assignment. Ask when your territory will next receive a formal review.

How should Balance Goals and account locks work together?

For non-revenue balance attributes, define Balance Goals tied to Balance Attribute, Balance Goal, and intent data before applying locks. Then publish Account Locking Criteria, lock only qualifying accounts, optimize the movable book, and score the complete territory so locked burden and residual imbalance remain visible. Check that your locked accounts remain in the final health calculation.

When should a spreadsheet be replaced with a planning system?

For non-revenue balance attributes, a spreadsheet remains adequate while one owner can preserve Balance Attribute, Balance Goal, and intent data, plus versions, account detail, approvals, and deployment without manual reconciliation obscuring the rule. Move to a planning system when scenario volume, collaboration, or audit work overwhelms the decision itself. You need a system when manual reconciliation makes the rule impossible to inspect.

In Summary

Revenue is the laziest balance metric. Workload, intent, and renewal timing often predict success better. Use the sequence above to keep the decision governed, evidence-based, and inspectable at both the account and territory levels.

See Territory Planning in Practice

Related Content

• Balance Goals: The Complete Guide to Territory Equity
• Designing Books of Business: The Complete Guide
• How to Communicate a New Territory Plan Effectively

Schedule a Live Demo to model non-revenue balance attributes, compare scenarios, and make the account-level tradeoffs visible before activation.