Key takeaways
- The monthly close tells you what happened. The operating review tells you what to do about it. A business that closes the books but does not review them in a structured, decision-oriented meeting is producing reporting without deriving accountability.
- The most common failure mode of a monthly operating review is that it becomes a reporting presentation rather than a working session. When leaders present results without being asked to explain variances, propose actions, and commit to outcomes, the meeting produces information but not decisions.
- The operating review should be designed around variance, not performance. A month where everything is on plan requires 20 minutes. A month with material variances requires 60 minutes focused on root cause and corrective action, not on celebrating what is on track.
- PE boards require a monthly operating review as a governance standard. Founders who build one before a sale or recap are not doing extra work, they are building the management system the new owner will require, and demonstrating it is already running.
- The output of a good operating review is not a set of slides, it is a list of decisions made, actions assigned, and owners accountable. Without those outputs, the meeting is a status update, not a management event.
In this article
Operating diagnosis
What this means in practice: the first improvement is usually not a new dashboard; it is a named owner, a fixed metric definition, and a recurring decision cadence that forces action.
Operator Checklist
- Name the metric, process, or decision this issue affects.
- Assign a single owner with authority to change the process.
- Pull the last 12-24 months of data and identify the pattern, not just the latest month.
- Choose one corrective action that can be tested in the next 30 days.
- Review the result in the next management cadence and document the decision.
Companies with a structured monthly operating review, including variance analysis, corrective action commitments, and accountability tracking, showed 18–24% lower performance variance quarter-over-quarter than those with only a monthly financial close and informal management discussion.
The most common reason operating reviews fail to produce behavioral change: the meeting is structured as a presentation by the CFO to the founder rather than a discussion among functional leaders who own the variances. When leaders present other people's performance rather than their own, accountability is absent.
PE operating partners rate "management team can run a meaningful monthly operating review without founder facilitation" as one of the top 5 post-close readiness signals. Founders who build this capability before a process demonstrate management depth that affects valuation.
Most middle market businesses have a monthly close. Fewer have a monthly operating review. The distinction matters: a close is an accounting event that produces a set of numbers. An operating review is a management event that produces a set of decisions. The numbers without the meeting are reporting. The meeting without the numbers is conversation. The combination, a structured review of current-period results that produces specific decisions and accountability, is the <a href="/insights/operating-cadence-management-reviews" class="subtle-link">operating cadence</a> that determines whether the <a href="/insights/management-package-buyers-trust" class="subtle-link">management package</a> actually improves business performance or just documents it.
The monthly management reporting package covers what to include in the report. The operating cadence post covers the broader cadence structure. This post covers the mechanics of the meeting itself: how to run it, what to ask, and how to ensure it produces decisions rather than information.
18–24%
Lower performance variance for companies with structured monthly operating reviews vs. those with only a monthly close
Top 5
PE operating partner rating of "management team can run a meaningful operating review without founder" as a post-close readiness signal
#1 failure mode
Meeting structured as a CFO presentation rather than a functional-leader accountability session
Meeting design: who is in the room and what they own
The monthly operating review should include every functional leader who owns a material P&L or operational metric: the CFO or controller (financial results), the VP of Sales or Revenue (revenue, pipeline, new bookings), the VP of Operations or Delivery (cost, utilization, gross margin), and any other leader whose domain is represented in the management package. The founder or CEO chairs the meeting.
Each leader reviews the performance of their own function, not a CFO summary of everyone's performance. The meeting design creates accountability because each leader is explaining their own results, not observing someone else present them. When the VP of Operations explains why direct labor costs were 4% over budget, they own that explanation. When the CFO presents "ops was over budget on labor," no one is accountable.
The founder should not present at the monthly operating review, they should chair it. The difference is significant. A founder who presents the financials to their management team is performing the CFO's job. A founder who asks each functional leader to present their results, explain variances, and commit to actions is building the management depth that makes the business independent of the founder. See the founder vacation test for why this independence matters for transaction value.
The meeting structure: how to run 90 minutes that produce decisions
Monthly Operating Review: A 90-Minute Agenda
0–10 minutes: Prior month scorecard
The CFO presents a one-page scorecard: revenue vs. plan, gross margin vs. plan, EBITDA vs. plan, and 3–5 KPIs that track the operating drivers of the financials. No narrative, just the numbers vs. plan and the year-to-date position. The scorecard sets the context for what deserves deep discussion.
10–30 minutes: Revenue and pipeline review
The Sales lead presents: revenue vs. plan (actuals), new bookings vs. plan, pipeline weighted value vs. target, and 3 deals by stage. For each metric off plan: root cause in one sentence and proposed corrective action. No discussion of on-plan metrics beyond acknowledgment.
30–55 minutes: Operations and margin review
The Operations lead presents: gross margin by service or product line, utilization or production efficiency vs. plan, and any significant variance in direct costs. For each variance: root cause, whether it is recurring or one-time, and the corrective action if recurring. This section is typically the longest because margin variances are the most consequential.
55–70 minutes: Cash and working capital
The CFO presents: current cash position vs. the 13-week forecast from the prior month, AR aging and days outstanding vs. target, and any significant working capital movement. If there is a cash or credit facility issue, it surfaces here with full context.
70–85 minutes: Decisions and actions
The CEO facilitates: list every decision that needs to be made based on the prior discussion. Assign each decision to an owner with a due date. Confirm that each functional leader has a specific action commitment from their section. Capture in writing before the meeting ends.
85–90 minutes: Prior month actions review
Pull up the action list from the prior meeting. For each action: was it completed? If yes, note and close. If no, why not, and what is the new commitment? This 5-minute review is the accountability mechanism that gives the decision-making in the prior 80 minutes any teeth.
The 85–90 minute prior actions review is the most important 5 minutes in the meeting. Without it, the monthly review produces action commitments that are never followed up on and the meeting degrades into a status report. With it, the meeting creates a visible accountability loop: leaders know that what they commit to in one month will be reviewed in the next.
Operating workflow scan
Turn the issue in this article into a ranked AI workflow roadmap with readiness gaps and estimated time savings.
Find the first workflow →What to do with variances: the three questions
Every material variance in the management package deserves three questions. The meeting should be structured to produce answers to all three for every variance above a defined threshold (typically any variance exceeding 5% of plan for a major metric).
The Three Questions for Every Material Variance
Question 1: What happened? (Root cause)
Describes the specific cause of the variance, not a description of the variance itself. "Revenue was $180K below plan" is a description. "Revenue was $180K below plan because two contracts scheduled to close in March slipped to April based on customer procurement timelines" is a root cause. The distinction matters because the corrective action depends on the root cause.
Question 2: Is it recurring or one-time?
A one-time variance (a customer payment that arrived late, a one-off cost in an unusual period) requires acknowledgment but not corrective action. A recurring variance (labor efficiency has been below plan for 3 consecutive months) requires a structural response. Conflating the two produces either overcorrection on one-time events or inaction on recurring problems.
Question 3: What is the corrective action and who owns it?
Every recurring variance should produce a specific action commitment with a named owner and a due date. "We will improve" is not a corrective action. "The VP of Operations will implement revised scheduling protocols by April 15 to reduce overtime to within 5% of plan" is a corrective action. The distinction determines whether the review produces accountability.
A $9M commercial HVAC services company had been running monthly closes for 3 years but reviewing results in an informal 30-minute meeting that produced no written outputs.
When the founder formalized the operating review with the structure above, the first meeting with written action tracking revealed: the VP of Operations had committed to "address technician overtime" in the prior informal meeting but had not changed the scheduling model. In 4 months of informal reviews, the overtime issue had been acknowledged 4 times without a corrective action being assigned. Once the formal review required a written owner and due date, the issue was resolved in the following 30 days.
The margin improvement from reduced overtime was $42K annually.
How PE boards run the operating review and what that means for founders
PE-backed companies run a monthly operating review as a board governance requirement, typically presented to the board or a board committee within 15 days of month-end. The format is standardized: management package, variance bridge, YTD vs. plan, revised full-year forecast, and action items from the prior meeting.
For founders preparing for a sale or recap, building a functional operating review before the process demonstrates that the management team can govern the business without the founder's daily involvement, which is one of the key signals PE buyers assess. A management team that runs a clean monthly operating review independently, with no founder facilitation required, is a management team that can operate post-close without the founder at the center of every decision.
Common operating review mistakes
Frequently asked questions
How is an operating review different from a board meeting?
A board meeting includes external governance (board members, investors) and covers strategic decisions, capital allocation, and investor-level reporting. An operating review is an internal management meeting focused on operational execution: results vs. plan, variance accountability, and corrective action decisions. Most PE-backed companies have both: an operating review at the beginning of each month (management team only) and a board meeting quarterly (management plus board). Founders building toward institutional governance should distinguish between these two forums.
How long should a monthly operating review take?
For a $5–25M business, 60–90 minutes is the right duration. Less than 60 minutes does not allow meaningful variance discussion. More than 90 minutes typically means the meeting is covering too much ground, the reporting format has too much data, or participants are not prepared. Effective operating reviews are enabled by pre-reading: distribute the management package 24 hours before the meeting so participants arrive with context, not requiring a full data walkthrough.
What if the management team is not used to this kind of accountability?
The first 2–3 operating reviews under the new structure are uncomfortable. Leaders who have not been expected to explain their variances will present vaguely and avoid specificity. The founder's role is to ask the three questions, what happened, is it recurring, who owns the corrective action, consistently and patiently for the first few meetings. The behavior normalizes by month 3–4 as the team adapts to the expectation.
Work with Glacier Lake Partners
Explore Operational Advisory
Useful when building or improving the operating review cadence that supports business performance and diligence readiness.
Explore Operational Advisory →Operating workflow scan
Find the reporting or execution workflow worth automating first.
Turn the issue in this article into a ranked AI workflow roadmap with readiness gaps and estimated time savings.
Find the first workflow →Research sources
Disclaimer: Financial figures and case-study details in this article are anonymized, composite, or representative examples based on middle market operating situations, and are not guarantees of outcome. Statistical references are drawn from cited third-party research; individual transaction and operational results vary based on business characteristics, market conditions, and deal structure. This content is for informational purposes only and does not constitute legal, financial, or investment advice. Consult qualified advisors for guidance specific to your situation.
Explore adjacent topics
