You’ve probably been on this call.
Forecast review. Your manager pulls up an account. Green. Renewal in 60 days. The last note says “Good call, all on track.”
Everyone moves on.
A few weeks later, you email the champion. It bounces. She left the company months ago.
Nobody did anything wrong. You wrote “all on track” after a good call, as a quick note for yourself. Nobody updated it when things changed.
But on the forecast call, that old note was all your manager had to go on.
The Job Asks For The Forecast And Skips The Inputs
I wanted to see if companies even expect this to work, so I went to the job posts.
I took the 279 CSM roles on the TopCSJobs board, posted since mid-July and still open this week, and extracted what each one asks the CSM to do.
54 ask you to forecast renewals or expansion.
8 ask you to keep CRM records accurate.
Only 2 ask for both.
One of them is 1Password. It asks for “strong Gainsight and Salesforce hygiene; consistent forecasting discipline” in the same line.
Almost everyone else treats the forecast and the data behind it as two separate jobs.
And the forecast is often the only one that makes it into the job description.
Sales Handoffs Show It Best
Think about the handoff doc.
The Account Executive fills it in after the deal closes. But the AE won’t use it. You will.
So it gets done fast, to tick a box, and you end up learning what was promised on your first customer call.
The teams that fix this don’t write a better template. They give the AE a reason to care about what happens next:
Part of the AE’s commission depends on the customer still being there at 90 days.
No commission until the handoff and kickoff are done.
The AE joins the first customer call.
Once the person writing the notes has a stake in what happens next, the notes get better.
Your CRM Works The Same Way
Think about how notes get written on your team.
You write them fast, for yourself. A few words, enough to remember the call next time.
Then your manager reads those same notes to build the forecast.
And everyone logs things differently. One CSM writes a risk in the notes. Another changes the health field. A third mentions it on Slack and moves on.
Same risk, three places, and the forecast only sees one. It’s easy to blame busy CSMs. But the real issue is simpler.
When the person who writes a field is the same person who uses it, it stays accurate.
But when they’re different people, it slowly goes stale, and nobody notices until the forecast call.
Most teams have never checked which of their fields are which.
One Fix You Can Start This Week
Start with the easiest one: the field everyone fills in differently because nobody ever showed them how.
Pick the task that goes wrong most on your team. Logging a call, updating renewal notes, or flagging a risk.
Write down the exact steps, in the order you click, with a screenshot for each.
Then hand it to your newest CSM. If they can follow it without asking you a question, it’s done.
A simple doc works fine.
Tools like Tango, one of my recent sponsors, make it faster. It captures the steps while you click and turns any workflow into a step-by-step guide with screenshots.
So that fixes one field. Now let’s find the rest.
Find The Stale Fields First
Pick one account in your next forecast. Which of its fields would you actually bet the renewal on?
The 30-min audit I built tells you, field by field. It’s right below, and Q4 renewals are already on the calendar, so start there.
Step 1: Run The Writer–Reader Audit
List every field that feeds your forecast, health score, or handoff.
Most teams land on 8 to 15: renewal risk, health status, champion, next step, renewal date, last contact, ARR, handoff notes.
For each field, fill in five columns:
Writer
Who enters it?
Name the role → CSM, AE, CS Ops, or a system.
Reader
Who makes a decision with it?
CS leader, finance, the next CSM.
Writer uses it (0 to 2)
0 if the writer never looks at it again.
1 if sometimes.
2 if they use it every week.
Consistency (0 to 10)
Pull 10 accounts at random.
Count how many have the field filled in the same way, current, and in a format the reader can act on.
Decision weight (0 to 3)
How much does a renewal or forecast decision depend on it?
Risk = Decision weight × (10 − Consistency)
Any field with risk of 15 or more is red.
Any field where the writer scores 0 and the decision weight is 2 or higher is red too, even if it looks clean today.
That’s a gap waiting to drift.
→ Expect three or four reds.
They’re almost always the fields your forecast leans on hardest.
Found Your Reds? Here’s What To Do With Them
Steps 2 and 3 show you the right fix for each red field and the 15-min monthly check that keeps them accurate.
Paid members also get the full Forecast Fields Workbook, which does the scoring for you, and can send me their renewal plan or exec update for review before it reaches leadership.
PS. What’s the one renewal, QBR, or exec conversation you’re most worried about between now and year-end? Hit reply, one line is enough. I read every answer and will point you to the right playbook.