Skip down to the research record

Backup frequency: 4 survey shares for forecasts

Quota Forecast Editorial Team · Published · 12 min read

A 2023 survey of U.S. computer owners found that 11% back up their data daily, 8% weekly, 15% monthly, and 18% never.

Key takeaways

  • Confirm where your working forecast file lives.
  • Check the backup with IT rather than relying on a reported habit.
  • Save dated copies after deal reviews and before commit calls.
  • Test a restore and open the recovered file before quarter end.

Backblaze runs the survey each June with The Harris Poll. Its results offer a useful starting point for one planning question: how much forecast work would survive a bad day?

A forecast file has a short, busy life. Its numbers change most days, and a rep may rebuild the same workbook several times before quarter end. If that file is lost, corrupted, or overwritten, the damage goes beyond one missing spreadsheet. The pipeline view your team uses to commit numbers, plan hiring, and brief finance may go with it. So the useful question is not whether a file is "in the cloud." It is how far back you can recover it on the day something breaks.

We will follow one example case through every section. The example is a sales rep who keeps a weekly forecast workbook on a company laptop. This rep has never thought much about backups, and that is why the example is useful. For each of the four groups, we will ask what it would mean for this rep's file, and what a revenue leader can do to keep that file recoverable through quarter end.

Where the four shares come from

The survey asks a single core question, and the answer is self-reported. People say how often they back up all the data on their computer. That means the shares describe what owners say they do, not what a technical audit would find. The survey also covers people who own a computer, which is a different group from a sales team. Your company may run backups centrally on every laptop, and a survey cannot see that. Treat the shares as a picture of general habits, not as a measure of your own setup.

The survey results for Americans who own a computer:

  • Daily: 11% backed up their data at least once a day in 2023, compared with 10% in 2022 and 11% in 2021.
  • Weekly: 8% in 2023, and 7% in each of the two previous years.
  • Monthly: 15% in 2023, compared with 13% and 14% in the two previous years.
  • Never: 18% said they had never backed up data in 2023, compared with 20% in each of the prior two years.

A revenue leader reads these numbers differently from a survey analyst. The question is not which habit is most popular. The question is how much of a team's forecast history would survive a bad day. Two of these figures matter most for planning. The daily group is the tightest of the backed-up groups, but it is also one of the smaller ones. The never group, at 18%, is the largest of the four. That is the number a revenue leader should keep in mind, because it describes owners who say they have never backed up data.

The example rep's file in each group

The first question is which group the rep's habits fall into. Ask, do not assume. The answer shapes what recovery looks like if the laptop fails or the file is deleted.

If this rep backs up daily and the backup succeeds, a loss could cost the work done since the last backup. Daily is the tightest window of the four, and that is a real advantage. The label alone is not proof that the file can be recovered. A daily backup that has been quietly failing for a month gives the same result as no backup at all.

If this rep backs up weekly, a loss could take back up to a week of edits. For a forecast that gets revised after every deal review, a week can hold several versions of the commit numbers. Weekly is the smallest of the three backed-up groups in the survey, at 8%, which is one more reason to check it rather than assume it.

If this rep backs up monthly, a loss could take back a month. For a forecast that is rebuilt through the quarter, that gap can wipe out a large part of the quarter's history. Monthly is the most common of the backed-up groups at 15%, which is a reminder that a backup habit can look reassuring while still leaving a long gap.

If this rep never backs up, check whether the laptop is the only copy. A failed drive or a lost laptop would take the file and its history with it, unless the rep has made copies by hand. Hand copies tend to be inconsistent, so they are a poor plan on their own.

The lesson for this file is that the recovery target should follow the file, not the person. A forecast that drives commit decisions needs the same protection whatever the rep's personal habits happen to be.

What to check beyond the survey

For forecast files, evidence means a recent copy that opens, a location your company controls, and a restore that has been tried at least once.

Reading small changes without overreading

Weekly and monthly results look much like earlier years, and the overall picture stays close to what came before.

The survey is run with 95% confidence, and the post notes that if it were collected 100 times, differences like these would appear by chance in only five of those collections, assuming no real change in the group.

For a revenue leader, the practical reading is this. A one-point change in a national survey is not a reason to change how you protect forecast files. Plan recovery around the risk each file carries.

Why the laptop is the weak point

Laptops fail, get lost, get stolen, and get replaced. Each of these events can separate a person from their working files in a single day. A rep who travels, works from several locations, or changes devices during a quarter multiplies those chances. Forecast work often happens in the gaps between meetings, on whatever device is nearby, which makes the laptop a weak home for the only copy.

Devices are not the only issue. A file can be deleted, overwritten with an older version, or damaged by a sync conflict. None of these needs a broken laptop. That is why the recovery question has to cover the file's location and its history, not just the hardware it sits on.

Checking where the file really lives

Many teams keep forecast files in shared sites rather than on individual laptops. If the workbook lives in a SharePoint site, Microsoft's SharePoint recovery page says: "When you delete items (including OneDrive files) from a SharePoint site, they're sent to the site Recycle Bin (also called the first-stage Recycle Bin), from where you can restore them if you need to."

Dropbox's own guidance on sharing puts the point plainly: "Sharing large files with Dropbox helps you stay in control." For a forecast, control means knowing which copy is the master, who can edit it, and which backup covers it. The same question applies to any shared workbook.

That gives the rep a first recovery step. It is a recycle bin for deleted items, though, and it does not answer every question. The same page says that customers also have the option to use Microsoft 365 Backup for data recovery. It describes that product as offering a longer protection time and fast recovery from common business continuity and disaster recovery scenarios, such as ransomware or accidental or malicious employee content overwrite or deletion.

Ask your IT team whether Microsoft 365 Backup is in use for your company and what period it covers. A revenue leader does not need to run the backup. You do need to know which option applies to each rep's file, and where that file would be restored from. Use the backup and recovery checks to guide that conversation.

Setting a recovery target for each rep

A recovery target is a plain statement: for this file, how much work can we afford to redo? For a forecast that feeds a commit call, most leaders would say the answer is very little. Write the target down with the rep, because a target nobody has heard does not protect anything.

Start with three questions for each rep. Where is the working file saved? What copy exists on the day the laptop is lost? How long would it take to restore the file and check it against the latest deal notes? The answers show whether the rep is in a strong, weak, or unknown position, and they will differ from one rep to the next.

Keep the list short. A revenue leader does not need every rep's personal backup settings. Use a short check at regular intervals, plus a confirmed shared location for each forecast file, to identify recovery gaps.

How often to save a dated copy

The right frequency depends on how fast the forecast changes and how costly a loss would be. A forecast that changes after every deal review needs more frequent copies than one that changes once a month.

Survey groupShare of owners (2023)Illustrative loss if the backup succeeds
Daily11%Illustrative: work since the last daily backup
Weekly8%Illustrative: up to a week of edits
Monthly15%Illustrative: up to a month of edits
Never18%Illustrative: the whole file if no other copy exists

For a forecast file during quarter end, a practical rhythm is a copy at each checkpoint, plus whatever automatic backup your company already runs. Keep the checkpoint copies in the shared location, not only on the laptop. Name each copy with the date and the checkpoint, such as "after deal review," so the team can tell versions apart at a glance. The weekly pipeline snapshot guide can help with the related export task.

Do not overwrite the last good copy. Keep the previous version until the new one has been opened and checked. A copy made in a hurry is only useful if it opens, so the habit of opening it is as important as the habit of saving it.

Illustrative example: checking a recovered file

Suppose a forecast has 20 deal rows when a checkpoint copy is saved. The rep then edits 5 rows before losing the working file. Restoring the checkpoint copy brings back the 20 rows, but those 5 later edits still need to be rebuilt from deal notes. Open the recovered copy and compare it with those notes before using it for the commit call. This illustrates the work since the last copy, not a survey result or a promised recovery time.

A routine for a rep through quarter end

Here is a routine for each rep and the team. It is simple, and none of it needs a special tool.

  1. Confirm where the working file lives. Move it into a shared location that your company backs up, instead of keeping the only copy on the laptop.
  2. Ask the rep which of the four groups describes the laptop's backups today, and check the answer with IT. The self-reported answer is a starting point, not a final check.
  3. Save a dated copy at natural checkpoints, such as after each deal review and before each commit call.
  4. Keep the file somewhere another person can open it. If the rep is out, your team should be able to reach the forecast without a phone call.
  5. Test one restore before quarter end. Pick an earlier version, restore it to a new folder, and open it. A backup that has never been restored is an assumption.
  6. Confirm with IT whether Microsoft 365 Backup or a similar service covers the shared location, and what it covers.

Repeat the routine at the start of the last few weeks of the quarter, since that is when the file changes most and the cost of a loss is highest.

Owners matter as much as steps. Give each step a named person on the team, so that a missed checkpoint is noticed by someone rather than discovered at the commit call. The rep usually owns the working file, the revenue leader owns the standard, and IT owns the backup settings and any restore. When those lines are written down, a problem has an obvious first call to make.

Talking to a rep about backups without blame

Many reps will hear a backup question as a judgment about their work. Frame it as a question about the forecast, not the person. The forecast drives decisions for the whole team, so its safety is a shared concern, and nobody should feel singled out for asking.

Habits also vary in ways a manager cannot guess.

A short script helps. Ask which file the forecast is in, where it is saved, and what happens if the laptop stops working tomorrow. Then ask what the rep would need from you to make the answer better, such as access to a shared folder or a slot with IT. Write down the answers, and agree on one change for the next checkpoint. Keep the conversation short and specific.

Reps who travel or work from several devices need extra attention. Ask which device the forecast is edited on most often, and whether that device is the only place the file lives. The answer may differ from what the rep expects, and it is far easier to fix before a laptop is lost than after.

When a file goes missing on a bad day

Suppose the rep opens the workbook one morning and finds it gone. Stay calm and work through the same steps in order. First, if the file was deleted from a SharePoint site, check that site's recycle bin. Second, check whether a dated copy exists from the last checkpoint. Third, ask IT whether a broader backup can recover the file to a point before the problem.

Two habits make a bad day easier. The first is a clear owner: one named person knows where the file lives and who to call. The second is a written record of the last good copy, so the team can say exactly how much work needs to be rebuilt. Rebuilding a forecast from your CRM and call notes is slow, but it is possible. Rebuilding it from memory is much harder.

Your next step today

Choose your current forecast workbook and ask IT to help restore an earlier version to a new folder today. Open it and compare it with the latest deal notes so you know what would need rebuilding.

Related guides: Stalled deal benchmarks: 2 survey figures to compare · restic backup exit codes: 3 results to check.

Questions about forecast backups

Does a daily backup guarantee recovery?

No: a daily schedule alone does not prove the backup succeeded. Check a recent copy and try restoring it.

Is a shared location enough?

A shared location needs a confirmed backup and recovery path. Ask IT which option covers the workbook and where a restored copy would come from.

Sources