Bank sales performance management works when you standardize what counts before you launch a competition, then normalize every result against each branch's own baseline, not the raw total. A 400-sale month at your flagship urban branch and a 30-sale month at a two-person rural branch can represent the same effort, or wildly different effort. Rank on raw totals and the small branch never has a shot. Rank on percentage-of-baseline and you find out who's actually over-performing relative to what their market allows.
Why regional banking teams struggle with consistency
Most decentralized banks run sales performance the same way: corporate sets a target, branches self-report against it, and leadership reviews results once a month in a spreadsheet. It mostly works until you try to run something that spans branches: a national incentive, a cross-regional SPIFF, a "team of the quarter" award. Then someone asks the obvious question: is this actually fair?
It's not a hypothetical concern. It shows up directly in how support requests get framed. One recurring request we see is a bank wanting to build an incentive specifically around fixed-line MRR: a metric that behaves completely differently branch to branch depending on the existing customer base. Another is more blunt: a manager asking, in so many words, how to structure a regionwide competition so it "feels fair". That question, not "how do I track this" but "how do I make people believe the ranking is legitimate," is the real problem regional banks are solving for.
Three things tend to break down at once:
- The metric isn't standardized. One branch counts a "sale" as a signed application; another counts it as a funded account. Roll those into one leaderboard and you're not comparing performance, you're comparing definitions.
- Volume differences get treated as a performance signal. A branch with 400 existing accounts will generate more raw activity than a two-person branch in a small town, regardless of who's working harder.
- Managers have no lever besides the raw scoreboard. When the ranking feels arbitrary, managers stop trusting it as a coaching tool and start explaining it away instead of using it.
Solving this isn't about finding a smarter dashboard. It's about sequencing three decisions correctly before you ever launch a competition.
Step 1: Standardize the metric before you launch
Before any cross-branch ranking goes live, get explicit agreement (in writing, not just verbally) on what counts. For a sales competition, that usually means defining:
- What activity actually qualifies as the countable unit (a signed application, a funded account, a completed cross-sell — pick one and hold every branch to it)
- Which products or lines are in scope (don't let one branch include a product line that another doesn't sell)
- What the reporting window is and how mid-period corrections get handled
This sounds basic, but it's the single most common failure point. If two branches are quietly using two different definitions of "a sale," no amount of downstream normalization will fix the ranking. You're just averaging bad inputs into a bad output faster.
Step 2: Normalize for baseline volume differences
Once the metric is standardized, the real fairness problem is volume. A raw-total leaderboard structurally rewards branch size, not branch performance. The fix is to index each branch's current result against its own historical baseline, so every branch is being measured against itself, not against a bigger neighbor.
The table below shows why this matters. All three branches are ranked by raw total first, then by their result as a percentage of their own historical baseline.
On raw totals, Branch A wins every time: it's the biggest branch, so it produces the biggest numbers. Indexed to each branch's own baseline, Branch B is actually the strongest performer this month, outgrowing its own history by the widest margin. That's the ranking that reflects effort and momentum rather than headcount and existing book size.
The baseline itself should be a rolling average (trailing 3 to 6 months works well for most banks) rather than a single prior month, so one unusually strong or weak month doesn't permanently distort a branch's comparison point going forward.
Step 3: Give regional managers a culture lever, not just a scoreboard
Standardizing the metric and normalizing the score fixes the fairness math. It doesn't automatically fix engagement: that still depends on whether managers have a way to make the numbers feel real day to day, not just at month-end review.
This is where moving off manual tracking changes the day-to-day culture, not just the reporting accuracy. SalesScreen's case study on Sparebank 1's customer center describes exactly this shift: the team moved from manually updating spreadsheets to a real-time "Wall of Fame" leaderboard, with instant notifications on the app and desktop when a rep hits a milestone. As Sales Manager Siri Søyland put it, the change "helped us to establish a clear organizational strategy and build a real performance culture." Managers are able to layer in personalized coaching and rep-specific budgets on top of the shared, standardized scoring model, rather than managing every branch's numbers by hand.
That combination, a national-level competition alongside department- or branch-level competitions that managers can run themselves, gives regional managers something to actually manage, rather than just a number to report upward.
Case study: Rogaland Sparebank
Rogaland Sparebank is a decentralized Norwegian bank with more than 60 branches and roughly 400 employees, close to the structural profile most regional banks are working with when this problem shows up. Bank Manager Konrad Kvitvær described the layered structure this way: "We create competitions at different levels… we have a national level and then each department creates its own competitions." Branch Manager Hans described the shift in feedback speed directly: "We don't have to wait for the end of the month… we see results from minute to minute."
The results, per SalesScreen's published case study:
- Goal attainment for customer service teams increased 200%
- New customer acquisition for the private sales department increased 133%
- Customer satisfaction increased 35% between 2018 and 2022
- Insurance sales increased 25% in 2022 versus 2021 — described internally as the bank's best year ever in insurance sales
None of those gains came from a smarter leaderboard alone. They came from a structure where corporate-level standardization coexisted with local competitions branch managers could run and adapt themselves.
What this doesn't fix
Normalization is a fairness mechanic, not a magic fix, and it's worth being honest about its limit: it only works if the baseline data is clean. If a branch's historical numbers are inflated by a one-time bulk import, a temporary staffing surge, or inconsistent reporting before the metric was standardized, indexing against that baseline will just carry the distortion forward. Before rolling out an indexed scoring model bankwide, audit each branch's baseline period for exactly those kinds of anomalies. Be prepared to manually adjust or exclude a distorted baseline rather than trusting the average blindly.
Bringing it together
Fair cross-branch performance management isn't a reporting problem. It's a sequencing problem. Standardize what counts, normalize for the volume differences that raw totals can't see, and give managers a way to run the culture locally rather than just report the numbers upward. SalesScreen's gamification and performance platform is built to handle exactly this kind of standardized, normalized, real-time scoring across distributed banking teams, without asking anyone to maintain it by hand.
FAQ
Do we need new software to normalize scores across branches, or can this be done in a spreadsheet?
You can calculate indexed scores in a spreadsheet: it's simple percentage math. The friction shows up at scale: recalculating baselines monthly across dozens of branches, keeping the underlying activity data consistent, and surfacing results to reps in real time all get harder to sustain manually as branch count grows. That's the operational gap a dedicated performance platform is built to close.
How often should we recalculate each branch's baseline?
A rolling 3 to 6 month average, recalculated monthly, is a reasonable default for most banks. It's responsive enough to reflect real growth or decline in a branch's book of business without letting one anomalous month permanently skew the comparison.
Should every branch be on the exact same competition, or can regions run their own?
Both, and that's the model that shows up in practice: a national-level competition on the standardized, normalized metric, with individual departments or branches layering their own local competitions on top, as long as the underlying scoring definition stays consistent.