How to write a sales rep performance review template that reps and finance both trust

The first failure mode of a rep performance review is writing it as a bigger scorecard. The scorecard answers whether the rep did the work this week, the review answers whether the rep is growing in the role and earning the comp the business is paying. Open the template with an explicit section header that names what this document is for and what it is not. One section covers quota attainment and leading indicators across the full review period, another covers qualitative skills ratings, another sets goals for next period, another lays out development, and a final section captures comp calibration. Reps who open the template and see the structure know what the conversation is going to be about, which lowers the defensiveness that kills review conversations.

• Write a one-paragraph purpose statement at the top so the rep reads what the review is for before they read any ratings.
• Call out explicitly that weekly scorecard metrics live elsewhere and will not be relitigated line by line in this document.
• Lock the five sections (attainment, skills, next-period goals, development plan, comp calibration) and stop pattern-adding new ones each cycle.
• Version the template once per fiscal year and keep a changelog so reps see the document evolve on evidence, not manager whim.

Quota attainment is the anchor section, and the trap is weighting it toward whatever quarter closed most recently. For an annual review, show attainment by quarter alongside the annual number, segment it by product line and segment, and include ramp-adjusted attainment for anyone still inside their ramp window. For a quarterly review, show the trailing three quarters so a one-off bad quarter sits in context. Pair the raw attainment with the two or three leading indicators that drive it (pipeline coverage ratio, win rate, average deal size, cycle time) so the review captures whether the number came from a healthy funnel or a hero close. Reps who overindex on a single big deal and reps who grind out a consistent base show up very differently when the leading indicators sit next to the attainment line.

• Show attainment at the period level and the segment or product-line level so mix skews are visible to both parties.
• Include ramp-adjusted attainment for new hires still inside their ramp window and footnote the ramp formula.
• Pair attainment with pipeline coverage, win rate, average deal size, and cycle time so the number has context.
• Flag any period where a single deal moved attainment by more than 25 percent and discuss that deal explicitly in the conversation.

The qualitative section is where reviews either compound into fairness or collapse into vibes. Use the same four-to-six-dimension rubric across every rep on the team and across every cycle. The default dimensions for an AE review are discovery depth, negotiation and commercial judgment, forecasting accuracy, pipeline hygiene, and cross-functional collaboration (sales engineering, customer success, marketing, legal). Score each dimension on a fixed scale (a 1 to 5 or a four-level named scale like developing, performing, strong, exceptional) and anchor the scale with written descriptions of what each level looks like. For every rating, write a two-to-three-sentence justification that cites a specific deal, call moment, or forecast call rather than a general impression. Reps retain feedback tied to their own words and their own deals; they discard feedback tied to vague labels.

• Freeze the rubric dimensions at the start of the fiscal year so ratings compare across cycles for the same rep.
• Anchor each scale level with a written description of the behavior that earns it, visible in the template itself.
• Require a two-to-three-sentence evidence block per rating that names a specific deal, call, or forecast moment.
• Calibrate ratings across the team with another manager before you share any review so no one rep absorbs rubric drift.

Forecasting is the one qualitative dimension that has a hard numeric answer, which is why it deserves its own treatment inside the skills section. Pull the rep's forecast submissions across the review period and compare each one against actual close. Compute two numbers: the mean absolute error between committed and closed revenue, and the directional bias (does the rep habitually overcommit, undercommit, or hit the number). Pair those with a short note on the forecast calls themselves (did the rep know their deals, did they bring risk signals early, did they revise commits honestly when the data changed). Forecasting accuracy is often the single most load-bearing qualitative input to comp conversations and promotion decisions, so it carries its own math block inside the rubric rather than disappearing into a general judgment rating.

• Pull every weekly or monthly forecast submission across the review period and align each one to actual close.
• Compute mean absolute error and directional bias so reps see habit, not just one bad quarter.
• Score the forecast calls themselves on preparation, risk disclosure, and willingness to revise commits on new data.
• Separate the math score from the behavior score so a rep who hits the number by sandbagging does not get credit for forecasting judgment.

A review that ends with next quota and nothing else teaches the rep that the only input they control is harder closing. Set two or three next-period goals and write them as behavior changes paired with a measurable outcome. A rep who scored low on multi-threading gets a goal like 'engage a second economic buyer on every deal above 50k ARR before stage three, measured by named-contact logging in the CRM.' A rep who scored low on forecasting gets 'submit commits with explicit risk notes on every deal above 25k and revise within 24 hours of new signal.' Numeric goals (next period quota, pipeline coverage target, activity floor) sit alongside the behavior goals, not instead of them. Reps who leave a review with behaviors they can run tomorrow engage with the plan; reps who leave with only a number disengage until the next cycle.

• Pick two or three goals per rep, never five, and freeze them for the full next review period.
• Write each goal as a one-sentence behavior change paired with a measurable outcome and a timeframe.
• Pair at least one behavior goal with a numeric target that will show up in the next scorecard trend.
• Tie goals to the skills rubric dimensions so the rep sees the line from rating to goal to next cycle rating.

The development plan is where the review stops being a verdict on the rep and starts being a shared contract. For every goal, name the enablement, coaching, deal shadowing, course, or stretch assignment that will support the behavior change, and name who owns each one. If the goal is multi-threading, maybe the plan commits the manager to coaching the rep on executive emails every other week and connects the rep with a tenured peer on three joint calls. If the goal is forecasting, maybe the plan commits the sales operations team to a one-on-one on commit discipline. Development plans with no manager commitments read as 'you fix yourself and we will check in next quarter,' and reps correctly treat them as busywork. Commitments in writing from both sides is what makes the plan land.

• Pair every rep-side goal with at least one manager-side or org-side commitment to support it.
• Name the person who owns each development action, including the manager, the enablement partner, or a peer coach.
• Set checkpoints (30, 60, 90 days) rather than waiting for the next review to inspect progress.
• Capture the plan in the same system of record the rep already uses so it does not get buried in a shared drive.

The comp calibration section is the one most managers want to write first and should write last. Pull the finance-approved comp bands for the role and tenure, the merit matrix for the cycle, and any promotion or PIP triggers that apply. Then write a short calibration narrative: this rep is at this attainment, these ratings, this tenure, and here is the recommended merit percentage, promotion decision, equity refresh, or performance plan status with a one-paragraph justification tying it to attainment, rubric ratings, and policy. Comp decisions get challenged, so the narrative is written to be defended to finance, HR, and the rep. Reps who read a comp decision tied to clear policy and clear ratings accept it, including bad news, because they can see the math. Reps who read a decision that reads like a manager verdict push back whether the number is good or bad.

• Pull the current comp bands, merit matrix, and promotion or PIP policies before writing any recommendation.
• Reference the attainment numbers and rubric ratings explicitly in the comp narrative so the chain is auditable.
• Separate base salary adjustment, variable rate change, equity, and promotion decisions as distinct lines, not one blob.
• Flag any recommendation that falls outside the band for finance review before the conversation happens, not during it.

A review written in isolation is a review that drifts. Before any rep sees their document, pull the full set of draft reviews into a calibration session with peer managers or a second-line leader. Review the ratings distribution, flag any outliers (a team of nine reps with eight exceptional ratings on negotiation is a calibration problem, not a team of superstars), and align comp recommendations against the finance-approved bands. The point is not to downgrade high performers but to make sure the same evidence produces the same rating across managers. Reps compare notes, finance compares distributions, and a review cycle without calibration will produce a comp decision that one rep's manager can defend and another's cannot, which erodes trust in the whole process within one cycle.

• Schedule a 90 minute calibration session with peer managers after draft reviews are written but before any rep sees them.
• Review the ratings distribution per dimension and flag outliers for a second look, not an automatic downgrade.
• Compare comp recommendations against the merit matrix and finance-approved bands to catch outliers early.
• Document the calibration decisions in a changelog so the next cycle starts from a shared baseline.

The template is only as good as the conversation that lands it. Share the written review with the rep 24 to 48 hours before the live meeting so they can process attainment, ratings, and comp before they have to react in the room. Open the meeting on the data (attainment and leading indicators), move to the rubric ratings with specific evidence per dimension, pause for the rep's view, cover goals and the development plan next, and close on comp calibration. Keep the comp conversation last and short; it should feel like a conclusion the written document already made, not a surprise. End with a written commitment from both sides on the next period's goals and the development checkpoints, logged in the same system the rep already uses, so the review flows into the next cycle instead of sitting in a drive folder.

• Share the written review 24 to 48 hours in advance so the rep is not reacting to ratings and comp in real time.
• Open on attainment, not ratings, so the conversation starts on numbers both parties already see.
• Reserve the final 10 minutes for next-period goals and development commitments, not for the comp decision.
• Log the agreed goals and development checkpoints the same day in the system of record so momentum does not evaporate.