TL;DR
A COO dashboard should carry exactly 12 metrics across four domains — no more, no fewer. The domains are:
- Revenue Health: MRR/ARR, net revenue retention, pipeline coverage ratio, customer acquisition cost
- Cost and Margin: gross margin, operating expense ratio, burn rate or free cash flow, COGS variance
- Operational Efficiency: cycle time or on-time delivery, customer satisfaction score, support resolution time, process defect rate
- People and Capacity: headcount versus plan, revenue per employee, voluntary attrition rate, open role age
Each metric needs a defined threshold. Without one, a dashboard is just a scoreboard — not a decision tool.
The COO does not need more data. The COO needs the right 12 numbers, updated every week, with clear thresholds that say: this is normal, this is a warning, and this requires action today.
In practice, most COO dashboards look nothing like that. A Gartner analysis of executive dashboard usage found that the majority of leadership dashboards contain more than 25 metrics — a number so high that the signal disappears into the noise. Operators spend their weekly reviews asking "which of these numbers actually matters this week?" instead of acting on the answer.
This guide solves that problem. It presents a definitive 12-metric COO dashboard organized by domain, explains how to structure it differently for a weekly operating review versus a monthly board meeting, draws the precise boundary between a COO dashboard and a CEO dashboard, and catalogs the four most common mistakes that cause dashboards to fail in practice.
If you are building or redesigning your operating review cadence, see the companion piece on the Operating Intelligence Framework — the four-pillar system that determines how dashboards connect to decisions and actions across the organization.
COO Dashboard. A real-time operational view — typically reviewed weekly — that aggregates 12 to 20 metrics across revenue health, cost structure, process efficiency, and people capacity. Its purpose is not to report on the past but to surface anomalies against plan so the operating team knows where to intervene this week.
Why 12 Metrics — Not 8, Not 25
The number 12 is not arbitrary. It is derived from the cognitive and operational constraints of a weekly leadership review.
Research published by Harvard Business Review on data discipline consistently finds that executive teams make higher-quality decisions when operating with 5 to 8 KPIs per functional domain. With four domains — revenue, cost, efficiency, and people — that produces a range of 20 to 32 metrics, which is already above the cognitive limit for weekly review. The practical answer is to pick the three highest-signal metrics in each domain: the ones that, if they move adversely, predict problems before those problems become expensive.
The result is a 12-metric core dashboard with additional secondary metrics available on drill-down for each domain. The 12 metrics are the weekly agenda. The drill-down is what the operating team investigates when one of those 12 signals a problem.
A dashboard that requires a 90-minute briefing to interpret is not a dashboard. It is a report that no one has read yet.
| Domain | Core Metrics (Weekly) | Update Frequency | Owner |
|---|---|---|---|
| Revenue Health | MRR/ARR, NRR, Pipeline Coverage, CAC | Weekly | RevOps / CRO |
| Cost and Margin | Gross Margin, OpEx Ratio, Burn / FCF, COGS Variance | Weekly | CFO / Finance |
| Operational Efficiency | Cycle Time / OTD, CSAT / NPS, Resolution Time, Defect Rate | Weekly | VP Operations |
| People and Capacity | Headcount vs. Plan, Revenue per Employee, Attrition, Open Role Age | Weekly | VP People / COO |
Domain 1 — Revenue Health
Revenue health metrics answer the question every COO asks first: is the top line on track, and is the customer base stable? These four metrics give that answer with precision. For a deeper breakdown of operating metrics in context, the Operating Intelligence Metrics framework covers how to govern definitions and ownership at the organizational level.
Metric 01
Monthly Recurring Revenue (MRR) / Annual Recurring Revenue (ARR)
What it measures: The predictable revenue base of the business. MRR is the weekly operating view. ARR is the board-level view.
Formula: MRR = Sum of all active subscription revenue in the period
Why COOs track it: MRR is the single number that captures whether the business is growing, contracting, or flat. It separates signal from noise in a way that total revenue cannot — because total revenue includes one-time items that obscure the underlying trend.
Alert threshold: Any week-over-week MRR decline of more than 1% warrants immediate review. Month-over-month growth below the plan rate by more than 5 percentage points triggers a formal root-cause exercise.
Metric 02
Net Revenue Retention (NRR)
What it measures: The percentage of recurring revenue retained from existing customers after accounting for expansions, contractions, and churn.
Formula: NRR = (Beginning MRR + Expansion MRR − Contraction MRR − Churned MRR) ÷ Beginning MRR × 100
Why COOs track it: NRR above 100% means the business grows revenue from its existing customer base without acquiring a single new customer. It is the most powerful indicator of product-market fit and operational delivery quality. A declining NRR signals a delivery or support problem before it shows up as churn.
Alert threshold: NRR below 100% for two consecutive months requires immediate cross-functional review. Best-in-class SaaS benchmarks from the SaaS Capital 2025 survey place elite NRR above 115%.
Metric 03
Pipeline Coverage Ratio
What it measures: The ratio of qualified pipeline to the revenue target for the next quarter.
Formula: Pipeline Coverage = Total Qualified Pipeline ÷ Revenue Target
Why COOs track it: Pipeline coverage is the leading indicator the COO controls through resource allocation. If coverage falls below the threshold, the COO can redirect sales capacity, adjust quota distribution, or trigger a pipeline generation campaign — but only if the signal arrives early enough. Waiting for end-of-quarter results is waiting for the outcome of a decision that should have been made eight weeks earlier.
Alert threshold: Coverage below 3x for a quarter that closes in 12 weeks or fewer requires an immediate pipeline audit. Below 2x is a revenue risk that belongs on the board agenda.
Metric 04
Customer Acquisition Cost (CAC)
What it measures: The total cost to acquire one new customer, including sales, marketing, and onboarding costs.
Formula: CAC = (Total Sales + Marketing + Onboarding Costs) ÷ New Customers Acquired
Why COOs track it: CAC rising faster than customer lifetime value (LTV) is the earliest warning of a unit economics problem. A COO who watches CAC weekly can identify whether cost increases are structural — a go-to-market efficiency decline — or temporary, such as a one-time campaign spend.
Alert threshold: CAC increasing more than 15% quarter-over-quarter without a corresponding increase in average contract value requires go-to-market review.
Domain 2 — Cost and Margin
Cost and margin metrics answer the question the CEO will always ask at the board meeting: are we getting more efficient as we scale? These four metrics give the COO the ammunition to answer that question precisely — or to identify where efficiency is eroding before the board asks.
Metric 05
Gross Margin
What it measures: The percentage of revenue remaining after the direct cost of delivering the product or service.
Formula: Gross Margin = (Revenue − COGS) ÷ Revenue × 100
Why COOs track it: Gross margin is the boundary between a scalable business and one that spends more to serve each new customer. For SaaS businesses, a gross margin below 65% signals a structural cost problem in the delivery stack. A McKinsey analysis of SaaS performance found that top-quartile SaaS companies maintain gross margins above 75%, which gives them the operating leverage to invest in growth without burning cash.
Alert threshold: Any gross margin decline of more than 2 percentage points in a single quarter warrants a COGS decomposition review.
Metric 06
Operating Expense Ratio (OpEx Ratio)
What it measures: Operating expenses as a percentage of revenue — the signal for whether the cost structure is scaling in proportion to the business.
Formula: OpEx Ratio = Total Operating Expenses ÷ Revenue × 100
Why COOs track it: An OpEx ratio that declines over time demonstrates operating leverage — the business is getting more efficient as it scales. An OpEx ratio that holds flat or rises signals that costs are growing at least as fast as revenue, which will compress operating margin regardless of top-line growth rate.
Alert threshold: OpEx ratio rising for three consecutive months without a corresponding strategic investment rationale (such as a deliberate hiring surge ahead of a new product launch) triggers a departmental cost review.
Metric 07
Burn Rate / Free Cash Flow (FCF)
What it measures: For pre-profitability companies: net cash consumed per month. For profitable companies: cash generated from operations after capital expenditures.
Formula: Burn Rate = Cash at Start of Period − Cash at End of Period
Why COOs track it: Burn rate determines runway. A COO who knows the current burn rate and current cash balance can calculate runway in real time and make resource allocation decisions accordingly. A rising burn rate without a corresponding increase in growth rate is the earliest signal that the business is consuming capital without generating proportional return.
Alert threshold: Runway dropping below 12 months at the current burn rate requires immediate cost structure review and fundraising preparation. Below 9 months is a board-level conversation.
Metric 08
COGS Variance
What it measures: The difference between budgeted and actual cost of goods sold, expressed as a percentage of budgeted COGS.
Formula: COGS Variance = (Actual COGS − Budgeted COGS) ÷ Budgeted COGS × 100
Why COOs track it: COGS variance is where delivery inefficiency first appears in the financial data. A consistent positive variance — actual costs exceeding budget — signals that the cost model for delivering the product is wrong, or that delivery processes are less efficient than planned. Identifying this weekly means corrective action can happen in days, not at the quarterly close.
Alert threshold: COGS variance above +8% for any two-week period triggers a delivery cost audit.
Domain 3 — Operational Efficiency
Operational efficiency metrics answer the question that distinguishes a COO from every other C-suite executive: are the processes that deliver value to customers running at the designed spec? These metrics are where the COO has the most direct influence — and where the most correctable margin leaks typically hide.
Metric 09
Cycle Time / On-Time Delivery Rate (OTD)
What it measures: For product businesses: the percentage of orders or deliverables completed by the committed date. For service businesses: the average time from request to completion for a core workflow.
Formula: OTD = On-Time Deliveries ÷ Total Deliveries × 100
Why COOs track it: Delivery performance is the most direct measure of whether operations are executing to plan. An OTD rate below 95% correlates strongly with customer churn in the subsequent quarter, according to industry benchmarks from supply chain research firm APQC. The root causes — capacity constraints, process breakdowns, or demand misalignment — are visible in the operating data before they manifest in the revenue data.
Alert threshold: OTD below 92% for any rolling 4-week period triggers a capacity and process review.
Metric 10
Customer Satisfaction Score (CSAT) / Net Promoter Score (NPS)
What it measures: The proportion of customers who rate their experience positively (CSAT) or the net percentage who would recommend the product to a peer (NPS).
Formula: NPS = % Promoters − % Detractors
Why COOs track it: CSAT and NPS are the voice of the customer translated into a single number. For a COO, a declining NPS is a leading indicator of churn — and churn shows up in NRR 60 to 90 days after the satisfaction signal appears. Tracking NPS weekly allows the COO to intervene at the point of dissatisfaction rather than at the point of cancellation.
Alert threshold: NPS declining more than 5 points in a rolling 30-day window triggers a customer success review and a root-cause analysis of recent negative responses.
Metric 11
Support Ticket Resolution Time
What it measures: The average time from ticket creation to resolution, segmented by ticket priority tier.
Formula: Avg Resolution Time = Total Resolution Hours ÷ Total Resolved Tickets
Why COOs track it: Resolution time is both a customer experience metric and an operational capacity metric. Rising resolution times signal one of three things: ticket volume has exceeded team capacity, process complexity has increased, or there is a product quality issue generating repeat support load. Each root cause has a different operational fix — and the COO needs to identify which one quickly.
Alert threshold: P1 (critical) ticket resolution time exceeding SLA by more than 20% for any two-week period requires immediate escalation review. P2 time trending upward for three consecutive weeks warrants a capacity assessment.
Metric 12
Process Defect Rate
What it measures: The percentage of outputs from a core process that fail to meet the defined quality standard on first pass.
Formula: Defect Rate = Non-Conforming Outputs ÷ Total Outputs × 100
Why COOs track it: Every defect costs money twice — once to deliver the non-conforming output and again to correct it. A rising defect rate in any core process predicts cost overruns before they appear in the financial data. For software companies, this metric maps to error rates, failed deployments, or data quality issues. For service businesses, it maps to rework rates or escalation rates.
Alert threshold: Defect rate above 3% for any core process for two consecutive weeks triggers a process audit.
Domain 4 — People and Capacity
People and capacity metrics answer the question that determines whether every other metric is achievable: do we have the right number of the right people, deployed in the right roles? For a deeper analysis of what the COO role requires at each stage of a startup's growth, see What Does a COO Do at a Startup.
People 01
Headcount vs. Plan
What it measures: The delta between actual headcount and the headcount plan approved at the start of the quarter, by department.
Formula: Headcount Variance = Actual HC − Planned HC (per department)
Why COOs track it: Headcount underage in a revenue-generating function is a direct constraint on capacity. Headcount overage in a support function without a corresponding increase in supported activity is a cost efficiency problem. Tracking at the department level — not just in aggregate — surfaces misallocations that total headcount numbers hide.
Alert threshold: Any revenue-generating department more than 15% below planned headcount for more than four weeks triggers a recruiting escalation.
People 02
Revenue per Employee
What it measures: Total annualized revenue divided by total full-time equivalent headcount.
Formula: Revenue per Employee = ARR ÷ Total FTE Headcount
Why COOs track it: Revenue per employee is the single most direct measure of organizational productivity. It tells the COO whether the business is becoming more or less efficient as it adds headcount. For SaaS companies at Series A, a benchmark of $150,000 to $200,000 ARR per employee is typical. Top-quartile companies at scale reach $300,000 or above. For more on how investors read this metric, see SaaS Metrics Series A Investors Actually Care About.
Alert threshold: Revenue per employee declining for two consecutive quarters without a deliberate investment rationale warrants a workforce productivity review.
People 03
Voluntary Attrition Rate
What it measures: The percentage of employees who voluntarily left the organization in the trailing 12 months, expressed as an annualized rate.
Formula: Voluntary Attrition = Voluntary Departures ÷ Average Headcount × 100
Why COOs track it: Voluntary attrition is the leading indicator of organizational health. High-performing companies, according to McKinsey's Great Attrition research, maintain voluntary attrition below 10% annually. Rates above 15% signal one of three root causes: compensation misalignment, management quality issues, or role clarity problems — each requiring a different operational response.
Alert threshold: Voluntary attrition exceeding 15% annualized, or a single department exceeding 20% in any quarter, triggers a retention root-cause analysis.
People 04
Open Role Age (Days to Fill)
What it measures: The average number of days a role has been open from job requisition approval to accepted offer, segmented by department and seniority.
Formula: Avg Open Role Age = Sum of Days Open per Role ÷ Total Open Roles
Why COOs track it: Open role age is the operational signal of recruiting pipeline health. A role open for more than 60 days in a revenue-generating function is consuming opportunity cost every day it remains unfilled. Tracking this at the department level identifies where the recruiting process is stalling — sourcing, assessment, or offer stage — and allows the COO to intervene with precision rather than pressure.
Alert threshold: Any revenue-generating role exceeding 60 days open triggers a recruiting process review and potential external sourcing escalation.
How to Structure the Dashboard for Weekly Review vs. Monthly Board Prep
A COO dashboard is not one artifact — it is two views of the same data, structured for different decisions with different audiences and different time horizons.
The Weekly Operating Review
The weekly review is a decision meeting, not a reporting meeting. The dashboard serves as the agenda. The structure is as follows:
| Time Block | Agenda Item | Dashboard View | Output |
|---|---|---|---|
| 0–5 min | Metrics review — current week vs. plan | All 12 metrics, RAG status | Flag any metric in red or amber |
| 5–25 min | Deep dive on flagged metrics only | Domain drill-down for flagged items | Root cause identified or investigation assigned |
| 25–40 min | Action items from prior week | Action tracker | Resolved, escalated, or re-assigned |
| 40–50 min | New actions from this week's flags | — | Owner, deadline, and success metric assigned |
The critical design principle: only metrics that are outside threshold get time on the agenda. Green metrics are acknowledged and moved past in 30 seconds. The entire meeting runs on exceptions, not on completeness.
Weekly Review Done Right
- Dashboard reviewed in under 5 minutes because everyone saw it before the meeting
- Only metrics in red or amber generate discussion
- Every flagged metric produces an action with an owner and a 7-day deadline
- Prior-week actions are resolved before new ones are created
- Meeting ends with a written action log, not verbal agreements
The Monthly Board Preparation View
The board version of the COO dashboard is a distillation — not an export. Board members need context, not completeness. The monthly board view should answer four questions:
- Is revenue on track against the annual plan? MRR trajectory with 12-month trend line and plan overlay.
- Is the business becoming more efficient? Gross margin trend, OpEx ratio trend, and revenue per employee trend — trailing four quarters.
- Are operational risks contained? Any metric that was in red for more than two consecutive weeks during the month, with the root cause summary and corrective action taken.
- Is the team scaling appropriately? Headcount vs. plan by department, voluntary attrition rate, and open critical roles with age.
Board Prep Mistakes to Avoid
- Presenting the same 12-metric weekly dashboard without narrative — board members need interpretation, not raw data
- Omitting metrics that show unfavorable trends — boards lose confidence faster when they discover omissions than when they see problems with a plan
- Presenting metrics without trend lines — a single data point is not information
- Using different metric definitions than prior months — definition drift destroys comparability and trust
COO Dashboard vs. CEO Dashboard: The Precise Difference
The COO and CEO dashboards share many of the same data sources but serve fundamentally different decisions. Conflating them produces a dashboard that serves neither role well.
| Dimension | COO Dashboard | CEO Dashboard |
|---|---|---|
| Primary question | Are our processes executing to plan this week? | Is the company on track against strategic objectives? |
| Time horizon | Weekly (with rolling 13-week trend) | Monthly (with rolling 12-month trend) |
| Revenue view | MRR, NRR, pipeline coverage, CAC — with weekly delta | ARR, revenue growth rate, net new ARR — with quarterly delta |
| Cost view | COGS variance, OpEx ratio, burn rate, gross margin | EBITDA or operating income, cash position, Rule of 40 score |
| Operational view | Cycle time, defect rate, resolution time, OTD | Summary NPS trend, major operational risks only |
| People view | Headcount vs. plan by department, open role age, attrition | Total headcount growth rate, senior leadership changes only |
| Update cadence | Weekly, reviewed in operating review meeting | Monthly, reviewed in leadership team meeting |
| Audience | COO, department leads, RevOps | CEO, board, investors |
The clearest way to think about the difference: the CEO dashboard measures whether the company is winning. The COO dashboard measures whether the company is executing in a way that makes winning possible. They are complementary, not redundant. A company that has a CEO dashboard but no COO dashboard has a strategy view with no execution visibility — which is how companies miss targets they understood intellectually for months before they missed them.
For the deeper architecture that connects both views to a structured decision cadence, the Operating Intelligence Framework covers how to build the system that makes both dashboards function as designed.
Sample COO Dashboard Layout
The following layout represents how the 12 core metrics appear in a well-designed weekly operating dashboard. Each tile shows the current value, the week-over-week delta, and a RAG (Red-Amber-Green) status relative to the defined threshold.
COO Weekly Dashboard — Week of 2026-05-29
MRR
$487K
+2.1% WoW
NRR (TTM)
108%
+0.4 pts
Pipeline Coverage
3.4x
+0.2x WoW
CAC
$4,210
+8% QoQ
Gross Margin
71%
−0.5 pts
OpEx Ratio
84%
+3 pts MoM
Burn Rate
$218K
14 mo runway
COGS Variance
+4.1%
vs budget
OTD Rate
96.2%
+0.3 pts
NPS (30-day)
54
−6 pts MoM
P1 Resolution
3.2 hrs
vs 4hr SLA
Defect Rate
1.8%
−0.2 pts
HC vs Plan
−3
Sales team
Rev / Employee
$198K
ARR / FTE
Voluntary Attrition
9.4%
TTM annualized
Avg Open Role Age
44 days
+8 days WoW
In this example, four metrics warrant immediate attention in the weekly review: CAC rising 8% QoQ, OpEx Ratio increasing 3 points month-over-month, NPS declining 6 points, and headcount in the sales team running 3 below plan. Each of those four items gets dedicated time on the weekly operating agenda. The other eight metrics are green — they are acknowledged and not discussed further.
Four Common COO Dashboard Mistakes
Mistake 1: Too Many Metrics
The most frequent failure mode is a dashboard that grows incrementally as each department adds its "must-track" metrics, eventually reaching 40 or 50 items. At that scale, every weekly review becomes a tour of data rather than a sequence of decisions. The fix is a formal metric governance process that requires every metric on the dashboard to have a clear owner and a defined alert threshold — if a metric has neither, it does not belong on the primary view.
Mistake 2: No Thresholds
A metric without a threshold is decoration. It tells you a number exists but does not tell you whether that number is good, bad, or requires action. Every metric on the COO dashboard must have three defined states: green (on plan, no action required), amber (deviation from plan, monitor and investigate), and red (breach of threshold, action required this week). Without this structure, every meeting turns into a debate about whether a number is concerning — a debate that should have been resolved in advance when the threshold was set.
Mistake 3: No Trend Lines
A single data point is not information. An NPS score of 54 means nothing in isolation. An NPS score of 54 that has declined from 67 over eight weeks is a signal that requires action. Every primary metric on the COO dashboard should be displayed with at minimum a 13-week rolling trend line. The trend line is what separates a metric from intelligence.
Mistake 4: Metric Definitions That Change
Definition drift is the silent killer of dashboard trust. If MRR is calculated differently this month than last month because someone updated the billing export logic, the trend line becomes meaningless — and the leadership team stops trusting the dashboard. Metric definitions must be version-controlled, written down in a single governance document, and subject to a formal change process. Any change to a metric definition requires a re-statement of historical data and a formal communication to all dashboard users.
The Four Dashboard Anti-Patterns
- Metric sprawl: More than 20 metrics on the primary weekly view
- Threshold-free reporting: No defined green/amber/red states for any metric
- Point-in-time only: No trend lines; decisions made from a single data point
- Definition drift: Metric calculations change without governance or re-statement
Key Takeaways
- A COO dashboard should carry exactly 12 core metrics organized across four domains: revenue health, cost and margin, operational efficiency, and people and capacity.
- Every metric requires a defined threshold with green, amber, and red states. Without thresholds, a dashboard cannot drive a decision meeting.
- The weekly operating review is structured around exceptions: only metrics outside threshold get time on the agenda.
- The monthly board view is a distillation of the weekly dashboard — four strategic questions with trend lines and variance narratives, not a data dump.
- A COO dashboard measures execution. A CEO dashboard measures strategic progress. They are complementary views that require different structures and update cadences.
- Trend lines, not point-in-time values, are what make metrics into intelligence. Every primary metric needs a rolling 13-week trend.
How Fairview Powers the COO Dashboard
Fairview is an Operating Intelligence Platform built for COOs, operators, and founders who manage revenue operations across fragmented data systems. The platform connects to CRM, billing, finance, and support systems to produce a single, governed view of the 12 metrics that belong on every COO dashboard — updated continuously, with threshold alerts that surface exceptions before they become problems.
Unlike generic BI tools that require an analyst to interpret outputs, Fairview is designed to answer the three questions a COO asks every Monday: what is making money, what is leaking margin, and what needs attention this week. The weekly operating review view mirrors the structure in this guide — four domain panels, RAG status for each metric, trend lines, and a built-in action tracker that closes the loop between insight and outcome.
For teams moving from spreadsheet-based operating reviews to a structured dashboard, Fairview includes metric definition governance, threshold configuration, and a decision cadence template that connects daily data to weekly reviews to monthly board packages — without requiring an in-house data engineering team to maintain it.