Monthly Management Report Template
Three documents and five sheets, built around a register where every action names the line it must move, by how much, and by when.
Free download · No account needed
Action Register Procedure
[Entity] — three fields, or it is a note
The commentary resets every month. The register does not.
| Field | What goes in it |
|---|---|
| Line or metric | One line on the departmental P and L, or one flash metric. Not a theme |
| Committed effect | A monthly dollar amount, with a direction. Not a percentage |
| Month due | One calendar month. Not a quarter |
The distinction this makes, on one real item
| Note | We need to tighten up on delivery |
| Action | Duluth delivery cost down 14,000 a month from April, by routing every drop into one daily run |
The second one can be wrong, which is what makes it worth writing down. Notes are often true and belong in the commentary. They never get a status column, because there is nothing to score.
Tolerance, fixed when the action opens
| lands at | = | committed amount less 10 percent, floor 1,000 |
A threshold that can be revised once the result is known is not a threshold. If the commitment turns out to be unreachable, that is what versioning is for: v2 carries the smaller number and v1 stays readable.
Four verdicts, computed off the ledger
| Open | Inside the month it was due |
| Landed | The named line moved far enough, by the month named |
| Missed | It did not. Stays in the register with a cause, and ages |
| Superseded | Replaced or withdrawn with a reason. Never deleted |
Nobody is asked whether their action worked. The register reads the line.
Page one for this query already has action items. The free management report templates carry them with an owner and a due date, and one of them tells you to review progress on last month's actions before you write this month's. That is where all of them stop. Progress is what the owner says happened. Nothing on page one names the line an action is supposed to move, or the amount, or checks the ledger afterwards.
Here an action needs three fields or it is a note: the line, the monthly dollar amount, the month due. Halvorsen Equipment Rental, an illustrative four-branch equipment rental company, put 34 actions through nine months of that. Seven more items were proposed and stayed notes because they could not name a line and an amount. Of the 27 actions that came due, 19 landed and 8 missed, and 77,600 of committed dollars never reached a ledger line.
The verdict comes off the ledger, so a miss gets the line decomposed before it gets a cause. The Rochester branch's base wages fell 14,300 against a commitment of 15,000 while overtime on the same line rose 15,200, so the line moved 2,800 and the action missed. Federal audit rules keep an uncorrected finding on the schedule with the reasons for its recurrence, and COSO's framework sends a finding to whoever can act on it. The outward-facing version of the same month is a board package.
What's in the pack
Action Register sheet
One row per action, carrying its number, owner, department and version. Then the commitment: the line it must move, the monthly effect, the month due. Then the score: realised movement, the threshold it lands at, the verdict, the cause, months past due. Nothing is ever deleted.
Space rule
An action names a line, an amount and a month. Three required fields, a tolerance fixed when the action opens, four verdicts computed off the ledger, six causes for a miss, and versioning rather than rewriting. It governs every prompt in the space.
Action Effect Log sheet
The arithmetic behind every verdict, one row per component measured: the baseline month and figure, the measured month and figure, the change, and a note. This is where an offsetting movement gets found, and it is the reason a verdict is evidence rather than an assertion.
Action Register Procedure
The standing method rather than a monthly document. What qualifies as an action, the tolerance formula, the six-step scoring run, how to decompose a line for a miss, the ceiling test before anyone argues about execution, and four escalation triggers with one response each.
P and L by Department sheet
Revenue, direct cost, contribution and margin per department with the prior month and budget alongside, then the overhead departments and operating income. The open actions and the year-to-date landed ones sit in two columns beside each department. Seeded from whatever the close produced.
Trend sheet
Six months of every line and every flash metric, with a source column on each row, plus two rows nobody else keeps: actions landed in the month and actions missed in the month. A series whose mapping changed gets restated rather than quietly broken.
Flash Metrics sheet
Six operational rows with a definition, the system and query behind them, three months of history, a direction and the action attached. A metric drifting the wrong way for three months with nothing attached is the flag the space raises first.
Management Commentary
Written after the register is scored, never before, and reading from the sheets so no figure is retyped. The month in four numbers, what the register says with both rates, the misses that found something, anything aged past three months, then a block per department. Distinct from the board package and the investor update.
Department Owner Brief
Sent to each owner once, so the first meeting is not spent explaining why a status is not an answer. What they own, the three fields, how the verdict is computed, why the line counts and not the component, and how to size a commitment before making one. The same owner presents these numbers again, department by department, at the quarterly finance review.
How to use it
- 1
Download the files, or open the pack
Three Word documents and five CSV sheets, with no account. Or open the pack in River and give it a departmental ledger, and the read and the register get built from your own accounts.
- 2
Send the ledger with departments intact
The last closed month at minimum, three or more for a usable trend, plus whatever operational data the business runs on. If a line needs explaining rather than tracking, the flux commentary tool handles that half.
- 3
Turn what you already decided into rows
Most of it will come out as notes, which is the intended result. The one or two items that can name a line, an amount and a month get a baseline, a threshold and a ceiling check before the row is written.
- 4
Score, then write, in that order
After each close the register reads the named lines and assigns verdicts. Misses get their line decomposed and one cause. Only then does the commentary get written, because a commentary written first credits actions the ledger has not confirmed.
Frequently asked questions
Is this template free?
Yes. Three Word documents and five CSV sheets, no account, no card, no trial. Edit with AI is there for anyone who would rather hand over a departmental ledger than map accounts to lines by hand and set up the register columns themselves. Everything else is in the free templates library.
The free templates already have action items. What is different here?
They have an owner and a due date, and they ask you to review progress. Progress is self-reported. Here the action names the line and the dollar amount, and the verdict is read off the ledger against a threshold fixed when the action opened. Nobody is asked whether their action worked.
Is it fair to score the line when the component moved as promised?
It is the point. A saving that never reaches the line is not a saving, and the department is accountable for the line. What stops it being punitive is the decomposition: the offsetting component gets named with its amount, so the record says the work was real and exactly what ate it.
What happens to an action that keeps missing?
It stays in the register, gains a cause and ages. Past three months past due it is resized or withdrawn rather than carried unchanged, which is a normal outcome. Deleting it would remove the only evidence that the same problem has been discussed since February.
Can I use this if I have no budget to compare against?
Yes. The register scores movement against a baseline month, not against a plan, so it works from the ledger alone. The budget columns stay empty until there is one, and the annual budget pack is where that gets built if you want it.
How is this not just a board pack with different sections?
Audience and consequence. A board package explains a quarter to people who were not there, so its register tests whether last quarter's explanations turned out to be true. This one is read by the people who decided, so its register tests whether what they decided moved the line they aimed at.
Most of what comes out of our meetings will fail the three fields. Is that a problem?
No, and it is worth seeing. In the worked example seven of 41 proposed items stayed notes. Notes go in the commentary and are often true. What they do not get is a status column, because tracking something nobody can measure is the habit this pack exists to break.
Give your monthly read a memory
Download the blank pack as Word and CSV files, or open this exact pack in River and let it build the departmental read and the register from your own ledger.
Edit with AI