Restoring yesterday’s spreadsheet can bring back a damaged value and remove today’s valid work at the same time. When the damage affects a few cells, keep the current file and recover the specific values you can verify. Use an earlier version as evidence, rather than immediately replacing the whole sheet.
This approach suits a shared project or operations tracker. It requires someone with permission to inspect the history and someone who can resolve conflicting business information. If you cannot identify the correct value, mark the uncertainty instead of guessing.
Pause edits and preserve the current state
Tell collaborators which sheet you are repairing and ask them to pause changes briefly. Agree on a person responsible for the repair. If a form, import, or automation writes to the file, arrange a safe pause with its owner; do not disconnect it without understanding the consequence.
Make a copy of the current spreadsheet before changing values. Give it a clear name such as Project tracker — before recovery — 6 October. Keep the original sharing boundary: a repair copy should not become a new public document or expose client information to additional people.
Record the affected tab, columns, and approximate time of the overwrite. If an imported value or a repeating formula caused the damage, address that cause before resuming writes. Otherwise, the same process may overwrite the repair.
Copy an earlier version
Google’s version-history instructions explain how to inspect and copy earlier versions on a computer. You need edit permission to browse the history. Open version history through the Last edit control, find a version before the damage, and use its More menu to make a copy.
Choose a version that actually contains the missing value. The latest version before the reported incident is a starting point, not proof that every value in it is correct. Keep the recovery copy separate from the live tracker while comparing it.
Cell edit history can help, but it is incomplete: certain structural, formatting, and formula-driven changes do not appear there. Use the file history and the underlying business record when necessary. If you cannot see the needed version, ask the file owner or an editor; do not promise that every historical state is recoverable.
Match by identity, not by row position
Sorting, inserting, or deleting rows can move a project. Compare a stable project or record ID in both copies. If the tracker has no reliable ID, use enough fields to distinguish the record and ask its owner to confirm the match. A repeated client name alone may identify several jobs.
Here is a fictional recovery example:
| Record ID | Earlier version | Current version | Recovery decision |
|---|---|---|---|
| JOB-104 | Due October 15 | Due October 5 after an accidental overwrite | Restore October 15 after the project owner confirms it |
| JOB-105 | In progress | Complete, with a confirmed handoff today | Keep the current completion |
| JOB-106 | Not present | New job entered today | Keep the new record |
| JOB-107 | Assigned to Alex | Assigned to Jordan | Ask who owns the work now; do not overwrite automatically |
Only JOB-104 has an agreed restoration. Replacing the entire sheet with the earlier version would discard JOB-106 and reverse a valid update to JOB-105.
Build a small recovery log
For each damaged item, record the ID, field, current value, proposed recovered value, evidence, and decision owner. Add restore, keep current, or needs confirmation as the outcome. This gives collaborators a usable explanation without requiring them to compare entire files.
Restore confirmed cells only. Treat formulas separately from typed values: check the intended references and the affected range before copying a formula. Do not paste entire rows if that would also overwrite newer notes, links, or status changes.
Verify before reopening the tracker
Check every restored field against the recovery log. Then check that today’s valid records and updates remain. Recalculate any affected totals and look for errors caused by missing references or shifted ranges.
Ask the responsible person to confirm unresolved business values, then let collaborators resume editing. Keep the before-recovery copy and log according to your existing retention practice. Share the result in one short note: which fields were restored, which newer changes were preserved, and which items remain uncertain.
Whole-file restoration can be appropriate for broad damage when nobody needs the intervening changes. That is a separate, agreed decision. For a few overwritten cells, a documented selective repair gives you a clearer result and less work to reconstruct afterward.