Weekly sales report template
Most weekly sales reports are a dashboard screenshot with a line saying pipeline is strong. Nobody can tell what changed since last week, so the report gets skimmed and the real conversation happens in side channels. This template reports the change, not the state: what closed, what moved in and out of the quarter, how the commit moved and why, and which deals are at risk.
Download it
What you get
- A headline block comparing this week to last week for bookings, attainment, commit, best case, and pipeline
- A pipeline movement bridge that reconciles starting and ending in-period pipeline
- A forecast change table by manager with a required reason for every movement
- A top risks table with owner, action, and due date
- A checklist for making the report consistent enough to compare week over week
Who it's for
- RevOps analysts who own the weekly numbers
- Sales managers who explain their forecast changes
- VPs of Sales who need the week's changes on one page
What's inside
7 sections, each listed with its own size. The first is previewed below; the remaining 6 come with the download, with blank rows ready to fill in.
| Section | Size | Previewed |
|---|---|---|
| Report header | 5 fields to complete | Below |
| Headline numbers | 5 columns, 5 worked example rows | In the download |
| Pipeline movement bridge | 4 columns, 8 worked example rows | In the download |
| Forecast change by manager | 5 columns, 4 worked example rows | In the download |
| Top risks | 8 columns, 2 worked example rows | In the download |
| Before you send | 8-point checklist | In the download |
| Why report movement instead of totals | Guidance notes | In the download |
Preview of section 1
Report header
- Week ending
- e.g. 2026-09-18
- Quarter and week
- e.g. Q3, week 12 of 13
- Snapshot time
- e.g. Friday 5pm
How to use it
1. Snapshot the pipeline at the same time every week
Take the snapshot at a fixed time, such as Friday 5pm, and build the report from that snapshot. If you pull live data on Monday, weekend updates distort the week-over-week comparison and the bridge will not reconcile.
2. Make the bridge reconcile before anything else
Starting pipeline plus created and pulled-in, minus won, lost, pushed, and amount changes, must equal ending pipeline. If it does not, there is a definition problem, and you should fix it before sending, not add a footnote.
3. Require a reason for every commit change
Any manager whose commit moved by more than your threshold (for example 50,000) writes one sentence naming the deals. A number without a reason is not reported.
4. Limit risks to five deals
List the five deals whose loss or slip would change the quarter most. Each gets an owner and a dated action. A list of twenty risks is a pipeline report, not a risk list.
5. Send it before the forecast call
Distribute the report at least a few hours before the weekly forecast call so the meeting starts from shared facts and spends its time on the risks.
Frequently asked questions
What should be in a weekly sales report?
Closed won to date against target, the change in commit and best case since last week, a bridge showing how in-period pipeline moved (created, won, lost, pushed), forecast change by manager with reasons, and a short list of at-risk deals with owners.
How long should a weekly sales report be?
One page. If it runs longer, move detail into an appendix or the CRM. The weekly report exists to show what changed and what needs attention, not to replace the dashboard.
Who should prepare the weekly sales report?
RevOps usually builds it from a fixed pipeline snapshot, and sales managers supply the reasons for forecast changes. Keeping the numbers with RevOps and the commentary with managers keeps it consistent and accountable.
What is a pipeline movement bridge?
A reconciliation from last week's pipeline to this week's: starting pipeline, plus created and pulled-in deals, minus won, lost, and pushed deals, plus or minus amount changes, equals ending pipeline.