Five Questions Your CRO Will Ask About the Forecast (And How to Answer Them)

If you've run a forecast review with a CRO in the room, you know the questions that always come up. They're not random. Every CRO has a set of concerns that are consistent across companies and quarters, because the structural problems with sales forecasting are consistent. The questions are the same because the failure modes are the same.

What varies is whether RevOps can answer those questions with signal-backed data or with a shrug followed by "I'll check with the rep." The teams that answer with data change the dynamic of the meeting entirely. They shift from defending a number to diagnosing a pipeline. That shift is what makes the difference between a CRO who trusts the forecast and one who treats it as a starting point for their own mental adjustment.

Here are the five questions, what the CRO is actually asking, and how to build the answer capability before you need it.

Question 1: "How much of this commit can we actually count on?"

What they're really asking: the CRO has learned through experience that commit numbers are not commitments. They reflect a mix of genuinely high-confidence deals, deals the rep is trying to protect by categorizing them conservatively, and deals the rep is genuinely uncertain about but feels pressure to commit. The CRO wants to know the distribution.

The signal-based answer: for each deal in commit above your ACV floor, you should be able to report engagement health independently of the rep's category submission. If a deal is in commit and the economic buyer engaged in the past 10 days, response latency is normal, and the rep has a specific next step with a named owner on the buyer side, that deal's commit classification is supported by signal. If none of those conditions hold, the commit classification is rep-submitted confidence without signal backing.

A useful metric: what percentage of your commit deals have signal-backed classifications versus CRM-only classifications? If it's 60% signal-backed, your effective commit number is probably 0.6x the submitted number plus some portion of the unverified 40%. That's a more honest answer than reading the commit total off a spreadsheet.

Question 2: "What's at risk of slipping out of this quarter?"

What they're really asking: the CRO knows that slip is the primary mechanism by which forecast misses happen. They want to know which deals are at highest risk of becoming next quarter's problem, so they can either intervene or adjust their mental model of the quarter.

The signal-based answer: slip risk is highest for deals that show at least two of the following: close date has been pushed at least once in the past 45 days, buyer-side engagement has declined week-over-week for the past two weeks, stage duration is above your P75 for the deal size and segment, and the champion's last substantive interaction was more than 10 days ago.

Deals that show two or more of these markers are your at-risk cohort. They may not all slip. But they're the ones worth flagging by name in the forecast review, with a specific account of what would need to happen to keep them in the quarter. If you can't describe what would need to happen, the deal probably shouldn't be in your committed number.

Question 3: "What happened to the deals we had in best-case last quarter?"

What they're really asking: this question is about forecast calibration over time. The CRO wants to understand whether best-case is functioning as a meaningful forecast category, or whether it's a catchall where deals go when reps aren't sure what to do with them. If best-case deals from last quarter are now either closed or moved to next quarter's pipeline, that's informative. If they mostly disappeared, something is wrong with how best-case is being classified.

The signal-based answer: maintain a simple quarterly cohort view of best-case deals. For each quarter's cohort of best-case deals at quarter start, track what happened: closed won this quarter, closed won next quarter, moved to pipeline, or lost/inactive. This gives you a best-case conversion rate and a sense of how much best-case volume from any given quarter actually converts.

If your best-case conversion rate over the past three quarters has been 25% to 35%, your current quarter's best-case number should be weighted accordingly. If the CRO asks what happened to last quarter's best-case, you can answer with actual outcome data rather than deal-by-deal recall.

Question 4: "Which reps are I worried about?"

What they're really asking: the CRO is thinking about two things simultaneously. One is whether specific reps are likely to miss quota this quarter in ways that affect the team number. The other is whether specific reps have forecast submission patterns that inflate or deflate the aggregate number in systematic ways. These are related but different concerns.

The signal-based answer: per-rep forecast accuracy over the past four to six quarters is the right starting point. A rep whose submitted forecasts have been within 10% of actuals consistently is a reliable input to your aggregate number. A rep whose submitted forecasts have been off by 25-35% in either direction consistently is a systematic distortion in your model. You should be applying an adjustment factor to their current submission based on their historical accuracy, not treating their submission as equivalent to a more calibrated rep's submission.

On the quota attainment question: review the pipeline health signals for each rep on the team. Reps whose current-quarter pipeline shows declining engagement across their book are at elevated attainment risk. This isn't about blaming or flagging people; it's about giving the CRO an honest picture of where the team stands with time to do something about it.

Question 5: "Do we have enough pipeline for next quarter?"

What they're really asking: the CRO is thinking ahead. A quarter where you close the number but leave the pipeline thin for Q+1 is not a win; it's a setup for the next quarter's miss. They want to know whether the pipeline creation activity is keeping pace with consumption.

The signal-based answer: pipeline coverage is a topic we have written about separately, and the short version is that raw coverage ratio is a weak indicator. What matters is signal-weighted coverage: how much of your next-quarter pipeline has active engagement signals that suggest it's real and moving? A coverage ratio built on stale or single-threaded deals is nominal, not functional.

The answer you want to be able to give is: "Our next-quarter pipeline is $X, of which $Y has been actively engaged in the past 21 days and is multi-threaded at the decision-maker level. That $Y figure represents Z months of coverage at current close rates, which puts us at [comfortable / adequate / thin] for Q+1."

Giving that answer requires having the signal layer running on your next-quarter pipeline now, not after the current quarter closes. By the time the current quarter is decided, it's too late to build real pipeline health for the next one. The signal view on Q+1 should be part of every current-quarter forecast review.

The through-line across all five questions is the same: CROs ask these questions because they don't have visibility, and they don't have visibility because their RevOps team is presenting submitted rep data without signal context. Building the signal layer and surfacing it in the forecast review is not a technology problem. It's a process and prioritization decision about what RevOps is responsible for knowing before walking into that room.