Why Reps Hate Forecasting (And How to Fix It)
- No invented stats
- Written for UK readers
- 3 min read
- Published 6 October 2026
Ask a sales manager why their forecast is unreliable and you'll usually hear that reps are optimistic, or lazy about updating the CRM. Ask a rep and you'll get a different answer: forecasting is a game where being honest costs you something and being vague costs you nothing.
That's the real problem. Forecast accuracy is not a discipline issue. It's an incentive issue, and no amount of chasing people to update close dates will fix an incentive.
What reps are actually responding to
Consider what happens to a rep who forecasts honestly. They say a deal won't land this quarter. The response is a series of questions about why, an offer of "help" in the form of their manager joining a call, and their name mentioned in a meeting they weren't in. Forecast low across the board and you get put on a performance plan before the quarter has even ended.
Now consider the rep who keeps everything in the forecast at 70%. Nobody asks them anything until the last week of the quarter, at which point the deals slip and everyone agrees the customer was unreliable. The optimistic rep has a much quieter life.
Same with close dates. The rep who moves a date out honestly gets asked why. The rep who leaves it at the end of the month and shunts it forward on the 1st gets left alone. The system is teaching them exactly what it wants, and they're learning.
Three changes that actually help
Separate the forecast from the judgement. If the forecast call is also the performance conversation, you will never get a clean number. Run them separately, and make the forecast review about evidence rather than about the rep's character. "What has the customer done that makes you think this closes?" is a question about a deal. "Why is your number down?" is a question about a person.
Define stages by buyer behaviour, not rep activity. A lot of forecast inaccuracy starts with stages that mean nothing. If "Proposal Sent" is a stage, deals sit there indefinitely, because sending a proposal is something you did, not something they did. Define stages by what the buyer has done — they've confirmed a budget exists, they've introduced you to the approver, they've given you a date for signature. Then a stage is evidence, and the forecast is a summary of evidence rather than of feelings. We go deeper on this in our guide to pipeline stages.
Ask for two numbers, not one. A single number forces the rep to pick a lie. Asking for a commit (deals they'd stake their reputation on) and a best case (deals that could land if things go right) lets them be honest about both. It also gives leadership something far more useful: a range, which is what a forecast actually is.
Worth adding: if your team is weighting deals by stage probability, know what that number is doing. A weighted pipeline is a portfolio estimate — it's reasonable across forty deals and meaningless across four. Our weighted pipeline calculator shows the arithmetic, and the honest caveat that comes with it.
The counter-argument
Someone has to hold reps accountable, and there's a version of "forecasting should be blame-free" that turns into nobody ever being wrong about anything. If a rep commits a deal three quarters running and it never lands, that's a conversation worth having, and treating it as purely a systems problem would be daft.
Accuracy should be tracked and it should matter. The distinction is in what you track it against. Measuring a rep on whether their commit lands rewards accurate forecasting. Measuring them on whether their forecast is big enough rewards fiction. Plenty of teams think they're doing the first and are actually doing the second — usually because the same meeting that reviews the forecast also reviews whether the team will hit target, and the pressure leaks across.
The simplest test: when a rep drops a deal out of the forecast, what happens in the next five minutes? If the answer is "they get a hard time", you have your explanation.
Spotted a mistake or a number we can't back up? Tell us and we'll fix it.