# The weekly sales report a manager will actually read

https://salesbond.app/blog/weekly-sales-report-what-to-include-and-what-to-cut/
Published: 2026-09-29 · Updated: 2026-10-26

A weekly sales report should fit on one page and answer three questions: what changed since last week, which deals are at risk, and what you will do about it. Everything else is reference material.

Put simply, a weekly sales report is a one-page summary of the week’s won, lost and moved deals that a sales manager uses to decide what the team does next week.

That sounds obvious, and most reports still fail it. They open with twenty metrics, each with a sparkline, and leave the reader to work out which three matter. The manager skims, the VP skims, and on Monday the team does exactly what it did last week. A report that nobody acts on is an export with a logo.

What follows is the layout we use when building weekly reports on top of Pipedrive data: five blocks, a short list of things to cut, and a note from the manager that turns the numbers into decisions. You can read it in five minutes. That’s the whole design goal.

## Pipeline first, activity second

Every CRM gives you two families of numbers, and they answer different questions.

Pipeline numbers describe deals: what was won, what was lost, what was created, what advanced a stage, and which close dates got pushed. They live on the deal record, in its value, stage, expected close date and won/lost status. Activity numbers describe effort: calls logged, emails sent, meetings held, tasks closed.

Read pipeline first. It tells you whether the week moved money. Activity is useful as an explanation for something the pipeline already showed you. If new pipeline dropped for one rep, the activity log might show why (a week of onboarding calls with a big new customer, or simply two days off). If new pipeline is healthy, a dip in calls is not worth a paragraph.

Reports that lead with activity invite the wrong conversation. “You made fewer calls” is easy to say and easy to game. “Two of your deals had their close dates pushed a month and neither has a next step” is harder to hear, and its the one that changes Monday.

So in the report below activity never gets its own block. It shows up inside the manager’s note, and only when it explains a pipeline change.

## What goes in a weekly sales report: five blocks

A weekly sales report needs five blocks, in this order: headline, won and lost, pipeline movement, at-risk deals, manager note. The order follows the three questions from the top down, so a reader who stops after the first block still knows what happened.

You can use the list below as a weekly sales report template. Each block comes with one line from a hypothetical week 39 for a team of four reps. The figures are invented for illustration; they add up to each other, not to anyone’s real quarter.

1. The headline: one sentence with the week’s result against plan and the single biggest reason for the gap or the win. *Won $48,000 against a $60,000 weekly plan. The gap is one deal, Harbor Dental ($12,000), whose close date was pushed to October.*
2. Won and lost deals, with value, count and the lost reason recorded in the CRM. *5 deals won, $48,000. 3 lost: two to “no decision”, one to price.*
3. Pipeline movement, meaning new deals created, deals that advanced a stage, pushed close dates and deals that sat in the same stage with no activity. *11 new deals, $95,000. 6 moved to proposal. 4 pushed close dates, $31,000 in total, Harbor Dental included.*
4. A short list of at-risk deals, largest first, each with a named problem and a named next step. *Harbor Dental, $12,000: champion on leave, no meeting booked. Next step: Dana books a call with the finance lead by Wednesday. Two more deals follow in the same format.*
5. The manager note, two sentences per rep (more on this below).

![Manager note segment in the weekly sales report highlighting actions for sales representatives.](https://salesbond.app/wp-content/uploads/2026/09/weekly-sales-report-2.png)

Look at what the headline names: a deal. “Revenue was down” would also be true, and it would leave everyone guessing. With Harbor Dental in the first line, the reader already knows where Monday’s first conversation goes.

The pipeline block is where most of the thinking happens. A pushed close date is an open deal whose expected close date was moved later during the week, and it’s the number we’d fight hardest to keep. One push is normal. A deal that gets pushed every week while its stage stays the same is a forecast problem wearing a costume. Listing pushed value next to new value also breaks a common illusion, where a healthy-looking total pipeline hides the fact that half of it was supposed to close last month.

Keep the at-risk list short. If everything is at risk, nothing is. We’d rather see three deals with a real next step than twelve with the word “follow up”.

## What to leave out, and why

The hardest part of this report is the stuff you remove, because every number you cut was added by someone who thought it mattered.

Start with cumulative totals that don’t move week to week. Year-to-date revenue, total pipeline value, number of open deals: they change slowly, they’re on the dashboard anyway, and putting them on a weekly page trains the reader to skip lines. If a total matters, show what changed in it this week and leave the total itself on the the dashboard.

Then drop raw activity counts per rep. Activity explains a pipeline change after the fact; it isn’t the thing the report is about. A table of calls and emails by rep turns the report into a leaderboard, and leaderboards get gamed fast. If the team wants a board, [a leaderboard built on one number](https://salesbond.app/blog/sales-leaderboard-small-team-pipedrive/) a rep controls belongs on its own page, not in this report. Keep the activity log one click away for the manager who needs it, and keep it off the page.

Ratios computed on tiny samples are next. Win rate is the share of closed deals that were won, and on five closed deals it swings wildly from one week to the next. It tells you almost nothing, but it looks precise, and precise-looking numbers get argued about. Save win rates and conversion rates for the monthly or quarterly view, where there’s enough volume for them to mean something. If you do want [stage-to-stage conversion in HubSpot](https://salesbond.app/blog/hubspot-funnel-report-stage-conversion-weekly-manager-read/), read it over a rolling 90-day window rather than a single week.

Also gone: charts that need a legend to read, forecasts nobody on the team would defend out loud, and anything the reader can’t act on this week. Point at each line and ask: if this number were twice as big, what would we do differently on Monday? If nobody has an answer, the line goes.

None of this means those numbers are useless. They belong on a dashboard or in a monthly review. The weekly page has one job, and it does that job better with less on it.

## Where the numbers come from, and what makes them true

Every block above maps to fields that already exist on a deal or an activity in a CRM like Pipedrive. The report is only as honest as the data entry behind it, though, and each block has one field that quietly breaks it when it’s empty.

- Won and lost needs a lost reason on every lost deal. Without it, the block is a list of numbers with no lesson.
- Pipeline movement depends on an expected close date on every open deal, and on reps updating it when reality changes instead of leaving last month’s date in place.
- New pipeline: a deal value from the moment the deal is created, even a rough one. Deals with no value vanish from every sum.
- For stalled deals, activities have to be logged and marked done, and each open deal needs a next activity scheduled.
- The at-risk list needs an owner on each deal, so the next step has a person attached.

That’s five fields. If they’re filled in, the report almost writes itself from a saved filter or two. If they aren’t, no layout will save it, and the first few weeks of this report are mostly about fixing the data. That’s fine. A report that exposes empty close dates is already doing its job.

One practical habit helps: pull the numbers on the same weekday and at the same time every week. Pipeline totals change by the hour, and comparing Monday-morning numbers to Friday-evening numbers creates movement that never happened. If the data lives in Salesforce, here is [which Salesforce reports a manager opens](https://salesbond.app/blog/salesforce-reports-sales-manager-weekly/) on Monday.

## The manager note: two sentences per rep

This is the part that turns a report into a decision, and it’s the part most templates skip.

For each rep, write two sentences. The first says what happened in their pipeline this week, in plain words. The second says what you’ll do about it, and it has to name an action with a day attached.

Using the same hypothetical team:

> Dana: Harbor Dental’s close date was pushed to October because her champion is on leave, and her other two proposals are on track. I’ll join her call with their finance lead on Wednesday.
>
> Marcus: He opened four new deals, but none has a value yet, so his new pipeline reads as zero. We’ll fix the values in our one-on-one on Tuesday.

That’s all it takes. The note forces you, the manager, to look at each rep’s deals before the week starts, and it tells each rep what you’ll ask about. Activity data earns a mention here when it explains something (“fewer calls because she spent two days on the Harbor Dental security review”), and not otherwise.

Can’t write the second sentence for a rep? That’s information too. It usually means you don’t know their pipeline well enough yet, which is a better thing to discover on a Friday than in a quarterly review.

## Ship it the same day every week

A weekly report that arrives on Tuesday one week and Thursday the next stops being read within a few weeks. Pick a slot and hold it, whether that’s Friday afternoon so the team starts Monday with it or Monday morning before the pipeline meeting. The report and the meeting are different things: the page is what everyone reads on their own, and the meeting goes better when they already have. Send it as a page in the message itself rather than an attachment, keep the five blocks in the same order every time so people learn where to look, and resist the urge to add a sixth block the first time someone asks for “one more number”. Put that number on the dashboard and see if anyone misses it on the page. Usually nobody does.

## FAQ

### What is the difference between a sales report and a sales dashboard?

A dashboard is always on and holds every metric for whoever wants to look something up. A weekly sales report is a short document with a point of view: what changed, what is at risk and what the manager will do. Totals and trends stay on the dashboard.

### How often should you send a sales report?

Weekly for pipeline movement and at-risk deals, on the same day and at the same time every week. Win rates and conversion rates belong in a monthly or quarterly view, where there is enough volume for them to mean something.

### What is the difference between a daily and a weekly sales report?

A daily report is how the pipeline looks when the rep closes the day: which deals moved or slipped, what was done and how it went, what is overdue and what comes first tomorrow. Most of it comes straight from the CRM if you [close the day in Pipedrive](https://salesbond.app/blog/daily-sales-report-close-the-day-in-pipedrive/). A weekly report tracks deals for the manager: won, lost, created, moved forward and pushed, and it decides what the team does next week.