The problem with copies
Everyone has seen it: a document called “Report_final,” another called “Report_final_v2,” and a third called “Report_final_v2_Sam edits.” Nobody is sure which is current. Two people have edited different copies, and merging their changes takes an afternoon. This happens when files are shared by email attachment or when several people save their own versions to separate places.
Version control is simply the practice of keeping track of changes to a file so that there is one clear current version and, if needed, a way to look at earlier ones. For most teams, it does not require specialist software.
Keep a single source of truth
The simplest rule is that each document has one home. Instead of attaching a file, share a link to the file in the shared location. Everyone opening that link sees the same current document.
Most teams get this through cloud storage or an online editor where several people can work in the same file. When a document lives there, an “attachment” is only a pointer, and the question of “which is latest” disappears. If you must send a copy outside the team, label it clearly as a copy and say it may become out of date.
Choose between live editing and checkout
There are two broad ways of handling multiple editors.
Live co-editing. Several people edit the same file at once and see each other’s changes. This suits drafts, notes and meeting agendas. Conflicts are rare, but accidental deletions can happen, so history matters.
Check-out or turn-taking. One person edits at a time, either by locking the file or by agreement. This is useful for files that cannot be merged, such as some design or spreadsheet models. It is slower but avoids clashes.
Agree on which approach applies to which kind of document, and write it down.
Use edit history
Most shared editors keep a record of changes: who did what and when, with the option to restore an earlier state. Learn where it is. It is the safety net that allows people to edit boldly. Before a major rewrite, consider saving a named version or a labeled snapshot, for example “Before restructure, October.”
Edit history is not a replacement for backups, though. A deleted folder, an account problem or a mistaken sync can still lose work, so it helps to have a backup strategy for important files too.
Naming conventions
When files do need names that carry meaning, a consistent pattern prevents confusion. A useful pattern includes:
- the subject or project
- a short description
- a date in year-month-day order, which sorts correctly
- a status word where needed, such as draft or approved
For example: 2026-10-31_pricing-review_draft. Avoid words like “final” and “latest,” because they stop being true. If you want a numbered series, use a simple pattern such as v1, v2, v3 and increment it only for meaningful milestones, not every save.
Folders and ownership
A tidy structure saves time. Keep folder depth modest, so files are not buried. Give each important document or folder an owner, who is responsible for keeping it current and for archiving it when it ends. Anything unowned tends to rot.
A “drafts” area separate from an “approved” area is a helpful split. Only the owner or a small group moves files into approved. Approvals can be written into the document itself, or recorded with a digital signature where a formal sign-off is needed.
Permissions
Not everyone needs to edit. A good starting point is to give people the lowest access that lets them do their job: view, comment or edit.
- View only for reference material and published policies.
- Comment for reviewers, so they can suggest changes without altering the text.
- Edit for those responsible.
Be careful with links that anyone can open. Check sharing settings regularly, especially for files with customer or financial information. When people leave a team or the company, access should be removed promptly, which is covered in staff offboarding. For personal data in particular, think about the wider issues described under data breaches.
Suggestions and comments instead of silent edits
When changing someone else’s work, use suggestion mode or comments so the author can accept or reject. This keeps accountability and avoids unwelcome surprises. Resolve comments once dealt with, so the document is not cluttered with old threads.
Regular clean-up
Every few months, archive finished work, delete true duplicates, and check that links in guides and wikis still point somewhere. A short monthly or quarterly clean-up prevents the slow return of clutter. Many teams also keep a single index page listing key documents and owners, which speeds up onboarding.
A short team agreement
A one-page agreement is usually enough. It could say:
- Files live in the shared location, not in email.
- Share links, not attachments.
- Use the agreed naming pattern.
- Comment or suggest rather than overwrite others’ work.
- Owners archive finished documents.
- Ask in the team channel when unsure.
Small habits like these remove most confusion, and they make remote work much calmer.