Automated reporting means a short summary of your key numbers arrives in your inbox at the same time every week, pulled from the systems where the numbers actually live, so you stop building the report by hand. The best version has five numbers, one source for each, and a note when something looks wrong. A fifteen-tab dashboard nobody opens is the version to avoid.
Below: how to choose the five numbers, where each should come from, how the weekly job runs, and the checks that keep a report you can trust.
Why most business reports go unread
Owners tend to end up in one of two places. Either nothing is reported and decisions run on feel, or someone spends Friday afternoon copying figures from three systems into a spreadsheet that is out of date by Monday.
Both fail for the same reason. The numbers are not defined, not in one place and not delivered when a decision gets made. Automating the delivery fixes the third problem only. The first two need you to decide, once, what you are counting and where it comes from.
If the cost of doing nothing is unclear, our guide to calculating automation ROI shows how to put hours and dollars on a task like this. Reporting is often a good candidate because it is repeated, rule-based and easy to check.
Pick five numbers
Five is a rule of thumb and not a law, but it forces a useful discipline. Every number must change a decision. If nobody would act differently whether it went up or down, leave it out.
A service business might choose:
| Number | Question it answers | Source of truth |
|---|---|---|
| New enquiries this week | Is demand healthy? | CRM, counting each enquiry once |
| Quotes sent and quotes accepted | Are we converting? | CRM pipeline or quoting tool |
| Jobs booked or work scheduled | Is the diary full for the next month? | Calendar or job management tool |
| Money invoiced and money overdue | Is cash coming in? | Accounting software |
| New reviews and average rating | Are customers happy? | Google Business Profile |
These are examples for a typical local service business. A clinic might swap quotes for appointments attended and cancellations. A builder might track signed contracts and progress claims outstanding. Choose yours by asking what you would want to know on Monday morning before you have spoken to anyone.
Website visits are tempting to add, and they can matter, but they rarely change a weekly decision. Look at them monthly, using a tool such as Google Analytics, and keep the weekly report for numbers you can act on within days. If you are weighing a ready-made dashboard tool, read Power BI for a small business, or a custom dashboard.
One source of truth for each number
Every number needs one home. If enquiries are counted from the website form in one report and from the CRM in another, you will have two answers and an argument.
For each number, write down:
- The system that holds it.
- The exact definition. “Enquiry” might mean a new contact with a service request, excluding spam, suppliers and existing customers.
- The date it counts under. Date created, date accepted or date paid can give different totals for the same week.
- The owner who fixes it if it looks wrong.
This is dull work and it is the work that matters. A fully automated report built on a loose definition delivers wrong numbers on time. If your data is scattered, the first step may be a single place to hold it, and a CRM is usually where it ends up once a spreadsheet stops coping.
How the automated reporting job runs
Behind a weekly email there is a short chain of steps. Written out for a Monday 6am report, it looks like this:
- Trigger. A schedule fires at 6am every Monday.
- Pull. The workflow asks each system for last week’s figure, using the definitions you wrote down.
- Compare. It looks up the previous week and the four-week average, and works out the change.
- Flag. Anything that moved by more than a set amount, or is zero when it should not be, gets marked for attention.
- Write. It assembles the summary and sends it by email, or posts it in a team channel.
- Store. It saves the week’s figures to a sheet or database, so you build up a history without re-pulling old data.
Step four is what separates a report from a printout. A figure of zero enquiries on a normal week is more likely a broken form than a quiet week, and the report should say so.
What the report should look like
The test of a good layout is whether you can read it standing in a driveway or between appointments, and know whether anything needs your attention today.
Keep it to something you can read on your phone in under a minute. For example:
Week ending 10 November
Enquiries: 14 (last week 11, four-week average 12)
Quotes sent: 6. Accepted: 2
Invoiced: $18,400. Overdue: $6,200 (3 invoices over 14 days)
New reviews: 2. Average rating unchanged
Check: web form enquiries were 0 on Saturday. Test the form.
Those figures are made up to show the layout. Yours will reflect your own data.
Put the last line, the thing to check, at the top if there is one. Add a link to the underlying list for any number you might want to look into, such as the three overdue invoices.
Tools: spreadsheet, dashboard or workflow
You have three realistic routes.
- Spreadsheet with scheduled refresh. A Google Sheet or Excel file that pulls from your systems and gets emailed. Cheap and familiar, and it works up to a point. See our notes on Google Sheets automation.
- Dashboard tool. Tools such as Google’s Looker Studio or Microsoft’s Power BI draw charts from connected sources and some can email a scheduled copy. Check each vendor’s help pages for what your plan allows.
- Workflow tool. A tool like n8n or Zapier pulls the numbers, applies your rules, writes the summary and sends it. This suits flags and plain-language notes, which a chart does not do.
Dashboards suit people who like to explore. A weekly email suits people who want the answer without logging in. Many owners want the email and nothing else.
Checks that keep the report accurate
An automated report can be wrong without anyone noticing, because nobody rebuilds it by hand. Build these checks in.
- Reconcile monthly. Once a month, compare the report’s totals with the source system by hand. Invoiced totals should match your accounting software exactly.
- Watch for zeros and gaps. A missing figure should produce a warning, not a blank.
- Log the last successful run. If the report does not arrive on Monday, you should know whether the job failed or there was nothing to send.
- Keep definitions in one document. When someone changes how a status is used in the CRM, the report changes meaning.
- Name a maintainer. Connections expire and fields get renamed, which is why automations break.
Be careful with attribution, such as which marketing channel gets credit for a sale. It is a harder problem than counting, and a weekly email is the wrong place to settle it. See marketing attribution for small business before you add it.
Is it worth building?
Reporting is a good first automation because it is easy to see whether it worked: the email arrives, and the numbers match, or they do not.
A weekly report that costs you or your office manager an hour is about fifty hours a year. If the numbers also catch a broken form or a stack of overdue invoices a week sooner, that is money kept. The calculation is yours to do with your own hours and rates.
If you are comfortable with spreadsheets and your data sits in two systems, you can build the first version yourself. When the numbers come from four or five tools, or you want flags and plain-language summaries, a workflow built and looked after for you is easier. CentriWeb builds most client automations in n8n and can build the reporting flow and keep it running, but it will not suit you if your data is already clean in one tool and a built-in report does the job.