Skip to content
Aurora

The Sharing Playbook

How can a small firm organize several client document reviews?

Give each client review its own document collection, a named owner and an access check before invitations. Includes a free private review register.

Access And Responsibility · Aurora Datarooms

Archive Date Published
Colleagues organize separate client document packs at a standing island in a brick-walled office.

Get The Free Worksheet

Give each client engagement its own home for source files, with one person who looks after it. Share a checked selection with each outside audience. Keep a private register of who runs each review, what is open and when access needs another look. Before anyone gets an invitation, test the setup from each recipient's side, including the files they shouldn't be able to see.

In a small firm, three reviews can run in the same week. One client is preparing a sale, another is assessing a property, a third is checking a supplier. The same colleague might be helping on all three. The hard part is keeping each client's documents, people and decisions apart while you switch between them all day.

Give each engagement a home you can recognize

Start with a separate collection for each engagement. Name it after both the client and the work, such as Client A / Business Sale or Client B / Property Review. If one client has two unrelated projects, give each project its own home too.

Inside each collection, keep the structure small and fitted to the job. A property review might use Survey, Title and Operating Costs. A supplier review might use Scope, Technical Information and Commercial Terms. Drafts and internal preparation stay out of anything shared externally.

Agree which collection holds the maintained source files. When a revision arrives by email, the person looking after the review checks it and updates that collection before pointing reviewers to it.

Folder names and colors help people recognize a project. Access settings decide who can open it. Microsoft draws the same line in its SharePoint guidance: confidential material that should stay internal goes in a site with external sharing turned off, and separate sites handle external sharing. That advice is specific to SharePoint, but the idea of keeping internal material apart from what you share works anywhere. Microsoft's external sharing guidance.

Keep a private register of active reviews

One short internal register lets you see everything the firm has moving. Link to each maintained collection and write down the next action. The register itself can reveal client names or sensitive stages of work, so only staff who need the overview should see it.

Here is one way a two-person advisory firm might start:

EngagementLooks after itOutside audienceWhat they seeNext check
Client A / Business SaleEngagement leadBuyer advisorsApproved accounts and agreed business informationCheck new advisor list before invitations
Client B / Property ReviewProject coordinatorLender teamSurvey and selected operating recordsCheck replacement survey before release
Client C / Supplier ReviewEngagement leadTechnical specialistSpecification and test summaryReview access when the specialist finishes

The person who looks after a review keeps it organized. That label doesn't give them administrator rights in your software, or the authority to approve every document. When different people approve disclosure, manage access or pay for extra capacity, write each of those down separately.

Name a backup for holidays and sick days. A good backup can find the source collection, understand who the current audience is and see the next decision without asking anyone to forward a private email chain.

Decide who prepares, who shares and who reviews

For each engagement, answer three questions:

  • Who maintains the source documents?
  • Who decides what leaves internal preparation?
  • Who needs to read the selection that goes out?

A specialist reviewing one report may only need that report and its supporting material. A colleague preparing several engagements may need wider access. Give that wider role on purpose, and check what it exposes across the firm.

The UK's National Cyber Security Center recommends limiting access to the permissions and resources a role needs. Its cloud guidance also covers understanding who has management access and removing permissions people no longer need. Apply them when you split preparation, administration and review. NCSC secure user management guidance.

When someone works on two clients, record each assignment on its own. Working on Client A is no reason to add them to Client B. In the same way, one client approving a document doesn't clear it for use on another engagement.

Check the boundaries before invitations go out

Run a small check with sample files before any real client information goes in. Use an account with the permissions a participant would actually have. A staff administrator sees a wider view, so their screen tells you little about a reviewer's.

Test accountShould openShould not openRecord
Client A reviewerClient A's approved review fileClient B's file and Client A's internal draftResult, date and any fix
Client B reviewerClient B's approved review fileClient A's file and Client B's internal draftResult, date and any fix
Staff reviewer for Client AThe assigned Client A materialOther clients' collectionsResult and any wider role found

Check navigation, search results and a direct link to a sample file outside the assignment. Look at document titles and folder names too. A revealing name can matter even when the file itself won't open. Test viewing and downloading separately.

If anything doesn't match what you planned, fix the assignment or sharing settings and run the check again before inviting the real audience. A passing check covers only the setup you tested. When a new collection, role or audience changes that setup, repeat the checks it affects.

Reuse the preparation routine with care

A blank folder structure, a checklist and a register row can save time on the next engagement. Look at the content of anything you reuse, though. Old recipient lists, private notes, client names and source documents each need a deliberate decision before they go into a new project.

If your tool has a copy function, find out exactly what it copies. Build the new audience list from the people on the current engagement. Confirm the destination and the document contents before you share a copied collection.

When you're switching between clients during the day, pause at the moment of release. Confirm the engagement name, the file, the destination and the recipient. The private register can hold that check and the next open action. It should point to the working collections and hold no client files itself.

Keep reviews current and close them on purpose

Look at the register when someone joins or leaves, a document is replaced, a review moves to a new stage or the work ends. Confirm who handles the next action and whether existing access is still needed.

For revisions, send reviewers to the maintained source and explain any change that affects their work. When a review finishes, agree the handover and what will be kept, then remove access nobody needs. A downloaded copy can stay on the recipient's device after their access ends. The download decision guide helps you plan that part of the handover.

How this looks in Aurora

When the firm administers the work, its Aurora organization can hold a separate library for each client engagement. Rooms give each audience access to the files you select from those libraries. A room can draw on more than one library, so check every connected library when you set up a client review. Access groups and individual permissions narrow access further inside the room.

Organization owners and administrators can manage the whole library, and separate libraries don't hide client work from them. If a client agreement calls for different administrators or for the client to keep independent control, settle that and the right organization setup before uploading anything. Access to one organization gives no ownership in another.

The Starter trial and paid plans include unlimited libraries; room, user and storage allowances still apply. To try the method, start with one sample client library and two rooms for two review audiences. Put an approved sample file in each room and keep an internal sample out of both, then check the result with test recipients you control. That fits the 30-day trial, which includes one organization, unlimited libraries, two rooms, three internal users and 25 external users, with no card required. Try a sample review in Aurora.

Start with the free worksheet below: list the firm's active reviews and give each one a next check. If reviewers then struggle to find evidence inside a collection, the question-to-evidence index guide can help.

Client review register and access check

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

Download Worksheet (.md)

Use this inside the firm to keep several engagements straight. It's free to copy and adapt, and you don't need an Aurora account. Keep completed copies with the people allowed to see the firm's client overview.

Active reviews

Engagement and purposeWhere the source livesLooks after it / backupWho approves disclosureOutside audiencesNext action and date
[Client / engagement][Internal link][Person / backup][Person or agreed process][Who needs which selection][Action / date]
[Client / engagement][Internal link][Person / backup][Person or agreed process][Who needs which selection][Action / date]
[Client / engagement][Internal link][Person / backup][Person or agreed process][Who needs which selection][Action / date]

Who does what

  • Who maintains the source documents?
  • Who approves disclosure for this engagement?
  • Who can change participant access?
  • Which administrators can see or manage several clients' collections?
  • Do the client agreements and the work allow that wider access?
  • Who signs off extra paid capacity if you need it?

Check the recipient's view

Use test files first and record what actually happened. A file opening for an administrator tells you nothing about what a participant can see.

Test account and roleSample they should openSample or name they shouldn't seeNavigation / search / direct linkView / downloadChecked by and date
[Client A reviewer][Client A shared sample][Client B sample / internal draft][Observed][Observed][Person / time]
[Client B reviewer][Client B shared sample][Client A sample / internal draft][Observed][Observed][Person / time]
[Assigned staff reviewer][Assigned material][Unassigned material][Observed][Observed][Person / time]

Fix and retest

  • What went wrong:
  • Setting, assignment or content fixed:
  • Who fixed it:
  • Retest account and result:
  • Date checked:
  • Anything still open before invitations:

Before each release

  • Confirm the engagement name and destination.
  • Confirm the file contents and version.
  • Check the audience and recipient addresses.
  • Review inherited access and anything reused from an earlier setup.
  • Confirm who answers questions and maintains the source.
  • Write down the next access or document check.

When work changes or ends

Record who takes the handover, what you'll keep, the next retention decision and the access to remove. Note how important revisions will reach people working from downloaded copies, since files they've already downloaded don't change when the source does.

Keep this register internal. When a client needs something from it, prepare a shorter handover note just for them.

Sources