# RevOps Reporting — Standard Operating Procedure > Source: https://b2bprocess.com/revops-reporting > Last updated: 2026-07-08. Adapt owners, tools, and thresholds to your organization. ## 1. Purpose RevOps reporting is the process of defining, producing, and governing the reports that describe how the revenue engine is performing — the full funnel from lead to closed-won to renewal, pipeline health and coverage, forecast accuracy, conversion rates by stage and segment, and retention economics. Its output feeds three distinct audiences: operators (daily/weekly dashboards for running the business), leadership (monthly/quarterly business reviews), and the board (quarterly narrative with standardized SaaS metrics). ## 2. Scope & prerequisites Formalize RevOps reporting once more than one team consumes funnel data — in practice, as soon as sales and marketing argue about whose number is right. Prerequisites: a CRM that is the enforced system of record for pipeline, defined funnel stages with entry/exit criteria, and executive sponsorship for a single source of truth. ## 3. Roles & responsibilities | Role | Responsibility | | --- | --- | | Revenue Operations | Owns the metric dictionary, data quality, report production, and the reporting calendar. | | CRO / Revenue leadership | Sponsors single-source-of-truth discipline; consumes and acts on the leadership pack. | | Sales / Marketing / CS leaders | Enforce data hygiene in their teams; own the 'why' behind their sections of the numbers. | | Finance | Co-owns revenue definitions (ARR, bookings); reconciles CRM to the books monthly. | | Data / Analytics engineering | Owns warehouse pipelines, transformations, and BI-layer modeling where the stack extends beyond CRM. | ## 4. Procedure ### Step 1: Write the metric dictionary **Owner:** Revenue Operations Define every reported metric in one document: name, plain-language definition, exact formula, source system and field-level lineage, owner, and refresh cadence. Resolve the contested definitions (What counts as pipeline? When does an MQL exist? Is ARR contracted or live?) in a room with sales, marketing, CS, and finance — once — and record the rulings. - [ ] Inventory every metric currently reported anywhere - [ ] Adjudicate conflicting definitions with all stakeholders present - [ ] Publish the dictionary and treat changes like schema changes: versioned, announced ### Step 2: Define the funnel and stage gates **Owner:** Revenue Operations + functional leaders Codify the lifecycle: stages from lead through MQL, SQL, opportunity stages, closed-won, then post-sale states — each with objective entry/exit criteria and required fields. Conversion reporting is only meaningful when stage transitions mean the same thing across every rep and every quarter. ### Step 3: Fix the data layer **Owner:** Revenue Operations Reporting inherits every upstream sin: duplicates, empty required fields, stage-skipping, sandbagged close dates. Enforce hygiene at the source — validation rules, required fields at stage transitions, dedupe automation — and decide the architecture: CRM-native reporting as far as it goes, warehouse + BI when you need cross-system joins (product usage, billing, marketing). - [ ] Instrument stage-transition timestamps (the raw material of velocity metrics) - [ ] Automate hygiene checks: stale opportunities, missing amounts, past-due close dates - [ ] Establish the warehouse pipeline when CRM reporting hits its joins limit ### Step 4: Build the three-audience reporting stack **Owner:** Revenue Operations Operator dashboards: pipeline creation, stage movement, activity, SLA attainment — live, self-serve. Leadership pack: bookings vs. plan, coverage, conversion trends, retention — monthly, annotated. Board pack: ARR waterfall, NRR/GRR, CAC payback, magic number, forecast vs. actuals — quarterly, narrative-first. Fewer, better reports beat dashboard sprawl. - [ ] One canonical dashboard per audience; kill shadow copies - [ ] Annotate leadership reports with 'so what' commentary, not just charts - [ ] Standardize board metrics so trends are comparable quarter over quarter ### Step 5: Report pipeline health, not just pipeline size **Owner:** Revenue Operations Coverage ratio by segment and rep, pipeline age and stage-velocity, created-vs-needed pacing against future-quarter targets, slippage and push rates, and win rates by source and segment. A big pipeline number with rotting contents is the classic false comfort RevOps exists to expose. ### Step 6: Run the reporting cadence **Owner:** Revenue Operations + Revenue leadership Reports don't create accountability; meetings that use them do. Weekly pipeline council (operators), monthly revenue review (leadership, funnel end-to-end), quarterly business review (strategy, targets, capacity). Every meeting opens from the canonical report — anyone bringing a private spreadsheet gets sent back to the source of truth. - [ ] Fix the calendar and the report-freeze timestamp (e.g., Monday 6am snapshot) - [ ] Assign a narrator per section: RevOps presents the what, leaders own the why - [ ] Log decisions and follow-ups; review them at the next cadence ### Step 7: Instrument forecast accuracy **Owner:** Revenue Operations Snapshot the forecast (and the pipeline behind it) weekly, then score it against actuals: accuracy by stage, by rep, by category. Publishing forecast-accuracy history is the single strongest corrective for both sandbagging and happy ears. ### Step 8: Audit and evolve quarterly **Owner:** Revenue Operations Quarterly: retire unused reports (check view counts), re-validate metric definitions against reality, reconcile CRM-reported revenue with finance's books, and review whether the reporting answered the quarter's actual questions. Reporting is a product; treat usage decline as churn. - [ ] Reconcile bookings/ARR with finance to the dollar; investigate every gap - [ ] Retire or merge reports with no viewers - [ ] Collect leadership feedback: what decision lacked data this quarter? ## 5. Metrics to monitor | Metric | Definition | Formula | Target | | --- | --- | --- | --- | | Pipeline coverage ratio | Open qualified pipeline against the remaining quota for the period. | Open pipeline ÷ remaining target | commonly 3–4×, calibrated to your actual win rate | | Stage-to-stage conversion | Share of opportunities advancing from each stage to the next; the funnel's diagnostic X-ray. | Advanced from stage N ÷ entered stage N (cohorted) | trend-stable; investigate step changes | | Forecast accuracy | How close committed forecasts land to actuals, scored weekly. | |Actual − Forecast| ÷ Forecast | within ±10% by mid-quarter | | Net revenue retention (NRR) | Revenue from the existing customer base after expansion, contraction, and churn. | (Starting ARR + expansion − contraction − churn) ÷ starting ARR | > 100%; > 110% strong for mid-market+ | | Sales velocity | Revenue throughput per unit time — the composite of volume, value, win rate, and cycle length. | (# opps × avg deal × win rate) ÷ sales cycle days | trending up; use for scenario math | | Data hygiene score | Composite of required-field completeness, stale-opportunity share, and past-due close dates — the reliability rating of everything above. | Weighted composite per RevOps definition | > 90%, published by team | ## 6. Known failure modes | Failure | Symptom | Corrective action | | --- | --- | --- | | Competing sources of truth | Sales, marketing, and finance bring different numbers for the same metric; meetings spend 20 minutes reconciling. | Metric dictionary with adjudicated definitions; one canonical report per audience; executive enforcement. | | Dashboard sprawl | Hundreds of reports, most unviewed; every leader has a private variant; nobody trusts any of them. | Quarterly report audit with usage data; kill or merge ruthlessly; one dashboard per audience per cadence. | | Garbage in, confident out | Beautiful dashboards atop stale opportunities, missing amounts, and skipped stages; decisions made on fiction. | Hygiene enforced at entry (validation, required fields) plus a published data-quality score that makes rot visible. | | Reporting without cadence | Dashboards exist but no meeting opens with them; numbers are consulted only when convenient. | Fixed weekly/monthly/quarterly rhythm where the canonical report is the agenda. | | Snapshot amnesia | Nobody can say what pipeline looked like six weeks ago; slippage and sandbagging are invisible; forecast misses are unexplainable. | Automated weekly snapshots of pipeline and forecast; report movement, not just position. | | Metrics without decisions | The pack reports 40 KPIs and answers no question; leadership skims and moves on. | Anchor each report section to the decision it informs; annotate with commentary; cut vanity metrics. | | CRM–finance divergence | Board deck ARR disagrees with the books; credibility damage outlasts the correction. | Monthly reconciliation with finance to the dollar as a standing RevOps ritual. | --- This SOP is maintained as part of the B2B process encyclopedia at https://b2bprocess.com. Check the source page for the latest revision.