How Small Business Owners Can Write a Weekly Report That Gets Read
November 21, 2026
A weekly report earns its place when it helps one person make one decision faster. For small business owners, that means a single page with three to five numbers, a short note on what changed, and one clear request. This guide walks through the steps and a worked example.
Why most weekly reports go unread
Most reports fail for the same reason: they are written to prove that work happened, not to help someone act. They grow longer each week, include every number available, and bury the one item that needs attention.
Readers learn quickly that the report demands effort and rarely changes what they do. So they skim it, then stop opening it.
A useful report works the other way around. It starts from the decision the reader has to make, and includes only what supports that decision. The steps below build the report in that order.
Step 1: Name the decision the report supports
Before choosing any numbers, write one sentence that completes this phrase: "After reading this, I will decide whether to..."
Good examples include:
- Whether to hire another person next month.
- Whether to pause a marketing channel.
- Whether to chase overdue invoices this week or next.
- Whether to accept more work or hold capacity.
If you cannot finish the sentence, the report has no job yet. Resolve that first, because every later step depends on it. If you have several decisions, write a separate short report for each rather than one long one.
Step 2: Choose three to five metrics
Pick the numbers that would change your answer to the decision in Step 1. A quick test helps: for each candidate metric, ask "If this number doubled or halved, would I act differently?" If the answer is no, cut it.
Keep the list short for two reasons. A reader can hold three to five figures in mind at once, and a short list forces you to understand what really drives the business.
For each metric, record three things:
- The definition, in plain words, so it means the same thing every week.
- The source, such as your accounting software, a spreadsheet, or a booking system.
- The owner, meaning the person who updates it.
Write these down once and reuse them. Changing a definition midstream makes past weeks incomparable.
Step 3: Fix a format and stick to it
Consistency matters more than design. Readers should find the same items in the same place every week, so they can scan in under a minute.
A simple one-page layout works well:
- Top line: one sentence stating whether things are on track, at risk, or off track.
- Numbers: your three to five metrics, each with this week, last week, and your target.
- What changed: two or three short sentences.
- Request: the single thing you need from the reader.
Send it at the same time each week. A predictable rhythm turns the report into a habit rather than an interruption.
Step 4: Add one sentence of explanation per number
A number alone invites guessing. A short explanation tells the reader whether to worry.
Keep each note to one sentence and answer two questions: what moved, and why do you think it moved? If you do not know why, say so. "Cause unclear, checking with the crew leads" is more useful than a confident guess that turns out wrong.
This habit matters because it separates observation from interpretation. The reader can see the figure, see your reading of it, and disagree if they have other information.
Planning guidance often stresses that the act of thinking matters more than the document itself. As Dwight D. Eisenhower put it, "Plans are worthless, but planning is everything." A weekly report works the same way: the value comes from the weekly habit of asking what changed and why.
Step 5: End with a request
Every report should close with something specific for the reader to do or decide. Without a request, a report is just a status update that is easy to ignore.
A good request has three parts: the action, the person, and the date. For example: "Approve the second delivery van purchase by Friday." If nothing is needed this week, say "No action needed." That sentence itself saves the reader time and builds trust that a request, when it appears, is real.
Worked example: a ten-person landscaping company
The figures below are invented for illustration only. They are not real data from any business.
Step 1, the decision. The owner must decide whether to hire a seasonal crew member in two weeks.
Step 2, the metrics. She asks which numbers would change her answer and chooses four:
- Jobs booked for the next four weeks
- Jobs completed this week
- Overtime hours this week
- Unpaid invoices older than 30 days
Step 3, the format. She builds a one-page template and sends it every Friday at 3 p.m.
Step 4, the notes. This week's entry reads:
- Jobs booked, next four weeks: 38 (last week 31, target 35). Spring cleanup requests rose after the warm spell.
- Jobs completed: 14 (last week 15, target 15). One job was delayed by rain.
- Overtime hours: 22 (last week 12, target under 10). Crews are stretching to keep up with the new bookings.
- Unpaid invoices over 30 days: 3 (last week 3, target 0). Same three accounts, no change.
Step 5, the request. "Approve a seasonal hire by next Friday. Bookings are above target and overtime has nearly doubled."
The top line reads: "At risk: demand is ahead of capacity." In under a minute, the reader sees the situation, the reason, and the action. The overdue invoices do not drive the hiring choice, but they stay on the page because they affect cash and can change the timing of the hire.
Common mistakes to avoid
Once the report is running, watch for these problems:
- Metric creep. Adding a new number every time someone asks. Add one only if you remove one.
- Changing definitions. If you must redefine a metric, note the date and restate recent weeks.
- Hiding bad news. A report that always says "on track" teaches readers to ignore it.
- Skipping weeks. Missing one report breaks the habit. If there is nothing new, send the short version.
- No review. Every quarter, ask whether the decision in Step 1 is still the right one.
If a report has run for a month and nobody has acted on it, treat that as information. Either the decision, the metrics, or the reader is wrong, and it is better to find out early.
Next step
Start small this week. Write the decision sentence, choose your metrics, and send a first draft to one person. Ask them one question: "What did you do differently because of this?" Their answer will tell you what to keep and what to cut.
If you want to know whether working with me suits your business, read Who this is for and what it costs and get in touch from there.