A weekly report read in three minutes that leads to one decision. What belongs on the page, where each number comes from, and how it survives a busy month.
Key takeaways
- One page, seven numbers at most, each beside its previous value.
- Every number needs one source and one person responsible for it.
- The report is read in a short meeting, not emailed and buried.
- A report that led to no decision in a month gets changed or dropped.
A good weekly report is read in three minutes and leads to one decision. A report taking half an hour to prepare and fifteen minutes to read dies within two months - exactly when the business gets busy, which is exactly when it was most needed.
What goes on the page
| Section | What it contains | How many lines |
|---|---|---|
| Numbers | The standing metrics, beside last week | 5-7 |
| Exceptions | What fell outside range, and why | 2-3 |
| Stuck | What has waited too long, and with whom | 2-3 |
| Next week | The decision or action that follows | 1-2 |
The last section is the only mandatory one. A report with no action line is a snapshot, and a snapshot is available without a report - just by asking.
The third section deserves attention: "stuck" usually produces the fastest decisions, because it points at something concrete with a person's name attached. Two lines saying what is waiting and with whom are often worth more than all the numbers above them.
Where each number comes from
Every line needs a single documented source. It sounds bureaucratic and it solves the most common problem: two people arriving at the meeting with two different numbers for the same thing, and the discussion moving from the conclusion to an argument about the data.
So build a small table on the side: metric, source, who updates it, and when. That list is written once, and when somebody changes role it is what lets the report survive. The logic of choosing the metrics themselves is in operational KPIs for a small business.
Keeping it alive
The number one reason weekly reports die is preparation time. Three rules keep it breathing:
- Twenty minutes of preparation, maximum. Anything longer will not be collected in a busy month.
- The same day and hour every week - routine beats reminders.
- Whoever prepares it is not whoever decides, where possible. That prevents an unconscious tendency to flatter.
The first rule decides the structure: if a particular number takes half an hour to gather, it does not belong in a weekly report - either it moves to a monthly one, or its source gets fixed first.
What does not belong on the page
- Data with no comparison to last week.
- Individual metrics about employees - they change the culture rather than the outcome.
- Charts needing interpretation. On one page, numbers win.
- Long explanations - those are spoken in the meeting, not written.
- Anything unchanged for three months.
The last is worth a quarterly review: a metric that has not moved in a whole quarter is either not sensitive enough or simply not interesting. Either way, replace it.
The meeting attached to it
The report is not sent - it is read together, in ten minutes. The order that works: run through the numbers without discussion, stop only on what fell outside range, decide what to do about it, and finish. Content discussion about a specific deal or customer is deferred to another conversation.
What kills this meeting is turning it into a round of updates: everyone describing their week. That takes an hour, produces no decision, and creates exactly the feeling that meetings are a waste. The expansion on this is in reducing status meetings.
Three months in
After a quarter, stop and ask three questions: which decisions came from the report, which numbers nobody looked at, and what is missing that we would want to know. The answers usually lead to swapping one or two metrics, which is healthy.
What is worth keeping is the format. Businesses that restructure the report monthly lose the ability to compare backwards, and that comparison is precisely the value that accumulates - a page from a year ago tells you something available no other way. The wider frame of management routines is in how to improve business efficiency.
What does this look like in a business of two or three?
At that size the obvious question is why a report is needed when everyone knows everything. The answer is that people know what happened but not what the trend is. Seeing the picture up close every day makes it very hard to notice something declining slowly - and that is exactly what a weekly page does.
In a very small business the report can be four numbers and two lines of text, and the meeting can be a five-minute conversation between two people. What does not change is that it is written in the same format every week and kept - because the value comes from the comparison rather than from any single week.
What is worth adding at that size is one line that is not a number: what is most worrying this week. In a small business the answer to that question usually precedes the numbers by two or three weeks, and it is a source of information not worth giving up.
What to do when the numbers are bad
This is the point where reports disappear. When the month is weak, the temptation to postpone the meeting or "update it later" is strong, and that is exactly when the report is most useful. The simple rule is that the report stays identical - same numbers, same format - even when they are unpleasant.
What does change is the action line. In a good month it is often "carry on"; in a weak month it has to be specific: what we will do this week differently from last week. A report showing three consecutive weeks of decline with an action line saying "we will keep monitoring" is a report documenting a fall rather than preventing one.
Sources
Frequently asked questions
Who should prepare the report?
Somebody with access to the data for whom it is part of the job, not whoever is free. If possible, not the owner - both to save their time and so the numbers reach them from outside rather than through their own interpretation.
Weekly or monthly?
Weekly for operations, monthly for money. Operational metrics move fast and allow mid-course correction; full financial data arrives on a monthly rhythm anyway, so a weekly financial report usually produces noise rather than information.
What if there is no time for the meeting?
Better to shorten than to skip: five minutes standing with the page in hand beats a report sent and unread. What does not work is emailing it and assuming somebody reads it - in practice, a report sent and never discussed stops being prepared within a month.
How do you start with no data at all?
Start with three numbers that already exist somewhere - enquiries received, deals closed, outstanding debt. After a month of orderly collection it usually becomes clear what is missing and what is redundant, which is a better starting point than a perfect list on paper.
Keep reading
Related service
Dashboards
One screen with the few numbers that actually change a decision.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.