A forecast call agenda is a fixed list of checks settled before the weekly call, so the meeting works on the number, not status. The Salesloft page describes forecast calls as check-ins built into a system of action rather than a spreadsheet, according to Salesloft. The five checks in this guide cover one source of opportunity data, commit status set from deal score, live dashboards for every touchpoint, a structured recurring format, and agreed actions for each deal.
Key takeaways: five checks before and after the call
- one source of opportunity data, confirmed before anyone opens the agenda
- commit status set from a written deal score rule, not from the status round
- every touchpoint read from dashboards built on the same live data
- one fixed recurring order that the call follows each week
- one agreed action and one owner for each deal before the call ends
Why a forecast call needs its agenda fixed in advance
The weekly call settles the number only when the agenda is fixed before anyone starts talking. If each person reads out their own deals in turn, the discussion tends to drift toward status, and the number gets left for the end of the meeting. A fixed agenda gives the call the same shape each week, so people can prepare for each check rather than for a general update.
The Salesloft page says that leaders, managers, reps, and account teams remain aligned and focused on the actions that move deals forward, according to Salesloft. The agenda is where that alignment becomes visible, because each check names the person who answers it. As an editorial recommendation, keep the agenda to five short checks on one page, and send it to the people who run the call before the meeting starts. A one-page agenda also means nobody has to scroll during the call to find the next check.
The table below lists one quoted sentence from each publisher this guide relies on. Each row uses that publisher's own wording, and the rows describe the products rather than your team's rules.
| Publisher | Page | Quoted sentence |
|---|---|---|
| Aviso | Revenue forecasting product page | "Toggle deals in and out of commits in 1 click based on deal score." |
| Xactlycorp | Xactly Forecast product page | "Operationalize your go-to-market plans with a single source of truth for managing territories, people, opportunities, credits, and quotas." |
| Salesloft | Sales execution software page | "Live custom dashboards for every touchpoint, so teams have the data to drive discussion, and then act." |
Before the call: one source and commit flags
The first check is the source of opportunity data. The Xactlycorp page places opportunities inside its single source of truth, which it presents as a way to operationalize go-to-market plans, according to Xactlycorp. A practical step is to draw the agenda's opportunity list from that source, and to avoid building the list from an export that someone made earlier in the week. If a deal is missing from the source, add it there before the call, so every later check reads the same list. Mark any deal whose details differ between the source and the agenda, and treat that mark as an open item for the meeting. Keep a short record of who changed the list and when, so any number on the agenda can be traced back to its source.
Give the source list one owner who answers questions about it before the call, so changes are made in one place. Agree on a cut-off time for edits to the list, and close the list at that time. Anything added after the cut-off goes on the agenda as an open item, so the list the comparison uses does not move during the call.
The second check is commit status. The Aviso page says deals can be toggled in and out of commits in 1 click based on deal score, according to Aviso. That describes how the product behaves, and it does not write your commit rule for you. Your team should write down the deal score conditions that place a deal in commit, then list the deals that crossed those conditions since the last call. Each condition can be phrased as a sentence that someone could check without asking the deal owner a question. Store the written rule beside the agenda, so anyone on the call can read the conditions before the meeting starts. When a deal crosses a condition, note which condition it met, so the discussion starts from the rule rather than from memory. Any disputed commit decision goes on the agenda as an open item rather than into a side discussion. For the category side of this check, read forecast category rules before you word your conditions.
Before the call: dashboards for each touchpoint
The third check is the dashboard view. The Salesloft page describes live custom dashboards for every touchpoint, and it says they give teams the data to drive discussion, according to Salesloft. For the forecast call, each touchpoint on the agenda should have its own dashboard, and each dashboard should read from the opportunity list you confirmed in the source check.
Opening each dashboard once before the call, and comparing the deals it shows with the source list, is the core of this check. One person can make that comparison, so the check has a single owner. Name each touchpoint on its own line of the agenda, next to the dashboard that supports it, so anyone can see which view answers which question. A short comparison sheet with one line for each deal, naming the dashboard, the value in the source, and the value the dashboard shows, is enough to show differences. If two dashboards show different values for the same deal, record the difference as an open item before the meeting. Differences that someone could have checked in advance should not take up call time. Read the dashboards in the same order as the agenda, so the review does not jump between views. For a wider set of visibility checks, the separate guide on report visibility checks is a useful reference.
Set a cut-off time for the dashboard check, and finish the comparison before that time so any open differences reach the agenda in time. As an editorial recommendation, read the dashboards on the same day each week, so the readings come from the same kind of data. If a dashboard shows a deal that is absent from the source list, record it as an open item and check the source before the call rather than during it.
During the call: run the recurring touchpoint
The fourth check is the structure of the call itself. The Salesloft page lists pipeline reviews, forecast calls, QBRs, 1:1s, and renewal risk reviews as critical recurring activities that are structured and ready to deploy, according to Salesloft. Apply the same idea to your own call by running it as a fixed sequence rather than an open status round. The order below is an editorial recommendation:
- source: confirm the opportunity list before any deal is discussed
- commit status: review the deals that changed against the written deal score rule
- dashboards: read each touchpoint view against the same list
- actions: move to the agreed actions for each deal
One person should keep the call to that order and pause any discussion that drifts back into status. A copy of the agenda with open items marked can go to that person, so the pause has a clear reference. Keep the agenda's order on screen or on paper during the call, so the person running it can point to the current check. Side topics belong on their own touchpoint on the calendar, so they do not take the forecast call's time. Before the meeting, send the agenda, the open items, and the comparison sheet to the people on the call, so the first minutes are not spent reading. For how the roles on the call can be divided, read forecast call co-organizer roles.
Before the call ends: agree actions for each deal
The fifth check is the action list. The Salesloft page names two kinds of action that move deals forward, closing a deal and stopping risk in its tracks, according to Salesloft. Before the call ends, read each deal on the agenda and agree one action and one owner for it. Each action can be written as one line that names the deal, the action, and the owner. The full list can be read back aloud, so each owner hears their own line before the call closes. The list should go into the call notes the same day, so the next call starts from the list rather than from memory.
Sort the deals on the agenda before owners are assigned, so each deal appears once on the list. As an editorial recommendation, a deal with no action agreed should stay on the list with the reason written beside it, so the next call can see why it was left open.
If a deal's action depends on a commit decision, link that action to the open item from the commit check, so both stay on one list. Count the open items that remain at the end of the call, and list each one with an owner, so the next agenda starts with them. If a new topic comes up after the list is set, it goes on the next agenda instead of reopening the call. At the next call, each owner can report on their line first, so the review starts with the actions already agreed.
What vendor claims about call time do not prove
Vendor pages describe the call in their own terms, and those descriptions do not measure your call. The Aviso page quotes one user who describes personal time saving from the product, according to Aviso. That is one person's report about their own work, so it does not show how long your forecast call will take. The same page includes a quoted speaker who describes asking for a single pane of glass across operation roles, according to Aviso. That describes a request for a single view, and it does not show that your calls improve.
The Salesloft page also offers a 15-minute call with its team to walk through what rollout looks like for your specific motion, according to Salesloft. That call is about rollout, not a step in your forecast call, so it does not belong on this week's agenda. It does not replace the checks in this guide.
As an editorial recommendation, record the start time, the end time, and the number of open items for each forecast call, so the comparison across several weeks uses the same measures. Each vendor claim can be tested against your own calendar and call notes, and the changes worth keeping are the ones your own records support.
Your next step is to write the five checks on next week's forecast call agenda and assign one owner to each check.
FAQ: forecast call agenda questions
Which check should come first before a forecast call?
The source check should come first, because every later check reads from the opportunity list it produces. Build that list from one source, then run the commit and dashboard checks against it. If the list changes after those checks, rerun the comparison so the commit and dashboard views match the final list.
How fast can commit status be set from a deal score?
Commit status can change in 1 click based on deal score, according to Aviso, but that describes the product rather than your rule. As an editorial recommendation, write the deal score conditions before the call, so the one-click change is made against a rule the team already agreed.
Should call data come from live dashboards or a spreadsheet?
The Salesloft page describes forecast call check-ins that run from live data, according to Salesloft. As an editorial recommendation, build the views for the call from live dashboards rather than from a spreadsheet kept for the meeting. If you keep a spreadsheet, use it as a record of the call rather than as the source of its figures.
What other recurring touchpoints sit next to the forecast call?
The Salesloft page names pipeline reviews, QBRs, 1:1s, and renewal risk reviews alongside forecast calls as recurring activities, according to Salesloft. Keep topics from those reviews out of the forecast call, so the call stays on its five checks.