How to automate weekly reports to WhatsApp and email

Why automate the weekly report at all?

In most companies the weekly report is a ritual: someone exports from three systems on Monday morning, pastes into a workbook, checks it, saves a PDF and forwards it to a list. It takes two to four hours, it arrives at a different time each week, and when that person is on leave it does not arrive at all.

Automating it does three things. The report lands at the same time every week, so the meeting can run from it. The numbers come straight from the source, so nobody has to ask whether they were pasted correctly. And the hours go back to the person who used to build it, who can now spend them explaining what changed. This guide covers the daily and weekly operational sends; for the monthly pack, see how to automate the monthly board report.

What should a weekly report contain?

A report people read on a phone has less room than a dashboard on a laptop. Keep it to one page:

• Three to five headline numbers with a comparison each — this week against last week and against plan. “Sales 412k · 96% of plan · +4% on last week.”
• One trend chart of the most important number over 8–13 weeks, so a bad week is seen in context.
• One ranked table — stores, reps, branches or products — with the worst performer visible, because that is where the conversation goes.
• The update time, so nobody asks whether it is current.

A worked example: a café chain sends each site manager a Monday 07:00 report with covers, average spend, labour cost % and waste for their site, plus the week’s trend. The area manager gets the same page with every site ranked by labour cost. One dashboard, one schedule, twelve different reports.

WhatsApp, email, Slack or Telegram: which channel?

Send the report where the reader already looks. Each channel has its place:

• Email is the record. A PDF in the inbox can be filed, forwarded to the auditor and found again in six months. Use it for owners, boards, clients and anything that may be referred to later.
• WhatsApp is where store managers, field sales, branch heads and owners in the Gulf, India and South-East Asia actually read messages. An image of the dashboard opens instantly, even on a weak connection.
• Slack suits office teams that already run their day in channels: a Monday report in #sales starts the week’s thread.
• Telegram works well for groups and for markets where it is the everyday messenger.

Rule of thumb: the PDF to email for the record, the image to chat for reading. Many teams send both from one schedule.

When should it arrive?

Time the report to the decision, not to the end of the working day. A weekly sales report is most useful 30 minutes before the Monday sales meeting; a daily trading report before the store opens; a weekly cash report before the Tuesday payment run. Send it in each recipient’s own time zone — a group with sites in Dubai, Riyadh and Mumbai should not send everyone’s report at the same instant.

Set the schedule to run after the data has refreshed. If the overnight import finishes at 05:30, a 06:00 send is safe; a 05:00 send would deliver last week’s numbers with this week’s date.

One schedule, a different report for each person

The mistake that makes report automation unmanageable is building one dashboard per recipient. Forty branches become forty dashboards, forty schedules, and forty things to fix when the layout changes.

Instead, set row-level permissions once — each branch manager sees their branch, the regional manager their region, the owner everything — and send one schedule to the whole list. Each person receives the report with only their rows, and sensitive columns such as salaries or cost prices stay masked for those who should not see them. When the layout changes, it changes for everyone.

Alerts vs scheduled reports

A schedule sends at a time; an alert sends when something happens. Both belong in the same setup:

• Schedule the reports people review on a rhythm: the Monday pack, the 07:00 daily trading report, the month-end close.
• Alert on the numbers that cannot wait: stock of a fast seller below 50 units, a day’s refunds above a threshold, a large order from a new customer, a plant line stopped.

A good alert says the value and the line it crossed (“Stock of SKU 1182 is 42, below 50”) and links to the dashboard. Keep alerts few. If an alert fires every day, it is a report; if people start muting it, raise the threshold.

Setting it up in an afternoon

1. Pick the one report that costs the most hours each week. Start there, not with everything.
2. Rebuild it as a dashboard from the source systems, with the comparisons built in.
3. Set the permissions so each recipient sees only their rows.
4. Schedule it: day, time, time zone, format (PDF or image) and channel.
5. Run it in parallel with the manual version for two weeks, then switch the manual one off.
6. Add two or three alerts for the numbers that cannot wait a week.