TL;DR
Operating review is the recurring meeting where leadership reviews operating performance against plan — typically weekly or monthly, with attendees from sales, finance, product, marketing, and CS. Goal: spot variances early, decide on interventions, align cross-functional execution. Best-in-class operating reviews follow a fixed agenda, use single source-of-truth data, and produce documented decisions — distinct from open-ended status updates. WBR is the most common variant.
What is an operating review?
An operating review is the recurring cross-functional meeting where leadership reviews the operating performance of the business against plan. Typical attendees: CEO/COO, CRO, CFO, VP Product, VP Marketing, VP CS, and the leader of any function with material variance to discuss. Cadence: weekly (most common for sub-$200M ARR), bi-weekly, or monthly.
It is the operating mechanism that scales as the company grows. At sub-$5M ARR, decision-making can be informal (founder + leadership Slack threads). Above that, the operating review is the formal mechanism for spotting variances early, deciding on interventions, and aligning execution across teams.
Weekly business review (WBR) is the canonical Amazon-popularized variant of the operating review.
Why operating reviews matter
Companies without disciplined operating reviews suffer from variance blindness: problems are discovered weeks after they start because no one is looking at the data with structured leadership attention. By the time a CFO flags margin erosion in a monthly board prep, it has been compounding for 4-6 weeks. A weekly operating review surfaces the same erosion in days, with cross-functional leadership in the room to decide on intervention.
For RevOps and FP&A, operating reviews are the primary forum for delivering insights. A perfect dashboard that's never reviewed in a cross-functional setting is worthless. The operating review is where data meets decision-making at the leadership level.
Operating review structure
- Fixed agenda. Same structure every meeting — variance review, pipeline review, retention review, action items. Variation kills consistency.
- Single source-of-truth data. Everyone reads the same numbers. Pre-read distributed 24 hours in advance to avoid "what does that mean?" tangents in the meeting.
- Variance-first. The agenda leads with what's off plan, not what's on plan. On-plan items get a one-line callout.
- Documented decisions. Every intervention has an owner, a deadline, and a follow-up at the next review.
- Time-boxed. 60-90 minutes. Anything that needs more is scheduled separately, not allowed to consume the meeting.
- Forward-looking. 70%+ of time on the current and next 30-60 days, not on past quarter retrospective.
Operating review vs. status meeting
| Trait | Operating review | Status meeting |
|---|---|---|
| Agenda | Fixed variance-first agenda | Open-ended updates |
| Data | Single source-of-truth pre-read | Team-by-team narrative |
| Outputs | Documented decisions | Awareness of activity |
| Time horizon | Forward-looking | Backward-looking |
| Owner accountability | Tracked across meetings | Implicit |
| Outcome | Faster decision velocity | Updated information |
Related concepts
Operating review is the umbrella; WBR is the canonical weekly variant. Connects to operating cadence, operating intelligence, decision velocity, metric tree, and single source of truth.
At a glance
- Category
- Category Creation
- Related
- 5 terms
Frequently asked questions
What is an operating review?
An operating review is the recurring cross-functional meeting where leadership reviews operating performance against plan — typically weekly or monthly. Goal: spot variances early, decide on interventions, align execution. WBR is the most common variant.
How often should you run an operating review?
Weekly is the most common cadence for sub-$200M ARR companies. Bi-weekly works for slower-cadence businesses (long sales cycles, predictable seasonality). Monthly is too slow — variance compounds for 3-4 weeks before it's surfaced. Daily ops standups complement, not replace, the weekly operating review.
Who attends an operating review?
CEO/COO, CRO, CFO, VP Product, VP Marketing, VP CS, and the leader of any function with material variance to discuss. Some companies include the head of RevOps as the data steward. Junior team members can listen but typically don't attend — keeping the meeting tight to decision-makers.
What's the difference between an operating review and a status meeting?
An operating review has a fixed variance-first agenda, single source-of-truth data, documented decisions, and forward-looking emphasis. A status meeting is open-ended team-by-team updates that build awareness but don't drive decisions. Operating reviews accelerate decision velocity; status meetings update information.
Sources
- Colin Bryar, Bill Carr. Working Backwards: Insights, Stories, and Secrets from Inside Amazon, 2021.
- Andy Grove. High Output Management, Vintage, 1983 (revised 2015).
- Pavilion. 2025 Operating Cadence Report, 2025. joinpavilion.com
Fairview's operating intelligence layer is built to feed operating reviews with single-source-of-truth data and variance-first surfacing.
Definitions reviewed by Siddharth Gangal, Founder, Fairview.
See it in Fairview
Track Operating Review automatically.
14-day free trial. No credit card. First data source connected in 5 minutes.