# Sales rep scorecard: a monthly one-pager your Pipedrive Insights can already build

https://salesbond.app/blog/sales-rep-scorecard-pipedrive/
Published: 2026-10-05 · Updated: 2026-10-26

A sales rep scorecard is a one-page monthly summary of one rep’s numbers placed next to the team’s. In Pipedrive you can assemble it from three Insights reports, deal performance, deal duration and activities performance, saved once for the same rep and refreshed each month, so nothing is retyped and every figure traces back to a report your rep can open themselves. The page is not a grade. It is the agenda for one conversation a month, and it works only if both people trust where each number came from.

Scoring how a rep handles calls is a different sheet for a different meeting, the [call review scorecard](https://salesbond.app/blog/sales-call-review-scorecard/); here we only deal with what the CRM already counted.

## The template you downloaded has a problem you can’t see yet

Most scorecard templates in search results are the same spreadsheet. Columns for calls, emails, meetings, deals won, revenue, maybe average deal size and conversion. A row per rep, targets in another block. You fill it on the last day of the month, from memory or from a few reports, and it looks finished.

If a sheet like that already runs next to Pipedrive, we went through a [sales tracking spreadsheet](https://salesbond.app/blog/sales-tracking-spreadsheet-pipedrive/) column by column: what becomes a field, a filter or a report.

The problem appears in the one-on-one. The rep looks at “Calls: 64” and asks where that came from. You say the CRM. They open Pipedrive and find 71, or 58, because the template counted something slightly different from what the report counts: scheduled instead of completed, or the whole team’s pipeline instead of theirs. Now the meeting is about the spreadsheet, not about the deals. We have seen this often enough to call it the default outcome of a retyped scorecard.

So the rule for the rest of this article: a number goes on the scorecard only if the rep can open the report it came from and see the same figure. Everything else is commentary.

## Three Insights reports behind a sales rep scorecard

Pipedrive Insights is the reporting part of the product: reports grouped by category, goals, dashboards and export, with the number of reports you can keep depending on your plan ( [Pipedrive: Insights](https://support.pipedrive.com/en/article/insights-feature)). A scorecard needs three of them.

Set up **Activities performance** first, because its filters are documented and they do exactly what a scorecard needs. The path is Insights, then “+ Create”, Report, Activity, Activities performance. The filter fields include Assigned to user, Type of activity, Status, Add time, Due time, Pipeline and Team, and the report has an Export option ( [Pipedrive: Activities performance report](https://support.pipedrive.com/en/article/insights-reports-activities-performance)). “Assigned to user” set to one rep, “Status” set to done, a date range of one month: that is the activity half of the scorecard, with a column per activity type if you want it.

**Deal performance** counts how many deals were started, won and lost. Two defaults matter. The filter starts at “Deal created is this year”, and archived deals are included unless you filter them out ( [Pipedrive: Deal performance report](https://support.pipedrive.com/en/article/insights-reports-deal-performance)). The chart has view by, measure by and segment by controls, so the same report can show count or value, by month or by stage. Pipedrive’s help for its deal reports lists owner among the deal fields you can filter on ( [Pipedrive: Deal conversion report](https://support.pipedrive.com/en/article/insights-reports-deal-conversion)). The date filter works on creation date, so a one-month range would miss old deals closed that month; we leave it on this year and compare with last month’s page. Decide what to do about archived deals, and open the report together with the rep so you both read the same filter row.

**Deal duration** shows the average time a deal takes to move through the pipeline. Its defaults are “Deal created this year”, Pipeline set to your default pipeline, and Status won or lost; the formula is total time in all stages divided by the number of deals ( [Pipedrive: Deal duration report](https://support.pipedrive.com/en/article/insights-reports-deal-duration)). Read that formula twice. It is an average over closed deals, including lost ones, in one pipeline. Change the pipeline and the the number changes completely.

Save each report with the rep’s name in it’s title. Next month you change one date range, and the rep can still open all three.

## One rep, one month, read out loud

An illustration: the rep and the numbers are made up and deliberately ordinary, so the reading method is the point.

![Sales rep scorecard for Marit, September, illustrative: seven rows compare her with the team and name the Insights report behind each](https://salesbond.app/wp-content/uploads/2026/10/sales-rep-monthly-scorecard-pipedrive-2.png)

Marit works in a team of five. On her September page the deal rows cover deals created this year: 14 started against a team average of 11, four won against five, six lost against three. Deal duration in the main pipeline for those deals: 41 days for her, 27 for the pipeline as a whole. The activity rows cover September alone. 68 calls done and 19 meetings done, both above the team, and 11 activities overdue at month end, where the team sits at four.

Read as a ranking, that page is confusing. She is above the team on effort and below it on wins. A template would color three cells green and three cells red and leave you to make a speech.

Read row by row with the source next to it, the page tells a story. The activity rows are high and the won row is low, so the question is not “work harder”. She has lost six deals so far this year, twice the team’s count, and the deal duration says those deals were old: a 41-day average over won and lost deals, in a pipeline that averages 27, means she carried deals longer before calling them. The overdue activities point the same way. Eleven tasks left open at month end usually means deals that were still “in progress” on paper while nobody had a next step.

Now the conversation has a shape. Not “your win rate is down”, but “six of your deals this year ended as lost, and most of them sat for a long time first. Which of the ones still open look like those six did at the start?” That is a question about deals, and she can answer it with Pipedrive open. The diagnosis itself is in [rep problem or pipeline problem](https://salesbond.app/blog/rep-or-pipeline-problem/); the scorecard is where you notice you need it.

## The numbers you should not compare between people

Some scorecard rows are honest for one rep and dishonest the moment you put two reps side by side. Three cases come up every month.

Different pipelines. Deal duration runs on one pipeline by default. If one rep works the new-business pipeline and another works renewals, their averages describe two different processes. Calling the faster one better is a reporting mistake. Compare each rep with thier own pipeline’s average, as the example above does.

Different deal sizes. “Measure by” in deal performance switches between deal count and deal value, and two large wins or nine small ones can both be a good month. If your deal sizes vary, show both measures or talk about the deals by name. The same goes for a team that mixes a [desk rep and a field rep](https://salesbond.app/blog/inside-sales-vs-outside-sales-crm-tracking/): call counts will not compare, and here is what does.

Unequal starts. Deal performance counts deals by creation date, and the default range is the whole year ( [Pipedrive: Deal performance report](https://support.pipedrive.com/en/article/insights-reports-deal-performance)). A rep who joined in June and one who has been here since January are not counted from the same line. The scorecard cannot fix that. It can only make you say it out loud before you compare.

The habit that protects you is dull: rows that are not comparable across the team get read only against the rep’s own previous months. The [six numbers a sales manager actually needs](https://salesbond.app/blog/sales-manager-dashboard-six-numbers/) are the team-level view; this page is the person-level one, and the two should not borrow rows from each other.

## How the conversation goes when the page is on the screen

We run it with the scorecard open in one window and Pipedrive in the other, and we have come to think the second window matters more than the first.

The rep speaks first. Not about the numbers, about the month: which deals they are glad about, which ones they would do differently. Then we go down the page one row at a time and for every row that looks unusual the question is the same: which deals are in there? Deal performance shows a count of lost deals; the useful part is the list behind it, and in the meeting we open it. The activity report shows overdue tasks. We open those too, and most months half of them belong to two deals that should have been marked lost weeks ago. For a single lost deal from that list, [a separate one-on-one debrief](https://salesbond.app/blog/lost-deal-debrief-rep/) works better than the monthly page.

A monthly scorecard talk is not a sales rep performance review, and it goes wrong in two ways. Either the manager has already decided what the numbers mean and the rep starts defending, or the page turns into a ritual both people glance at. The fix is the same: pick the one row that surprised you most and spend the time there.

Agree on one thing to change before you close the page, and write it down on the deals, not on the scorecard. If Marit’s old deals were the issue, the follow-up is a next activity on each deal she still has open, not a target for “fewer lost deals”. Targets on a scorecard are easy to hit by not entering deals. Next activities on deals are hard to fake. If the conversation keeps landing on the same row three months in a row, that is when it stops being a scorecard talk and becomes a [performance plan](https://salesbond.app/blog/sales-performance-improvement-plan-small-team/). The [one-on-one agenda](https://salesbond.app/blog/sales-1-on-1-agenda/) we use has a slot for this page; it is one slot, not the whole meeting.

## Twenty minutes a month, and what to stop doing

The scorecard dies the same way the template did: someone keeps adding rows until it is a dashboard nobody reads. Keep it to what the three reports give you, and run the same routine every month.

1. Change the activities report’s date range to last month. Don’t rebuild anything.
2. Leave the two deal reports on deals created this year and check that archived deals are still handled the way you decided.
3. If the rep works a pipeline other than the default one, confirm the deal duration report is on theirs.
4. Write the team figure next to a row only where the row is comparable. Leave the others blank on purpose, so nobody reads a gap as a zero.
5. Pick the one row that surprised you and open the deals behind it before the meeting.
6. After the meeting, add next activities on the deals you discussed.

The scorecard itself gets nothing written on it. If the routine takes more than twenty minutes, something the reports don’t produce has crept in. Remove it. The [activity metrics piece](https://salesbond.app/blog/sales-activity-metrics-small-team/) argues the same point from the activity side: a small team needs fewer measures, read more carefully.

## Where SalesBond fits

A disclosure, since the scorecard showed Marit’s problem months late: we build SalesBond, a sales management layer that works with Pipedrive, HubSpot, Salesforce and Zoho CRM. Its Deal Health part checks every deal against more than 20 rules across categories such as Activity, Progression, Data, Ownership and Forecast. It also has a per-rep view with the rep’s average score, their deal list and their problem areas, and it gives a plain explanation of what lowered the score and a recommended action for each violation. In Marit’s case that view would have flagged those deals while they were still open, rather than leaving them to show up as six lost deals on a September page. The monthly scorecard still earns its place as the conversation. It just should not be the first time you hear about the deals. [Check your CRM with SalesBond](https://salesbond.app/).