Skip down to the research record

Sales goal for a forecast call: 3 checkable parts

Quota Forecast Editorial Team · Published · 13 min read

A sales goal a forecast call can check has three parts: a number you can count, a deadline, and a definition of what counts.

Key takeaways

  • State the goal as a count or an amount, not a direction.
  • Set one specific deadline and say whether the last day counts.
  • Write the definition of what counts before the quarter starts.
  • Split the team number into shares that add up to the team goal.

Why a vague goal fails on the forecast call

Every quarter, a sales leader writes a goal and asks the team to report against it. The forecast call is where that goal gets tested. Someone reads the number, reps say where they stand, and the room either agrees on what is true or argues about what the goal meant in the first place.

Most goals break at that moment, not when they are written. "Increase revenue" sounds fine in a planning meeting. On a forecast call it cannot be checked. Which revenue: booked, invoiced, or collected? Counted from what date? Including which deals? Each rep answers those questions a little differently, and the call turns into a debate about definitions when it should be a review of the business.

The Xactly article uses a direct contrast to make this point. Its weak example is a goal such as "increase revenue." Its stronger example is "Close 15 new enterprise accounts by Q4." (Xactly, How to Improve Sales Performance) The second version can be checked. You can count accounts, see which ones have closed, and see how many are still needed before the deadline.

This post shows how to build a quarter goal from three parts: a number, a deadline, and a definition of what counts. Each part gives the forecast call something concrete to check. Together, they turn a target into a commitment the team can report against every week, not just at the end of the quarter.

First, a number you can count

The first part is the number itself. It has to be a count or an amount, not a direction. "Grow the pipeline" tells people which way to move. It does not tell them whether they got there. A number tells them when they are done.

A useful test is this: if two people count the result on the same day, do they get the same answer? If they do not, the number is not ready. Counting accounts is usually easier to agree on than counting revenue, because an account is either closed or it is not. Revenue carries timing, currency, and recognition questions, and each one is a place where two people can disagree.

The Xactly example is a good model. It names a count (15), a type of thing being counted (new enterprise accounts), and an action (close). Each word narrows the goal. A rep looking at a deal can tell whether it belongs in the count, and the leader can tell whether the count is on track.

Keep the number to one or two for each team. If a team has six goals, the forecast call becomes a list of six status updates, and none of them gets the attention it needs. Pick the result that matters most this quarter, and let other work support it.

Choose a number that is ambitious but still tied to what the team can actually do. Look at last quarter's results, the size of each territory, and how many active deals are in the pipeline now. A number no one believes will be ignored after the first few weeks. A number that is too easy tells the forecast call nothing, because the team will hit it without anyone having to think about how.

Write the number in the same units your CRM uses. If the CRM counts opportunities by stage and the goal is written in a different unit, someone has to translate every week, and the translation is where errors creep in. Match the goal to the report the team already produces.

Second, a deadline the call can see

The second part is the date. Write the deadline as a specific point in time, and say whether it is inclusive. "By Q4" works in the Xactly example because the team knows which quarter it means. But the forecast call needs more than a quarter name. It needs to know the last day to close, and whether a deal signed on that day counts.

The deadline does a second job. It tells the team how much time is left. On each forecast call, the leader should be able to say how much of the target is done and how much time remains. If the answer is "a lot" or "about the same as last week," the deadline is not doing its job yet. Put the remaining time next to the remaining count so the room sees both at once.

When the deadline is clear, you can answer the question every useful forecast call asks: at the current pace, will we get there? That answer depends on when deals will close. If it depends on guesses about closing dates, the goal needs a tighter definition of which stages a deal must pass before it counts as likely to close.

Avoid moving the deadline partway through the quarter. A moved deadline makes last week's report and this week's report impossible to compare. Sometimes a change really is needed, such as a company-wide shift in fiscal calendar. When that happens, record the old date, the new date, and the reason in a close date change log, then report both views on the call.

Make the deadline visible outside the call, too. A goal sheet, a dashboard tile, or the top line of the weekly update can all show the date. The call goes better when people walk in already knowing how many days are left and what the last day to close is.

Third, a definition of what counts

The third part is the one most leaders skip, and it causes the most trouble. The definition answers one question: what has to be true for an item to count toward the goal?

Take the word "enterprise." Every person on the team may have a picture of an enterprise account, but those pictures may not match. One rep may think of any company with many employees. Another may think of a company that signs a multi-year contract after a security review. Neither picture is wrong on its own, but the forecast call cannot work with two private pictures. Write down the rule your business uses, such as the company type, the size threshold, or the contract structure, and keep it in one place the whole team can open.

Words like "new" need the same care. Does a new account mean a company that has never bought from you, or a new business unit inside an existing customer? Does an expansion deal with a current customer count? Does a deal already open on the first day of the quarter count? These choices change the number. Make them before the quarter starts, not during the call.

Stages are part of the definition too. If the goal counts closed accounts, the team needs to agree on what "closed" means and which stage comes before it. Nutshell's free resource library shows recommended pipeline stages for a variety of common B2B sales models. (Nutshell, helpful resources) You do not need to copy those stages exactly. Use them as a starting point, then name the stages your team actually uses and mark the one that makes a deal count. For how stages relate to forecast categories, see Pipeline, Best Case, Commit: Forecast Categories Explained.

Write the definition as a short sentence the call can apply on the spot. A good test is whether a rep could read the sentence about a deal they are currently working and answer yes or no without asking the leader. For example, an account might count once it is a new customer, meets the enterprise rule, and has a signed contract dated on or before the deadline. The exact words are yours to choose. What matters is that they are specific enough to give the same answer every time.

Put the definition where the goal lives. If the goal sheet says "15 new enterprise accounts" and the definition sits in a separate document no one reads, the two will drift apart. Keeping them together on one page prevents most arguments on the call.

How the three parts work together on the call

Put the three parts into one sentence, and the goal is complete. The sentence should name the number, the deadline, and the definition in an order that reads clearly. Once it is written, the forecast call has something to check.

Each rep reports three things: how many counted accounts have closed, how many are in the late stages the definition names, and how many more are needed to reach their share. The leader adds those figures, compares the total to the team number, and checks the time left against the deadline. Each answer can be verified by looking at the CRM.

Ask the questions in a fixed order. First, are we at the number? Second, are we on pace for the date? Third, do the deals in the count meet the definition? The third question matters most, even though it comes last. If deals are counted that do not meet the definition, the first two answers are not reliable. A clean number built on loose definitions will fall apart the first time someone audits it.

Share a one-page goal sheet before the call with the number, the deadline, the definition, and the stages. Use it as the agenda, alongside Forecast call agenda: 5 checks before the meeting. When someone asks whether a deal counts, the answer is on the page. When the answer is not on the page, the call pauses, the definition gets updated in writing, and everyone sees the change.

Keep the call focused on decisions. Once the numbers are on the screen, the useful discussion is about what to do about the gap, not whether the gap exists. Reps can say which deals are at risk, what help they need, and which stages are slowing down. Those are the conversations a forecast call exists to have.

Illustrative example: a team goal in practice

A team of 5 reps sets the goal of closing 15 new accounts by the last day of the quarter, so each rep's share is 3. A deal counts only if it passes the definition in the third part. On the call, each rep reports counted accounts that have closed, the deals in late stages, and how many more are needed. The leader adds the figures and checks the days left against the deadline.

Splitting the team number into individual shares

Once the team goal is set, it has to be divided among the people who will work toward it. The Xactly guide describes the work this way: "Optimize go-to-market strategies by creating coverage models, balancing territory potential, and driving ideal quota allocations." (Xactly, How to Improve Sales Performance) The line names three separate tasks. Coverage models decide which accounts each person works. Territory potential decides how much opportunity each territory holds. Quota allocation decides how much each person is expected to deliver.

Splitting evenly is the easiest approach and often the least accurate. A territory with many small accounts and one with a few large ones may look the same on paper and behave very differently in the pipeline. An even split can leave one rep with a share they cannot realistically reach and another with a share that is too easy. Splitting by potential takes more work, but it gives the forecast call shares that reflect where the opportunity is.

Each rep's share should use the same three parts as the team goal. The rep's number, deadline, and definition should match the team's, so the rep figures add up to the team total. If the shares add up to less than the team number, the call will show a gap no one owns. If they add up to more, the team is planning to exceed its goal, which may be deliberate, but it should be a decision and not an accident.

Review the splits before the quarter starts and again once the first few weeks of real data are in. Potential estimates are only estimates. If a territory has few active deals, its share may need to move. Changing a split midway is harder than getting it right at the start, so explain any later change in writing.

Common mistakes to avoid

Most weak goals fail in a handful of predictable ways. Each one is easy to spot once you know what to look for.

  • Mixing units. One goal counts accounts, another counts revenue, and the call has no way to show how they relate. Pick one primary unit and use secondary measures only as support.
  • Defining terms during the call. If the team first hears the definition when someone asks about a deal, the call loses time and trust. Write the definition before the quarter starts.
  • Changing the definition midway. Tightening or loosening the rule after results come in makes earlier numbers meaningless. If a change is truly needed, recount progress to date under the new rule.
  • Measuring only at the end. A goal checked once a quarter gives no time to act. A weekly check on the number, the time left, and the pace makes the forecast call useful.
  • Depending on data no one captures. If the goal needs a field that reps do not fill in, the number will be wrong or late. Confirm every input is captured in the CRM before the quarter begins.
  • Treating the number as the whole plan. A target sets direction but does not change how people work. The Xactly productivity guide lists "15 ways to increase sales productivity that actually make an impact." (Xactly, What is Sales Productivity?) Use the number to decide which actions to focus on, and report on those actions as well as the result.

Each mistake has its own fix, listed above; most come down to writing the rule down and checking it on a schedule.

A quick check before you send the goal

Before you share the goal, run through a short list. If any answer is no, fix that part before the quarter starts.

  1. Can two people count the result on the same day and get the same answer?
  2. Is there one specific deadline, and is it clear whether the last day counts?
  3. Is every term defined in writing, including what "new" and "closed" mean?
  4. Do the individual shares add up to the team number?
  5. Can you say right now how far along the team is and how much time is left?
  6. Is the goal written in units the CRM already tracks?

These questions take about ten minutes to answer. They prevent most of the problems that make a forecast call slow or unproductive later in the quarter.

Closing thoughts

A sales goal is a sentence, and the forecast call is where that sentence is tested. Many goals read well and fail in the room because they cannot be checked. Three parts make the difference: a number you can count, a deadline the call can see, and a definition that says exactly what counts.

Write those three parts before the quarter starts and share them in one place. Split the number fairly across the team, check it weekly, and handle any change in writing. When the forecast call opens, the team should already know the goal, the time left, and what counts. That leaves the call free to do its real job: finding the gap and deciding what to do about it.

Your next step today

Open your current sales goal and read it against the three parts. If you cannot state the number, the deadline, and the definition in one sentence each, rewrite the goal before your next forecast call.

Frequently asked questions

Can a team use a revenue goal instead?

Yes, but first agree which revenue counts (booked, invoiced, or collected) and the date it is counted from, or the call will debate definitions instead of results.

How often should the goal be checked?

Weekly, against the number, the time left, and the pace, so the team can still act before the deadline.

Sources