Operations & Systems

Spreadsheet Version Control: Record Which Workbook a Business Decision Used

The team approves a plan at ten. Two people update the workbook before lunch. At three, someone asks which number the approval covered.

The current sheet cannot answer that question alone.

Spreadsheet version control should preserve the state a decision used. Name the workbook, the review version, the input cutoff, the assumptions, and the person accepting the result.

The method below creates that decision record for a small team. Its fields and review sequence are editorial recommendations. The Google Sheets example uses fictional collaborators and synthetic planning inputs. It describes no live account or completed business engagement.

Separate the Five Things People Call a Version

Start by asking what the word version means in the conversation. Different answers require different evidence.

Term Meaning in this review method What it does not establish
Filename A human-readable label on a file Which contents a decision used
Cloud revision A historical state shown by the storage product Business acceptance of that state
Named version A historical state given a review label Approval of its assumptions or output
Exported copy A separate file captured in a chosen format Equivalent behavior across applications or complete decision evidence
Approved decision snapshot A retained workbook state connected to an explicit decision record Authority to use later edits without another review

These distinctions define the proposed method. They are not product guarantees.

A filename such as Capacity final leaves the review boundary unspecified. Add the exact source identity and review label to the decision record. If a review copy has a different identity, record both.

An exported copy can be useful supporting material. Verify what it contains before relying on it. A screenshot of one result does not establish the inputs or formulas behind that result.

Keep the decision record readable without opening every attachment. A later operator should be able to identify the accepted output and its conditions first.

State the Input Cutoff Before Review Starts

For the fictional example, the team plans next week's service capacity. Use synthetic contributor labels rather than personal records.

Set the input cutoff to 2026.10.28 at 09:00 UTC. The review starts at 10:00 UTC. Those times describe different boundaries: what the inputs include and when the reviewer examines them.

Write the cutoff above the planning table. Specify which commitments belong in the plan. For this example, include only commitments confirmed by the cutoff. Track later additions separately until the owner chooses how to handle them.

Record the roster, scheduled hours, unavailable hours, and committed hours. Name who accepted each source. If an input is missing, leave it unresolved instead of treating the review time as proof of completeness.

An automated refresh in a Google Sheets workflow should also have a visible data boundary. A refresh timestamp records activity. The decision record needs the period that activity established.

Before naming a review version, have the owner confirm the input boundary in writing. Otherwise the team can preserve a precise workbook state while disagreeing about what it represents.

Create a Named Review Version in Google Sheets

In Google Sheets on a computer, open version history through Last edit. Select the review state, open its More menu, and choose Name this version. Use an identifiable label such as CAP-042 review inputs through 2026.10.28 09:00 UTC.

Google documents named versions as a way to prevent their merging. Sheets allows up to fifteen named versions. Browsing earlier versions requires edit permission. These limits make a name useful for locating a state, rather than sufficient evidence of business approval.

Copy the label into the decision record. Record the workbook link, the review time, and the output cell. The name should be specific enough for someone else to locate the intended state.

In this proposed method, the reviewer examines a separate review copy. Label that copy as review material. Record its connection to the source workbook and selected historical state.

Choose the review boundary before inviting corrections. If the reviewer finds an incorrect formula, preserve the finding. Prepare a revised candidate and identify it separately before seeking acceptance.

Work Through a Fictional Decision

Two fictional collaborators maintain the planning sheet. Mira owns the capacity inputs. Leon reviews the operational plan. These roles describe the example only.

At the cutoff, the sheet contains three contributors. Remaining hours are eight, four, and six. Their total is eighteen. A separate assumption uses six hours per project block, producing three provisional blocks.

Mira names the review version CAP-042 review inputs through 2026.10.28 09:00 UTC. She records the source identity and prepares the review copy. Leon checks the three input rows and the total.

At 10:20 UTC, Leon accepts eighteen remaining hours for the planning discussion. His acceptance excludes any promise that all three blocks fit the calendar. Skill requirements and scheduling still need review.

The decision record states the output in hours first. It preserves the six-hour assumption separately. That separation lets a later reader distinguish the accepted arithmetic from a provisional interpretation.

Leon records the result against the reviewed state. He does not authorize future values merely by accepting this one. The live workbook can continue to change while CAP-042 remains the record of the earlier decision.

Use a Decision Handoff Table

Keep one record per decision. If the team selects a different output after review, create a replacement decision entry and connect it to the earlier one.

Field Fictional CAP-042 entry
Decision Use the reviewed capacity figure for next week's planning discussion
Source workbook identity Team capacity workbook, exact source link retained internally
Review copy identity CAP-042 review copy, separate link retained internally
Revision Named source version: CAP-042 review inputs through 2026.10.28 09:00 UTC
Input cutoff 2026.10.28 09:00 UTC; confirmed commitments only
Review observation 2026.10.28 10:00 UTC; three contributor rows examined
Assumptions Non-overlapping deductions; six hours per provisional project block
Chosen output E6: 18 remaining hours; F6: 3 provisional blocks
Reviewer Leon, arithmetic and evidence review
Decision owner Leon, capacity figure accepted at 10:20 UTC for planning discussion only
Open conditions Skill fit and calendar feasibility remain unapproved
Later changes Record as new candidates; do not overwrite CAP-042

Use actual links in an internal record. This public example intentionally contains no private workspace address.

Ask the receiver to locate the named state and the review copy. Then ask them to explain which output was accepted. Correct the record if either answer depends on the original author's memory.

Put this procedure in the team's operating documentation. Keep the procedure separate from the individual decision records it governs.

Handle Two Collaborators Editing After Review

At 11:00 UTC, Mira adds four committed hours to Person C's row. Remaining hours become fourteen across the team. This change describes new planning information after the cutoff.

At 11:15 UTC, Leon changes the provisional project-block assumption from six hours to seven. Fourteen divided by seven produces two blocks. The live sheet now answers a different question from the reviewed eighteen-hour state.

Both changes may deserve consideration. Neither should silently replace the evidence for CAP-042.

Record the changes with their times, authors, and reasons. Keep the earlier named state and review copy available. Prepare CAP-043 as the next review candidate with a new cutoff and assumption record.

The comparison is explicit: CAP-042 used eighteen hours and a six-hour assumption. CAP-043 proposes fourteen hours and a seven-hour assumption. The reduced block count has two causes. Do not attribute the whole difference to newly committed work.

If the team still needs to act on CAP-042, ask the decision owner whether the later information changes that action. Record the answer. Preserving an earlier decision does not require continuing to use it after its assumptions change.

Know What History Cannot Explain

Google's history guidance says revisions may merge. Cell edit history can omit row or column additions and deletions, formatting, and formula-driven changes. It also omits changes before a past-version restoration. Use the decision record to preserve business reasons and approval conditions beyond that history.

Do not infer an explanation from a changed number. Ask which input or rule changed, then compare the relevant states. Record an unknown reason as unknown.

A collaborator's name in history identifies an editor. It does not establish that the editor approved an operational consequence. Keep editing responsibility and decision authority explicit.

For the fictional plan, history can support inspection of the changes. The handoff table supplies the accepted cutoff and Leon's bounded decision. Read those records together before interpreting the live total.

Avoid turning every keystroke into a decision entry. Record the state selected for review, the accepted output, and material changes that could alter its use. Choose that threshold with the decision owner.

Check Review Copies and Access

Google documents making a copy of an earlier version. The copy flow includes an option to share with the same people. Verify the resulting access instead of assuming the review audience can open it.

In this method, give the reviewer access to the material needed for the decision. Check the source identity, copy identity, and selected state from the receiver's perspective. Keep confidential inputs within the team's authorized workspace.

If the receiver cannot browse source history, arrange an authorized review copy and the supporting record. Do not broaden access to unrelated material merely to make one review convenient.

Check the copy before accepting it as evidence. Compare the relevant input rows, formula text, output value, and assumptions with the selected source state. Record any difference that affects interpretation.

An operations handover should include a location check. Have the next person retrieve CAP-042 without asking Mira which copy she meant. A link that only the author can use leaves the handoff incomplete.

Keep Restoration Separate From Approval

Google documents that restoring a spreadsheet clears cell edit history for changes before the restoration. Review that restoration limitation before changing the live workbook. Prefer examining a copy when the task is to understand an earlier decision.

Restoration changes the current working state. Approval records acceptance for a stated purpose. Keep those actions separate in the procedure and the decision record.

If a correction is needed, preserve the relevant evidence first. Identify who owns the working sheet and who can accept the revised output. Record the replacement decision before treating the new candidate as approved.

Do not delete history as part of ordinary decision review. History cleanup solves no missing-approval question. Retain records according to the team's applicable policy rather than inventing a retention period here.

Finish with the state, the cutoff, the accepted result, and its owner. Leave the later candidate visibly pending until reviewed.

Every decision needs its own workbook state.

Sources

Topic map: Spreadsheets, CSV files, and data handoffs

Articles in this cluster, then the 3 clusters that share the most topics with it.

This cluster: Spreadsheets, CSV files, and data handoffs

Neighbor: Business reporting and statistics

Neighbor: Records, access, and continuity

Neighbor: APIs, webhooks, and automation