To hand off a readable forecast, state its purpose and owner, label confirmed figures and assumptions, and explain changes in dated notes.
Key takeaways
- State what the forecast covers and who owns it before any table or chart.
- Show confirmed and assumed subtotals on separate lines if a total mixes both kinds of figures.
- Explain each change in the log, because a bare update tells readers nothing unless the reason says what happened.
- Before sending the file, check that a reader outside your team can explain its purpose and largest changes using only the file.
At some point, a revenue leader hands a forecast file to someone else. The reader might be a manager who needs to review the numbers before a meeting, a teammate covering while you are out, or the person who takes over the file when the next quarter starts. In every case, the reader was not in the room when the numbers were built. They see totals, categories, and notes, and they have to decide how much to trust each one. They may not be able to ask you first.
A file can be accurate and still be hard to hand off. The reader may see a number without knowing what it assumes, or see a change without knowing why it happened. That gap is what this post is about.
This post covers 3 checks to run before you send the file. None of them needs new software or a new process. Each asks you to reread the record as a stranger would, and to fill in the answers that stranger would otherwise have to request from you. Work through them in order, because the first check gives the other two their context.
Think of the checks as a way to remove follow-up questions before they happen. A handoff that triggers a long list of questions in the first week costs the new owner time, and it costs you time answering them. A record that answers those questions up front lets the reader start working on the forecast instead of on its history.
Check 1: state what the forecast is for and who owns it
The first check is to write, at the top of the file, what the forecast covers and who is responsible for it. Put this before any table or chart, because every other entry makes more sense once the reader knows the scope.
A reader who opens a forecast without context has to guess at the basic questions. Is this the whole company or one region? Is it bookings, revenue, or pipeline? Does it cover the current quarter, the rest of the year, or a single list of deals? A file that answers none of these can be filled in correctly and still be hard to interpret. The reader may treat a total as a commitment when you meant it as a working estimate, or compare it with last quarter's file, which used a different definition.
Start with a short header block. Include the period the file covers, the unit of measure, the currency if more than one is in use, and the date the figures were last refreshed. A reader who sees a refresh date from three weeks ago knows to check whether anything has happened since. Leaving out the date forces them to guess, and a guess is a weaker input than a date.
Next, name the owner. The owner is the person who can answer questions about the figures and who decides what changes. Be specific. A team name or a shared inbox tells the reader where to send a question, but not who will answer it. If ownership is changing, name both the outgoing owner and the incoming owner, and say which entries each person made. That way, the new owner does not have to wonder whose judgment produced an older line.
Write the purpose in one or two sentences. The purpose tells the reader which parts of the file matter most for the decision in front of them. A reader using the forecast for a hiring plan will care most about the timing of expected closes and how reliable each category is. A reader using it for a board update will care more about the total and how it compares with plan. The same file can serve both uses, but the reader needs to know which use you intended.
Keep the header short. Its job is to orient the reader, not to repeat every detail below it. If the header runs longer than a screen, move the detail into a separate section and point to it.
Label the version too. A forecast file may go through several rounds of review before it is handed over. Give the version you are sending a clear name, such as the date and a short tag like "after pipeline review," so the reader can tell it apart from earlier copies still in circulation. Without a version label, two people can quote two different totals and both be right about the file they opened.
A simple test for this check: send the first screen of the file to someone outside your team, and ask them to say, without help from you, what the forecast is for, what period it covers, and who to contact about it. If they cannot answer all three, the header needs more work. If they can, the first check is complete.
Check 2: separate firm figures from assumptions
The second check is to mark which figures are confirmed and which depend on assumptions, and to write each assumption next to the number it supports.
A forecast file can mix two kinds of entries without making the difference obvious. The first kind is a figure taken from a record of what has already happened, such as a signed order or a closed invoice. The second kind is a figure that rests on judgment, such as the expected close date for a deal still in negotiation, or the share of a pipeline you think will convert. Both can appear as plain numbers in the same column, and the reader often cannot tell which is which from the number itself.
A reader who cannot tell the two apart will treat them the same way. They may plan around a judgment as if it were a signed commitment. Or they may discount a confirmed figure because it sits next to a shaky one. Either mistake comes from missing information, not from bad arithmetic, and the fix is a label.
Give each judgment a plain label. If your file already has a status column, a tag, or a color, use it, but state what each value means in a key at the top. Words like "confirmed" and "estimate" are clearer than codes only you understand. Be consistent. If one part of the file says "likely" and another says "probable," a reader may wonder whether those words mean different things. For category labels, see forecast categories explained.
For each assumed figure, write one sentence that states the assumption. For example: "Assumes the procurement review finishes before the end of the month." That sentence does two jobs. It lets the reader judge whether the assumption is reasonable given what they know, and it tells them what to check if the assumption turns out to be wrong. A number with no stated assumption can only be accepted or rejected whole. A number with a stated assumption can be adjusted.
Write down the source of each confirmed figure as well. A reader should be able to see whether a number came from a contract, a billing record, or a conversation with a customer. You do not need a long citation. A short phrase such as "from signed order form" is enough, as long as it points to where the figure can be verified. Keep the source notes in the same place throughout the file. A reader who learns where to look once can check every confirmed figure without searching for its origin.
Be careful with totals. If a total combines confirmed and assumed figures, say so next to the total. A total that looks precise can lead a reader to believe every part of it is equally firm.
Rounding deserves the same care. If you round figures for display, say so in the header, so the reader does not try to reconcile a column that adds up to a slightly different total. A small mismatch is easy to explain once and very confusing to explain again and again to a new owner.
The test for this check is simple. Pick three figures at random and ask whether a reader could tell, from the file alone, whether each one is confirmed, what it depends on, and where it came from. If the answer is no for any of them, add the missing label, assumption, or source before you send the file. A few spot checks will not catch every gap, but they will show you where the pattern breaks.
Check 3: record changes and make the notes readable
The third check is to keep a dated record of what changed, who changed it, and why, and to make sure every note can be read by the people who need it.
A forecast changes between the time it is built and the time it is handed over. Deals move, amounts get revised, and categories get reclassified. A reader who sees only today's total cannot tell whether the forecast is trending up or down, or whether one large change explains the whole gap from the last version. A change log gives them that history without asking you to reconstruct it.
Keep the log in the file, either at the bottom or on a separate tab. For each entry, record the date, the person who made the change, the figure affected, the old value, the new value, and a one-line reason. A log with only dates and values tells the reader that something moved. The reason tells them what happened.
"Moved to next quarter after the customer asked to delay the start date" tells them what happened, what caused it, and what to watch for if the customer changes its mind again. Write the reason in the words you would use if the reader asked you about it in a meeting.
Keep the log short enough to read. You do not need to record every edit. Record the changes a reader would want to understand: changes to large items, changes to the rules used to categorize items, and changes that move a figure across a period boundary. State at the top of the log what level of detail you chose, so the reader knows what is and is not included.
Notes are the other half of this check. Comments in a forecast file can explain why a number looks the way it does. They are only useful if the reader can see them, and if they make sense to someone who was not part of the conversation that produced them.
Before you hand off the file, read every comment and ask three questions. Is it clear who wrote it? Is it clear when? Is it written for the reader, or only for you? A comment such as "see the thread from last month" points to something the new owner may not be able to open. Either copy the relevant point into the comment itself or remove the pointer. A comment that is only shorthand for its author does not help anyone else.
Check the visibility of each note as well. Some tools let you limit a comment to specific people. Gong's help page on adding comments, for example, states: "Note: Comments set for specific people are only visible to those people." Gong, "Add a comment" Before the handoff, decide which notes should stay limited and which the new owner needs to see. A note that only you could see while building the file may be exactly what the next owner needs. Both mistakes are possible: a note can stay hidden when it is needed, or become visible when it was meant for one person. Review the setting for each note rather than assuming the default is right.
Also review how you dated your comments. A comment that says "pending" with no date does not tell the reader whether the thing it describes is still pending. Add a date to any comment that describes a status, so the reader can tell how old that status is.
The test for this check is to open the file as if you were the new owner. Using only the change log and the comments, try to explain the three largest changes since the previous version. If you can explain them without asking anyone, the record works. If you find yourself needing to ask the previous owner, the gap is in the record, and that is where the next entry belongs.
Before you send the file
Send a short cover note with the file, too. Keep it to a few lines: the file's name, the version, the one thing you most want the reader to check, and the person they can contact with questions. The cover note does not replace the record, but it tells the reader where to start.
Why the record matters after the handoff
The record matters after the handoff because the next owner will rely on it when you are no longer there to explain it. A forecast that is clear to a stranger is also clear to you months later, when you need to compare a new quarter with an old one and cannot remember why a figure moved.
Clear records also make review easier. A manager who can see the assumptions, the sources, and the change log can focus on the judgments that matter rather than on rebuilding the file. Questions still come up, and they should. A good record changes the kind of question. Instead of asking what a number means, the reader asks whether the assumption behind it still holds.
None of these checks requires a perfect forecast. A forecast can turn out to be wrong and still be a good record. What the checks protect is the reader's ability to see what was known, what was assumed, what changed, and who to ask. That is what makes a handoff work, and it is the part of the job that outlasts any single quarter.
Illustrative example: explain a revised estimate
An illustrative forecast entry shows 30 units, assumed to close this quarter. The customer asks to delay the start date, and the current-quarter estimate becomes 0 units. The change log records the date, editor, affected entry, old value of 30, new value of 0, and the customer's requested delay. The next owner can see why the estimate changed without treating it as lost confirmed business.
Today, open your current forecast and use its notes to explain the largest change since the previous version. Add the missing reason if you cannot.
Related guides: Forecast data refresh limits: 9 figures to read each week · Forecast period rules: read 4 before the weekly number · AI call scorecard checks: 5 rules before the forecast.
Questions before the handoff
Does a confirmed figure still need a source note?
Yes, a confirmed figure needs a source note so the reader can find the record behind it.
Should every edit go in the change log?
No, record changes that affect the reader's understanding of amounts, categories, or forecast periods.
Can the cover note replace the file's header?
No, the file needs its own context because the next reader may open it without the cover note.