How to Name Scorecard Result Bands as Identities
How to name scorecard result bands: use identities people recognise, not grades, and remember the overall band sells while the per-pillar band delivers.
To name scorecard result bands, write each one as an identity the respondent recognises, such as "The [adjective] [kind of person or organisation]", and avoid grades like "Level two of five". A good name is what people repeat, forward and get sorted by.
Naming feels like the last cosmetic step. It is not. The label travels into several places, and it decides whether anyone remembers the result at all. This post covers what makes a band name work, the two verdicts a scorecard carries, and the two mechanical rules that stop a rename from breaking things. For the numbers that put people into those bands, see how to set scorecard band boundaries.
How to name scorecard result bands: identities, not grades
Grades invite argument, and identities invite recognition. Nobody forwards a message that says they scored level two of five. People do forward a message that says, apparently, they are a particular kind of founder. The first is a rank. The second is a mirror.
The guide notes that in live instruments one pattern emerged on its own, without anyone writing it down: "The [adjective] [kind of person or organisation]". Examples include The Ad-Hoc Org, The Emerging Framework and The AI-Native Org. Each tells you at a glance what sort of place this is and roughly how far along it is.
A second family is sharper still. Some bands name the owner's relationship to the business, not the business's level of maturity: Founder Trapped, Consultant Plus, Emerging Machine, Scalable Business and Founder Optional. These describe what the respondent actually feels, which is why they land so strongly.
| Grade | Identity | |
|---|---|---|
| Example | Level two of five | The Ad-Hoc Org |
| Does the reader remember it? | Rarely | Yes |
| Will they forward it? | Unlikely | Often |
| Does it invite argument? | Yes, about the rank | No, it invites recognition |
| Is it useful in a notification? | No | Yes |
The label travels to four places
A band name is not just a headline. It propagates into at least four places, and each is a reason to choose it carefully.
- The headline the respondent reads and repeats to a colleague.
- The tag attached to their record in your contact system.
- The notification an owner reads when a new lead completes the scorecard.
- Any display rule keyed to the band, such as which message appears for whom.
The notification gives you the test. Read a line as the owner would, in a hurry. A line that says a named person scored a number and belongs to The Half-Built tells you everything you need to know. The same line ending in "Level two" tells you nothing. If your band names do not sort a lead in one glance, they are wrong.
Test each name against the follow-up
A name should make the next step feel obvious. Say the band to yourself and then the follow-up message that goes with it. If the name and the follow-up feel as though they belong to different people, rewrite the name. Because a band exists to trigger a different consequence, it deserves a name that points at that consequence. How the follow-up is built is in how to write a scorecard action plan.
It also helps to read the full ladder aloud, from lowest to highest. The names should feel like steps in a story, not a list of synonyms. If two names could be swapped without anyone noticing, one of them is not doing its job, and you may have one band fewer than you think.
Two verdicts, not one
A scorecard actually delivers two verdicts, and naming should respect the difference.
| Verdict | Question it answers | Role |
|---|---|---|
| Overall band | Who are you? | This is what sells |
| Per-pillar band | What do you do next? | This is the deliverable |
The overall band is the memorable identity, so it earns the most careful naming. The per-pillar bands are working labels attached to advice. They can be plainer, but they still need to be distinguishable from one another, and each must lead to something specific.
One instrument can carry both. Take a design with a few overall bands and several levels across each pillar, so that the number of per-pillar rows matches the number of roadmap slots you planned to fill. Then the overall name gives the respondent a sentence to repeat, and the pillar bands give them a plan to follow.
Two hard rules about identifiers
Naming has a mechanical side, and ignoring it causes quiet damage.
The identifier is derived once and then frozen
In typical engines, a band's internal identifier is created from its label at the start and never updated. Rename the band and the identifier stays as it was, while anything keyed to the old name can be orphaned. Treat a rename as a change that needs checking, and look at your follow-up rules afterwards.
Branch on the identifier, never on the label
The label is the translated part. If a rule matches against the translated label, it will work in one language and silently stop working in every other. The scoring path should never touch a translated string. Values, weights, boundaries and identifiers decide. Option text, band labels, descriptions and advice display.
Get this right and a multilingual instrument becomes one population, not several incomparable ones. A respondent answering in one language and another in a different language, with identical answers, land in the same band with the same tag, and you can add a language to a live scorecard without invalidating existing results. If you ever find a translated value inside a matching rule, that is the bug, not a rounding difference.
A way to draft the names
If you are staring at a blank page, work in four short steps. They keep the exercise concrete and stop it from becoming a search for clever words.
- Describe the person in each band in one plain sentence. Say what their situation feels like from the inside, not what score they achieved.
- Find the noun. Is this person a founder, an organisation, a team or a business? Choose the kind of thing the respondent believes themselves to be.
- Find the adjective. One word that separates this band from the one above and below.
- Test it in the notification line. Read it beside a name and a score, as an owner scanning a list would.
Where the band is about the owner's relationship to the business rather than the business itself, switch the noun. The respondent feels trapped, or free, or in the middle. A name that matches that feeling will be recognised faster than a name that describes the company.
Names that quietly fail
| Name style | Why it fails | Better direction |
|---|---|---|
| A bare number or level | Cannot be remembered or sorted at a glance | A recognisable kind of person or organisation |
| A school grade or medal | Invites arguing with the rank | A description the person can see themselves in |
| Names that all sound alike | The ladder reads as one band repeated | One distinguishing adjective per step |
| Praise for every band | Destroys credibility | At least one honest, uncomfortable name |
| A name that relies on a translated word in a rule | Breaks silently in other languages | Rules keyed to the identifier |
Design the top of the page for a stranger
The band name is the first thing on the results page, and results links are shared. Someone who has never seen the assessment may open the link cold, so the name should make sense without any explanation. An identity such as the examples above passes that test. A grade does not, because a stranger has no idea what the scale means or how many levels there are.
That is a further argument for identities. They carry their own context. They survive being forwarded.
Names that tell the truth
A flattering name defeats the point. The ladder needs at least one band that tells someone something uncomfortable and specific, and its name should be honest about it. The tone to aim for is the one a perceptive friend would use: direct, not cruel, specific, not vague. A result that cannot be uncomfortable produces no urgency and no credibility, and thoughtful respondents see through a ladder of compliments in seconds.
Check each name by asking whether someone who scores badly would still forward it to a colleague. If the answer is yes, the name is probably recognisable and honest at the same time.
A short naming checklist
- Every band is an identity, not a grade or a number.
- The pattern is consistent: the same grammatical shape across the ladder.
- Each name sorts a lead at a glance when read in a notification.
- Each name matches its follow-up and none could be swapped for another.
- I have chosen identifiers deliberately, and I will not rename a live band casually.
- No rule anywhere matches on a label.
Names are also part of what you calibrate. When a band turns out to be nearly empty, the conversation about its cut points is in how to calibrate a scorecard.
Frequently asked questions
Can I use numbers or levels as well as a name?
You can show a number alongside, but make the name carry the meaning. A number alone is a grade, and it does not travel.
Is it safe to rename a band after launch?
Treat it with care. The identifier usually stays fixed while the label changes, and anything keyed to the old label can be orphaned. Check every follow-up rule after a rename.
Should per-pillar bands have memorable names too?
They can be plainer, because they point to advice. What matters is that each is distinct and leads to a specific next step.
How do I name bands for a multilingual scorecard?
Write the names for display only, translate them freely, and make every rule use the identifier. That keeps one population across languages.
The full method, with the checklists, is in The Scorecard Playbook, a free 39-page playbook.