Microsoft 365 Backup offers two restore windows for OneDrive and SharePoint coaching files, with finer choices for recent changes.
Key takeaways
- Write down when a file was changed before requesting a restore.
- Check which restore window applies with your IT admin.
- Compare recovered content before replacing the current file.
- Save important drafts separately and tell the file owner about any restore.
Why restore windows matter to a coaching team
If you manage front-line reps, more of your working life sits in Microsoft 365 than you might notice. Coaching notes live in a folder for each rep. Call review files grow after every session. Rep plans get edited when quotas shift or a territory changes. Most days nobody thinks about these files until one goes missing, gets overwritten by a teammate, or ends up with the wrong content after a bulk edit.
When that happens, the first question is usually "can we get it back?" The better question is "how far back can we go, and how precisely?" Knowing where each window starts and stops tells you which version you can realistically recover, and how much recent work you might lose along the way.
This post explains those two windows in plain terms. It also covers a common misreading of the "10-minute" figure, a point about disaster recovery copies, and a short routine you can share with your team. It is general guidance for managers, not an admin runbook. Your IT team sets up the service and decides who can run restores, so treat the details below as questions to bring to them.
The first window: the last two weeks
The first window covers the trailing two weeks. Microsoft's guide says that for OneDrive and SharePoint, the recovery point objective for that trailing period is 10 minutes ( Microsoft Learn guide). A recovery point objective measures how much recent work you could lose. Read as a number of minutes, it means the restore points inside this window are close together. You are not choosing between a few broad dates. You can aim for a moment just before the mistake.
The guide gives a concrete example. If it is Monday at 8:00 AM, you can go back to any 10-minute period up to two weeks in the past ( Microsoft Learn guide). Apply that to a real case. A rep plan gets overwritten on Tuesday afternoon. If you know the edit happened around mid-afternoon, you can look for the 10-minute period just before it. The restored file then shows the plan as it stood before the bad change.
Speed still matters, because a mistake only stays inside this window for two weeks. A problem you notice on Thursday is a very different job from one you notice the following month. Write down the approximate time of the edit while it is still fresh. A rough timestamp from your own notes or from the file's edit history beats a vague memory of "sometime last week." For a consistent record, use the timestamped call notes guide.
The window does not replace careful editing. It gives you a reliable way back when an edit was not caught in time. Treat it as a second line of defense, and keep the first line in place.
The second window: one week at a time, back to 52 weeks
The second window starts where the first one ends. The guide says that beyond two weeks, you can go to any one-week period of time in the past from 2 to 52 weeks ago ( Microsoft Learn guide). The change matters. You stop choosing a 10-minute slot and start choosing a week.
That changes how you handle older problems. Suppose a coaching form was altered in March, but nobody noticed until September. You would not pick the exact moment of the change. You would pick the one-week period that contains a clean version, then check the content before you accept it. Expect some comparison work. The week you pick may include good edits alongside the bad ones, so you may need to copy specific sections back by hand.
The range also helps with planning. A window that reaches back 52 weeks gives you a long reach for quarterly reviews and year-end rep plans. But the reach only helps if you know roughly when a problem began. Finding the start date is often the hardest part of an older restore. Teams that record change dates in their files have a much easier time here.
Anything older than 52 weeks falls outside what this post covers, so plan for those cases separately, through your own archive habits or with your IT team.
What the 10-minute figure does not mean
Many managers read "10 minutes" as a promise that Microsoft takes a snapshot of every file every 10 minutes. The guide addresses that reading directly. It says: "Let's start with what it doesn't mean: We're not taking snapshots every 10 minutes." ( Microsoft Learn guide)
The accurate reading comes next in the same guide. A backup frequency of 10 minutes means that all changes made to the item are saved as a new version every 10 minutes, regardless of how many changes occur within that 10-minute period ( Microsoft Learn guide). The phrase "regardless of how many changes" carries most of the meaning. The interval sets when a version is saved. It does not set how many edits end up inside each saved version.
For a coaching team, this has practical effects. If you edit a call review file five times in four minutes, do not assume each edit is a separate restore point. If you make a change and reverse it within a few minutes, the state you wanted to keep may never be captured as its own version. The safest habit is to save meaningful milestones yourself, such as a note marked final after a session.
This matters most for drafts. A draft rep plan that you rework several times in one sitting may appear in the restore list as a single state, or not at all as the exact draft you had in mind. If a particular draft matters, such as a plan you share with a rep for sign-off, save a copy with a clear name when you send it.
The disaster recovery copy is not a history book
The guide also makes a distinction that matters for anyone who assumes a backup holds every old version. It says: "A DR copy with Microsoft 365 maintains the current state of content, not any historical versions from prior points in time." ( Microsoft Learn guide)
If your plan for historical records relies on a disaster recovery copy, that plan has a gap.
Both ideas sound like "a copy of our files," which is why this is easy to miss. Ask your IT team which copies exist in your environment and what each one is meant to do. Then write down, for your team, which tool answers which question. A simple table in your shared guide works well: one row for "recover from a mistake," one for "see an old version," and one for "recover from a major loss."
Mapping your coaching files to the two windows
Not every file behaves the same way. The table below groups mistakes by when they happened and shows which window applies. The windows come from the guide. The file examples that follow are general and depend on how your team works.
| When the mistake happened | Window that applies | How precisely you can choose |
|---|---|---|
| Within the last two weeks | First window | 10-minute periods |
| 2 to 52 weeks ago | Second window | One-week periods |
| Older than 52 weeks | Outside these two windows | Plan separately with your IT team |
Different coaching files tend to fall into different patterns:
- Rep plans get edited often. Recent edits fall in the first window, which makes accidental overwrites the easiest to fix.
- Call review files grow session by session. A mistake in an older session usually becomes a week-level restore, so you may be checking several sessions at once.
- Coaching notes are often revised after a conversation. Save a final version inside the note itself, so your record does not depend on a restore. Problems may surface weeks later, which points toward the second window and a more careful comparison.
- Folder reorganizations can move many files at once. Check where the files went before you reach for a restore, since a move is not always a loss.
A rep plan that a manager reads every Monday is noticed quickly when something goes wrong. A form used once a quarter may sit unchanged for weeks, so a bad edit can go unseen until someone opens it again. Your restore routine should match that rhythm.
Common mistakes managers make
Most restore problems come from a small set of habits. None are hard to fix, but they are easy to fall into when a team is busy.
Waiting too long to report a problem can make the fix less precise. Encourage your team to flag problems on the day they notice them.
Another mistake is restoring over the live file without checking. A restored version can look right at a glance and still be missing a recent good edit. If your restore option supports a separate location, restore there first, then compare.
Another mistake is fixing a problem quietly. If a rep's plan was restored, the rep should know what changed. Silence can make a routine fix look like a hidden edit, and that damages trust faster than the original mistake did.
A restore routine you can share with your team
Write down a short routine so everyone handles problems the same way. Adapt the steps to your team's tools and to your admin's guidance.
- Write down what went wrong and when. Use your best estimate. A rough timestamp from the file's edit history or your own notes is a useful start.
- Check which window applies. Match the mistake's age to the table above before choosing a recovery point.
- Restore to a new location first. If your restore option allows it, do not overwrite the live file until you have checked the restored version.
- Compare before you accept. Confirm that the content you need is there and that the good recent edits are included. If they are missing, copy those sections back by hand.
- Tell the owner. If a rep's plan or call review was restored, let the rep know what changed and why.
- Record the fix. A one-line note in the folder about what was restored, from which point, and by whom keeps the history clear for the next person.
Run this routine the same way every time. If someone on your team is new to restores, walk through it once on a test file before they face a real one. For related recovery questions, see the guide to getting back an old coaching document version.
Illustrative example: checking a recovered plan
A rep plan is overwritten 10 minutes after a coaching session. Record the time of the overwrite and ask your admin to identify a restore point before it. If a separate restore location is available, compare the recovered plan there. Check the session's good edits before replacing the current file, then tell the rep what changed.
Today, choose one coaching folder and ask your IT admin to confirm its backup coverage and who handles restore requests.
Questions to take to your IT admin
You do not need to run restores yourself to benefit from knowing the windows. Bring a short list of questions to your admin:
Is Microsoft 365 Backup in use for our coaching files?
Your IT admin can confirm whether the OneDrive and SharePoint locations holding those files are covered. Include shared team sites and the folders your reps use.
Who can run a restore?
Your IT team decides who can run restores. Ask whether managers should request one through a ticket or a named contact.
Where are restore requests logged?
Ask your admin where your team records what was recovered, from which point, and when. Use that record when checking a completed restore.
What is our process for older files?
Agree on an archive or recovery process with your IT team. Ask which copies exist in your environment and which are meant to hold older versions.
Write the answers down and share them with your managers. A one-page summary is enough. The goal is that nobody has to guess what the backup can do during a stressful moment.
Protecting coaching files before anything goes wrong
Restores are a safety net, not a filing system. Some habits reduce how often you need one, and they make any restore faster when you do need it.
Use a clear folder pattern. One folder for each rep, with a consistent naming format that includes the date, makes it easier to find the right version and see what changed. A file named "call review, October session" is much easier to match to a timeline than "call review final v3." Dates in names also make it obvious which file belongs to which session.
Finalize notes at milestones. When a coaching note is done, mark it as final and say so in the first line. Milestones you record on purpose often reflect a decision, which is more useful than any automatic version.
Keep a short change log for big edits. If you rewrite a rep plan or restructure a form, add a line with the date and the reason. A log tells you what to look for and roughly when, and it helps when a rep asks why their plan changed.
Avoid bulk edits on live files. Run large changes on a copy first, then move the results into place once you have checked them. If a bulk edit goes wrong, you can compare against the copy rather than rebuilding the original from a restore point.
Review key folders on a schedule. A short monthly check can help you catch problems, but does not ensure they remain inside the first window.