Operating Cadence and Management Systems
The monthly operating review that isn't theater
A monthly operating review interprets numbers the monthly close has already produced. It is not the meeting where the books get built, and it is not a status recital. The working shape is a fixed agenda: variance against plan, margin by service line, cash and coverage, then a single block for deciding what changes. If nothing on the agenda can result in a decision, the meeting is theater and should be shortened to a memo.
Who this is for. You have a monthly meeting where the books get presented, everyone nods, nothing changes, and you suspect the whole hour exists because you scheduled it rather than because it decides anything.
Two meetings, not one
The most common reason a monthly review is worthless is that it is doing two jobs. The close produces the numbers; the review interprets them. When those collapse into one meeting, the hour is spent litigating whether a figure is right — was that accrued, is that job in the right period, why does the field system disagree with the ledger — and the decision the meeting existed to make never gets made.
Separating them requires a close checklist with a stated completion date and an owner, so the review can begin from the premise that the numbers are final. In an acquired business that premise is often false for the first several months, and the honest response is to run a shorter review against the two or three numbers you do trust rather than a full review against numbers you do not.
Trust in the numbers is downstream of two artifacts. The chart of accounts has to be structured to answer the questions the review asks — margin by service line cannot be produced from a chart that grew by accretion under the previous owner — and every recurring number needs a written definition, or two people will present the same metric differently and the meeting will discover it live.
The date is set by the lender, not by preference
In a leveraged acquisition the monthly close has a deadline that is contractual rather than administrative. The credit agreement specifies what has to be delivered and by when, and the close calendar is built backwards from that date. Operators who treat the close as an internal convenience discover the constraint the first time a reporting package is late, which is a conversation nobody wants to be having in month four.
That also determines part of the review's agenda. Whatever the credit agreement measures, the review measures — monthly, before the lender does, so that a covenant conversation is never the first time you have seen the number. Coverage of debt service is the obvious one; fixed-charge coverage is the one that catches people out, because it includes rent and lease obligations and those are exactly what breaks the arithmetic in a trades or distribution business with a yard, a fleet and a building.
Producing that reporting is the operator's job, and this page covers producing it. What an outside owner does with the numbers once received — the monitoring rights, the collection templates, the portfolio-level rollup — is a different object on a different side of the table, and conflating the two is how an operating review turns into an investor-relations exercise that helps nobody inside the company.
An agenda that produces decisions
The monthly review sits between two other meetings and should not duplicate either. The weekly leadership meeting handles the short-cycle numbers and this week's obstacles. The quarterly review resets priorities. The monthly is for the things that only become visible over a month: margin drift, mix shift, cash timing, and whether the quarter's priorities are actually moving.
A workable agenda has four blocks and a hard time box. First, variance against plan, presented by the person who owns each line rather than by the controller reading everything. Second, margin by service line and the customers or job types that moved. Third, cash — collections, the rolling forecast, and coverage. Fourth, a single decision block: what changes as a result of the previous three. Reserve at least half the time for the fourth block, because that is the only part of the meeting that produces anything.
The most useful single import from the framework literature here is the discipline of identifying, discussing and then solving one issue at a time rather than touring all of them. A monthly review that surfaces eleven issues and resolves none is worse than one that resolves two, because the eleven reappear next month with the added information that raising them accomplishes nothing.
One named owner per number, presenting their own line, is what converts the meeting from a report into a review. It also exposes rows nobody owns, which is diagnostic: an unowned number on a monthly agenda is usually a number nobody can act on.
The inputs that make it worth an hour
Three inputs carry most of the value. The first is margin by service line, which requires the account structure to support it and which almost always changes someone's mind the first time it is produced honestly — usually about a line the business has been running out of habit. The second is a customer-profitability view, because in an inherited business the loudest customer and the most profitable customer are frequently not the same one, and nobody has ever laid the two side by side.
The third is a thirteen-week rolling cash forecast, refreshed weekly and reviewed monthly. Build it direct — weekly receipts minus weekly disbursements, rolled forward — rather than deriving it from the profit and loss statement. A direct forecast is what tells a leveraged operator whether a payroll and a debt-service payment land in the same week; an indirect one, however elegant, does not answer that question on the timescale it matters.
Everything else on the agenda is negotiable. If a section of the review has run for three consecutive months without producing a decision, cut it and put the time into the decision block — or accept that the meeting is shorter than an hour, which is a legitimate outcome and a cheaper one. Management time in a company of this size is the scarcest input there is, and a review that exists to demonstrate rigour rather than to change something is spending it.
The formulas, and the benchmarks we will not print
Each metric below publishes what can be computed and refuses what cannot be sourced. A median with no traceable population is not a benchmark; it is a number someone repeated. Where a figure would go, this page says why it is absent.
Debt service coverage
cash available for debt service ÷ total debt service
Compute it yourself, monthly, before the reporting package goes out. What matters operationally is the trend and the headroom, and whether the number is being carried by something non-recurring.
No benchmark, because: The minimum threshold widely attributed to the loan programme is not verifiable from any of the agency's retrievable sources, and the standard operating procedure that would settle it is distributed only as a word-processor document in which the clause was not located. Your own credit agreement states your covenant; that document, not a published convention, is the threshold that binds you.
Fixed-charge coverage
(EBITDA − unfinanced capital expenditure + rent) ÷ (interest + principal + rent)
The measure that includes leases, and therefore the one that catches out operators of businesses with a yard, a fleet or a building. Review it monthly alongside debt-service coverage, because the lease line is what usually breaks the arithmetic.
No benchmark, because: The covenant level is a fact about your own credit agreement rather than an industry convention, and no retrievable source publishes a defensible threshold for businesses of this size. Formula and interpretation only.
Cash conversion cycle
days inventory outstanding + days sales outstanding − days payable outstanding
On a monthly agenda this is a timing measure rather than an efficiency score: it tells you whether cash will be present on the days debt service, payroll and the largest supplier run coincide next quarter.
No benchmark, because: A good value is entirely industry-conditional and the published answers describe a listed company with a treasury function. We publish the formula and the leverage-specific reading, and no target.
What the review costs to run
attendees × meeting hours × loaded hourly rate, plus preparation and pack-production time
Worth computing once. It is the number that justifies cutting a block that has produced no decision in three months, and it usually surprises operators who have added attendees for visibility rather than for decision rights.
No benchmark, because: No framework steward publishes the overhead of its own meeting rhythm, and no independent measurement of it was located. The arithmetic is publishable; a percentage-of-payroll target is not.
A ninety-minute monthly review, time-boxed to force the decision block
An acquired 45-headcount services business, close completed by the eighth working day, reporting package due to the lender on the fifteenth. The review runs on the tenth.
1. 0–15 min — variance against plan
Each line presented by its owner, not by the controller. Only lines outside a stated threshold get discussed; the rest are taken as read from the pack circulated two days earlier.
2. 15–35 min — margin by service line and mix
What moved, and whether it was price, cost or mix. This is the block that requires the chart of accounts to have been rebuilt deliberately; without that, it is guesswork with decimal places.
3. 35–50 min — cash, collections and coverage
Rolling thirteen-week forecast, receivables ageing, and coverage of debt service computed before the lender computes it. No surprises reach the fifteenth.
4. 50–85 min — the decision block
One issue at a time, identified, discussed, solved, with an owner and a date. Two resolved beats eleven raised. This block gets the largest share of the meeting by design.
5. 85–90 min — commitments read back
Every decision restated with owner and date, and carried onto the weekly meeting's to-do list so it is visible before the next monthly.
6. Standing rule
Any block that produces no decision three months running is cut, and the meeting gets shorter. The review is not required to fill the time that was scheduled for it.
The timings are illustrative. The load-bearing parts are the ordering — numbers first, decisions last and longest — and the standing rule that a block which never produces a decision loses its slot.
What to take away
The close builds the numbers and the review interprets them. One meeting doing both spends its hour litigating figures instead of making decisions.
In a leveraged acquisition the close deadline is contractual. Build the close calendar backwards from the lender's reporting date, not from what is convenient.
Compute coverage yourself, monthly, before the package goes out. A covenant conversation should never be the first time you have seen the number.
Give the decision block at least half the meeting, and resolve issues one at a time. Two resolved beats eleven raised.
One named owner per line, presenting their own number. Rows nobody owns are usually rows nobody can act on.
Margin by service line and a customer-profitability view are the two inputs most likely to change someone's mind — and both depend on a chart of accounts rebuilt to support them.
Build the thirteen-week forecast direct rather than deriving it from the profit and loss statement. Only a direct forecast tells you whether payroll and a debt-service payment land in the same week.
A block that has produced no decision for three months loses its slot. The review is not obliged to fill the hour it was given.
Sources
SOP 50 10, Version 8, effective 2025-06-01 (.docx only)
US Small Business Administration · A1
Used for: The lender reporting obligations that fix the monthly close deadline in an acquisition financed under the loan programme.
Federal Reserve Banks · A1
Used for: Credit conditions and debt structure for small employer firms, with the convenience-sample caveat, establishing why coverage sits on the monthly agenda at all.
The EOS Model — Six Key Components: Vision, People, Data, Issues, Process, Traction
EOS Worldwide · B1
Used for: The framework's separation of data from issues, and the scorecard's stated purpose, quoted as prescription rather than as best practice.
The Level 10 Meeting — 90 minutes, seven segments
EOS Worldwide · B1
Used for: The identify-discuss-solve discipline and the argument for a long, protected decision block.
Mastering the Rockefeller Habits / Scaling Up (Harnish)
Scaling Up · B1 · to-verify
Used for: The monthly slot's place inside a daily-to-annual rhythm, cited to the book rather than to a restatement.
Permanent Equity · B2
Used for: Practitioner treatment of governance cadence and reporting inside operating companies, attributed as a practitioner view.
Practitioner-common convention — named and labelled as convention wherever it is used in copy
OperatorBeast editorial · B2 · located
Used for: Practitioner convention on close checklists and pack circulation ahead of the meeting, labelled as convention.