Move a team from email attachments to shared documents

Email attachments create snapshots. That can be appropriate for a completed handover, but it becomes confusing when several people edit separate copies during active work. A shared document can reduce that fragmentation only if everyone knows which copy is maintained and which actions belong there.

Move one active workflow first

Choose a familiar type of document with a small group of contributors. Explain the change in terms of the problem it solves: reviewers will comment on one current draft rather than returning separate edited attachments. Do not begin by migrating every historic file. Old records and ongoing collaboration have different requirements.

Create the maintained document in the agreed location and test access with each type of participant. An internal editor, an external reviewer and someone using a different account may encounter different barriers. Use the least access needed for the role and involve the responsible administrator where necessary. A request for broader access should be a decision, not an automatic response to difficulty opening a link.

Make the request explicit

When sending the link, name the requested action and deadline. An illustrative message is: ‘Please comment on the service description in this document by Thursday. The pricing section is not ready for review.’ Explain whether recipients should edit directly or leave suggestions. Otherwise, people may download the file and recreate the attachment workflow you meant to replace.

Keep the link in the place people already use to coordinate the work. Avoid scattering equivalent-looking copies across chat, personal storage and a project folder. If somebody replies with an attachment, reconcile their changes carefully, then direct subsequent work back to the maintained document. Do not silently discard a contribution because it arrived through the old process.

Preserve a clear handover point

Agree how the team identifies approved work and what happens after handover. The shared draft can remain useful, but a publisher needs to know which state is authorised. Depending on the workflow, this may involve an identifiable revision or a separate handover copy. Being accessible to everyone does not make every edit approved.

After the trial, ask participants where they became uncertain. Access problems, unclear commenting rules and ambiguous approval are distinct issues and need different fixes. Keep the short instructions that prevented mistakes, remove unnecessary ceremony and expand gradually. The aim is fewer competing working copies, not a blanket ban on attachments when a fixed record is genuinely needed.