Reports get used when they feed a routine that ends in decisions. Keep the report to one page with four to seven core numbers. Have each manager prepare a short note on any number that’s off track. Then run a short weekly meeting built around three questions: What do the numbers mean? Who will act on them? By when? Open the next meeting by checking whether those actions happened.
To me, a useful conversation about the numbers is an action-oriented one: what the numbers mean, who will act on them, and by when. Most reporting routines stop at the first part. Without a name and a date, a team can discuss the same bad number every week and nothing changes.
Why Doesn’t Your Team Read the Reports You Send?
Often because reading them is not connected to a decision or a follow-up. A report emailed on Monday competes with customer calls, staffing problems, and everything else on a manager’s list. If no meeting depends on it and nobody will ask about it, reading it is optional, and optional work gets pushed to later.
Two other problems make it worse:
- The report makes the reader do the analysis. A ten-tab spreadsheet or a 15-page PDF asks each manager to find what changed and decide whether it matters. Most probably won’t.
- The report describes the past without asking for anything. If a report never leads to a decision, people reasonably conclude it isn’t meant for them.
If the problem runs deeper, and people don’t trust the numbers or can’t connect the metrics to their work, start with Why Nobody Looks at Your Dashboard. The routine below works best once people believe the numbers.
What Should the Report Look Like Before the Meeting?
One page. If it doesn’t fit on one page, each reader has to do the sorting the report should have done for them.
A one-page weekly summary needs four parts:
- The scorecard. Four to seven core metrics, each with its current value, target range, prior period, and a simple on-track or off-track status. Four to seven is my rule of thumb for most small businesses; How Many KPIs Should a Small Business Track? covers how to choose them.
- What’s off track. The metrics outside their range this week, called out at the top so nobody has to hunt for them in a table.
- What went well. One to three things that improved, and why. This keeps the meeting from turning into a list of problems and tells people what to keep doing.
- Decisions needed. Anything that needs an approval, a trade-off, or resources from the owner this week.
Everything else goes in an appendix or a linked file: full financial statements, transaction detail, breakdowns by customer or crew. People open it when they need to investigate. A monthly version can add that detail without crowding the weekly operating view.
How Should Managers Prepare for the Meeting?
They should read the one-page summary beforehand and write a short note for any metric they own that is off track. Meeting time is for deciding, and reading numbers aloud wastes it.
Send the summary early enough to read: Friday afternoon for a Monday meeting, or first thing in the morning for a late-morning meeting. Put the notes in one shared document so everyone can see them before the meeting starts.
The Off-Track Note
Each note answers four questions in a few sentences:
- What happened? The number, its target, and how far off it is.
- What does it mean? The effect on cash, customers, delivery, or cost.
- What will we do? The specific action.
- Who, and by when? One name and one date.
Here is a hypothetical example, not a client case:
What happened: First-pass yield fell to 88% this week against a target of 95%.
What it means: About 12 hours of rework, roughly $2,500 in scrapped material, and one order at risk of shipping late.
What we’ll do: Recalibrate the tooling on the cutting station and review the new tolerances with the operators.
Who and by when: Shop lead. Tooling done by Tuesday; operator review Wednesday morning.
A short note like this changes where the conversation starts: with a proposed fix instead of an argument about what went wrong.
One rule matters more than the format. Don’t penalize people for reporting a red number. Ask them to bring either a proposed next step or a clear request for help. If off-track numbers get people criticized in front of the team, expect to see numbers explained away instead of fixed.
How Do You Run the Meeting?
Keep it short, run it the same way every week, and end with names and dates. The agenda below is a 15-minute starting point for a small team; add time when several metrics need real decisions.
Here is a starting agenda for a 15-minute meeting. Stretch the off-track section if you need a longer one.
| Minutes | Topic | What happens |
|---|---|---|
| 0–3 | Last week’s actions | Each owner says done, in progress, or missed; a missed action gets a new date |
| 3–5 | Scorecard | Walk through the metrics and confirm which are off track |
| 5–12 | Off-track metrics | Each owner gives their note in about a minute; the group agrees on the action, owner, and date |
| 12–15 | Decisions and blockers | The owner approves resources or settles conflicts between departments |
A few rules keep it on track:
- Show the report itself. Put the one-page summary or the dashboard on the screen. A separate slide deck is one more document to maintain and one more place for numbers to disagree.
- Skip what’s on track. If a number is in range, move on.
- Take long problems out of the meeting. If something needs more than a few minutes, assign someone to work on it and set a date to report back.
- Record every action before anyone leaves, with its owner and due date.
How Do You Make Sure Actions Actually Happen?
Keep a running action log and open every meeting with it. This step is easy to skip, but it is the one that shows people the routine matters.
The log can be a simple table in the same shared document. The entries below are samples:
| Raised | Metric | Action | Owner | Due | Status |
|---|---|---|---|---|---|
| Sept. 8 | Days sales outstanding | Call the five largest overdue accounts | Office manager | Sept. 12 | Done |
| Sept. 8 | Labor cost as % of sales | Adjust Tuesday and Wednesday schedules | Operations lead | Sept. 15 | In progress |
| Sept. 15 | First-pass yield | Recalibrate cutting station tooling | Shop lead | Sept. 16 | Open |
When you review the log each week:
- Done: Check whether the metric responded. If it didn’t, the action didn’t address the cause, and the owner needs a new plan. Or, decide if the action did address the cause and the response needs more time to become indicative.
- In progress: Confirm the date still holds.
- Missed: Ask for a new date and what got in the way. If the same action slips twice, investigate whether the constraint is time, authority, resources, or an unclear assignment instead of sending another reminder.
Over a few months, the log also shows which problems keep coming back. That pattern can be more useful than any single week’s report.
What About Monthly Reviews and One-on-Ones?
Use the same pattern at a different pace.
A monthly review covers the numbers that only change meaningfully after the books close, such as gross margin, and looks at trends across several weeks. It uses the same off-track notes and the same action log, with additional financial and operating detail where needed.
A one-on-one is where you help a manager with their own numbers. Start with the metrics they own, look at the trend, and ask what they need to bring an off-track number back into range: time, budget, help from another department, or a decision from you. Asked that way, the conversation becomes about solving the problem together rather than checking up on them.
How Do You Keep Reports From Piling Up Again?
Review every recurring report once a quarter and stop the ones nobody would miss. Reports accumulate: someone asks a one-time question, the answer becomes a weekly report, and nobody ever turns it off.
For each scheduled report, ask the people who receive it: “If this report stopped tomorrow, what decision would you be unable to make?” If nobody can name one, stop sending it. If someone misses it later, you can bring it back.
Apply the same test to the metrics on the weekly summary. If your dashboard has grown well past what the meeting can use, How to Improve a Business Dashboard You Already Have walks through cutting it down.
Your First Four Weeks
- Week 1: Cut the report to one page with four to seven metrics, and assign an owner to each.
- Week 2: Send the summary before the meeting and ask owners of off-track metrics for their notes. Some notes will be missing; ask for them anyway.
- Week 3: Open the meeting with the action log from week 2.
- Week 4: Look back at the log. Which actions got done, which slipped, and did the numbers respond? Adjust the metrics, the timing, or the meeting length based on what you find.
Expect the routine to feel mechanical at first. It starts to stick once people see that a number raised in one meeting leads to an action, and that the action gets checked in the next one.