The Monthly Ops Report: The One Page That Makes Last Month Legible

One page, six fixed sections, written the morning after the month-end close and shipped the same day. The three honesty rules that keep it a report instead of a press release, the five traps that turn it into wallpaper, and the twelve-person print shop whose trend number caught an on-time-delivery slide three months before the customer did.

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 whoever 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, filled in the morning after the month-end close so every number comes from the books rather than from recollection. It is the monthly answer to what the weekly ops review answers every Friday — the review is where the month is steered; the report is where the month is recorded, so that next month’s decisions are made on this month’s truth instead of on whoever argued longest.

The one page matters more than it sounds. A report nobody reads is a report nobody wrote next month. The discipline is not “more reporting” — it is a fixed page, a fixed author, and a fixed morning, sixty days in a row.

1. The one-page rule — six fixed sections, in this order

1. The trend number. One metric that defines this operation — on-time delivery, pick accuracy, first-response time, gross margin, billable utilization — defined once, in writing, and never quietly redefined. Written as number, prior month, one-line cause if it moved more than the threshold. This is the line the whole report exists for.
2. Money. Revenue, gross margin percent, cash at month end — four lines at most, all pulled from the close, never from memory. This section has one job: make the budget vs actuals hour findable when someone asks “where did that number come from?”
3. Incidents and near-misses. The count, the worst one in two lines, and what changed because of it. Sourced from the post-mortems — if nothing changed, that is the line: “no change made” is an honest sentence that starts useful arguments.
4. People. Headcount, open roles with days-open, and one staffing risk with a name on it. The risk line is what makes the coverage plan get written before the crunch instead of during it.
5. Process changes shipped. Dated one-liners, “shipped” meaning live in the operation, not planned or proposed. This section is the receipt for the improvement list the weekly review keeps producing.
6. Next month’s known pressure. Two or three items, each with an owner and a date — the renewal, the launch, the audit, the season. This is where next month’s report goes to find out whether the pressure was handled.

That is the page. 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 the answer “none, add it anyway” is how one page becomes six pages, and six pages is how reports die.

2. The writing ritual — one author, forty-five minutes, the morning after the close

The report has one author (the ops lead, or the owner in a team of five) and one slot: the morning after the month-end close finishes, because the close is what makes the money lines true. The ritual is forty-five minutes: pull the three money lines from the close, the count and the worst incident from the post-mortems, and write the other sections from the weekly reviews of the past four Fridays — which is why the weekly review’s promise ledger is worth keeping. Distribution is the same day: team channel or one-page email, everyone, not a meeting. A report that requires a meeting to be read has already failed; the meeting is where it gets discussed, once a month, for twenty minutes, if a line earns it.

3. The three honesty rules

• Same definitions every month. The trend number is defined once — window, denominator, exclusions — and redefining it requires writing down why. A metric quietly redefined in month four is not a trend anymore; it is two unrelated numbers wearing the same name, and every month-over-month comparison is fiction from that day.
• Bad months ship the same page. A report that only goes out when it flatters is a press release. The bad months are the ones where the page earns its keep — they are also the ones where skipping it is most tempting, which is how you end up with a report habit that evaporates the first time it matters.
• Every line has a name and a date. Risks, pressures, actions — owned and dated or cut. “Someone should look at supplier lead times” is not a line in a report; it is a wish with formatting.

4. The five traps

• The novel. Six pages with appendixes. Nobody reads past page one, so nobody notices the trend number, which was the whole point. One page. The detail lives in the close file, the post-mortems, and the reviews — the report cites, it does not contain.
• The vanity report. Only good news, curated by the person who wants the month to have gone well. It reads fine for four months and then the business has no record of when the problem started — which is the only thing a report is actually for.
• The dashboard dump. A screenshot of the analytics dashboard pasted in and called a report. Dashboards answer “what is happening right now?”; the report answers “what happened last month, what changed, and what is coming?” A dump has no causes, no owners, no next month — and no reader.
• The drifting definition. Covered above and worth its own line, because it is the most common way a habit survives while becoming useless: the page keeps shipping, the numbers stop meaning anything.
• The late report. Ships on the 20th of the following month, after the decisions it was supposed to feed. A late report is a history book; the report is a steering input, and it only steers if it arrives before the decisions — which is why the slot is tied to the close, not to “when we get around to it.”

5. Worked example — the print shop that saw the slide coming

A twelve-person custom print shop — trade work for design agencies plus walk-in business — ran its first monthly ops report in March. The trend number they picked was on-time delivery, defined as orders shipped on the promised date, measured across the month. March read 96.4%. April, 95.1% — a one-line cause was owed under their own threshold and the line said “two rush orders rescheduled, no pattern identified.” May read 91.8%, and the cause line — which they now had to write, in front of the team, every month — could no longer say “no pattern.” 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 the supplier switch to the delivery dates because no one was reading the trend line monthly. The fix was small and unglamorous: dual-sourcing on the two stock grades that caused the slips, a one-week buffer, and a delivery-date commitment written into the new supplier’s renewal. On-time delivery was back to 96.1% by September. The stakes behind the trend number were real: their largest trade account — roughly $40,000 a year — had started quietly moving rush work to a competitor, and the account manager said later that the September report, with the 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.

Kits

Every page ships with a kit block — the paid tools behind the free advice:

• The First 30 Minutes — free incident quick-start checklist
• Ops Starter Kit — incident response for small teams — $14
• Ops Starter Kit Vol. 2 — advanced incident response & communications — $27
• Ops Mega Bundle — all 5 kits in one download — $49

Related: the weekly ops review is the four Fridays that feed this page’s incidents, changes, and pressures; the monthly close checklist is where the money lines come from — the report is written the morning after the close, never before it; the budget vs actuals review is the variance hour that runs off the same close, same coffee; the year-end close is twelve of these months plus adjustments — a year of honest monthly pages is what makes December’s runway short; and the post-mortem template is where section 3’s worst incident comes from, with the change it produced.

Related: the shift handover log is the five-minute crossover sheet that keeps open issues from dying with the shift that found them — flags, absences and supplier problems written down while they are still cheap.