Ask most small-business teams how last month went and you get a mood: "pretty good, I think?" Ask for a number and you get a different number from every person you ask — because nobody wrote it down, and memory quietly rounds bad months up.
The monthly ops report is the antidote, and it is deliberately small: one page, the same six sections every month, written the morning after the month-end close so every number comes from the books rather than from recollection. The weekly ops review is where the month is steered; the monthly report is where the month is recorded — so next month's decisions are made on this month's truth instead of on whoever argued longest.
The one-page rule: six fixed sections
- The trend number. One metric that defines the operation — on-time delivery, pick accuracy, first-response time, gross margin — defined once, in writing, and never quietly redefined. Number, prior month, one-line cause if it moved past the threshold. This is the line the report exists for.
- Money. Revenue, gross margin percent, cash at month end — pulled from the close, never from memory.
- Incidents and near-misses. Count, worst one in two lines, what changed because of it. If nothing changed, the line says "no change made" — an honest sentence that starts useful arguments.
- People. Headcount, open roles with days-open, one staffing risk with a name on it.
- Process changes shipped. Dated one-liners; shipped means live in the operation, not proposed.
- Next month's known pressure. Two or three items, each with an owner and a date — the renewal, the launch, the audit, the season.
If a seventh section is fighting to get in, the question is not "where does it fit?" but "which of the six does it replace?" — because "none, add it anyway" is how one page becomes six pages, and six pages is how reports die.
The writing ritual
One author (ops lead, or the owner in a team of five), forty-five minutes, the morning after the month-end close — the close is what makes the money lines true. Pull the three money lines from the close, the incident count from the post-mortems, and write the rest from the past four Fridays' weekly reviews. Ship it the same day to everyone, not a meeting. A report that requires a meeting to be read has already failed.
Three honesty rules
- Same definitions every month. A metric quietly redefined in month four is two unrelated numbers wearing the same name — every comparison after that is fiction.
- Bad months ship the same page. A report that only goes out when it flatters is a press release. Bad months are where the page earns its keep — and where skipping it is most tempting.
- Every line has a name and a date. Risks, pressures, actions — owned and dated or cut. "Someone should look at supplier lead times" is a wish with formatting.
The five traps
The novel (six pages nobody reads) · the vanity report (only good news — no record of when the problem started, which is the only thing a report is for) · the dashboard dump (no causes, no owners, no next month, no reader) · the drifting definition (the habit survives while becoming useless) · the late report that arrives after the decisions it was supposed to feed.
The print shop that saw the slide coming
A twelve-person custom print shop ran its first monthly ops report in March. Trend number: on-time delivery. March: 96.4%. April: 95.1% — the cause line said "no pattern identified." May: 91.8% — and the cause line, now owed in front of the team every month, could not say "no pattern" anymore. The slide had been invisible before because it lived in three separate weekly conversations, each small enough to absorb; the report stacked the three months on one line and the slide became a fact.
The trace led to a paper supplier change made in February: cheaper per sheet, two days slower, and nobody had connected it to delivery dates because nobody was reading the trend monthly. The fix was unglamorous — dual-sourcing on the two stock grades causing slips, a one-week buffer, and a delivery-date commitment written into the supplier's renewal. On-time delivery was back to 96.1% by September. Behind the trend number sat a $40,000-a-year trade account that had quietly started moving rush work to a competitor; the account manager later said the September report — recovery on one line — was the only reason the account was not already gone.
The counterfactual is the version they almost ran: six months of mood-based reporting, the slide discovered by the customer, and the first honest report written as a post-mortem of a lost account.
The full page — with the six sections in detail, the traps, and the worked example — lives at Hive Ops Notes.
Free: The First 30 Minutes — the incident quick-start checklist. If your operation needs the full system: Ops Starter Kit ($14), Ops Starter Kit Vol. 2 ($27), or the Ops Mega Bundle (all 5 kits, $49).
Top comments (0)