Label forecast quarters and dates with one quarter-year format, unambiguous dates, and a fiscal calendar note inside the record. You write it while the quarter is still moving, save it, and move on. Then someone else opens it weeks or months later. That reader might be a new sales ops analyst, a finance partner building a board deck, or you, after the details have faded. They will not have the call notes or the chat thread that explains what you meant. All they have is the label on each number.
Many forecast problems that surface later are not arithmetic errors. They are labeling errors. A row says "Q4" and the reader assumes the calendar fourth quarter, when your company's fiscal year starts somewhere else. A date reads 4/5, and the reader takes it as April 5 when you meant May 4. Nobody meant to mislead anyone. The record simply assumed a context the reader did not share.
It helps to picture the reader before you write a single label. In many teams, a forecast record gets read by three kinds of people. The first is a peer who was on the same calls and only needs a reminder. The second is someone from another function, such as finance, who needs to tie the numbers to the books. The third is a successor who inherits the role and has never seen the deal history at all. Labels that work for the first reader often fail the other two, so write for the third.
This post covers three habits that cost very little and remove much of that guesswork:
- Use one quarter and year format everywhere.
- Write dates so they cannot be misread.
- State your fiscal calendar inside the record.
This post does not tell you which fiscal calendar to use. That is often a finance decision. It covers how to label whichever calendar you already have, so that the label means the same thing to everyone who reads the record.
Pick one quarter and year format
Quarter labels cause the most confusion because "Q1" can mean different things in different organizations. Some companies follow the calendar year, so their Q1 is the first calendar quarter. Others use a fiscal year that begins in another month, so their Q1 can fall partway through a calendar year. If your record says only "Q1" and a bare year, the reader has to guess which calendar you used.
GitLab's communication handbook addresses this directly. It asks writers to refer to a year as CY18, never 2018, and to refer to a quarter as CY18-Q1, to prevent confusion with fiscal years and quarters. The "CY" prefix tells the reader the label follows the calendar year, which is exactly what someone reading later needs to know.
You do not have to copy GitLab's exact format. The point is to choose one pattern, write it down, and use it in every row, heading, file name, and chart title. A record that says "Q3 FY[YY]" in one place and "[year] Q3" in another forces the reader to work out whether those refer to the same period. Consistency removes that work.
Here is how the difference looks in practice. A header that reads "Q4 forecast, this quarter" depends on when it is read. The same header written as "CY[YY]-Q4 forecast, as of Nov 2, [year]" still means one thing a year from now. The second version costs a few more characters and removes the need to ask anyone what "this quarter" meant.
A few details make the pattern easier to keep:
- Put the calendar type in the label or the heading, such as calendar or fiscal, so the reader never has to infer it.
- Use the same order every time, either year first or quarter first, and do not switch.
- Check that labels survive exports. A spreadsheet can quietly change a label that looks like a date, so open the exported file and read the labels again.
Write dates so they cannot be misread
A numeric date such as 12/4 looks clear to the person who wrote it and confusing to everyone else. Depending on the reader's habits or region, it can mean December 4 or April 12. Even inside one company, two people can read the same slash date differently, and a record read months later gives them more time to get it wrong.
GitLab's communication handbook gives a simple rule for this: if the year is obvious from the context, it is acceptable to write Dec 4, but not 12/4. The useful part is the condition. A month name removes the day-and-month mix-up, but the year still has to be clear. A reader who opens the record months later may not share your sense of what the context implies, so write the year out in full the first time a date appears in each section.
Two dates matter most in a forecast record: the as-of date, when the numbers were pulled, and the period the forecast covers. Label them separately on the first page, so a reader does not mix them up. For example, a line such as "As of Nov 2, [year], forecast for CY[YY]-Q4" tells the reader two things at once. Keep the wording stable from one record to the next, so the pattern becomes familiar.
If you use numeric dates anyway, choose one order and state it once, near the top of the record. Formats that put the year first, such as [year]-[MM]-[DD], also sort correctly as plain text, which helps when someone exports the table. Whatever you choose, use it everywhere.
Date ranges need the same care. "Dec 4-8" is easy to read when you are looking at it, but the reader still has to know which year and whether the range includes both ends. Write the full range, such as "Dec 4 to Dec 8, [year]," and state whether both dates are included.
If a cutoff depends on time, add the time zone as well, because a forecast pulled at the end of a day in one office may already belong to the next day elsewhere.
Avoid relative words
Relative words cause quiet confusion in a forecast record. Words such as "this quarter," "next month," "last week," and "the current year" only make sense on the day they were written. A reader months later has to know the write date to decode them, and many will not bother. Replace each one with the calendar label or the actual date it describes.
The same goes for a deal marked "closing soon." Write the expected close date instead, and if the date is only an estimate, say that it is an estimate. Your future reader can then judge how much weight to put on it.
Watch for these in your own habits too. People often write "last quarter" in a draft they expect to read only next week, forgetting that the record will be read later still.
State your fiscal calendar inside the record
Consistent quarter labels still leave one gap. The reader needs to know how your fiscal year lines up with the calendar. Many organizations do not start their fiscal year in January, and a reader from another team may assume they do. Do not expect them to find your fiscal calendar in an old planning deck.
GitLab's communication handbook says that when financial data is presented, the writer should include a note indicating the fiscal year, and gives the example of a fiscal year ending in January. Use that approach for your own record. Put the note near the top, where the reader sees it before any number, rather than in a footnote on the last page.
A useful fiscal note answers three questions:
- Which month the fiscal year ends, or starts, written out in words.
- Which calendar months each fiscal quarter covers, so the reader can translate between the two systems.
- Who owns the calendar, and where the full definition lives, so the reader can check it.
Use this short fiscal note, filling in the bracketed parts for your company:
Calendar note: this record uses fiscal labels.
Fiscal year ends: [month name] [day].
Fiscal Q1 covers: [months]. Fiscal Q2 covers: [months].
Calendar labels (CY[YY]-Q4) follow the calendar year.
If one record mixes calendar and fiscal views, label each table on its own. A table headed "Fiscal Q2" beside a chart headed "CY[YY]-Q2" only makes sense when the note says whether the two periods match.
If your company changes its fiscal calendar, record the change the same way you would record any other label change. Say when it took effect, and whether earlier records were restated. A reader comparing a new record with an old one needs both facts.
Mistakes that break later readers
Four mistakes show up again and again. The first is changing a label partway through the quarter, such as renaming a region or a product line, without saying so. The old rows then look like they disappear, and the new ones look like new business. Add a dated note at the point of change, and say which rows it affects.
The second is using abbreviations nobody defined. FY, CY, QTD, and other shorthand feel obvious to the team that uses them daily. Spell each one out the first time it appears, and keep a short glossary at the end if the record is long.
The third is mixing the record's own totals with figures copied from somewhere else, without a source line. When a number came from a finance system, a CRM export, or a previous forecast, name the source and the date it was pulled. Otherwise a later reader cannot tell which figure is current.
A fourth mistake is splitting the year across pages. The header says [year], but the table on page three says only "Q4," and the chart on page five says "FY." Each page can look fine on its own, yet the record as a whole is not. Repeat the period and the calendar type wherever a table or chart appears.
If you inherit an unlabeled record
Sooner or later you will open a record that breaks these rules. Do not silently guess. Check the file's date and its neighbors, such as the previous and next records, to see which calendar the author probably used, then write down what you assumed. Mark the assumption in your own notes or in a comment on the file, so the next reader inherits your reasoning instead of starting from scratch.
Where you can, ask the author. A short message such as "Is Q4 here the calendar quarter or the fiscal one?" can settle in a moment what would otherwise take a long time to work out. If the author has left, say so in the file, and note what you could and could not confirm.
Roll the standard out to your team
A label standard only works if people use it. Write the pattern down in one place, such as the instructions for the forecast record, and link to it from the folder where the records live. A one-page note is enough. It should list the quarter format, the date format, the fiscal calendar, and the owner who answers questions.
Then build the standard into the record itself. If the header block already has fields for the as-of date, the period, and the fiscal calendar, people fill them in rather than invent their own. A blank field is easier to notice than a missing sentence. When someone changes a label, update the note first, so the standard never lags behind the practice.
Finally, review labels in the same meeting where you review the numbers. A quick scan of the header and date fields catches much of the drift before the file is shared. That is far cheaper than explaining a mismatch to someone after the numbers have already been used.
The same pattern should reach file names. A name such as CY[YY]-Q4_forecast_as-of-[year]-[MM]-[DD] sorts in a sensible order, says what the file is, and carries its as-of date even when someone saves it to a desktop. Pick a naming rule with the same care you give the labels inside the file.
Write for the reader you have not met
The reader you should write for is the one who was not there. That person has no memory of the quarter, no access to the chat history, and maybe no idea who you are. Give them the period, the as-of date, the source of each number, and one line on what changed since the last record. Most other detail can live in linked documents.
One line on what changed is worth more than it looks. If the forecast moved by a large amount, or a deal was removed, a single sentence explains why. Without it, the next reader may spend a long time comparing two files to find the cause. Put that line in the record itself, not in the email you sent to your manager. Records get forwarded, and the email often does not come with them.
Save the numbers, not only the link
Many forecast records point to a live dashboard or a shared spreadsheet. The link is convenient, but the data behind it can change after the quarter closes, and the reader will see a different number than the one you wrote down. Save a dated copy of the figures inside the record, or export them to a fixed file, and label that copy with its as-of date.
Keep the link too, but treat it as a pointer rather than the record. A reader who needs to check a figure can follow the link, while a reader who just needs the number has it in the file. This also protects you. If the dashboard is later reorganized or access is restricted, the record still says what it said. Save the file in a format that will still open later, such as a plain spreadsheet export or PDF, and keep the original next to it.
A before and after
Here is a forecast header before and after applying these habits. The bracketed amounts are illustrative.
Original header:
Q4 forecast, as of 11/2
Commit: [amount]
Close date: 12/4
Revised header:
Calendar quarter CY[YY]-Q4 forecast, as of Nov 2, [year]
Commit: [amount]
Expected close date: Dec 4, [year] (estimate, from the deal owner)
The second version is longer, but a reader can answer every basic question from it: which quarter, which calendar, when the numbers were pulled, and whether the close date is an estimate. The first version forces them to guess on every line.
A quick check before you save
Before you hand the record over, read it as someone who was not in the room. Check the following:
- Every quarter label follows the same pattern, with the calendar or fiscal type named.
- Every date is written as a month name or an unambiguous format, with the year where it is not obvious.
- The as-of date and the forecast period appear on the first page, labeled separately.
- The fiscal note sits near the top and answers the three questions above.
- A new reader can say, without asking you, which period and which as-of date the record covers.
That last item is the real test. If a colleague can answer it after reading only the file, the labels are doing their job. If they cannot, the fix is usually one sentence on the first page, not a longer explanation in a meeting the next reader will never attend.
Read the first page twice, once for the numbers and once for the labels. Reviewers often read only for the numbers, which is why labeling errors can survive review.
Related guides: Date and time formats: 4 tools for forecast exports · Close date mismatches: 5 mistakes in forecast records · Commission accrual: 3 mistakes before quarter-end close.