Skip to content
Aurora

The Sharing Playbook

How do you keep advisors on the same financial version?

When two advisors work from different financial versions, confirm each revision and issue one approved source with a change note. Free worksheet included.

Current Documents · Aurora Datarooms

Archive Date Published
Two advisers compare printed working copies in a private coworking meeting booth.

Get The Free Worksheet

When two advisors have worked from different financial documents, start by finding out exactly which copy and which review basis each one used. Ask the document's owner to confirm the current approved issue. Keep any changes the advisors made separately, then send each recipient a clear change note with a link to the agreed source. Before you combine their conclusions, confirm the revision, period and scenario behind each one.

You'll know the situation: two sets of comments come back on the same afternoon, and the numbers don't agree. Before the next call, everyone should be able to see what changed, which questions are still open and what they need to look at again.

What is actually different between the copies?

Two spreadsheets can have different filenames and hold the same information. Two copies with the same filename can hold different assumptions. Ask each advisor which revision they used, the reporting period, the scenario and whether they changed anything locally.

Save the actual file they used in an approved location before you ask anyone to replace it. Their comments or calculations may still be useful. Limit access to those working copies to the people who need them.

What you findWhat it meansNext step
One advisor used an earlier issued revisionTheir work may rest on information that has since changedFind the affected sections and ask for a review against the current issue
An advisor changed a current copyThe difference may be a proposed assumption or a correctionKeep it as a working copy and ask the document owner to decide
Both used the same revision with different periods, units or scenariosUploading a newer file won't settle itAgree the basis for comparison and label each result clearly
Nobody can say where the copy came fromThe conclusions have no confirmed starting pointMark them unresolved until the source can be checked

The highest revision number or the latest modified date isn't approval. A copy saved yesterday may still carry a change nobody has reviewed.

Who can confirm the issue?

Pick a document owner who can confirm what's approved for this review. That could be a finance lead, a business owner or someone else you've named as reviewer. Whoever looks after the shared folder may need their sign-off before issuing a replacement.

Give each issued document a fixed identifier, a clear revision and a one-line purpose. For example: Forecast F-01, revision 7, September actuals, base-case review. Add currency and units where they change how the numbers read.

This matches ICAEW's guidance to record a spreadsheet's owner, purpose and version, and to keep regular backups and version control. ICAEW also calls for review in proportion to how much the workbook matters. A tidy revision label can't show that the calculations are right. ICAEW's spreadsheet principles, 2024 edition.

Work through an example of conflicting copies

Here's an example. An operations lead has issued revision 7 of a forecast, which includes September actuals. One advisor sends comments based on revision 6, which used August actuals. A second advisor works from revision 7 but changes the timing of customer receipts in a downloaded copy.

Both sets of work deserve a clear outcome. The older review may raise fair questions, and the changed timing may be a useful sensitivity. Neither should quietly become the agreed source.

The operations lead records three entries:

  • Issued source: F-01 revision 7, September actuals, base case, with its approved location and issue date.
  • First advisor's working copy: revision 6 with comments. The document owner marks which comments need another look after the actuals update.
  • Second advisor's working copy: revision 7 with a proposed change to receipt timing. The document owner decides whether to reject it, approve a revised issue or ask for a separately labelled sensitivity.

The owner then records the decision and any questions left open. Until then, the proposed change stays visibly pending. That keeps an advisor's assumption from being presented as the company's approved forecast.

Keep the combined reconciliation log internal if it contains private advisor work. Send each recipient only the change information and documents they're entitled to. Two advisors on the same review don't automatically need to see each other's correspondence.

Send a change note that tells people what to do

"Latest version attached" leaves the recipient to work out why it matters. Give them enough to decide whether their earlier work needs attention.

For each new issue, include:

  1. The document identifier, revision, issue date and timezone.
  2. The purpose, reporting period, currency, units and scenario where they apply.
  3. The approved source link, one that recipient can open.
  4. What changed and which sections or outputs it affects.
  5. Any open questions or limits on how to use the document.
  6. The review you're asking for and a realistic reply date.
  7. Which earlier issue it replaces for this review.

Ask recipients to state the revision they used when they send back comments or conclusions. Keep the superseded copy as your record-keeping rules require, clearly apart from the current review material. Don't delete useful working history just to make the folder look tidy.

Use file history to back up the check

Your existing tools may help show what happened. Microsoft 365 Version History lets you look at earlier versions of files stored in OneDrive or SharePoint. Check where a file is stored before assuming history exists for a downloaded local copy. Microsoft's Version History guidance.

Excel's Show Changes can help you trace cell edits. Microsoft lists what it leaves out, including chart edits, formatting and filtering, and notes that its timeline can have gaps. So an empty changes pane doesn't show that two reviews used the same basis. Microsoft's notes on Show Changes limits.

Read the history alongside the actual files, the owner's decision and the basis each recipient says they used. Disputed assumptions or calculations go to the qualified reviewer responsible for the model.

Keep each audience on the approved source

In Aurora, you can keep the approved document once in a library and share it through a separate room for each advisor. Each room can hold different supporting material while sharing the same source document.

When you issue the next version, use Replace File on the existing library document. Rooms sharing it show the current permitted version when participants reopen or refresh, and earlier versions stay in the library's history. Uploading a separate document creates a new item, so check room selections and permissions whenever you add or reorganize material.

Aurora doesn't merge advisor spreadsheets or decide which financial assumptions to approve. Prepare and review changes in your usual tools. Copies already downloaded to a device stay as they are, and the recipient needs to act on them when an issue changes. The guide to updating shared documents explains that boundary in more detail.

If you're also choosing a sharing setup, the shared-folder review exercise helps you test the handover you need. Aurora's document-sharing overview shows how separate audiences can work from one maintained source.

For a small trial, use a test file called Forecast Sample in one library and two rooms. Replace version 1 with a clearly labelled version 2 and check it from each permitted recipient's view. If downloads are on, compare a copy downloaded earlier with the current source. That fits the 30-day, no-card trial's one organization, unlimited libraries, two rooms, three internal users and 25 external users, within its 10 GB storage allowance. When you're ready, take the product tour or start a trial.

When is the handover done?

The handover is ready when the owner has confirmed the issue, each advisor knows where to find it and returned work names its revision and purpose. An acknowledgement confirms receipt or a stated basis. It doesn't prove anyone understood the content or approved the numbers. A record showing a file was opened doesn't prove that either.

Start with one disputed document. Use the free worksheet below to log the copies, assign the open decisions and draft the next change note. It works with whatever sharing tools you already use.

Advisor version reconciliation worksheet

Free to use and adapt. Keep your completed worksheet in your own project files.

Download Worksheet (.md)

Use this record when reviewers send back work based on different copies or assumptions. Fill it in somewhere approved for this work. Keep the combined record restricted if it includes private advisor work, then send each recipient their own issue note. It's a manual sheet and works with any document-sharing tool.

Define the review

  • Document identifier and title:
  • What the review is for:
  • Document owner who can approve an issue:
  • Person handling distribution:
  • Reporting period, currency and units:
  • Scenario or other assumptions that define the review basis:
  • Next review date and timezone:
  • Approved location for source files and working copies:

Record each copy before replacing it

Add one row for the approved source and one for each working copy you receive. Keep the original files, or approved records of them, so useful comments aren't lost.

CopyRevision and basisChanges or questionsWho decides, and next step
Approved source and locationRevision; period; units; scenarioKnown open itemsOwner; issue status
Advisor A and working-copy locationStated revision and basisComments; proposed changes; unknownsOwner; next step; due date
Advisor B and working-copy locationStated revision and basisComments; proposed changes; unknownsOwner; next step; due date

Label each difference: earlier issue, local change, different review basis or unknown source. A filename or modified date alone can't show approval. If the source is unknown, write that down before you combine conclusions.

Worked example

Example: F-01 revision 7 contains September actuals. Advisor A used revision 6 with August actuals. Advisor B used revision 7 and changed receipt timing locally.

Log A's comments for review against revision 7. Keep B's working copy and mark the timing change as a proposal waiting for the owner. The owner may approve a replacement, ask for a separately labelled sensitivity or reject the proposal. Don't record an outcome until the owner decides.

Record the decision

  • Current approved issue and approval record:
  • Comments carried forward, and where they're recorded:
  • Proposals accepted, rejected or still pending, with the person responsible:
  • Checks needed before another issue can be approved:
  • Results or conclusions that need a fresh review:
  • Earlier issue superseded for this purpose:
  • Historical records kept in the approved location:

Prepare an issue note for each recipient

Copy this block into your usual approved channel and fill it in. Check the destination as that recipient would see it, and leave out confidential comments from other advisors.

Subject: [Document identifier] [revision] ready for [review purpose]

Issued: [date, time and timezone]. Approved by: [person responsible and approval reference].

Review basis: [period, currency, units and scenario].

Current source: [approved link].

What changed: [specific changes and the sections or outputs affected].

Open questions: [remaining issues or limits on use].

Action: [what to review and send back, with due date]. Please state the revision and basis you used in your reply.

Previous issue: [revision] is superseded for [purpose]. Keep any record you're required to keep, and use [current revision] for the next review. Copies you downloaded earlier won't update.

Check the handover

  • Confirm the document owner approved this issue for this purpose.
  • Confirm the link opens the permitted source for each recipient.
  • Keep unapproved advisor changes separate and name who decides on them.
  • Record which revision each recipient says they used in returned work.
  • Revisit conclusions the change affects, and leave open items visible.
  • Treat an acknowledgement or a file-open record as limited evidence. It doesn't approve the model or show the content was understood.

This worksheet organizes version decisions. Financial accuracy and the soundness of assumptions still need the right qualified review. It doesn't set a retention period or replace your organization's approval rules.

Sources