A weekly sales report should answer one question: what changed since last week. Totals restated every seven days teach a reader nothing, because the quarter's number barely moves week to week while the composition underneath it moves constantly.
ORM makes the same point about what converts with revenue leaders. The content that gets read is a weekly summary of what changed in the business from last week to this week, built on the specific numbers that team owns.
The five sections that belong in it
| Section | What it shows | Why weekly |
|---|---|---|
| Pipeline created | New qualified opportunities and their value | Creation rate compounds across the quarter |
| Stage movement | Deals that advanced or regressed | Regression is the earliest warning available |
| Close date changes | Deals pushed out or pulled forward | Directly changes the current-period number |
| Amount changes | Deals resized up or down | Reveals discounting and scope loss |
| Forecast delta | Week-over-week change in the commit | Ties the four sections above to the number |
Why close date changes lead the deal section
ORM identifies the strongest deal slippage signal plainly: a rep changing the close date. A deal that slips from one quarter to the next is less likely to close, even when it sits in commit. The weekly report is where that change becomes visible while there is still time in the period to respond.
The second signal is harder to see because it is an absence. ORM describes the earliest warning as the lack of any signal at all: no activity, no data changing, no notes. A weekly report that only lists deals that moved will never show those deals, so the report needs a companion list of open deals with no meaningful activity in a defined window.
What to leave out
Leave out quarter-to-date totals that have not moved. Leave out pipeline coverage as a standalone headline, since a coverage ratio without composition tells a reader the size of the pipeline and nothing about whether it will convert.
Leave out any metric nobody has ever acted on. Reports accumulate sections the way pipelines accumulate stale deals, and the fix is the same. Cut anything that has not changed a decision in a quarter.
Getting it read
Send it at the same hour every week, before the review meeting rather than during it. Name the deals. A line reading "three deals pushed out of the quarter" prompts a question. A line reading which three deals, owned by whom, and how far they moved prompts a decision.
Frequently Asked Questions
What should a weekly sales report include?
Five things: pipeline created this week, deals that changed stage, deals whose close date moved, deals whose amount changed, and the week-over-week movement in the forecast. Everything else belongs in a monthly or quarterly report. The weekly report exists to surface change, not to restate the quarter's totals.
How long should a weekly sales report be?
One screen. If the report needs scrolling, it has stopped being a change log and become a data dump. The named deals that moved should fit on the same screen as the forecast delta so the reader connects the two without clicking.
What is the difference between a weekly sales report and a pipeline review?
The report is the artifact and the review is the meeting. The report should be read before the review starts, so the meeting time goes to the deals the report flagged. Teams that read the report during the meeting spend most of the meeting on status updates.
Should a weekly sales report include activity metrics?
Include activity only where it explains pipeline movement, such as deals with no recorded buyer contact for several weeks. Raw call and email counts belong in a coaching report. In the weekly revenue report they crowd out the deal changes that actually move the number.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like what should be in a weekly sales report? into prescriptive action for your team.
Schedule a Demo