Most owners get numbers from five places and a picture from none of them. The ad platform says one thing, the CRM says another, the bank statement says a third, and the staff meeting fills in the rest from memory. A weekly report is supposed to fix that, and most do not, because they are either a dashboard nobody opens or a spreadsheet nobody reads. This article sets out what a weekly report for a small business owner should contain, and how the one in every Staffhand build is put together.
One page, same shape every week
The first rule is that the report has the same structure every week. The owner should be able to read it in ten minutes and know what changed. If a section needs more than a glance, the detail is one click away in the action log, not in the report itself.
The second rule is that every number in it ties back to something in your own systems. Nothing is estimated. If a figure cannot be traced to a record, it is not in the report.
Section one: leads, by source, with what happened to them
This is the section owners read first:
- How many new leads came in, by source: web form, phone, walk-in, referral, repeat customer, each ad platform
- How quickly each was answered
- How many were booked, quoted or converted
- How many are still open, and which desk is following up
The point is the full chain, not the top number. Twenty leads that got a reply in four hours and two bookings tells a different story from twelve leads answered in ten minutes and six bookings.
Section two: spend tied to leads and sales
Every Staffhand build includes attribution: marketing spend tied to the leads and sales it produced. The weekly report shows spend by channel next to the leads and sales from that channel, using the baseline set in the digital audit.
This is where owners find out that the channel with the most clicks is not the channel with the most customers, or that referrals and repeat customers outperform everything paid. Marketing ROI and attribution for small businesses explains how the attribution is built. The weekly report is where it shows up.
Section three: what the desks did
Each desk in the build gets a line: what it drafted, what was approved, what was edited, what was held. This is the owner’s check on the AI. If the review request desk drafted thirty requests and twenty-eight were approved unchanged, the wording is right. If half were edited, something needs tuning and the report says so.
Held messages are listed with the reason. This is also where routine messages that run on templates approved once are counted, so the owner always knows what went out without a per-message tap.
Section four: decisions waiting
Anything that has sat in the approval queue for more than a set time, any question routed to a person that has not been answered, and any price, estimate or financing request still waiting on a human. These are the leaks of the week. Listing them is how they get closed.
Section five: reviews, search and the public face
New reviews and the responses posted, with the response desk’s approval record. Changes in the local search listing. Social posts that went out and the ones waiting. These are the five things the digital audit scored at the start, so the report tracks them against the audit baseline week by week.
What the report leaves out
Vanity numbers. Impressions, followers and page views appear only when they explain a change in leads or sales. Forecasts and projections are left out, because the report records what happened. Anything the owner cannot act on this week is in the log, not on the page.
How it fits with the morning brief
The morning brief is daily and forward-looking: what came in overnight, what needs a decision today, what the desks plan next. The weekly report is backward-looking: what happened, what it cost, what it produced. Together with the single approval queue and the live action log, they are the four things an owner sees in every build. The morning brief describes the daily side. How it works describes all four.
Frequently asked questions
Who writes the weekly report?
The weekly report desk compiles it from your systems and the action log. A person at Staffhand reviews it before it is sent, because nothing in a build runs unattended.
Can I change what is in it?
Yes. The sections above are the default. Owners add lines for the numbers they already watch and drop what they do not use.
Does the report include my revenue?
It includes the sales and revenue recorded in your systems, tied to source. The revenue baseline from the audit is the comparison point. All of this is in your accounts and stays with you.
What if the numbers look bad?
Then the report says so, in plain terms, with the leak named. A report that only carries good news is not worth reading.
The baseline for the weekly report is set in the digital audit, which scores your website, search presence, reviews, social and lead handling and maps spend to results. Start with a digital audit.
