Excel Co-Authoring: One Workbook Does Not Mean One Agreed Plan
Your colleagues can see the same planning workbook and still disagree about what its numbers authorise. Co-authoring solves the circulation problem. A dependable weekly plan also needs input ownership, a review boundary and a clear release.
16 October 2026 · UK business planning · Excel and Microsoft 365
-
Shared working file Contributors enter proposals in the canonical workbook.
-
Review still pending Saving a proposal does not make it an agreed commitment.
-
Release not yet authorised The coordinator must resolve the open review items.
All figures are an Illustrative example, not customer results. This is a proposed companion review log, not a native Excel conflict dashboard or an automatic count of all cell edits.
The meeting that exposes the problem
Nothing was lost. The team still acted on the wrong plan.
Imagine a professional services business preparing next week's capacity plan. Sales raises expected demand, operations reduces available hours and delivery adjusts the work mix. Everyone opens the same file. At the meeting, a manager reads the latest total as a promise to customers, although it was only a proposal.
The failure is not necessarily an overwritten cell. It is a missing agreement about meaning. Faster synchronisation can make an unreviewed assumption visible sooner without making it correct. The useful question is not simply “Can everyone edit?” but “When may someone rely on the result?”
Collaboration answers “who is contributing?”
A common working file reduces emailed copies and gives colleagues a place to work together. It is valuable when the team needs flexible modelling and can coordinate a manageable review.
Control answers “what has been accepted?”
A named reviewer decides whether a change is usable. A release owner decides which plan is agreed, what remains uncertain and how later amendments will reach the people using it.
Set the technical baseline
Make the shared-file experience reliable first
Microsoft documents co-authoring for supported Excel clients with
workbooks in supported OneDrive or SharePoint Online locations.
For a straightforward starting point, use an .xlsx
workbook, current Excel for Microsoft 365 or Excel for the web, and
verify AutoSave and sign-in on the actual devices. A network-drive copy
is not the same setup.
Test the real workbook rather than a blank demonstration. Unsupported clients or features can disrupt the experience. Confirm that every contributor opens the canonical link, can make an intended edit and can see another user's saved change. See Microsoft's co-authoring prerequisites and troubleshooting .
Write a small planning agreement
Decide what a row means before adding more editors
The workbook should make a proposal distinguishable from an accepted planning assumption. Start with these definitions, not a larger permissions spreadsheet.
| Decision | Working rule | Why it matters |
|---|---|---|
| Identity and unit | One row per workstream and week-start date; capacity recorded in hours. | A row keeps its meaning after sorting, and hours are not confused with headcount. |
| Input responsibility | One accountable contributor for each input area; a deputy is recorded. | Others can propose corrections without competing to be the last editor. |
| Material change | Log changes that affect promised capacity, delivery timing or agreed assumptions. | Review effort follows business impact, not every formatting edit. |
| Review state | Use Draft, Under review and Agreed with reviewer and review date. | A visible label communicates intent; the team must still follow the rule. |
| Release and amendments | Name the released plan, its cut-off and who may authorise later changes. | Consumers know which result to use and when a new version supersedes it. |
Keep assumptions, editable inputs and calculated outputs visibly separate. Use consistent table columns, validation and formula protection to reduce accidental mistakes. A status cell, however, is not an enforced approval engine; do not describe a convention as a technical control.
Three boundaries worth keeping
Saved, reviewed and released are different states
Saved is not approved
AutoSave preserves working changes; it does not ask the planning lead to accept their implications. Keep speculative modelling in a clearly labelled scenario area or a controlled separate scenario, not in the agreed output.
Protected is not confidential
Microsoft states that worksheet protection is not a security feature. It can restrict editing of locked cells. Do not use hidden sheets or locked ranges as the boundary between teams that must not see each other's data.
History is not an approval record
Show Changes helps investigate supported edits, but Microsoft lists untracked change types and possible gaps. Record the business reason and reviewer separately when the process needs them.
Platform references: worksheet protection and Show Changes limitations . The separation of planning states is a Smart Statistics design recommendation.
The architecture decision
Keep the workbook, strengthen the process or separate the records?
Keep co-authoring
Good fit: a small known team needs flexible modelling, contributors can share the file's contents, and a human review is proportionate. Document the planning agreement and make the release unambiguous.
Separate intake from modelling
Good fit: inputs are repetitive but the analysis still benefits from Excel. Assess a structured input list or form feeding a controlled model. Define the authoritative records and refresh timing so the two do not become competing truths.
Design a managed application
Assessment needed: contributors require different record visibility, approvals must be enforced, or several updates must succeed as one business transaction. Specify those controls before choosing a platform or estimating a migration.
Run a working-session rehearsal
Test the moments where the plan changes meaning
Before the planning meeting
The coordinator shares the canonical link, confirms contributors and checks input completeness. Each workstream owner identifies material changes and unresolved assumptions. Test a deputy's access instead of assuming cover exists.
During the review
Ask two contributors to propose different changes to the same planning assumption. Resolve the business disagreement explicitly, record the reason and verify the final value. Do not teach a “last editor wins” rule as an acceptance policy.
At release
The release owner records the agreed cut-off and outstanding caveats, publishes a clearly labelled output for consumers and confirms who received it. Define how a late amendment is authorised and communicated before it happens.
Recover without creating another disagreement
Rehearse a restore before the live plan needs one
Version History can open or restore previous versions of files stored in OneDrive or SharePoint in Microsoft 365. Treat a workbook restore as a coordinated recovery decision, not a private way to undo your own cell. An older file version may pre-date other people's valid work.
Use a test copy for the rehearsal
Make a known change, locate the earlier version and confirm who can inspect it. Compare versions and identify what a restore would replace. For a real restore, coordinate with contributors and wait until they are no longer co-authoring.
Validate the recovered plan
The coordinator checks inputs, formulas and the released output, then tells consumers which plan is current. Keep the incident reason and follow-up action. Ask IT to confirm the library's version-history configuration rather than assuming unlimited retention.
References: Microsoft Version History guidance and the restore cautions in Excel's co-authoring guidance .
Interactive decision check
Is the shared workbook ready for this process?
This local assessment separates operating readiness from requirements needing a different design. It submits and stores no answers. A high score does not override a confidentiality or control requirement.
Prove the benefit in the planning meeting
Measure agreement, not simultaneous cursors
The planning lead owns definitions and the released plan. Workstream owners maintain their inputs. The workbook maintainer controls formulas and structural changes. IT owns the access and recovery configuration. Name deputies so an absence does not turn the next cycle into an investigation.
| Measure | How to observe it | What it tests |
|---|---|---|
| Time spent reconciling copies | Record meeting and preparation minutes spent comparing competing files. | Whether the canonical-file approach removes avoidable coordination. |
| Material changes awaiting review | Count open entries in the defined change log at the release cut-off. | Whether the review capacity matches the planning process. |
| Post-release corrections | Classify corrections by cause: input error, misunderstood status or genuinely new information. | Whether apparent improvement comes from better controls rather than quieter demand. |
| Recovery rehearsal result | Record who restored the test copy, what was checked and any access gap. | Whether the documented fallback is usable by someone other than the main author. |
Frequently asked questions
Excel co-authoring: business FAQs
Where should a co-authored Excel workbook be stored?
Use a supported OneDrive or SharePoint Online location and supported Excel clients. A shared network folder is not a substitute for the cloud co-authoring setup described here.
Does AutoSave mean a planning change has been approved?
No. Saving a change and accepting its business meaning are different events. Define a reviewer, a cut-off and an agreed release separately.
Can worksheet protection keep other teams from seeing sensitive rows?
Worksheet protection is not a security boundary. It restricts editing of locked cells; do not use it as the design for separating confidential information between contributors.
Is Show Changes a complete audit record?
No. Microsoft documents gaps and unsupported change types, including formatting and some object changes. Use it as a review aid, not as a substitute for required audit controls.
Should every shared planning workbook be replaced with an app?
No. Keep the workbook when its modelling flexibility fits the task and its controls are proportionate. Assess a different design when restricted record access, enforced workflow or dependable transaction history is essential.
Sources and scope
Documented capabilities, practical operating choices
Microsoft documentation checked on 16 October 2026. The planning scenario, companion dashboard and operating agreement are illustrative Smart Statistics recommendations, not built-in Excel workflow guarantees. Licensing, client compatibility and tenant configuration should be checked for the proposed users. This article does not certify security, audit or regulatory compliance.