Monthly Business Review SOP for General Managers
A practical operating procedure for turning financial, customer, operational and people evidence into decisions, owners and follow-through.
Advanced Executive Program in Management & Business Administration develops connected capability across strategy, finance, customers, operations, technology and people. This practical SOP can be used before enrollment, during executive study or inside an authorized workplace exercise.
Monthly reviews often collect slides but fail to connect performance, causes, choices and accountable follow-through. The procedure below creates one operating rhythm across functions without turning the meeting into a reporting ceremony.
Operating principle
How should a general manager run a monthly review that produces decisions instead of a sequence of disconnected updates? Use the tool on this page to produce a repeatable monthly business review procedure, agenda and decision record. Start with a bounded decision, retain the evidence behind every material claim, and distinguish what is known from what is assumed. The tool is designed to improve management preparation and review; it does not replace the authority, specialist judgement or procedures required by an employer.
Why monthly review governance fails
The SOP creates a compact common language for those connections. It does not force every organization into the same answer. Instead, it makes local definitions, evidence, constraints and accountability visible. That is useful when a management team agrees on the goal but disagrees about the route, or when confident recommendations rely on incompatible assumptions.
SOP control architecture
| Element | Management purpose | Minimum evidence |
|---|---|---|
| Review charter | Define the business unit, decision horizon, participants and matters that belong in the meeting. | A one-page charter prevents the review from absorbing operational details that another forum should own. |
| Evidence pack | Freeze a small set of financial, customer, operational and people measures before the meeting. | Every metric needs a definition, owner, source, comparison and explanation of material movement. |
| Exception screen | Separate normal variation from issues that require management attention. | A threshold is a prompt for investigation, not automatic proof of a cause or failure. |
| Decision agenda | Convert exceptions into explicit questions with available options and constraints. | Participants should know whether they are being asked to inform, recommend, decide or execute. |
| Decision log | Record the choice, owner, deadline, assumptions and trigger for reopening it. | A decision without a named owner and observable next evidence is only meeting commentary. |
| Follow-through loop | Review prior commitments before opening new decisions. | Closure means evidence of completion or a documented change of decision, not a verbal status update. |
1. Review charter
Define the business unit, decision horizon, participants and matters that belong in the meeting. A one-page charter prevents the review from absorbing operational details that another forum should own.
Review question: What observable evidence would confirm that review charter is working in the selected scope, and who has authority to respond when it is not?
2. Evidence pack
Freeze a small set of financial, customer, operational and people measures before the meeting. Every metric needs a definition, owner, source, comparison and explanation of material movement.
Review question: What observable evidence would confirm that evidence pack is working in the selected scope, and who has authority to respond when it is not?
3. Exception screen
Separate normal variation from issues that require management attention. A threshold is a prompt for investigation, not automatic proof of a cause or failure.
Review question: What observable evidence would confirm that exception screen is working in the selected scope, and who has authority to respond when it is not?
4. Decision agenda
Convert exceptions into explicit questions with available options and constraints. Participants should know whether they are being asked to inform, recommend, decide or execute.
Review question: What observable evidence would confirm that decision agenda is working in the selected scope, and who has authority to respond when it is not?
5. Decision log
Record the choice, owner, deadline, assumptions and trigger for reopening it. A decision without a named owner and observable next evidence is only meeting commentary.
Review question: What observable evidence would confirm that decision log is working in the selected scope, and who has authority to respond when it is not?
6. Follow-through loop
Review prior commitments before opening new decisions. Closure means evidence of completion or a documented change of decision, not a verbal status update.
Review question: What observable evidence would confirm that follow-through loop is working in the selected scope, and who has authority to respond when it is not?
Procedure from T-5 to the next cycle
Step 1: T-5 working days
The review owner freezes definitions, requests commentary and identifies missing evidence. The immediate output is a versioned evidence pack with named gaps.
Step 2: T-2 working days
Functional owners submit one-page exception notes and proposed decisions. The immediate output is a decision agenda rather than a presentation queue.
Step 3: Opening
The chair confirms scope, previous actions and material changes since the last review. The immediate output is a shared baseline for the meeting.
Step 4: Diagnosis
The group distinguishes observed facts, interpretations, hypotheses and unknowns. The immediate output is a short causal view that can be tested.
Step 5: Decision
The accountable executive selects, defers or rejects an option and records the reason. The immediate output is a decision entry with constraints and assumptions.
Step 6: Close
The coordinator reads back owners, dates, dependencies and communication obligations. The immediate output is an agreed action register.
Step 7: T+2 working days
Owners confirm the written record and begin assigned actions. The immediate output is no silent reinterpretation after the meeting.
Step 8: Next cycle
The next review opens with evidence on prior commitments and decision outcomes. The immediate output is a learning loop instead of recurring rediscovery.
Case file: growth with margin leakage
A regional services business is above its monthly revenue plan but below contribution-margin plan. Customer renewal is stable, overtime is rising and one service line has repeated rework. The team must decide whether to add capacity, change the service promise or stop accepting low-quality demand.
| Evidence or choice | Current entry | Interpretation | Management response |
|---|---|---|---|
| Revenue | +6% vs plan | Commercial demand is not the immediate constraint | Do not reward volume before checking value |
| Contribution margin | -4 points vs plan | Higher activity is not converting to planned economics | Test price, mix, rework and labor causes |
| Overtime hours | +28% month on month | Capacity pressure is visible but not yet explained | Separate forecast error from process waste |
| Rework rate | 11% vs 4% threshold | Quality loss is concentrated in one service line | Assign root-cause review before hiring |
| Renewal | Stable at 91% | Immediate customer flight is not evident | Protect service continuity while testing changes |
Control defects and corrective actions
- Reviewing every metric with equal attention.
- Accepting commentary without a decision question.
- Changing metric definitions after results are known.
- Allowing slide owners to become default decision owners.
- Carrying actions forward without evidence.
- Treating a threshold breach as proof of a root cause.
Chair desk notes
How long should the meeting take?
A focused business-unit review usually needs 60 to 120 minutes. Scope and decision load matter more than a universal duration.
Who should chair it?
The person accountable for the integrated result should chair. A finance or operations partner can coordinate evidence without inheriting the final decision.
Should every function present?
No. Functions contribute evidence and recommendations only when their information changes the decision.
What belongs outside the review?
Detailed project stand-ups, individual performance conversations and incident command should use their own forums.
Evidence base and operating boundaries
The design is consistent with the process view in ISO guidance: management review has defined inputs and outputs, and evidence should allow a reviewer to determine whether the process is effective. The ISO 9001 Auditing Practices Group guidance on policy, objectives and management review is a useful primary reference for the distinction between conducting a meeting and maintaining a review process. This article adapts that logic to an integrated general-management forum; it does not assert that the supplied SOP establishes ISO conformity.
Two-cycle pilot protocol
Pilot the procedure with one business unit for two consecutive reporting cycles. Before cycle one, record the current duration, number of agenda items, percentage with an explicit decision request, overdue actions and known disputes about metric definitions. Do not use those observations as universal benchmarks; they are the local baseline.
After cycle one, interview the chair, process owner and two contributors. Ask which inputs arrived late, which item could not be decided, where authority was unclear and whether the written record matched the meeting. Correct only the controls connected to those failures. In cycle two, check whether the changes improved completeness without increasing preparation work beyond the value of the review.
The pilot succeeds when every agenda item has a disposition, every action has one owner and evidence rule, prior decisions can be reopened from their original assumptions, and participants can identify work that belongs in another forum. A shorter meeting is useful only if decision quality is preserved. A longer meeting may be justified during an exceptional transition, but recurring overtime should trigger scope reduction or a different cadence.
Record the local adaptation as a versioned change: field changed, reason, approver, effective cycle and effect on comparability. This provides evidence for later simplification and prevents the SOP from accumulating ceremonial controls.
Use a short exception taxonomy during the pilot: evidence late, definition disputed, authority absent, capacity unavailable, dependency failed or decision deferred. Count only the primary reason and retain a note. After two cycles, the pattern shows whether the problem is meeting discipline, source governance or a wider operating-model issue. Do not redesign the meeting to solve a responsibility gap that leadership has not addressed. Escalate the underlying gap with its evidence.
Escalation matrix for unresolved exceptions
Not every exception can be decided inside the monthly review. Use a simple escalation matrix so uncertainty does not become silent deferral.
| Condition | Immediate disposition | Required record | Return path |
|---|---|---|---|
| Decision authority is absent | Escalate to the authorized owner | Question, options, deadline and impact of delay | Return with a recorded decision or delegated authority |
| Evidence is materially incomplete | Narrow, test or defer | Missing evidence, owner, collection cost and latest useful date | Return when the named evidence exists |
| Mandatory specialist review is pending | Stop the affected commitment | Scope submitted, reviewer and due date | Return after the qualified conclusion is recorded |
| Capacity conflicts with approved work | Reprioritize explicitly | Scarce role, competing commitments and displacement options | Return with capacity reserved or scope changed |
| A critical dependency fails | Stabilize and redesign | Failed condition, consequence and safe interim state | Return with a new dependency path |
| Risk exceeds delegated tolerance | Escalate or stop | Exposure, limit, current controls and available alternatives | Return only under authorized acceptance |
The process owner keeps escalated items linked to the original cycle. The next MBR should not treat them as new topics or rewrite the date on which they became material. If the responsible executive accepts delay, the record states the operational, customer or financial consequence accepted. If the item is sent to another forum, name that forum, decision owner and expected return date. This makes escalation a controlled transfer of authority rather than a way to remove uncomfortable work from the agenda.
Decision-focused meeting script
Reserve the meeting for evidence conflicts, cross-functional choices and commitments. A ninety-minute agenda can work as follows: ten minutes to confirm scope and prior actions; fifteen minutes to review material changes in outcomes; forty-five minutes for no more than three decision items; ten minutes for emerging risks; and ten minutes to read back decisions, owners and escalation dates. Move information-only updates to the pre-read.
For each decision item, the chair uses the same spoken sequence. First: “What decision must be made, by whom and by what date?” Second: “Which observations are established, and which explanations remain hypotheses?” Third: “What alternatives are feasible within current authority and capacity?” Fourth: “What trade-off are we accepting?” Fifth: “What evidence will trigger continuation, adaptation, stopping or escalation?” The recorder captures the answer before the meeting moves on.
If discussion exceeds its time box, the chair does not force a choice. Select a disposition: decide now; authorize a bounded test; request named evidence; escalate authority; or defer with an explicit cost and latest responsible date. Record the reason. Repeated deferral of the same item is itself an exception and should be reviewed as an ownership, evidence or governance failure.
End by reading the official wording aloud. Contributors correct factual errors immediately; later changes require a new version. This brief discipline prevents different attendees from leaving with incompatible interpretations of what was decided.
The controlled monthly review procedure
This SOP treats the monthly business review as a governed management process, not a deck template. The difference matters. A template tells contributors where to put information; a procedure defines entry criteria, roles, timing, control points, outputs and the evidence required to close the cycle. Adopt it only after the general manager has assigned a process owner and agreed which decisions belong in the MBR rather than in daily operations, project governance, incident command, individual performance review or the quarterly strategy process.
Purpose, scope and decision rights
Purpose: integrate financial, customer, operational and people evidence so the accountable executive can decide what to continue, correct, stop, resource or escalate.
Scope: one defined business unit and one closed reporting period, with forward-looking risks that could materially change the next two periods. The meeting does not certify financial statements, determine regulated conclusions or replace specialist approval.
Entry criteria: the metric dictionary is current; the source cutoff has passed; prior actions have evidence; each proposed agenda item states the decision required; material data gaps are labelled; and the chair has confirmed decision authority. If a mandatory control or critical dataset is unavailable, the process owner records the exception and the chair chooses whether to defer, narrow the decision or invoke the authorized escalation route.
| Role | Accountable contribution | Cannot delegate silently |
|---|---|---|
| General manager / chair | Sets scope, resolves cross-functional trade-offs, makes or escalates decisions | Final interpretation of the integrated result |
| MBR process owner | Maintains calendar, version control, agenda, decision log and action register | Integrity of the official record |
| Finance owner | Reconciles actuals, forecast and value implications | Definition changes and material qualifications |
| Customer / commercial owner | Explains demand, retention, price, mix and customer-risk signals | Population and cohort definitions |
| Operations owner | Explains flow, quality, service, capacity and constraint evidence | Operational threshold rationale |
| People owner | Explains staffing, capability, workload and change-capacity evidence | Sensitive employee-level decisions, which stay outside the MBR |
| Risk, legal, compliance or technical specialist | Reviews matters within delegated professional authority | Required specialist conclusion or sign-off |
Calendar and hand-offs
At T-7 working days, the process owner publishes the reporting calendar, source cutoff and version identifier. At T-5, metric owners freeze data and submit a definition-change log. At T-4, functional owners write exception notes using the sequence signal → evidence → plausible causes → options → requested decision. At T-3, finance and the relevant operational owner reconcile inconsistencies. At T-2, the chair receives a pre-read containing no more than the agreed core measures, prior commitments and decision briefs. At T-1, attendees submit corrections or conflicts; new information after this point is labelled late evidence.
During the meeting, the chair opens with overdue commitments, then reviews only exceptions that cross an agreed threshold or create a decision. Each item ends in one of five dispositions: decide, authorize a bounded test, request evidence, escalate, or close with no action. The recorder reads back the wording, owner, due date and reopen trigger. At T+1, the process owner circulates the controlled record. At T+2, owners acknowledge assignments or raise a documented conflict. The next cycle starts by comparing expected and observed signals for earlier decisions.
Exception note: copy-ready form
MBR cycle / business unit:
Metric or event:
Definition, population, period and source:
Threshold or comparison:
Observed result:
Known fact(s):
Interpretation(s), labelled as such:
Cause hypotheses and disconfirming evidence:
Customer, financial, operational and people consequences:
Options, including continue / stop / test:
Decision requested and decision owner:
Required specialist review:
Latest responsible decision date:
An exception is not simply a red number. A measure can be within threshold while hiding a concentration risk, and a threshold breach can be normal variation. The owner must explain why the signal is decision-relevant. Conversely, a topic should not consume meeting time merely because a senior attendee is interested in it. Put information-only material in the appendix and invite questions before the meeting.
Decision and action records
Use two connected records. The decision log protects the rationale: question, alternatives, evidence, assumptions, constraints, selected option, authority, date, dissent and conditions for reopening. The action register protects execution: deliverable, owner, due date, dependency, required resource, status evidence and escalation date. Do not merge them into an ambiguous task list. A decision can be complete while its actions remain open; an action can finish without proving that the intended business result occurred.
Close an action only when the named evidence exists. “On track,” “discussed” and “almost done” are not closure states. If an owner or deadline changes, retain the prior entry and record who authorized the change. If a decision is reversed, link the new record to the old one so hindsight does not erase the original assumptions.
Control tests for the process owner
Before each meeting, sample three metrics and verify definition, source, period, population and owner. Sample three open actions and verify the referenced evidence. Compare agenda items with decision rights; remove items for which nobody present can decide. Check whether any proposed action depends on capacity already committed elsewhere. Confirm that confidential personnel details, customer identifiers and privileged material are held in approved systems and are not copied into a general meeting pack.
After the meeting, calculate three process indicators: the share of agenda items ending in a clear disposition; the share of actions closed with evidence by the agreed date; and the share of decisions reopened because a named assumption failed. The third is not automatically bad. A healthy review detects wrong assumptions early. A more concerning signal is repeated reopening without a changed evidence base or repeated deferral until the responsible decision date has passed.
Acceptance test and local adaptation
The SOP is ready for use when a new coordinator can run the cycle from the written procedure, every required role understands its contribution, the pre-read can be traced to controlled sources, and the output can be followed without oral reconstruction. Pilot it for two cycles. In the first retrospective, remove fields that never affect a decision and add only controls justified by observed failure. Keep the core distinction between evidence, interpretation, decision and action.
For a small business, one person may hold several roles, but the responsibilities should still be visible. For a regulated unit, add required approvals and record-retention rules. For a high-growth unit, shorten the cadence for volatile leading indicators without turning the monthly forum into a weekly operational meeting. In every case, the general manager remains accountable for the integrated result.
To strengthen the cross-functional judgement behind this operating rhythm, review the Advanced Executive Program in Management & Business Administration.