Most sales teams have a weekly report. Many of those reports are collections of numbers that people glance at and forget. The difference between a weekly sales report that drives decisions and one that just fills inboxes comes down to what you include, how it’s framed, and whether it’s set up to prompt action.

This guide covers what belongs in a weekly sales report, how to build it from your CRM data, how to schedule and distribute it efficiently, and how to format it so it actually gets read and used.

What a Weekly Sales Report Is For

A weekly sales report serves several distinct purposes:

1. Accountability: It creates a consistent record of what’s happening in the pipeline, which keeps reps accountable for maintaining accurate CRM data and for deals they’ve committed to.

2. Early warning: Patterns emerge over multiple weeks. A deal that stalls for two weeks in a row is more visible in a weekly report than in a monthly one.

3. Coordination: Sales managers, marketing, finance, and leadership all need visibility into pipeline health. A well-designed weekly report is the primary mechanism for that shared visibility.

4. Decision-making: Managers use weekly data to decide where to focus coaching, which deals need resources, and whether the team is on track to hit targets.

The report that does these four things well is short, concrete, and tied to action. The report that fails at them is long, data-heavy, and ends with nobody knowing what to do next.

What to Include in a Weekly Sales Report

Section 1: Deals Closed This Week

Start with wins. Listing every deal closed this week — name, value, rep, and close date — creates a moment of recognition and establishes the baseline for weekly performance.

Include the key metrics:

• Number of deals closed
• Total value of deals closed
• Comparison to weekly target (or prior week)

Keep it brief. This section should be scannable in 30 seconds.

Deal	Value	Rep	Close Date
Acme Corp	$24,000	Jordan	Nov 18
Blueridge Tech	$8,500	Casey	Nov 20
Summit Solutions	$15,000	Jordan	Nov 21
Total	$47,500

Section 2: New Deals Entered the Pipeline

This section shows what’s been added to the top of the funnel this week. New deals are a leading indicator — they’ll affect revenue 30, 60, or 90 days from now.

Include:

• Number of new opportunities created
• Total value of new pipeline
• Notable deals by name (especially large or strategic opportunities)

Section 3: Pipeline Movement

This is often the most valuable section of the weekly report — and the one most reports leave out. Pipeline movement shows deals that advanced from one stage to another during the week.

Deal	Previous Stage	Current Stage	Value	Rep
Harper Medical	Discovery	Proposal	$31,000	Alex
Northfield Group	Lead	Discovery	$12,500	Morgan
Coastal Analytics	Proposal	Negotiation	$42,000	Casey

This view tells you whether deals are moving, which is a better health indicator than total pipeline value alone. A pipeline where nothing has moved in two weeks is a problem, even if the total value looks healthy.

Section 4: At-Risk Deals

Every week, surface the deals that show warning signs: no activity in the past two weeks, missed follow-up dates, upcoming close dates that are unlikely to hit, or deals where a key contact has gone dark.

This is where the weekly report transitions from informational to operational — these are the deals that need manager attention, coaching, or resource intervention right now.

Present these concisely:

Deal	Risk Signal	Rep	Recommended Action
Oceanview Logistics	No activity 18 days	Jordan	Call scheduled for Nov 22?
Merced Partners	Close date missed	Alex	Re-forecast or disqualify
Ridgeline Capital	Champion went dark	Casey	Executive outreach from VP

Section 5: Key Metrics Summary

A brief metrics section at the top or bottom (your choice — some readers want it first, others want context before numbers) covering:

Metric	This Week	Last Week	Weekly Target
Deals closed	3	5	4
Revenue closed	$47,500	$61,000	$52,000
New pipeline created	$86,000	$71,000	$75,000
Deals advanced in stage	8	6	—
At-risk deals	3	2	0

What NOT to Include

A weekly report overloaded with data becomes background noise. Keep it tight. Leave out:

• Total pipeline by stage (this belongs in a pipeline review meeting, not a weekly email)
• Activity counts (calls made, emails sent) unless they’re specifically tied to a performance concern
• Year-to-date revenue (monthly or quarterly cadence is more appropriate for this)
• Individual rep rankings (these create politics in a shared report; save them for 1:1 reviews)
• Data that requires interpretation to understand — if it needs a paragraph of explanation, it belongs in a separate analysis document

How to Build the Report in Your CRM

Most CRMs let you create saved reports and dashboards that refresh automatically. The goal is a report that generates itself with minimal manual work, so it doesn’t become a burden to produce.

Step 1: Build the Component Reports

Create separate CRM reports for each section:

Closed deals report: Filter by Close Date = this week, Stage = Closed Won. Include deal name, value, owner, close date.

New pipeline report: Filter by Created Date = this week, Stage not equal to Closed Won or Closed Lost. Include deal name, value, owner, stage.

Pipeline movement report: This is the trickiest one. You need stage history data — deals where stage changed in the past 7 days. Look for “stage change” or “stage history” in your CRM’s report builder. Include deal name, previous stage, current stage, value, owner.

At-risk deals report: Build this with a combination of filters:

• Last activity date more than 14 days ago, OR
• Expected close date in the past (missed close date), OR
• A custom “At Risk” flag if your team uses one

Step 2: Combine into a Dashboard or Template

Once your component reports exist, you have two options:

Option A: CRM dashboard. Create a weekly dashboard that displays all component reports in one view. Share the dashboard link in your weekly distribution.

Option B: Exported report compiled into a document. Export each report weekly and compile them into a consistent document format. More work, but gives you full control over formatting and narrative context.

Most modern CRMs allow you to schedule report exports to be emailed automatically. If your CRM supports this, use it — automated distribution ensures the report actually goes out even during busy weeks.

Step 3: Add a Brief Narrative

Numbers without context invite misinterpretation. A two- or three-paragraph executive summary at the top of the report frames the week’s data with context:

• What does this week’s close number mean relative to the month/quarter trajectory?
• Are there specific deals driving the at-risk list that leadership should know about?
• Is there a pattern in this week’s pipeline movement (or lack of it)?

This narrative section is the most valuable part of the report for senior readers who won’t click through to the underlying data.

Scheduling and Distribution

Who Gets the Weekly Report

Define your distribution list intentionally:

Audience	What They Need from the Report
Sales reps	Their own deal status; team wins
Sales manager	Full report; at-risk deal intervention priorities
Marketing	New pipeline volume; lead source breakdown (if relevant)
Finance	Closed revenue; short-term forecast
Exec team	Brief summary only — consider a condensed version

When to Send It

Friday afternoon or Monday morning — teams differ on preference. Friday creates a natural close to the week. Monday gives reps a starting-week briefing. Avoid midweek, when it gets lost in operational emails.

Consistency matters more than timing. The same day and time every week trains your team to expect and read it.

Making the Report Actionable

The test of a good weekly sales report: does reading it change what someone does that week?

To make it actionable:

• Every at-risk deal should have a named owner and a specific next step
• Managers should review the report before weekly team meetings so pipeline discussions are informed rather than exploratory
• The report should link directly to the underlying CRM records so recipients can click through to the deal for more context
• Consider adding a “This Week’s Priority” section that names the two or three most important deals to focus on

A report that people read and then go back to their normal routine hasn’t done its job. A report that changes what three reps do on Monday morning has.

Frequently Asked Questions

How much time should producing the weekly report take? Once your CRM reports are built and scheduled, producing the weekly report should take no more than 20-30 minutes — enough time to review the auto-generated data, write a brief narrative, and send. If it takes longer than that, the process isn’t automated enough. Invest time once in building the CRM reports correctly, and the ongoing effort drops substantially.

Should individual reps write their own weekly updates? Some teams ask reps to submit a brief weekly update in addition to — or instead of — a manager-generated report. Rep self-reporting is valuable for qualitative deal color (“I think Acme is about to go dark because their CFO changed”) but less reliable for the metrics, since CRM data quality varies by rep. The most effective approach is a manager-generated report based on CRM data, supplemented by rep updates on specific deals.

What if my CRM data is consistently inaccurate? A weekly report that surfaces data quality problems — deals with missing close dates, no recent activity logged, stage data that doesn’t reflect reality — is actually doing its job. Use the at-risk report as a data quality audit as much as a sales intelligence tool. When managers ask about specific deals in the report, reps are incentivized to keep their data accurate. Data quality often improves once reps understand their CRM records are being reviewed regularly.

How is a weekly report different from a pipeline review meeting? A weekly report is an asynchronous artifact — people read it on their own time. A pipeline review meeting is a synchronous discussion. They serve different purposes. The report provides information; the meeting drives decisions and accountability. The best setup uses the weekly report to inform the meeting — managers review it beforehand, come with specific questions about at-risk deals, and skip the time that would otherwise be spent pulling up basic pipeline data during the meeting.