“Can you send me the most up-to-date version?” One colleague emails a file called final_v3. Someone else has a file with nearly the same name on their local drive. The customer may well have downloaded and opened a previous version.
So which is the correct version to rely on?
It’s simple enough to share documents with others, but establishing the current version, deciding who needs the ability to amend it, and knowing if it is fit to share externally is more complicated.
Gallup found that 54% of U.S. employees with remote-capable jobs worked in a hybrid arrangement as of August 2026. This makes a clear document process important when colleagues split their time between home and the office.
What you’ll learn:
-
Where File Sharing Breaks Down
-
Give Every Working File a Clear Home
-
Document Management System Requirements That Matter
-
Share Files Without Sharing Too Much
-
Make Good File Habits Stick
-
Wrapping It Up
Where File Sharing Breaks Down
It’s often a number of smaller actions that lead to uncertainty over files. An employee saves and takes a file with them at the end of the day, a line manager responds with comments against a version attached to an email, and others continue to update data that feeds into a report due soon.
Each action seems harmless on its own. Together, they leave several files claiming to be the latest version.
Colleagues may act on incorrect information, waste time re-doing elements, or share inappropriate information with customers. Agreements may be reached over instant message channels, away from the relevant file.
Some indicators to look out for include:
-
Multiple “final” versions, with no obvious indication of the preferred file
-
Comments and other decisions recorded away from the file itself
-
Multiple users able to amend a file, with no obvious owner
-
Delays while others try to locate and gain access to required information
Simply urging greater diligence from all users is unlikely to be effective. Ideally all contributors would be able to access a single version of the relevant document.
Read also: Samsung’s Galaxy XR: A New Spark in the Mixed Reality Race
Give Every Working File a Clear Home
It is sensible to designate a location for each live document. There will no doubt be references to it and discussion of its contents elsewhere, but there should be an agreed location for the file itself.
Rather than sharing further iterations, others should be pointed towards this existing file. All users would then know where to go to view updates.
Organisations with a Microsoft 365 subscription could consider using SharePoint as a document management system to meet some or all of these requirements. Ultimately though, organisations should look to establish where live versions of key documents would sit, and be readily accessible, with an easy way to review prior iterations.
Consider what status any other copies may have. For example, a version exported to PDF and provided externally would presumably be “final” as at a given point in time. It would be undesirable for internal users to continue to update this copy.
Similarly, it would be beneficial to feed any discussion and decisions held away from the file back into the main body, so the file owner should ensure this is done where applicable.
There can be several users contributing to the content of a file, but it’s useful to have one place to refer to.
Document Management System Requirements That Matter
With this in mind, organisations should establish a list of desirable functionality to aid their document management processes.
Read also: Walmart Says AI Can Personalize Shopping — Not Prices
These will likely relate to regular activities undertaken by users:
-
Ability to review past versions, and revert to one if necessary
-
Simultaneous contribution to a single file, subject to limitations of the application and file type
-
Search and filters based on customer, project or document type
-
Flexible controls over who has access, and whether they can view only or make edits, including externally
-
Identify appropriate users to sign off on documents prior to finalisation
-
Comply with any applicable retention requirements
Different departments will place varying emphasis on each area. Designers may want to easily access live files to collaborate, whereas Finance may wish to restrict amendment to certain key users only.
A quick check would be to ask users to locate and retrieve a sample finalised agreement, ascertain who currently has access to this, and view an older iteration.
This should not require extensive trawling through emails and various users’ drives.
Creating further sub-folders may not necessarily improve users’ ability to quickly navigate to relevant information, and using appropriate metadata may assist. It’s worth trialling this with end users.
Share Files Without Sharing Too Much
The level of access granted should be tailored to individual circumstances. There may be benefits in making certain documents available more widely, whereas only limited users would need to view a particular agreement.
Users may be able to generate links to grant to named individuals, all internal staff, or externally, subject to parameters set by the organisation. It is worth considering who you wish to allow to access the file, and their respective rights.
It may be preferable to restrict to named users with ‘view’ access only for certain documents. Of course, appropriate users would need higher levels of permission to complete their tasks.
Review access permissions regularly and remove rights people no longer need, such as when a project ends or someone changes roles.
Read also: Semiconductor Boom Is Getting Bigger Than AI
If it is onerous to securely share appropriate versions of files with others, there is a risk users will resort to alternative means, such as personal email accounts.
Make Good File Habits Stick
Users will need to adhere to certain practices to ensure smooth transitions of files as they progress through their life cycle.
At a basic level this could include:
-
Creating new files in an appropriate shared location
-
Others accessing this file to make any amendments
-
Identifying a user or users to take further action, as applicable
-
Identifying when a file has been agreed, for example labelling and noting a date
-
Moving to an appropriate final location for easy retrieval
There will inevitably be occasions where users need to make a copy, such as when someone works offline or a third party requests an attachment. This is acceptable so long as any subsequent updates are reflected back to the main file.
Rather than issuing comprehensive guidance, it may be more effective to focus on a sample process, and identify any points where files are ‘dropped’. For example, if files are hard to locate, this may warrant further thought around folder structure or metadata applied. Alternatively, if files appear to ‘stall’ awaiting sign-off, further clarification may be required around expected actions.
Naturally, the aim is to establish a process which can easily be adhered to in normal day-to-day operations.
Wrapping It Up
It is possible to mitigate some of the risks arising from staff accessing the office varying days per week.
Designate a location for each key file to be worked upon, ensure appropriate functionality is available and grant suitable levels of permission to others. Once established, trial this over routine activities to ensure it is workable for all users.
Comments
No comments yet — be the first to share your thoughts.