Monthly management reports arrive in the second week of the following month. Useful for trend understanding, late for operational decisions. The rostering issue that was visible in week two of the month doesn't surface in the report until week six — which is week two of the new month, with its own issues already in motion.
The fix is a weekly management report — a short, structured Monday-morning read covering operational metrics that move week to week. Not a replacement for monthly reports; an addition that makes weekly decisions sharper.
Here's how to build one that actually gets read.
What goes in the weekly report
Tight. The whole report should be readable in 90 seconds. Four sections:
Section 1: revenue snapshot
- Revenue this week vs last week vs same week last year
- Revenue by outlet (or channel for non-multi-outlet operations)
- MTD revenue vs forecast for the month
Section 2: operational ratios
- Labour cost ratio per outlet for the week
- Cash position week-end vs week-start
- Delivery platform reconciliation status (or equivalent for non-F&B)
Section 3: exceptions
- Things that got flagged this week — supplier issues, reconciliation gaps, platform shortfalls, missing receipts
- Compliance items coming due in the next 30 days
- AR/AP items needing attention
Section 4: narrative
- Two to three sentences from the account lead explaining what was notable this week and what the operator should think about for next week
How to assemble it
Pulled together late Sunday or early Monday morning. Sources:
- Revenue and labour data: from Xero (already populated via POS and payroll integrations)
- Exception feed: from the AI agents (Outlier, Vendor Chaser, Categoriser, Close Captain depending on what got flagged)
- Narrative: drafted by the Compass agent, reviewed by the account lead
The whole assembly takes 30-45 minutes when everything is wired properly. The Compass agent drafts the report end-to-end; the account lead reviews the narrative, adjusts where needed, sends to the operator.
Who should see it
Default: owner, operations lead, account lead. Optional addition: outlet managers (for the section covering their outlet).
The report doesn't need to go to everyone in the business. The operational sharing is via dashboards (different audience, different cadence). The weekly report is for decisions.
The Monday-morning ritual
For maximum value, build a routine around the report rather than treating it as a one-way email.
- Owner reads the report Monday morning (90 seconds)
- Brief check-in with operations lead (10-15 minutes) on anything flagged
- Decisions logged for the week — rostering changes, supplier follow-ups, pricing reviews, anything actionable
- Friday revisit: did the decisions land?
The report is the trigger for the conversation, not the conversation itself.
What to leave out
- Monthly metrics that don't move weekly — gross margin, COGS detail, prime cost. These belong on the monthly report.
- Long explanatory text — the narrative section is two to three sentences, not two paragraphs.
- Vanity metrics — all-time revenue, social engagement, total customers served. None of it drives a Monday-morning decision.
- Forecasts you don't trust — if the forecast isn't accurate enough to act on, including it weekly trains everyone to ignore it.
Format
The right format is whatever the operator actually reads. We've seen variations:
- One-page email with the four sections. Most common; works on phone or laptop.
- Slack / Teams post in a designated channel. Works for teams that already live in chat.
- Web-published page behind owner login, refreshed each week. Best for operators who want to refer back to recent weeks.
The format follows the operator's preference. The content stays consistent.
Common questions about weekly management reports
Do I really need weekly reports if I already get monthly ones?
For operators of high-cadence businesses (F&B, retail, multi-channel services), yes. The monthly report is too late for operational decisions. For slower-cadence businesses (B2B services with monthly invoicing, low-volume operations), monthly may be enough. The test: are there decisions you make weekly that the monthly report comes too late for?
Who writes the weekly report?
For Acuitas clients, the Compass agent drafts; the account lead reviews and sends. For operations without that automation, a bookkeeper or finance lead typically owns the assembly. The discipline matters more than the role — same owner each week, same cadence, same format.
What if my operator doesn't read it?
Usually means the report is too long, too generic, or built around metrics the operator doesn't care about. Sit down with them, redesign around what they actually want to know each Monday, and cut everything else. A 30-second read that triggers a decision beats a 5-minute read that triggers nothing.
How long should the report be?
Half a page, on one screen, readable in 90 seconds. Longer than that, the operator skims; shorter and you don't have room for the narrative that turns metrics into decisions.
Should the report include forward forecasts?
A short forward view (next 14 days of cash, next month's payroll commitment) is useful. Longer forecasts usually drift out of accuracy quickly and degrade trust in the rest of the report. Keep forward views to what's genuinely knowable.
A working weekly report is the difference between monthly review meetings that look backward and Monday-morning conversations that look forward. Build it short; build it consistent; build it around what the operator actually decides on each week.
— The Acuitas team