Pause and identify the file that changed

Imagine a village employee updating a shared equipment spreadsheet. A paste replaces several rows, and the mistake is noticed after the file has saved. Another employee added a new asset earlier that morning. The office needs the missing information back while preserving that valid update. Before rebuilding the sheet from memory, check whether an earlier version is available.

Pause further edits to the affected file and notify its working owner. Record the file name, its approved location or link, what changed, and the approximate time it last looked correct. Include any known changes made by coworkers. A useful support request identifies the actual file and affected content, so the owner and IT can assess a recovery option together.

Confirm where the working spreadsheet is stored

Microsoft’s guidance says version history in Microsoft 365 works for files stored in OneDrive or SharePoint in Microsoft 365. Confirm the location of the spreadsheet you are actually editing. A downloaded attachment or a separate local copy may be different from the shared working file. Having Microsoft 365 installed does not establish that every document has the same history available.

Open the approved shared location using your individual work account and confirm the file identity with the owner. Ask IT for help if the link, location, or available history is unclear. Do not move the spreadsheet into a new location just to try to obtain missing history. Keep the investigation tied to the existing file and the systems that already hold it.

Inspect an earlier version before restoring it

Microsoft documents the ability to view an earlier version without overwriting the current file. In supported Office apps, Version History lets you open a selected version separately. Use that inspection step to find the missing rows, formulas, or worksheet. Follow the controls available in your approved application, and ask support to guide you if the interface differs.

Compare the candidate with the current spreadsheet and your notes about the mistake. In the village example, check both the overwritten equipment entries and the asset added that morning. A timestamp helps locate a candidate, but the contents determine whether it is useful. Record which version contains the needed information and which later updates would need to be retained.

Coordinate a restore with the people using the file

Agree on the correction with the file owner and affected coworkers. Restoring a whole spreadsheet changes the current working version; it can also bring back older values in areas unrelated to the mistake. The owner may decide that recovering specific information into the current sheet is more appropriate. Have the responsible staff member or IT carry out the approved approach.

Microsoft’s OneDrive instructions explain that the selected version becomes current and the previously current version remains in the history list. Its SharePoint instructions describe creating a copy of the selected earlier version as the latest version. Coordinate a pause in editing while the change is made, tell coworkers when it is ready, and confirm everyone resumes from the agreed file location.

Check the work before calling it recovered

Have someone familiar with the spreadsheet verify the result. Check the affected rows, formulas, totals, and relevant worksheets, along with valid changes made after the version selected for recovery. A spreadsheet opening successfully does not confirm that the intended correction is complete. For an equipment list, that means checking the recovered entries and the newly added asset against the office’s approved information.

Record the chosen correction, the version or information used, the person who checked it, and any follow-up needed. If the spreadsheet feeds a report or another document, identify what must be regenerated or checked before it is used. Keep temporary comparison copies in approved locations and agree with the owner how they will be handled so staff can still identify the working copy.

Ask about history limits before an urgent mistake

Available versions depend on the library’s configuration. Microsoft describes automatic limits that keep fewer older versions and manual limits based on version count and, where configured, age. Ask your IT team which settings apply to the important shared libraries your departments use. Avoid assuming that an exact date or every saved change will remain available indefinitely.

Microsoft also explains that versions trimmed by automatic settings or expired under manual time limits cannot be restored from the recycle bin after they are purged. If the version you need is missing, give IT the file details and timeframe so it can assess other available recovery options. Include these libraries in your wider backup and recovery conversation, with a clear explanation of what is covered and who can perform recovery.

Give the office a short recovery checklist

IT for townships should make ordinary mistakes easier to report and resolve. At your next Michigan IT services review, use an approved practice spreadsheet to walk through these questions with the employee who owns the workflow.

  • Have we identified the affected working file and paused further edits?
  • Can we locate its history in the approved Microsoft 365 location?
  • Does an inspected version contain the information we need?
  • Which valid later changes must the correction preserve?
  • Who approves the correction and verifies the resulting spreadsheet?
  • Who can help when a needed version is unavailable?

YOUR NEXT STEP

Practice inspecting and recovering an earlier version of a sample spreadsheet with its owner. Document the file location, approval step, and checks needed to preserve valid coworker changes.

Need a hand putting a plan in place? Explore our Managed IT services for Michigan municipalities or talk with our team.

Further reading