Skip to content
GuideForecastingIntermediate

Running the weekly forecast call in RevTech

Will we hit the number? How to run the weekly call from Gap to Target through Forecast, Pipeline Coverage and Renewals, and end every session with the gap owned.

RRRevTech RevOpsRevenue operations team 6 minUpdated

Product walkthrough

See it in RevTech

Follow the operating rhythm from the forecast into the pipeline report, with the evidence behind the number kept in context.

Follow the operating rhythm from the forecast into the pipeline report, with the evidence behind the number kept in context.
Part 1 of 8

One question, a family of reports

Forecast exists to answer a single question every week: will we hit the number? The Forecast category in Reporting holds five reports that answer it between them, each on its own page. Gap to Target is the frame: how far the quarter is from target and what is open to close it. Forecast is the company read: where you land if nothing changes, and who is on pace. Pipeline Coverage is the deals behind the commit. Renewals is the half of the number that Customer Success carries. Weekly Change Log is what moved since last week.

Open them in that order. The instinct on a bad week is to start in Pipeline Coverage and argue about individual deals, which is how a forecast call becomes a deal review. Read the gap first. The deals are how you close it, not how you find it. Deal Risk and Quarter & Year Trends sit close by, and the deal-risk and reference guides cover them.

RevTech: The Forecast report combines closed won, commit, upside and pipeline with the quarterly target.
The Forecast report combines closed won, commit, upside and pipeline with the quarterly target. Captured from the current application with illustrative sample data. Screenshot of the RevTech application; sample data.
The Forecast report: AI Projection, Target with the gap, Closed Won, Commit, Upside and Pipeline Coverage, with the forecast by period beneath. This is the read the weekly call is built on.
Part 2 of 8

Scope before you read

Set fiscal year, quarter and team before anything else. Every card, chart and table in a report reacts to that selection, and the most common way a forecast call goes wrong in the first two minutes is that two people are looking at different scopes and do not know it.

For the weekly call, anchor on the current quarter. Switch the team filter before you read commit, not after; the option list is your own org teams. Forecast, Pipeline Coverage, Renewals and Gap to Target all take the Team filter. Weekly Change Log is the exception. Its feed cannot narrow to a team yet, so it shows no Team control rather than one that would quietly narrow nothing, and it always reads the whole company.

Part 3 of 8

Open on the gap

Gap to Target puts the call's opening question on one screen. The cards read Remaining gap against the target, Won so far, Commit + upside open with how many times it covers the gap, Wins needed and AI projection. How the gap closes draws the target as one bar: closed won, open commit and upside stacked against it, and the part nothing covers yet. Path to target and a chart of won and projected against each period's target sit beside it, and Gap by rep breaks the same arithmetic out per rep.

Wins needed is the remaining gap divided by your average won deal, so read it as an order of magnitude, not a count to hold anyone to. It does not tell you how many new deals to create; that needs a close probability RevTech does not have yet, so the report does not guess.

Gap to Target report: remaining gap, won so far, commit and upside open, wins needed, and closed won against target by period.
The Gap to Target report. Cards show the remaining gap to the period’s target, won so far, commit plus upside still open, an estimate of the wins needed at the average won deal, and the AI projection. Below, closed won and the projection are charted against target by period, beside rings showing the path to target. Sample data. Screenshot of the RevTech application; sample data.
Gap to Target: the remaining gap, what is won and open against it, wins needed and the AI projection, with how the gap closes beneath. Sample data.
Part 4 of 8

The Forecast read: projection, then the cards

AI Projection is the model's view of where you land if current patterns hold. Treat it as a starting point. It is not the commit, and the distinction matters: the projection is a prediction, the commit is a decision a manager makes and is accountable for. Compare it with the Target card, which carries the gap, to know whether you are working a surplus or a gap.

The rest of the row gives the operating read: Closed Won, Commit, Upside and Pipeline Coverage. Coverage is the one that should change behavior. The forecast chart below shows closed won, commit, upside and pipeline per period against the quota, with the AI projection, today marked and the periods still to come shaded. Path to target sits beside it, and the Forecast by rep table carries each rep's target, closed won, gap, commit, upside, pipeline and pace.

  • Target — the number, with the gap stated rather than left to arithmetic
  • Commit — the manager-owned forward number, the only figure here anyone is accountable for
  • Closed Won — what is banked
  • Pipeline Coverage — the early warning, and the one worth a rule of your own
Part 5 of 8

From the number to the deals

Once you have read the gap, open Pipeline Coverage. Its cards read Commit, Best Case, Pipeline and Won, and each opens the deals behind it. Commit and Best Case are levers you can move, Pipeline is raw cushion, Won is already in. To close a gap, open Best Case and inspect the candidates that could be pulled into Commit, then pick one or two on the call, with the rep, and assign an owner and a date before moving on.

Two charts break coverage out by rep. One shows the share of each rep's target that is won, committed and in upside, with a pace word at the end of each bar. The other shows each rep's coverage ratio, open pipeline over what is left to win, against the 3× rule of thumb the product draws, with the thin zone below 2× shaded. Use whatever multiple your own history supports. A bar opens that rep's page.

The pace badges, Hit target, On pace, Stretch and At risk, live in the Forecast by rep table on Forecast. That badge is the structured input for a 1:1. It turns "how are you tracking?" into a conversation that starts from the same facts on both sides of the desk.

Part 6 of 8

Renewals belong in the same call

Renewals is not a Customer Success meeting that happens somewhere else. Its cards read Renewal Commit, Best Case, Renewed, Overdue Renewals and Churn Risk. Renewal Commit is the floor of the CS half of the number and Renewed is banked. Overdue Renewals and Churn Risk are as of today, whatever period you selected. Churn Risk is open renewal value on accounts whose engagement health is below its threshold, and it behaves exactly like a missing deal.

Open Renewals immediately after Forecast so churn risk gets named in the same conversation as new business. When an at-risk renewal surfaces, escalate it to the Action Center before the call ends. An at-risk renewal that leaves the room without an owner is a renewal nobody is working.

Part 7 of 8

What moved since last week

Weekly Change Log answers the question every forecast call asks second: what changed? Choose a window of 7, 14 or 30 days. The cards read Changes, Close dates pushed, Net amount change, Moved into Commit and Moved out of Commit. Changes by day stacks each day's changes by the field that changed, Commit movement shows what entered and left Commit, and Every change lists each one with the deal, so any line opens the deal behind it.

Two limits apply. It is company-wide, with no Team filter, because its feed cannot narrow to a team yet. And commit movement is priced at each deal's amount today, because a change record carries no amount, so a deal that has since closed is counted but not priced, and the card says so.

Weekly Change Log: every material deal change in the window, charted by day and by its effect on commit.
The Weekly Change Log. Cards count the changes in the selected window. Charts show changes by day and how commit moved, and the full list of changes — amount edits, close dates pushed or pulled, stage moves and forecast-category changes — follows below. Sample data. Screenshot of the RevTech application; sample data.
Weekly Change Log: changes, pushed close dates, net amount change and commit movement for the window, with every change listed below. Sample data.
Part 8 of 8

What a forecast call must end with

Forecast is a rhythm, not a report you read once. The habit that makes it worth the hour is ending every session with three things named: what gap remains, which specific deals close it, and who owns the next move on each.

If your call regularly ends without those three, the problem is usually that the call is being spent re-deriving the number rather than acting on it. Ask reps to update their deals on My Pipeline before the call, so the number is already current when you sit down. Then the hour goes on the moves: a deal pulled forward, a play enrolled, a renewal escalated, a target revisited.

What to take away

  • Set the period and the team before you read a single number. Every card in a report reacts to that scope.
  • Open on Gap to Target: the gap, what is open against it, and roughly how many wins close it.
  • AI Projection is a starting point, not a number to commit to. The commit is the manager's, and it is a decision.
  • Read Forecast for the gap by rep, Pipeline Coverage for the deals that close it, Renewals for the half CS owns, in that order.
  • A forecast call that ends without a named deal, an owner and a date has not finished.
Demo

See how the work gets done.

Explore how agents prepare work across your revenue teams, and how people review it, guide it and decide what happens next. Fictional data. Real product.

Explore the demo