How-to guide

How to design a sales rep scorecard that holds up in 1:1s and reviews

A sales rep scorecard is the one artifact that has to work in three different rooms: the weekly 1:1 where the rep sees it first, the performance review where HR reads it as a record, and the promotion panel where leadership compares reps across segments. Most scorecards fail because they try to be a dashboard instead of a decision document, cram twenty metrics onto a page nobody reads, or compare reps on raw numbers that reward territory luck over skill. This guide walks through designing a weekly 1-page scorecard that normalizes across the team, covers quota attainment, win rate, average deal size, cycle length, activity, and CRM hygiene, and stays legible enough to anchor every rep conversation for a full year.

Before you start

What you need.

Time: 1 week to design, weekly to run

  • A current team roster with tenure, segment, quota, and ramp status for each rep so the scorecard can normalize against peers at the same stage
  • Trailing 180 days of pipeline data: deals created, stage progression, win rate, average deal size, and cycle length by rep and by segment
  • A documented definition of what counts as a qualified opportunity, a stage-two deal, and a closed-won deal so metrics are not reinterpreted every quarter
  • Agreement from sales leadership on the two or three outcome metrics the scorecard is scored against (usually quota attainment plus one leading indicator)
  • A system of record where activity, pipeline, and hygiene data all live in one place so the scorecard pulls from one source, not three spreadsheets
Design a sales rep scorecard

Step by step.

  1. 1

    Pick the one job the scorecard has to do before you pick metrics

    A scorecard that tries to do everything ends up doing nothing. Before you choose a single metric, write down the one decision this scorecard has to make easier. For most teams the answer is a weekly rep conversation that also feeds quarterly reviews, PIP decisions, and promotion panels. That single job dictates the shape of the page: one rep per view, trailing timeframes that match a review cycle, peer context so the number is not read in isolation, and a layout that reads in under 60 seconds. If the job is instead a leaderboard for the sales floor, you are building a different artifact and most of this guide does not apply. Pin the chosen job to the top of the design doc so every metric decision has a clear tie-breaker.

    • Write a one-sentence job statement for the scorecard, e.g. anchor every 1:1 and support review decisions across the year.
    • List the three downstream decisions it needs to survive: weekly 1:1 coaching, quarterly performance review, promotion panel.
    • Rule out jobs the scorecard is not doing: leaderboard, forecast call, pipeline review each need their own surface.
    • Share the job statement with two front-line managers and one HR partner before you draft a metric.
    Tip: If sales leaders cannot name the single job in one sentence, do not start designing yet. A scorecard without a job gets rewritten every quarter and loses the credibility that makes it useful in reviews.
  2. 2

    Lock the metric set to seven to nine fields, grouped into four blocks

    The 1-page constraint is the whole point. Hold the metric set to seven to nine fields and group them into four blocks the reader can scan in order: outcomes (quota attainment, win rate), economics (average deal size, cycle length), activity (calls, meetings, opportunities created), and hygiene (next-step freshness, close-date accuracy, required-field completeness). Each block answers a different question. Outcomes say whether the rep is hitting the bar. Economics say how they are hitting it, which matters for promotion. Activity says whether effort is at expected level, which matters for coaching and PIPs. Hygiene says whether the data behind every other block can be trusted. Any metric that does not clearly belong in one of the four blocks probably belongs on a different page.

    • List candidate metrics for each block and cut aggressively: no more than three fields per block.
    • For every metric, write the question it answers in plain language so reviewers can read the page without a glossary.
    • Reject any metric where you cannot name the behavior change you would ask for if it moved in the wrong direction.
    • Reserve one slot per block for a composite or trend indicator so the page shows direction, not just a snapshot.
    Tip: A scorecard with twenty metrics is a dashboard someone pasted into a template. If stakeholders ask for a twenty-first field, add it only by removing one.
  3. 3

    Define every metric with a public formula and a stable timeframe

    Ambiguous metric definitions kill a scorecard faster than wrong metrics. Write a public one-paragraph definition for every field that spells out the formula, the timeframe, the data source, and the edge cases: what counts as a meeting, when a deal counts as created, which stage counts as qualified, how pushed close dates are treated for cycle length. Pick timeframes that match how the scorecard is actually used. Trailing 30 days for activity and hygiene so coaching conversations are current. Trailing 90 days for win rate and average deal size so the sample is big enough to read. Quarter-to-date and trailing-four-quarter for quota attainment so both the current period and the annual trend are visible on the same page.

    • Write a one-paragraph definition per metric and publish it in the same place the scorecard lives.
    • Lock the definition for a full fiscal year so quarter-over-quarter comparisons remain valid.
    • Document the data source and the refresh cadence per metric so reps know how fresh the number is.
    • Spell out edge cases explicitly: multi-year ACV, co-sold deals, team-sold deals, inherited pipeline, no-decision losses.
    Tip: If two managers can read the same metric definition and disagree on how to score a borderline deal, the definition is not done. Rewrite it until the borderline case has one obvious answer.
  4. 4

    Normalize every rep metric against peers at the same tenure and segment

    Raw numbers reward territory luck. A rep in a mature segment with named accounts will out-earn a rep in a new segment on raw quota attainment, and neither number says anything about skill. Normalize every metric on the scorecard against a peer cohort defined by tenure band and segment, and show the peer median and top-quartile alongside the rep's own number. For reps still in ramp, show expected ramp curve by month rather than full quota. For reps in different segments, compare within segment and only roll up to a team-wide view when the segments are explicitly comparable. The normalized view is what makes the scorecard fair enough to support PIP and promotion decisions, and it is the single hardest thing to get right in version one.

    • Define three to five peer cohorts by segment and tenure band and publish the cohort map alongside the scorecard.
    • Show peer median and top-quartile for every outcome and economics metric so the rep sees their position in context.
    • Replace raw quota attainment with ramp-adjusted attainment for reps inside their ramp window.
    • Flag any rep in a cohort of fewer than four peers so the median is treated as directional, not conclusive.
    Tip: If a rep argues their numbers look bad only because of territory, and the scorecard cannot answer with a normalized peer view, the scorecard is not fit for review decisions yet. Fix normalization before you take it into a promotion panel.
  5. 5

    Add CRM hygiene as a scored block, not a footnote

    Every metric above the hygiene block depends on hygiene being real. If next steps are stale, close dates are three quarters out, or required fields are empty, the win rate and cycle length numbers are fiction. Treat hygiene as a first-class scorecard block with three testable fields: percentage of open deals with a next step dated within the last 14 days, percentage of deals with a close date inside the current or next quarter, and percentage of required fields completed on open opportunities. Score each as a simple percentage against a team-set threshold (often 85 to 90 percent for mature teams, lower during ramp). Hygiene scores that stay red for two consecutive weeks are an input to coaching before they are an input to performance. Reps who learn hygiene is scored keep hygiene clean.

    • Define three hygiene fields with explicit thresholds and surface them on the scorecard with the same weight as outcomes.
    • Pull hygiene from the same CRM record of truth managers and reps both see, not from a hidden admin report.
    • Trend hygiene over trailing 90 days so a bad week does not read as a crisis and a bad quarter cannot hide.
    • Flag red hygiene two weeks in a row as a 1:1 topic before it compounds into unreliable forecast and pipeline math.
    Tip: Managers who exempt their top rep from hygiene scoring poison the whole program. Score every rep the same way and resolve exceptions through conversation, not through quietly removing fields.
  6. 6

    Design the page so a reviewer can read it in 60 seconds

    The 1-page constraint is the entire point and layout decides whether it works. Put the rep header and the four block headings in a fixed order every time: outcomes top-left, economics top-right, activity bottom-left, hygiene bottom-right. Use the same unit per metric (percent, dollars, days, counts) and the same trend arrow convention across the page. Keep peer medians in a lighter weight so the rep's own number pops. Reserve a small freeform strip at the bottom for the manager's one-sentence read of the quarter so the page carries interpretation, not just data. Legibility is a strategic asset: a scorecard that reads in 60 seconds gets used in every 1:1, a scorecard that takes five minutes gets opened only when HR asks for it.

    • Fix the block order and metric order so every rep's page reads the same way every week.
    • Hold the whole page to one printable sheet so it can be dropped into a review packet without reformatting.
    • Use a single trend convention (up-arrow for better, down-arrow for worse) across the entire page.
    • Add a one-sentence manager read strip updated at the end of each quarter so the page carries narrative, not just numbers.
    Tip: Build the layout in paper form before you build it in software. Reps and managers reading a printout surface the layout bugs that a prettier screen version will hide for a quarter.
  7. 7

    Wire the scorecard into the weekly 1:1, not a monthly email

    A scorecard that lives in a monthly email is a scorecard nobody uses. Open every weekly 1:1 by pulling the live scorecard inside the CRM, walk the four blocks in order, and anchor the coaching priority of the week on the one block that moved most. The rep self-narrates the outcomes block, the manager narrates the economics and activity blocks, and both walk hygiene together. End the 1:1 by logging a one-sentence next-week commitment on the scorecard itself so the written record and the coaching record live on the same page. The weekly ritual is what makes the quarterly review feel like a continuation of a conversation the rep has already been having, not a verdict handed down from HR.

    • Open the scorecard live during the 1:1 instead of circulating a static PDF so the data is current and shared.
    • Rotate which block anchors the week's coaching priority so no block becomes background noise.
    • Log the week's commitment on the scorecard itself so the plan and the record are not stored in different places.
    • Review the manager read strip once a quarter together so the written narrative stays honest to the rep's own experience.
    Tip: If the scorecard only opens the day before a performance review, it is not a scorecard, it is a report. Build the weekly habit first and the review workflow lands on top of it for free.
  8. 8

    Use the scorecard as the shared surface for PIP and promotion decisions

    The payoff of a weekly scorecard is a defensible paper trail at the decisions that matter most. For PIP decisions, show the trailing-four-quarter trend on outcomes and the hygiene block together: a rep whose outcomes are below cohort and whose hygiene has been red for a quarter is a different conversation from a rep whose outcomes are below cohort but whose activity and hygiene are solid. For promotion panels, show normalized economics (average deal size relative to segment peers, cycle length relative to segment peers) alongside quota attainment, so panels can tell growers from territory inheritors. Document which fields were weighted in each decision and attach the scorecard to the review record. The scorecard then survives manager turnover, which is often where review quality collapses.

    • Attach the trailing-four-quarter scorecard view to every PIP memo so the rep and HR read the same data.
    • Attach the normalized economics view to every promotion packet so panels compare like-for-like.
    • Record which blocks the decision leaned on so later reviewers can audit the reasoning, not just the outcome.
    • Keep the scorecard definitions locked for the review period so no retroactive metric redefinition changes the story.
    Tip: A scorecard that gets quietly reweighted during a promotion debate loses trust across the team within a quarter. Lock the weights before the review window opens and defend them in the room.
  9. 9

    Revisit the scorecard once a year, not every quarter

    Resist the urge to tune the scorecard every quarter. Metric definitions and weights change with segment, pricing, or motion, and those changes should be rare and loud, not frequent and quiet. Set a formal annual review of the scorecard tied to the fiscal plan: audit which blocks correlated with the decisions the scorecard was meant to support, retire fields that never moved coaching or review outcomes, add fields only when a documented decision needed them and could not be made from the existing page. Communicate changes with a one-paragraph changelog that lists what moved and why. A scorecard that remains stable for a full year earns the credibility that makes it useful for the next year of decisions.

    • Book the annual scorecard review alongside the fiscal planning cycle so metric changes line up with plan changes.
    • Audit each metric against the decisions it supported in the year: coaching conversations, PIPs, promotions.
    • Publish a one-paragraph changelog with every change so reps can trust why their page is different.
    • Freeze the new version for a full fiscal year before accepting another round of changes.
    Tip: Teams that redesign the scorecard every quarter are often avoiding a harder conversation about territory, quota, or coaching. Fix those first and the scorecard usually turns out to be fine.
Avoid

Common mistakes.

  • Comparing reps on raw quota attainment without normalizing for segment or tenure. The scorecard then rewards territory luck and loses credibility the first time a strong rep in a tough segment is passed over for promotion.
  • Letting the metric count drift past ten fields. Every added field pushes the page past the 60-second read, and the scorecard stops being the artifact that opens every 1:1.
  • Treating CRM hygiene as a footnote. If next steps are stale and close dates are fiction, every outcome metric above the hygiene block is noise and PIP and promotion decisions get made on bad data.
  • Changing metric definitions mid-year. Quarter-over-quarter comparisons break, reps lose trust in the record, and reviews become arguments about methodology instead of performance.
  • Shipping the scorecard as a monthly email instead of a live weekly 1:1 surface. The paper trail disappears, coaching detaches from the record, and the review conversation starts cold every quarter.
  • Exempting top reps from hygiene or activity scoring. One quiet exemption teaches the whole team that the scorecard is political, and the data gets gamed within a quarter.
FAQ

Frequently asked questions.

How many metrics should a sales rep scorecard have?

Seven to nine fields across four blocks: outcomes (quota attainment, win rate), economics (average deal size, cycle length), activity (calls, meetings, opportunities created), and CRM hygiene (next-step freshness, close-date accuracy, required-field completeness). More than nine fields breaks the 1-page constraint and the scorecard stops getting read in weekly 1:1s. Any additional metrics belong on a dashboard, not the scorecard.

What timeframes should each metric use?

Pick timeframes to match how the scorecard is used. Trailing 30 days for activity and hygiene so coaching conversations are current. Trailing 90 days for win rate and average deal size so the sample is large enough to read. Quarter-to-date and trailing-four-quarter for quota attainment so both the active period and the annual trend show on the same page. Lock all timeframes for a full fiscal year so quarter-over-quarter reads remain valid.

How do I normalize scorecard metrics across different segments?

Define three to five peer cohorts by segment and tenure band, publish the cohort map alongside the scorecard, and show peer median and top-quartile beside every outcome and economics metric. Replace raw quota attainment with ramp-adjusted attainment for reps still inside their ramp window. Flag any cohort with fewer than four peers as directional only. Normalization is what makes the scorecard fair enough to support PIP and promotion decisions.

Can the same scorecard support 1:1s, PIPs, and promotion reviews?

Yes, if it was designed to from the start. The weekly 1:1 view shows trailing 30 and 90 day blocks. The PIP view surfaces trailing-four-quarter trends on outcomes plus the hygiene block together. The promotion view surfaces normalized economics alongside quota attainment so panels can tell growers from territory inheritors. All three views are reads of the same underlying scorecard, which is what makes the paper trail defensible.

How often should the scorecard be redesigned?

Once a year, tied to the fiscal plan. Freeze metric definitions and weights for a full fiscal year, audit annually against the decisions the scorecard was meant to support, and ship changes with a one-paragraph changelog. Teams that redesign the scorecard every quarter usually have an unresolved quota, territory, or coaching problem that metric tuning will not fix.

Should CRM hygiene really count against a top-performing rep?

Yes. Hygiene is the foundation every other metric sits on, and quietly exempting top reps teaches the whole team that the scorecard is political. Score every rep the same way, surface red hygiene two weeks in a row as a 1:1 topic before it is a performance topic, and resolve exceptions through conversation rather than removing the field. Reps who learn hygiene is scored keep hygiene clean, and the forecast and pipeline math become trustworthy as a side effect.

See it in Strkr

Related product surfaces.

Strkr CRM Strkr platform features

Give every rep a scorecard that holds up in reviews

Strkr pulls outcomes, economics, activity, and CRM hygiene onto a single rep view so sales leaders can run weekly 1:1s, defend PIP decisions, and compare reps across segments from the same page the rep has been looking at all year.

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.