Skip down to the research record

Forecast file versions: 3 retention layers to check

Quota Forecast Editorial Team · Published · 11 min read

Forecast file versions last according to the retention policies, storage plan and computer or account settings that apply to each copy.

Key takeaways

  • Ask which retention policies and labels cover the forecast file.
  • Check your plan's version history and when changes take effect.
  • Confirm computer settings with the administrator.
  • Record recovery options before you need an older version.

Why one forecast file can have several clocks

Most revenue teams picture a forecast file as one document with a history. Someone saves a new version every Friday, and the old ones stay until someone deletes them. That picture is often wrong.

Older versions of a forecast file are shaped by at least three separate layers. The first is the retention rules your organization sets for its storage system. The second is the version history included in your cloud storage plan. The third is the version history settings on the computer or account that syncs the file. Each layer can keep versions for a different length of time, and the layer that keeps a file longest is not always the one you expect.

This guide walks through those layers using vendor documentation as the source. It does not give you one number that applies to your company, because no such number exists. What it gives you is a way to find out where the rules live and which questions to ask. That way, when a director asks "can we get last quarter's version back," you know who to call and what to check first.

Retention policies and retention labels

Start with the retention documentation. Microsoft Learn's retention page explains that you can configure multiple retention policies for Microsoft 365 locations, as well as multiple retention label policies that you publish or auto-apply.

In practice, that means one file can be covered by more than one rule at the same time. A forecast stored in a shared site might sit under a policy that covers the whole site, and also under a label that someone applied to that one document.

The same documentation works through examples of how these rules interact. In one, a document is subject to two retention policies with delete actions of five years and 10 years, and also to a retention label with a delete action of seven years. The example shows how the rules are weighed against each other. Read the full example before you apply its logic to your own files.

Another example describes a site-wide policy that retains items in all SharePoint sites for 10 years after creation, while a retention label specifies a delete action after seven years. According to that example, the document is retained for 10 years, which is the longest retention period. It then says that because the retention label's delete action takes precedence, the document is permanently deleted after 10 years.

Two terms are worth keeping straight. A retention period says how long content must be kept. A delete action says what happens when that period ends. Some rules only keep content, some delete it, and a single file can be governed by rules that disagree. When you read a rule, ask which of the two it sets.

This is easy to miss with forecast files. A label is often applied for a good reason, such as keeping board materials for a long time. Check whether a retention label has been applied to the forecast document itself. Nobody has to decide anything about the forecast for it to be affected.

Ask your IT or records team these questions:

  • Which retention policies cover the site or library where the forecast lives?
  • Have any retention labels been applied to the forecast file?
  • What is the delete action of each rule, not only the retention period? The two can differ.
  • Where should the answers be written down, so the next person does not have to rediscover them?

The version history included in your plan

The second layer is less about policy and more about the storage product. Dropbox's extended version history overview covers three points that matter for forecasting teams.

First, the feature depends on your plan. The page says extended version history is available to customers on Dropbox Plus, Business, Business Plus, Standard, Advanced, or Enterprise. If your company is on a different plan, the details there may not apply, so check what your own plan includes.

Second, every plan has a default period, and an add-on can change it. The page says extended version history is an optional add-on you can purchase to extend your version history beyond the default period provided in your plan. The default comes with the plan. The add-on is the lever for lengthening it. Look up the default length in your plan's details rather than assuming.

Third, removing the add-on takes effect later. According to the page, when you remove the add-on, your selection goes into effect on your next renewal. A cost-cutting decision made mid-quarter may not change which versions are kept until the renewal date. Ask whoever manages billing what date a change would take effect, and whether the versions you need would still be inside the window on that date.

A practical test is to take each version you care about and ask whether it would still fall within the window on the date of your next renewal. If the answer is unclear, the safe move is to ask billing for the answer in writing.

Other storage products use different names and mechanics. Check each product's own documentation for its base period, extension options and change dates.

Computer and organization-wide settings

The third layer is the version history setting on the machines that sync the file. Backblaze's version history page states that version history allows you to recover previous versions of your data. That is the basic promise. It also explains where the setting lives. Version history can be changed for each computer on the 'Overview' page, and an admin can change it for the entire organization.

This matters because a forecast file often lives on more than one machine. A finance analyst may have it synced to a laptop while a sales operations lead keeps a copy on a desktop, and each may follow different settings. If the setting differs between computers, the older versions one person can recover may differ from what a colleague can recover, even for the same file. If an admin has set it for everyone, the individual setting may not be the one that governs.

If you are not sure which setting applies on a given laptop, do not guess from the file's history. Open the Overview page, note the setting, and record the machine's name next to it. Guessing is how teams end up planning around a window that does not exist.

The practical steps are simple but easy to skip:

  • Find out which computers the forecast syncs to, and who owns each one.
  • On each machine, check the version history setting on the Overview page.
  • Ask the admin whether an organization-wide setting is in place, and whether it overrides individual choices.
  • Note the answers so the recovery path is known before anyone needs it.

Putting the three layers together

A single forecast file can pass through all three layers. The storage system may apply retention policies and labels that decide when the file is deleted. The plan decides how far version history reaches by default and whether an add-on extends it. The computer or organization decides which version history setting applies to each person who syncs the file.

The layers do not always agree, and no single one tells the whole story. A file might be kept by a long retention policy but be hard to recover from a laptop whose version history is set short. Or a laptop may hold versions for a long time while the storage plan removes them sooner. The only reliable way to know is to check each layer and compare the results.

A sensible order helps. Start with retention, because it controls deletion. Move to the plan, because it sets the default reach. Finish with the machines and the admin, because they control what each person can actually recover.

A simple way to frame the question for a revenue leader is this: "For this quarter's forecast file, which versions can we recover today, from where, and until what date?" If the answer requires more than one team, that is normal. Forecast files are shared, and the people who manage storage are often not the people who use the file.

Illustrative example: checking a board version

Consider a sales operations team that keeps its quarterly forecast in a shared library. The library sits in a site covered by a retention policy set by the records team. Later, a finance manager tagged the forecast with a retention label because they wanted the board packet kept. After the quarter closes, a regional director asks for the version that went to the board before the final revision.

The records team confirms the site policy and the label. Illustratively, the policy retains the file for 10 years; that alone does not establish which earlier version is recoverable. Next, someone checks the synced copy on the operations lead's desktop. Finally, the admin confirms whether an organization-wide setting applies.

The team records the answers for each layer without assuming they give the same recovery date.

Common mistakes

Three mistakes come up often enough to name.

The first is treating a storage plan's version history as if it were the retention rule. They are separate layers, configured separately, so checking one does not answer the other.

The second is assuming that a setting you cannot see does not exist. Computer and organization-wide settings can both be in place. If you have never opened the Overview page on a machine, you cannot know its current version history setting.

The third is waiting until an employee leaves or a device is replaced before thinking about synced copies. A departing employee's laptop may be reset, and the synced copies on it may go with it. Check what happens to a file when an account closes, before that day arrives.

What to do before you need an old version

Waiting until a forecast is wrong is the most expensive way to learn your recovery options. A few steps taken early save time.

Start with an inventory. List every place a forecast file is stored or synced: the shared drive, the cloud folder, laptop copies, and any export sent to a planning tool. For each location, record the owner and the settings you found using the three layers above.

Then decide what you need to keep. Some teams need a version for every close. Others only need the version that went to leadership. Your answer changes which settings matter. If you need specific snapshots, save them yourself when they become official instead of relying only on version history. A copy with a clear name and date works regardless of vendor.

Finally, schedule a check. Settings change, plans change, and retention policies get updated after new compliance requirements. Put a reminder on the calendar, perhaps at the start of each quarter, to confirm your inventory is still accurate. Start from the vendor pages linked above each time, since they are the source for the rules discussed here.

A short checklist

Use this table as a starting point for each forecast file.

LayerQuestion to answerWhere to look
RetentionWhich policies and labels apply, and what is each delete action?Records or IT team
PlanWhat version history does the plan include, and does an add-on extend it?Plan details and billing
Change datesWhen would any reduction in settings take effect?Billing contact
ComputersWhich machines sync the file, and what is each version history setting?Overview page on each machine
AdminDoes an organization-wide setting apply?Administrator
SnapshotsWhich versions does the team save on purpose?Team's own folder

Recovering a version when you need one

When you do need an older version, work through the layers in an order that avoids wasted effort. Begin with the place most likely to hold the version you want. If the file is in a shared library with retention rules, ask the records team first, since they may be able to see what is preserved. If it lives in a synced folder, check the version history on that copy, then ask the admin about organization-wide settings.

Be honest about what a missing version means. It may have been removed by a rule, may have passed a window in your plan, or may never have been saved in any layer. Those are three different answers, and they lead to different fixes. Writing down the reason helps the team decide whether to change settings.

Document the request, too. Record who asked, which version was needed, and what was found. The next search then starts from notes rather than memory. For a deleted deal rather than a file version, see recovering deleted sales records.

Keep the tone calm when this happens. A missing forecast version is usually a process gap rather than a personal failure, and the fix is typically a tighter inventory and a better snapshot habit.

Limits of this guide

This guide relies on vendor documentation for three products. Those pages describe specific features and may be updated. Your organization may use other tools, or may have set custom policies that no public page describes. Treat the sources here as a map of where the rules live, not a complete answer for your company. Check the current pages, and confirm details with the people who administer your systems before you rely on a version being available.

What to check today

Choose the forecast version you would need for a board question today. Use the checklist above to record where it is stored, who manages it and which recovery settings still need confirmation.

Related guides: AI call scorecard checks: 5 rules before the forecast · Audit log retention: 8 options and license checks · BitLocker and FileVault: 8 steps for forecast files.

Questions

Does a retention label alone decide when a file is deleted?

No; retention policies and labels can interact. Read the applicable retention periods and delete actions together before assuming the label gives the deletion date.

When does removing the Dropbox add-on take effect?

Removing the extended version history add-on takes effect on your next renewal. Confirm that date with whoever manages billing.

Where can I check Backblaze version history settings?

Check the Overview page for the computer's setting. Ask the admin whether an organization-wide setting applies.

Sources