A weekly sales report is the recurring artifact that drives the weekly sales review — the regular snapshot of the engine that the team looks at each week to decide what to do — and like everything in sales metrics, it works only if it contains the metrics that drive decisions and is structured for action, not as a status recap of vanity numbers. The weekly report's purpose is to support the most important operational cadence: the weekly review where the team looks at the engine's near-term state (pipeline, in-flight deals, leading indicators, the near-term forecast) and decides what to do this week. A good weekly report surfaces the few weekly metrics that matter, organized to drive that review's decisions; a bad one is a data dump of vanity numbers that gets recited and noted without driving anything. This guide is a template for the weekly sales report: its purpose, what goes in it, structuring it for action, avoiding the vanity report, and using it in the weekly review. The throughline is that the weekly report is the artifact for the weekly review, so it should contain the few decision-driving weekly metrics, structured for action — making the weekly review a forum for decisions about the engine, not a status-update ritual reciting numbers that change nothing.
The reason the weekly report matters so much is that the weekly review is the workhorse cadence for managing the sales engine operationally — the rhythm at which you act in time on the near-term state — and the report is what makes that review effective or hollow. The weekly review is where the team manages the engine week to week: checking the pipeline's health, the in-flight deals (what is moving, what is stalling), the leading indicators (where things are heading), and the near-term forecast — and deciding what to do this week (which deals need help, where to focus, what is off-track). This is the cadence where timely operational action happens, so its effectiveness directly affects the engine's week-to-week management. The weekly report is the input to this review: it surfaces the engine's near-term state for the team to act on. A good report (the right weekly metrics, structured for action) makes the review effective — the team sees what needs attention and decides what to do; a bad report (a data dump of vanity numbers) makes the review hollow — numbers get recited, nothing gets decided, and the workhorse cadence drives no action. So the weekly report is not an administrative formality but the artifact that determines whether the most important operational cadence drives decisions or wastes time. Getting it right — the few decision-driving weekly metrics, structured for action — is what makes the weekly review a genuine management forum. The rest of this guide is about building a weekly report that does this: the metrics it should contain, the structure that drives action, and how to use it in the review.
The Purpose of the Weekly Report
The weekly sales report's purpose is to drive the weekly review's decisions — to surface the engine's near-term state so the team can decide what to do this week — which defines what it should contain and how it should be structured. The weekly review is an operational cadence focused on the near term: managing the pipeline, moving the in-flight deals, acting on the leading indicators, and tracking the near-term forecast — deciding what to do this week to keep the engine moving and address emerging issues. The report exists to support this: it should surface exactly what the team needs to make those weekly decisions — the near-term state of the engine and what needs attention this week. This purpose shapes the report. It should contain the near-term operational metrics (pipeline, in-flight deals, leading indicators, near-term forecast) that the weekly decisions act on — not the long-term strategic metrics (which belong in periodic reviews, not the weekly) or vanity numbers (which drive no decisions). It should be structured to surface what needs attention and drive decisions (action-oriented), not as a comprehensive data dump. And it should be focused on the week (what is happening and what to do now), not a broad recap of everything. So the weekly report is purpose-built for the weekly review: the near-term, operational, action-relevant metrics, structured to drive this week's decisions. Understanding this purpose is the key to building it well — everything in the report should serve the weekly review's decisions, and anything that does not (long-term strategic metrics better suited to periodic review, vanity numbers, comprehensive data) does not belong in the weekly report. Build the weekly report for its purpose — driving the weekly review's decisions — and it becomes a useful artifact; build it as a generic data dump, and it becomes the status-recap that wastes the review. The purpose defines the report.
What Goes in a Weekly Sales Report
A weekly sales report should contain the few near-term, operational metrics that the weekly review acts on. Pipeline status and health: the current pipeline (qualified opportunities, coverage against near-term targets) and any changes — so the team can see whether there is enough in the funnel and act if it is thin. The in-flight deals needing attention: the active deals, especially those that are moving, stalling, or need help this week — so the team can act to move them (the core of the weekly operational work). The leading indicators: pipeline creation and early-stage activity this week, revealing where results are heading and surfacing emerging issues to act on now. The near-term forecast: what is expected to close in the near term and against target — so the team can see whether the near-term results are on track and act if not. Key changes and flags: what changed this week (deals advanced or slipped, metrics that moved), highlighting what needs attention. And, where relevant, rep-level near-term status (for a team, how reps are tracking on the near-term work). This focused set gives the weekly review what it needs: the near-term state of the engine (pipeline, deals, leading indicators, forecast) and what needs attention this week (changes and flags). It deliberately excludes the long-term strategic metrics (saved for periodic reviews) and the vanity numbers (which drive no decisions), focusing on the near-term operational metrics the weekly decisions act on. The report should be focused — the few weekly metrics that matter — not a comprehensive recital of every number, because the weekly review needs to quickly see the near-term state and decide, which a focused report enables and a comprehensive one defeats. So the weekly report contains the near-term operational metrics — pipeline, in-flight deals, leading indicators, near-term forecast, and key changes — focused on what the weekly review acts on. These are what drive this week's decisions.
A weekly report reviewing vanity numbers drives nothing. The 47-Point Sales Audit tells you which metrics belong in your weekly report. Download it and make your weekly review about decisions, not a status recap.
Get the 47-Point Audit →Structuring It for Action
A weekly report should be structured to drive action — organized around what needs attention and what to decide, not as a flat data dump of numbers — because the structure determines whether the review acts on the report or just recites it. A flat data dump (a list of every metric with no organization toward decisions) makes the review passive: the numbers get read out, but nothing is highlighted as needing attention or decision, so the review recites rather than decides. An action-oriented structure organizes the report around the weekly decisions: highlighting what needs attention (the stalling deals, the thin pipeline, the metric that moved), framing the questions the review should answer (which deals need help? is the pipeline healthy? what is off-track?), and surfacing the flags that warrant decisions — so the review naturally moves to deciding what to do. Practically, this means structuring the report to lead with what needs attention (not buried in a data list), to highlight changes and flags (what moved, what is off-track), and to frame the near-term state in terms of the decisions it informs (is the pipeline enough? which deals need action? is the forecast on track?). The report should make it easy for the review to see what needs attention and decide, rather than requiring the team to extract that from a flat list of numbers. This action-oriented structure is what turns the report from a passive status document into an active decision-driver: by organizing around attention and decisions, it leads the review to act. So structure the weekly report for action — organized around what needs attention and what to decide, highlighting changes and flags, framing the near-term state in terms of decisions — rather than as a flat data dump. The structure, as much as the content, determines whether the weekly review drives decisions: the right metrics in a flat dump still produce a passive review, while the right metrics in an action-oriented structure drive decisions. Structure the report to drive the review's decisions, and the weekly cadence becomes a genuine management forum.
Avoiding the Vanity Weekly Report
A common failure is the vanity weekly report — a recap of feel-good numbers (total activity this week, total leads, cumulative figures) that gets recited in the review but drives no decisions, turning the weekly review into a status-update ritual. This happens when the report is built to report activity and progress (look how much we did this week) rather than to drive decisions (what needs attention and what should we do). A vanity weekly report fills with the easy-to-count, feel-good numbers — calls made, emails sent, leads added, cumulative totals — which are pleasant to recite but do not surface what needs attention or drive decisions, so the review becomes a passive recap of activity rather than an active forum for decisions. The cost is the same as any vanity-metrics failure, concentrated in the weekly cadence: the most important operational review is wasted on reciting numbers that change nothing, while the metrics that would drive decisions (pipeline health, stalling deals, leading indicators, the forecast) are absent or buried. Avoiding this requires the same anti-vanity discipline applied to the weekly report: include the metrics that drive the weekly decisions (pipeline, in-flight deals, leading indicators, forecast, flags) and exclude the vanity activity recaps that do not. The test is the same — would acting on this number change what we do this week? — which the decision-driving weekly metrics pass and the vanity activity recaps fail. So build the weekly report around the metrics that drive this week's decisions, not the activity numbers that recap the week, and resist the pull toward the feel-good recap that makes the weekly review a status ritual. The weekly report is especially prone to the vanity trap (it is natural to report what was done), so the discipline to make it decision-driving rather than activity-recapping is what keeps the workhorse weekly cadence valuable. A weekly report that drives decisions makes the weekly review a management forum; one that recaps activity makes it a ritual. Build for decisions, not recap.
Using the Report in the Weekly Review
The weekly report achieves its purpose only when used in an action-oriented weekly review — looked at to decide what to do this week, not recited and filed. Using the report well means the review works through it to make decisions: looking at the pipeline health (and deciding whether action is needed if it is thin), the in-flight deals (and deciding which need help and what to do), the leading indicators (and acting on emerging issues), the forecast (and addressing it if off-track), and the flags (and deciding what to do about what changed). The review's output should be decisions and actions — what we will do this week, who owns what — driven by what the report surfaces, not just a noting of the numbers. This means the review should be structured around the report's action-oriented content: going through what needs attention and deciding, rather than passively reading the report aloud. It also means the report and review form a loop: the report surfaces the near-term state, the review decides actions, and next week's report shows the effect of those actions and the new state — a weekly cycle of surfacing, deciding, acting, and reviewing the effect. Used this way, the weekly report drives the weekly management of the engine: each week, the team sees the near-term state, decides what to do, acts, and reviews the results next week. Used poorly (recited and filed, with no decisions), the report and review drive nothing despite happening. So use the weekly report in an action-oriented review that works through it to decide — making the weekly review a forum where the report's content drives decisions and actions, in a weekly loop of surfacing, deciding, acting, and reviewing. This is what makes the weekly report and review the effective workhorse cadence for managing the sales engine week to week — the report surfaces what needs attention, and the action-oriented review turns it into the weekly decisions that keep the engine moving. The report is the input; the action-oriented review is what makes it drive the week.
It's natural to report what you did this week — which is exactly why weekly reports drift toward activity recaps. Build it around what needs attention and what to decide, not what was done.RRClosers
A weekly sales report is the artifact that drives the weekly review — the workhorse operational cadence for managing the engine week to week. It works only if it contains the few near-term metrics that drive this week's decisions, structured for action — not a data dump of vanity activity recaps. Its purpose (driving the weekly review's decisions) defines its content: the near-term operational metrics, not long-term strategic ones or feel-good totals.
Include pipeline status and health, the in-flight deals needing attention, the leading indicators, the near-term forecast, and the key changes and flags. Structure it for action — organized around what needs attention and what to decide, not a flat data dump. Avoid the vanity weekly report (the activity recap that makes the review a status ritual) by including only the metrics that would change what you do this week. And use it in an action-oriented review that works through it to decide — a weekly loop of surfacing the near-term state, deciding, acting, and reviewing the effect.
FAQ: The Weekly Sales Report Template
The few near-term operational metrics the weekly review acts on: pipeline status and health (coverage against near-term targets), the in-flight deals needing attention (moving, stalling, needing help this week), the leading indicators (pipeline creation, early-stage activity), the near-term forecast (what's expected to close, against target), and key changes and flags (what moved, what's off-track). For a team, rep-level near-term status where relevant. Exclude long-term strategic metrics (for periodic reviews) and vanity activity recaps.
To drive the weekly review's decisions — to surface the engine's near-term state so the team can decide what to do this week. The weekly review is the workhorse operational cadence (managing pipeline, moving deals, acting on leading indicators, tracking the near-term forecast), and the report is the input that makes it effective or hollow. A good report makes the review a decision forum; a data dump makes it a status recap. The purpose defines the content: near-term, operational, action-relevant metrics.
Organize it around what needs attention and what to decide, not as a flat data dump. Lead with what needs attention (stalling deals, thin pipeline, a metric that moved), highlight changes and flags, and frame the near-term state in terms of the decisions it informs (is the pipeline enough? which deals need action? is the forecast on track?). This leads the review to act, rather than requiring the team to extract decisions from a flat list of numbers. The structure, as much as the content, determines whether the review decides or recites.
Becoming a vanity recap — a list of feel-good numbers (total activity this week, total leads, cumulative figures) that gets recited but drives no decisions, turning the review into a status ritual. It happens when the report is built to report what was done (look how much we did) rather than to drive decisions (what needs attention, what should we do). The test: would acting on this number change what we do this week? The decision-driving metrics pass; the activity recaps fail.
Work through it to make decisions, not recite it: look at the pipeline health (and decide whether action is needed), the in-flight deals (and decide which need help), the leading indicators (and act on emerging issues), the forecast (and address it if off-track), and the flags (and decide what to do). The review's output should be decisions and actions — what we'll do this week, who owns what — driven by what the report surfaces. Report and review form a weekly loop: surface the state, decide, act, review the effect next week.
Weight the leading indicators and near-term operational metrics you can act on this week (pipeline creation, in-flight deals, early-stage activity, near-term forecast), because the weekly review is where you act in time. The long-term lagging trends belong more in periodic (monthly/quarterly) reviews. The weekly report should surface where things are heading and what needs attention now — the leading and near-term metrics that drive this week's decisions — rather than the longer-term lagging results that periodic reviews handle.