Whichever the recipient actually reads. A short operational report works well as a message; a report with a table reads better in email. What does not work is sending both - that guarantees neither gets read seriously.

What if no system produces reports?

You can build from a spreadsheet or an export and schedule the send. Most first reports in a small business are built that way and they work - provided the source is stable, as covered in [fixing your spreadsheet before buying software](/blog/excel-automation-before-buying-software).

How many reports is too many?

Once somebody receives more than two or three regulars, they stop reading all of them. One consolidated report beats several split ones, even if it is slightly longer.

Whoever owns automation generally. A report is an automation in every sense, and it breaks for the same reasons - a changed column, permission or tool, as covered in [who maintains the automation](/blog/automation-ownership-and-monitoring).

Scheduled Reports Instead of Asking

Most update requests in a business are a report nobody defined. What belongs in a report that sends itself, to whom, how often, and how to know it did not arrive empty.

A large share of interruptions in a small business is update requests: "where is that order", "how much did we sell this month", "who has not paid yet". Each is a reasonable question, and each stops somebody mid-task. The answer is not replying faster but sending the answer before it is asked - which is exactly what a scheduled report does.

How to identify which report to build

Not by what sounds important but by what gets asked. A week of recording the questions asked in the business - who asked, what, how many times - produces the list almost by itself. The three most repeated questions are the first three reports.

What usually surprises people is that the most frequent question is not about sales but about status: where something specific stands. That changes the report design - instead of a monthly summary, what is needed is an open-items list.

What goes in a report, and what does not

Goes in	Stays out
Numbers that lead to an action	Numbers "for information"
A list of exceptions	A list of everything
Comparison to the previous period	A chart with no context
Who needs to do something	Data nobody asked for

The deciding rule: if nobody will do anything because of a line, it should not be there. A twenty-line report where three lines lead to action becomes, within a month, a report nobody opens - and that holds even when all twenty lines are accurate.

A structure that works

Five lines, in a fixed order: the headline number, the change from the previous period, two or three exceptions needing attention, and one sentence on what changed. That is it.

The reason it works is that it is readable on a phone in twenty seconds. A report requiring a computer gets read in the evening, or not at all - and in a small business that is the difference between a report that changes a decision and one that documents it afterwards. That structure is also the basis for the weekly management report in a one-page weekly management report.

How to stop a report becoming noise

A report, exactly like an alert, loses value once it arrives more often than anyone can act on. Three simple checks keep it useful: did anybody act on it in the last month, does it cover the period in which decisions are actually made, and can it be read without opening another file.

The third is the most practical. A report attached as a file adds a step, and every step lowers the read rate. Five lines in the body of the message get read; the same five lines in an attachment get read by half the recipients, and in a busy business by fewer.

Frequency: match the decision rhythm

Daily - only for what requires a response that day.
Weekly - most operational reports.
Monthly - money, trends, comparisons.
On a trigger - an exception not worth waiting until the end of the week for.

The common mistake is a daily report about something decided monthly. It creates noise, and within two weeks it is read as noise - meaning not at all. The logic of thresholds that do not create noise is in business event alerting thresholds.

Who it goes to

To a name, not a distribution list. A report reaching five people none of whom owns it is a report nobody acts on - everyone assumes somebody else is handling it.

The simple rule: every report has one recipient responsible for acting, and others copied if they need to know. That distinction looks formal and it is what decides whether the report produces action or only transparency.

The silent failure: a report that arrives empty

An automated report that stops receiving data does not stop sending - it keeps arriving with zeros or an empty table. In the first week somebody asks, in the second they assume it was quiet, and by the third nobody looks.

The prevention is simple: every report states how many records it read to produce itself. One line - "143 orders checked" - turns an empty report from "a quiet week" into "something broke". That is the same principle as in silent failures in Zapier and Make, and it applies to reports exactly as it does to automations.

How to build the first report

Pick the question asked most often.
Write the answer in five lines, by hand, once.
Send it manually for a week and see whether anyone responds.
Adjust based on what they asked to add or remove.
Schedule it only once the content has settled.
Add a control line stating how many records were read.

This order avoids the common mistake: automating a report before knowing what should be in it. A week of manual sending costs twenty minutes and reveals exactly what is missing - and sometimes reveals that nobody actually wanted the report, which is an answer worth far more than the automation.

What about a report somebody asked for once

A one-off request is not a reason for a standing report, and that is one of the common ways unread reports accumulate: somebody asked something once, a report was built, and it keeps sending two years later.

The simple rule is that every scheduled report gets a review date - six months out - at which you ask whether it is still needed. A report without such a date stays forever, because nobody feels authorised to cancel something somebody else requested.

What do you do when the report is not being read?

First find out why, and do not add to it. The three common reasons: it is too long, it arrives at the wrong time, or it leads to no action. All three are solved by shortening rather than expanding.

The simplest check is to ask the recipient what they did because of the last report. If the answer is "I looked at it", the report documents; if it describes an action, it works. And if it turns out nobody did anything for a month - stop sending it and see whether anyone asks.

Scheduled Reports Instead of Asking for Updates

Key takeaways