Write a sales weekly report leadership actually reads

The headline is the only paragraph every executive is guaranteed to read, so it has to carry the week on its own. Open with one sentence that names the number for the week, one sentence that names the delta against the prior week or the plan line, and one sentence of narrative that explains what moved. Keep it to three sentences. No caveats, no table, no chart in the headline block. A CRO who reads only this paragraph on a phone should know whether the week was good, bad, or flat, by how much, and why. If the opener needs context to make sense, the context belongs further down the page where the detail already lives.

• State the headline number for the week in plain language, with the delta against last week in the same sentence
• Name the single driver that explains most of the delta, not a list of contributing factors
• Keep the third sentence to narrative, not analysis, so the reader is handed a story they can act on rather than a problem to solve

The body of the report is five short blocks, each one answering a question leadership is already asking in their head. New pipeline tells them whether the top of the funnel is healthy. Closed deals tell them what landed and from which segments. Losses tell them where the motion is leaking. At risk tells them what the sales team is actively defending. Commitments tell them what the team promised last week and whether those promises were kept. Each block is three to five lines. If a block runs longer than five lines, the detail belongs in the dashboard, not the report. Consistency across weeks is what lets leadership scan the five blocks in under a minute and spot pattern changes without rereading history.

• Report new pipeline by segment or source, not just a total, so leadership can see where the top of the funnel is strong or weak
• Separate losses by reason category (price, timing, no decision, competitor) rather than listing every lost deal by name
• Call last week's commitments by name and mark each as kept, missed, or rolled, so the loop closes in writing every Friday

The first of three charts belongs at the top of the data section because it answers the question leadership is asking most urgently, which is whether there is enough pipeline to deliver the next number. Show coverage ratio against the next period target by segment, with a reference line at the coverage threshold the team already uses. Keep the chart to one view. If coverage is below target in any segment, call it out in the same line that reports the chart, not in a separate commentary paragraph. The point of the chart is not to show every segment and every ratio. The point is to answer in one glance whether the next period is in trouble.

• Plot coverage by segment, not just a company level roll up, so concentration risk is visible on the first read
• Mark the coverage threshold with a reference line, so a reader does not have to remember the target to interpret the chart
• Call out any segment below threshold in the chart caption, not in a separate note elsewhere on the page

The second chart gives leadership the trend view, so a weak or strong week does not read in isolation. Pick one metric that matters most to the quarter in motion and plot it across the trailing eight weeks. New pipeline created, bookings closed, and win rate are the three most defensible choices. Resist the urge to plot all three. One trend chart that the team actually inspects is worth more than three that nobody opens. If the metric drifts outside its normal range for two weeks in a row, flag it in the chart caption and name the action already in flight. Trend charts are the earliest honest signal leadership gets that the quarter is bending, and the weekly report is the place to catch that signal first.

• Pick one trailing metric per report and keep the choice stable across weeks, so the chart becomes a familiar reference the reader learns to interpret quickly
• Use eight weeks of trailing data as the default window, long enough to show pattern and short enough to stay current
• Flag any two week drift outside the normal range in the chart caption, with the action already underway named in the same line

The third chart gives leadership a by rep view, scoped to a single metric that is already part of the operating conversation. Attainment to date, pipeline created this week, or activity against SLA are the three defensible options. Rank reps from highest to lowest, keep the chart small, and let the reader see the shape of the distribution without reading every bar. Below the chart, name one ask from leadership for the coming week. One. The ask can be an exec intro to a stuck deal, air cover on a pricing exception, or a help request on a strategic account. One ask per week is a feature, not a limitation. A weekly report that asks for everything gets nothing. A weekly report that names one specific ask with the owner and the deadline earns a response.

• Rank reps by one metric per report, not a composite, so the chart answers one question cleanly
• Phrase the ask as a specific action with a named exec, a deal or account, and the day the response is needed by
• Separate the ask from the risks list, so leadership knows the ask is where the team wants help, not just where it is tracking exposure

The send time matters almost as much as the content. Ship the report by Friday 2pm local time, so executives have the back half of Friday and the full weekend to react, forward, or reply. A report that lands at 5pm Friday competes with inbox fatigue and never earns a response until Monday morning. A report that lands at 2pm earns a short asynchronous question loop before the weekend. Format the email with the headline paragraph in the body, the five blocks as short sections, the three charts inline where possible, and the ask bolded in the final line. Make it easy for an executive to reply with a single sentence. Narratives that create a question loop before Monday standup shorten the standup itself and surface the hard questions in writing where evidence lives.

• Draft the report Thursday evening or Friday morning so the Friday 2pm send is a review and send step, not a write step
• Put the headline paragraph in the email body, not as an attachment, so a mobile reader sees the number first
• End the email with the single ask in bold, with the response deadline on the same line, so the action is impossible to miss

A weekly report archived cleanly is worth more than one that ships well and disappears. Save every Friday send, every leadership reply, and every outcome against last week's commitments in one place inside Strkr. At the end of the quarter, run a short retro that compares what the reports said week over week with what actually landed at close. Over twelve weeks, the archive becomes the single best coaching tool for the sales leader. Risks that kept repeating point to structural work that was never done. Commitments that kept slipping point to planning that was too optimistic. Teams that run this retro faithfully tighten their weekly reports and their quarterly numbers in lockstep, and the report quality itself becomes a leading indicator of forecast accuracy.

• Store every weekly report, leadership reply, and commitment outcome as one artifact per quarter, not as scattered emails and threads
• Compare predicted at risk deals and commitments against actual close results at the end of every quarter, not just at year end
• Feed the retro findings back into the next quarter's at risk thresholds, commitment language, and ask cadence so each cycle writes a tighter report than the last