# CRM reporting for an owner and a head of sales: five reports, who reads them and when

https://salesbond.app/blog/crm-reporting-owner-head-of-sales-report-set-weekly-cadence/
Published: 2026-10-28 · Updated: 2026-11-12

A CRM report is a saved view of the deal, activity or pipeline data in your CRM, filtered to answer one question (which deals have no next step, what closes this month) and sent to a named reader on a schedule. An owner and a head of sales need five of them: pipeline movement, period forecast, deals without activity, won and lost with reasons, and rep activity.

CRM reporting is giving each of those reports a reader and a day, scheduling it to arrive by email, and deleting any report nobody acts on. The logic is the same in Pipedrive, HubSpot, Salesforce and Zoho CRM; only the object names differ.

## Reports are for decisions: who reads what

A report earns its place by naming the one person who will do something after reading it, with a decision they can take that day.

An owner decides two things from CRM data: is the period on track, and is something structural wrong (a rep, a stage, a product). A head of sales decides what to do today, with which deal and which rep. Different questions, so different reports, even when they read the same table.

So what is the difference between a CRM report and a CRM dashboard? A report reaches people by email on a schedule, and a dashboard stays in the CRM until somebody opens it. The screen and its tiles are in [the CRM dashboard for an owner and head of sales](https://salesbond.app/blog/crm-dashboard-owner-head-of-sales-tiles-and-fields/).

Our rule: every report in the CRM has a named reader, a day of the week and one sentence that starts with “when I see this, I will”. A report that cannot fill that sentence goes on the delete list. The sections of a single [sales report built from your CRM](https://salesbond.app/blog/sales-report-what-to-include-built-from-crm/) follow the same rule.

## The five CRM reports an owner and a head of sales need

Most “CRM reports” lists run to eight or twelve. We cut to five because each answers a question that comes up every single week, and because the sixth is the one that stops getting read.

| Report | Reader | Arrives | After reading, I will… |
| --- | --- | --- | --- |
| Pipeline movement | Owner, head of sales | Monday | ask about the stage where deals stopped moving |
| Period forecast | Owner | Monday | decide whether the month needs a plan B |
| Deals without activity | Head of sales | Every morning | pick three deals and ask the rep what happens next |
| Won and lost with reasons | Owner, head of sales | Monday, for last week | one change to make: a price, a stage exit, a qualification question |
| Rep activity | Head of sales | Every morning | compare effort with results, rep by rep, before the stand-up |

Pipeline movement is deals by stage with what entered, advanced, slipped and left since the last run. Stage totals alone give the size of the pipeline. This report adds which deals moved since the last run, so the review can start with the the deals that sat still.

Period forecast is open deals with a close date inside the period, summed by stage or forecast category. It is the only one of the five the owner may want without the head of sales in the room, because it decides spending.

Deals without activity is open deals with nothing logged and no next activity scheduled for longer than your sales cycle tolerates. It is the head of sales’s working list, and the one most often built once and then avoided.

Won and lost with reasons is closed deals for the previous week with the lost reason visible. Without the reasons, a win rate tells you the score and gives you nothing to change.

Rep activity is calls, emails and meetings logged per rep, next to deals moved per rep. The second column is what makes it a coaching report: activity that moves nothing is a topic for a conversation. One weekly document for a wider audience is a different thing; see [what goes into a weekly sales report and what to cut](https://salesbond.app/blog/weekly-sales-report-what-to-include-and-what-to-cut/).

## Monday for the owner, every morning for the head of sales

The owner reads once, on Monday: pipeline movement, forecast, then last week’s won and lost. Movement first because it explains the forecast; won and lost last because it generates questions for the head of sales.

Why weekly and not monthly? A report that lands on the first Monday of the month still leaves three weeks to act on what it shows, and a monthly report arrives after the month is closed.

The head of sales reads two reports every morning, deals without activity and rep activity. On Monday the three owner reports arrive too, read before the owner does, so the Monday conversation is about what to do.

![Weekly grid: owner reads three reports on Monday, head of sales reads two reports every morning plus the owner's three on Monday](https://salesbond.app/wp-content/uploads/2026/10/crm-reporting-owner-head-of-sales-report-set-weekly-cadence-2.png)

We keep the owner off the daily reports on purpose. An owner who reads the no-activity list every morning starts managing deals, and then nobody is managing the head of sales.

## Scheduling reports so they arrive without anyone opening the CRM

Every one of the five should be a scheduled email. A saved view depends on somebody remembering to look, and that tends to slip in the busiest weeks.

Most CRMs can email a saved report on a schedule; check your CRM’s help on scheduled reports for the exact options. Pipedrive’s Insights help describes view-only dashboard links rather than report emails, so on Pipedrive the Monday habit lives in the calendar instead. The Salesforce version is written up in full, including the trap of whose permissions build the email: [Salesforce schedule report: the three Monday subscriptions and the running-user trap](https://salesbond.app/blog/salesforce-schedule-report-subscription/). How to build the reports themselves is a CRM-by-CRM job, covered for [Zoho CRM](https://salesbond.app/blog/zoho-crm-reports-sales-manager/), [Salesforce](https://salesbond.app/blog/salesforce-reports-sales-manager-weekly/) and [Pipedrive](https://salesbond.app/blog/pipedrive-reports-pipeline-health/); this page stays with the decisions, which carry over whatever the CRM.

Send each report from the account of the person who owns the decision, so it keeps arriving after the admin who set it up has left. Give every report its own recipient list: the owner does not want the daily no-activity list, and a rep does not want the forecast. Time each one to land before the meeting it feeds, Monday reports before the Monday review and daily ones before the stand-up.

Empty emails are the last trap. Salesforce lets a subscription send only when a condition is met, so a no-activity report can stay quiet until it has rows. Where the CRM has no such switch accept the empty email for a week or two and then ask whether the report is still needed.

## The data each report quietly depends on

A report is a filter over fields. When the field is empty the report does not go blank; it shows a confident wrong number.

The basics are the same ones a dashboard needs: a stage that moves both ways on the day it changes, and a close date and amount somebody touched after the deal was created. We went through them tile by tile in [the field behind each CRM dashboard tile](https://salesbond.app/blog/crm-dashboard-owner-head-of-sales-tiles-and-fields/#the-field-behind-each-crm-dashboard-tile). Two obligations matter more for reports, because a report travels and nobody is there to explain it.

Won and lost with reasons needs lost reason as a required field at close, with a short fixed list. Free text gives you “price” spelled nine ways and a report nobody can group.

Deals without activity needs activity logged on the deal itself. Log the call on the contact and the deal still looks abandoned, so the report flags work that was done and the head of sales stops believing it.

If a field is not maintained, drop the report that reads it rather than keep sending a number everyone has learned to ignore.

## Reports to delete

Open the reports folder and count. Anything beyond the five above, plus what finance and marketing actually use, was mostly built for a question somebody asked once.

Delete a report when any of these is true: no named reader, no day it is read; nobody can finish “when I see this, I will”; the field it reads is not maintained. Delete the second copy of anything.

What is left is five emails to two people, on the days they are read, built on fields the team keeps honest.

A disclosure, since this is where a team starts wiring things up: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. It checks open deals and explains what needs attention, which is the no-activity list with the why next to it. Its first step is a free CRM audit, a PDF report on the last 30 days of your CRM, followed seven days later by a second PDF with what changed. Build the five reports first, because they show which fields your team actually fills; when you want the reasons on top, [check your CRM with SalesBond](https://salesbond.app/).
