Reporting Templates & Cadence
#owner/anton #status/active
How Arkanza marketing reports up and across. The rule that keeps reports from bloating: each cadence reports only what its cadence can see. Daily catches problems, weekly catches pace, monthly catches trend and margin.
| Cadence | Audience | Answers | Lives in |
|---|---|---|---|
| Daily task log | Team (self) | Did today’s work get done? | App / daily sheet |
| Weekly report | Anton + team | Are we on pace this week? Any blockers? | <weekly template — to fill> |
| Monthly report | Abib / management | What’s the trend, are we on target, what decision is needed? | TEMPLATE_Monthly_Report |
Monthly report — how to use
- Copy TEMPLATE_Monthly_Report → rename
Monthly_Report_<Month_YYYY>, drop it in the month’s folder or here. - Fill numbers from the App / source sheets. Every KPI is defined in KPI_Definitions — don’t redefine on the fly.
- Targets come from Benchmarks. No target = add one first.
- Write Section 1 (exec summary) last.
- Anything that closed → separate post-mortem, not stuffed into the monthly.
Design principles
- Aggregate, don’t restate. Monthly ≠ four weeklies stapled together.
- Every number has a target and a source, or it doesn’t belong in the report.
- Contribution margin outranks GMV. Growth that loses margin gets flagged, not celebrated.
- End forward-looking. The report closes on next-month priorities + one decision ask, not on last month’s numbers.