How to Name Scorecard Result Bands So People Share Them
How to name scorecard result bands: use identities, not grades. Name the owner's relationship to the business, and test every name in your own inbox first.
Name scorecard result bands as identities, not grades. "The Half-Built" gets remembered and forwarded. "Level two of five" doesn't. The sharpest names describe the owner's relationship to the business, and each one has to sort a lead the moment it lands in your inbox.
How to name scorecard result bands people repeat
The score is a number. Nobody repeats a number.
What the person actually takes away is the name. It's the headline they quote to a colleague. It's what they remember a week later. So you can get every boundary right, and every weight, and lose it all with a label like "Level two".
Grades invite an argument. "Why only a two?" Identities invite recognition. "Ha. That's me."
Good scorecard result bands read like people, not scores. Nobody forwards "I scored level two of five". People forward "apparently I'm a Founder Trapped".
What the live names have in common
I counted. Across thirty-nine live result names, thirty-four follow the same pattern that nobody wrote down: "The [adjective] [kind of person or business]". It converged on its own. The Half-Built. The Scrappy Operator. That shape works because it sounds like something a person could be.
The five exceptions are the sharpest of the lot. They name the owner's relationship to the business, not the business's maturity.
| Type of name | Example | What it describes | Does it land? |
|---|---|---|---|
| Grade | Level two of five | A position on a scale | No. Unmemorable, unforwardable. |
| Maturity label | Developing | The business, from outside | Weakly. Polite and flat. |
| Adjective plus noun | The Half-Built | A kind of business or person | Yes. The pattern most real names settle on. |
| Relationship to the business | Founder Trapped, Consultant Plus, Emerging Machine, Scalable Business, Founder Optional | What the owner feels | Best for scorecard result bands. It names the person's actual experience. |
Read those five exceptions again. Founder Trapped. Founder Optional. They tell a story with an arc, and the person can see which direction they want to travel. Nobody needs a legend to read them.
For you, the lesson is plain. If you're a solopreneur who wants to scale, your readers care less about how mature the business is and more about how much of it still depends on them. Name the dependence.
Free guide · 28 pagesBuild a scorecard that tells the truth.The Scorecard Playbook: an assessment that separates people and gives you a reason to talk.Get the free guide →Test scorecard result bands where they will actually land
This isn't just aesthetics. It's mechanical. A result name travels into four places:
- The headline the person repeats.
- The tag on their contact record.
- The notification line you read when someone finishes.
- Any rule keyed on the result.
So test it in the notification line. Picture it arriving in your inbox. "Name, score, The Half-Built" tells you everything about who this is and what to say. "Name, score, Level two" tells you nothing. You'd have to open the report to find out what they are.
If your result names do not sort a lead in one glance, they're wrong. That's the whole test. Run it on every band.
Write the follow-up first, then name the band
Here's a sequence that makes naming easier. Write the follow-up email for each result before you name anything.
Once you know what you'd say to this person and what you'd suggest they do next, the name almost writes itself. It's the one phrase that sums up that email. If you can't find a name, the band probably doesn't have a distinct follow-up, and if two results would get the same email, you have one fewer result than you thought. Merge them. The follow-up is also what decides whether the boundaries you set mean anything, and how to set scorecard band boundaries shows how to make the edges land.
Don't flatter
The temptation is to give the lowest band a kind name. Resist. A scorecard that can't tell someone something uncomfortable and specific is a horoscope with arithmetic. The people you want to reach spot flattery in seconds and discount everything after it.
A name can be honest without being cruel. Founder Trapped is blunt, and it's the kind of blunt people recognise themselves in. The test: would someone who scored badly still forward it to a colleague? If yes, you've got the tone right.
One ladder, one story
Names work best when they read as a sequence. Say you sell a productised audit and your scorecard is about how much the business leans on you. Your ladder might run from a name that sounds like a trap, through a few that sound like progress, to one that sounds like freedom. Someone reading the whole list should be able to find themselves and see the road ahead.
That's the quiet strength of the owner-relationship names. Founder Trapped to Founder Optional is a whole journey in two labels. The person doesn't need a chart to know where to go next. They need the advice that gets them there, and that is the job of the write-up underneath each name.
Contrast it with a ladder of maturity words. Beginner, Developing, Established, Advanced. Each is correct and none of them is anyone. You can't picture a person saying "I'm Developing" with a wince or a grin.
Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →The name is the shallow end; the verdict has two parts
A scorecard gives two verdicts. The overall result answers "who are you". The result per pillar answers "what do you do next".
The name belongs to the first. It's what gets shared. The second is what gets acted on, and it doesn't need a clever label, it needs specific advice. Spend your cleverness on the headline and your honesty on the pillars.
Don't confuse the two jobs. A beautifully named band with thin advice behind it is just a better-looking quiz.
Two things that break names after launch
The name is frozen into an identifier
Usually the internal identifier for a level is derived from its name once, and then frozen. Rename the level later and everything keyed to the identifier is orphaned, silently. Rules, tags, follow-up sequences, all pointing at something that has moved.
So rename early or not at all. Get the name right in the first week with real respondents, then leave it alone. This is part of the wider rule that anything which decides a result should be fixed before you send traffic, which how to weight scorecard questions goes into for values and weights.
The name must never decide anything
Keep what decides separate from what displays. Option values, weights and boundaries decide. Option wording, result names, descriptions and advice display. The scoring path should never touch a translated string.
Get that right and a scorecard in eight languages is one population instead of eight incomparable ones. Someone answering in Portuguese and someone answering in English with the same answers land in the same place. You can add a language later without invalidating a single result.
The leak is subtle. In one system rigorous enough to enforce this in its engine, a display rule one layer up was matched against the translated result name. A rule written as "Developing" silently stopped matching in every other language. If you find a translated value inside a matching rule, that's a bug, not a rounding difference.
So key your follow-ups to the identifier, never to the visible name, and check them after any rename. Most validators check rule-to-result and never result-to-rule, which means a result with nobody listening is structurally invisible. It doesn't error. It just looks like a quiet week.
One more reason to be fussy: the name is the only part of the result that reaches people who never take the scorecard. A colleague hears it second-hand, in one phrase, and decides in a second whether they're curious. Make the phrase worth repeating.
Free guide · 28 pagesBuild a scorecard that tells the truth.The Scorecard Playbook: an assessment that separates people and gives you a reason to talk.Get the free guide →Name them on a Monday evening
- Write each follow-up in a sentence. What would you say to this person?
- Draft the name as an identity. "The [adjective] [noun]", or the owner's relationship to the business.
- Put it in the notification line. Does it sort the lead at a glance?
- Check for flattery. Would a poor scorer still forward it?
- Freeze it. Then connect your tags and sequences.
Naming scorecard result bands is one small part of the whole job, which is how to build a scorecard that people remember and you can act on. And once the name has done its work on the screen, the advice behind it matters, which is the subject of how to write a scorecard action plan.
Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →Frequently asked questions
Should scorecard result bands have names or numbers?
Names, written as identities. A grade invites an argument and nobody forwards it. An identity such as "The Half-Built" invites recognition and gets repeated.
What pattern do good result names follow?
Most follow "The [adjective] [kind of person or business]". The sharpest ones describe the owner's relationship to the business, such as Founder Trapped or Founder Optional.
Can I rename a band after launch?
Avoid it. The internal identifier is usually derived from the name once and then frozen, so renaming orphans everything keyed to it, silently. Rename early or not at all.
Should a low band have a gentle name?
No. A result that can't be uncomfortable creates no urgency and no credibility. Be blunt in a way people recognise themselves in.
The full method, with the checklists, is in The Scorecard Playbook, a free 28-page playbook.
How trapped are you, really?
Take the Corporate Suffocation Index, the free solopreneur readiness assessment.