Sales Report Template: A Free Weekly Activity Report With Dial Benchmarks

Sales report template cover: a free Google Sheet with four working tabs and UK dial benchmarks by weekday

Publish date: Nov 13, 2026

This sales report template is a free Google Sheet. It turns one week of calls and deal changes into a one-page report for leadership. Its Weekly activity tab reads your dials against Spona's call records: 347,133 dials to UK professional services numbers, by weekday. Make a copy of the Sheet.

The sheet judges a quiet Monday against Mondays, not against the week. Its five tabs are Instructions, Weekly activity, Pipeline changes, Benchmarks and Summary. Example rows for three reps and twelve deal changes show every formula working before you clear them. The sheet never connects to your CRM; you paste two exports a week, and the Summary tab does the arithmetic.

The Extractor
The Refiner
The Verifier
The Exporter

Get thousands of leads in 4 minutes.

Stop stitching tools together.
Start with verified sales data, delivered in minutes.

SCALE SALES NOW

No contracts · No setup · No onboarding

Sales report template: what leadership reads first

Leadership reads a sales report the way the Army reads a memo. AR 25-50 wants writing "understood by the reader in a single rapid reading", with the main point first: bottom line up front. Barbara Minto asks consultants for the same thing, ideas organized as a pyramid under a single point.

Most templates ignore this. Close notes that most business reports start with an executive summary. Pipedrive says one gives sales leaders a quick view of performance without the full report. Close's free templates leave that summary out, so the Summary tab here adds it, in this reading order:

Block on the Summary tabThe question it answersWhere the numbers come from
Bottom line (three typed lines)What happened, what matters, what you wantYou, after reading the rest
This weekDid we hit target, and how does it compare with last week?Weekly activity, Pipeline changes and the Weekly log
Connects and conversations per dial (inside This week)Is the calling where UK professional services calling usually lands?Weekly activity against the Benchmarks tab
Pipeline movementWhy did open pipeline change, and is every change logged?Pipeline changes, plus two CRM totals you type
Month roll-upWhere does the month stand against its revenue target?The Weekly log, one row per Friday

The three lines at the top are the report. The sheet ships with an invented example: "Won 34,500 from two deals. October closed at 87% of its 120,000 target."

The second line names the biggest problem, a slipped deal. The third names the ask: a senior call on that deal next week.

Everything below the lines is evidence. Write the lines last, after the tables fill. Each line carries one fact and no adjective. If a reader stops after line one, they still know the result.

Weekly sales report template: the UK dial benchmark

The Benchmarks tab separates this weekly sales report template from a plain activity log. It holds Spona's call records to UK professional services numbers over a recent three-month period. The cut covers every number type and every local hour, Monday to Friday. Each weekday row holds at least 67,000 dials, and Spona labels any hourly cell under 500 dials a small sample.

Jesse Chan at Spona confirmed the row and its counting rule: "Unique dial event classified once; repeated attempts remain distinct dials."

WeekdayDialsConnectsConversationsConnects per dialConversations per dial
Monday67,42210,7675,72816.0%8.5%
Tuesday67,31211,3055,86016.8%8.7%
Wednesday72,27112,2366,68816.9%9.3%
Thursday67,98511,3856,13616.7%9.0%
Friday72,14311,5786,21016.0%8.6%
All weekdays347,13357,27130,62216.5%8.8%

First, the weekday spread is small. Connects run from 16.0% on Monday to 16.9% on Wednesday, under one point. Conversations run from 8.5% to 9.3%. Monday and Friday sit lowest on both.

Second, mid-week ran slightly ahead of Monday and Friday, and that is all the data supports. Wednesday's lead partly reflects a larger share of mobile dials that day. There is no best day in these rows. For the time-of-day view, read our best time to cold call post.

Third, the whole line comes to 6.1 dials per connect and 11.3 per conversation. Put differently, 53.5% of connects became conversations. The rows blend direct dials, mobiles, switchboards and unclassified numbers, and they include calls outside office hours. A list of mostly mobiles will read differently from a list of switchboards.

Outside figures from Belkins and Cognism sit on the same tab, and none compares directly. Belkins reports a 14.7% live rate for UK dials, where any live human counts, gatekeepers included. It calls its UK sample directional.

Cognism's report counts 27,513 conversations from 41,936 connected calls worldwide. Different definitions, different bases, so neither figure confirms the Spona line.

One UK rule comes before any of this. Business numbers need screening against both the CTPS and TPS registers plus your own do-not-call list. Some businesses, such as sole traders and some partnerships, register with the TPS. The Instructions tab carries that line so nobody skips it.

Count calls the way the benchmark does

The line only means something if you count the way it counts. A connect is the intended prospect reached. A gatekeeper who answers and takes a message is not a connect. A conversation is a substantive exchange about a need or a next step, not a pleasantry before a hang-up.

Both rates divide by every dial attempt, not by answered calls. A rep who dials one prospect three times logs three dials. Hours are the recipient's local time.

Most CRMs record a call outcome field, so map its values before the first week. "Connected" and "Left voicemail" are easy. "Spoke to assistant" is not a connect.

How much one week of dials can tell you

You cannot judge a single rep-day of 60 dials against a line built on hundreds of thousands, and the sheet says so. Any weekday under 500 dials prints "Small sample" in its Read column, the same label the Benchmarks tab uses. Above that, the Read column compares your gap with the margin chance alone produces on that many dials. The margin uses 95% confidence.

Dials in the periodWhat it is in the exampleMargin either way on a 16.5% lineWhat the Read column can say
180About one weekday, three reps5.4 pointsSmall sample
895The team's week2.4 pointsBelow, within or above the line
3,520The month, four weeks logged1.2 pointsBelow, within or above the line

The example week lands 3.0 points under the line on connects, with 895 dials behind it. That gap is bigger than chance, so the sheet prints "Below the line". The same week sits 1.0 point under on conversations, inside the margin, so it prints "Within range". Two verdicts from one week, and only the first deserves a conversation with the team.

Example week of 895 dials against the Spona line: connects below the line and outside the margin, conversations within range
The same week earns two different verdicts, and only the connect gap deserves a conversation with the team.

The Week row weights the line by your own mix of weekdays. A team that dials heavily on Friday gets Fridays as its yardstick. If connects fall short while conversations hold, the reps are fine once they get through, and the list is the question. If conversations fall short while connects hold, the opener is the question, and our cold calling tips post is where to start.

Sales activity report template: filling it from your CRM

The weekly routine takes about 20 minutes once you have saved both exports. That is our estimate from the example rows, not a measurement. Six steps, in the order the tabs expect them.

Make a copy of the Sheet and keep the example rows in place while you read. The verdicts in the Read columns make more sense once you have seen one week fill.

  1. Set the week and the targets. On the Instructions tab, type the report week's Monday into WeekStart. Type the dial, meeting, new pipeline and monthly revenue targets below it. Type your reps into the Reps list in column H. Google Sheets dropdowns reject anything not on their list unless the rule shows a warning instead. The Rep dropdown warns, so you can type a new hire's name. The Change dropdown stops, so the pipeline math stays clean.
  2. Export call activity and paste one row per rep per day. The Weekly activity tab is the sales activity report template inside the sheet. HubSpot exports a filtered view as CSV, XLS or XLSX, and its download links expire after 30 days. Group the calls by rep and day and count them the way the benchmark does. Then fill Date, Rep, Dials, Connects, Conversations and Meetings booked on the Weekly activity tab. Weekday fills itself. The Check column turns red when connects exceed dials or conversations exceed connects. If your CRM is still a spreadsheet, the Activities tab in our CRM template logs each call as a row, ready to count.
  3. Export deal changes and paste one row per changed deal. Salesforce writes an OpportunityHistory record each time Amount, Probability, Stage or Close Date changes. HubSpot can keep Date entered and Date exited properties for every stage, and both work in reports and filters. Each changed deal gets one row on the Pipeline changes tab. Pick the Change. Then fill Stage before and Stage after, Value before and Value after, and Close date before and Close date after. Add the Next step.
  4. Clear every red Check cell. The Pipeline changes Check column names what is missing: "Pick a change", "Add the value before", "Add the later close date", "Value did not go up". Validity surveyed 602 CRM users, and 76% said less than half of their CRM data is accurate and complete. The red cells are where that shows up.
  5. Type two totals and read the Summary. Type the open pipeline at the start and end of the week from your CRM into the Pipeline movement block. Read This week and Pipeline movement, then write the three lines at the top.
  6. Every Friday, log the week. Copy Summary row 38, the snapshot, and paste it as values into the next empty row of the Weekly log. The log carries the ISO week number, which Google computes with weeks starting on Monday. The month roll-up reads nothing but that log.

Pipeline changes in the weekly sales report

The problem with most weekly reports is one number. Open pipeline went from one total to another, and nobody can say why. Xactly surveyed 405 sales and finance professionals in North America and found that 60% were unsure where their pipeline data came from. A total without its movements is a guess with a decimal point.

The method is a log of changes, not a list of deals. Seven change types cover every move a deal can make, from New and Advanced through Slipped, Value up and Value down to Won and Lost. The Pipeline effect column turns each row into a signed number. Won and Lost remove the value before, and every other change adds the value after minus the value before.

Stage names follow your own sales pipeline, and the Stage list on the Instructions tab is where you rename them. Days moved counts how far a close date moved. Gong studied 13,439 B2B opportunities and concluded that when sellers push the close date three weeks or more, "that's not a hiccup, it's a hold up". A close date that moves 21 days or more later turns the row amber, and SlipDays on the Instructions tab changes the threshold.

Slips are common enough to count. Ebsta's data scientist reports that the share of deals slipping past their close date fell to 36%, from 44% a year earlier.

The example week shows the check in action with twelve changed rows. Three deals are new, two advanced, two slipped, one went down in value, one went up, two were won and one lost. The Pipeline movement block starts at the CRM's opening total and adds the logged effects. It lands exactly on the CRM's closing total, and the last row reads "Every change is logged".

Waterfall from an opening pipeline of 410,000 through new, changed, won and lost deals to a close that matches the CRM
When the logged changes land exactly on the CRM closing total, nobody has to explain the pipeline from memory.

A nonzero difference turns red and names the job: find the deal nobody logged. Example deal 06 is the one to talk about. It slipped four weeks in Negotiation and is worth 30,000, the largest open deal in the example. The Summary counts it under "Close dates moved past the flag".

The bottom line asks for a senior call on it, which is what a slipped deal of that size should trigger. This tab records movement only. Probabilities and forecasts belong in a forecast, not a report.

What should a monthly sales report show leadership?

The same five blocks, with the month replacing the week, so you need no separate monthly sales report template. One more line joins them: how the month closed against its revenue target.

The Month roll-up on the Summary tab builds it from the Weekly log alone. Type the month's first day into one cell and it sums the weeks whose Monday falls inside that month. Open pipeline at month end comes from the last logged week.

The roll-up is where the benchmark earns its place. One week of 895 dials carries a margin of 2.4 points. Four logged weeks of the example reach 3,520 dials, and the margin tightens to 1.2 points.

The example month's connect rate reads "Within range" against the line, while the example week reads "Below the line". A month tells you about the list and the team. A week mostly tells you about the week.

Month roll-up card from four logged example weeks: dials and connect rate, meetings, revenue won, win rate and open pipeline
Four logged weeks give leadership a connect rate it can trust and a revenue line against the month target.

Leadership needs the month view because the quarter view keeps failing. Xactly found that 4 in 5 sales and finance leaders missed a quarterly forecast in the past year. Half of sales leaders (52%) say their forecasts are off by 10% or more.

A monthly report built from logged weeks shows revenue won, deals won and lost, new pipeline and the win rate as they happened. It makes no forecast, and that is why leadership can trust it.

How often you send the full report is your call. Pipedrive puts it plainly: there is no one-size-fits-all reporting frequency. The sheet assumes a weekly snapshot and a monthly roll-up because the log needs the weekly row either way. A team that reports fortnightly still logs every Friday.

Where Spona fits, and where it does not

Spona supplies the list the report measures. You describe your ideal customer in a chat, and Spona returns a verified, scored lead list priced per lead. A Deep Search lead costs 60 to 200 credits. At the plans' credit prices that is $0.48 to $2.00 a lead.

New leads that match a finished search appear every week, at the same price per lead. That gives the reps fresh numbers to dial each week.

Spona also supplies the benchmark. The Benchmarks tab holds Spona's call records, and the Read column is the only place where a Spona figure touches your numbers. If connects run below the line for a month on a list of similar numbers, the list is the first suspect. This post makes no claim that a Spona list raises your connect rate; the records describe calls, not customer results.

Where Spona does not fit: it is not a CRM, and it does not fill this report. The dial counts come from your dialer or CRM. Spona's own dialer is coming soon, so today you type the Weekly activity tab from an export.

For a live dashboard that refreshes itself, look elsewhere. Your CRM's own reporting or a connector such as Coupler does more than this sheet ever will. The sheet is for the written weekly report, read once, on a phone, by someone who did not make the calls.

The Extractor
The Refiner
The Verifier
The Exporter

Get thousands of leads in 4 minutes.

Stop stitching tools together.
Start with verified sales data, delivered in minutes.

SCALE SALES NOW

No contracts · No setup · No onboarding

Sales report template FAQ

How do you write a weekly sales report?

Start with three lines: the result, the biggest problem and the ask. Then give the evidence in a fixed order: this week against target, last week and a benchmark, then pipeline movement. Keep the layout identical every week so readers find the same number in the same place. The Summary tab in this template holds that order, and the example rows show a finished week.

How do I create a sales report?

Pick the period, export two things from your CRM, and paste them into a sheet that does the arithmetic. The two exports are call activity by rep and day, and every deal change in the period. The six steps above take about 20 minutes a week once you have saved the exports, which is our estimate. The free sales report template linked at the top of this post is set up for exactly those two pastes.

Does the template work in Excel?

Yes. For an Excel sales report template, open the Google Sheet, then use File, then Download and choose Excel. The formulas use standard functions. The one to watch is MAXIFS, which Microsoft lists as available in Office 2019 or a Microsoft 365 subscription. In older Excel that one cell, the open pipeline at month end, shows an error.

What is a sales report?

A sales report is a fixed-period summary of what a sales team did and what it changed. The doing is calls made, conversations held and meetings booked; the changing is pipeline added, moved, won and lost. A good one separates activity from results and compares both with a target or a benchmark. A dashboard is live for the team all day; a report is read once, by people who were not in the room.

Does it work as a daily sales report?

The Weekly activity tab already holds one row per rep per working day, so a daily view is a filter away. Judge a single day with care, though. The example's three reps make about 180 dials a day, and the sheet prints "Small sample" for any weekday under 500 dials. Use the daily rows to spot a rep who stopped dialing, and the week or the month to judge rates.

How often should you send a sales report?

Weekly for the team's manager, monthly for leadership, with the same sheet feeding both. The weekly snapshot takes one paste into the log every Friday, and the monthly roll-up reads that log. Send fewer reports if nobody acts on them. Keep logging every week, though, because nobody can rebuild the month roll-up from memory.

Share this article

GET FREE LEADSSparkle

Similar Topics For You

see all texts