Organise around the next person looking
Start with the questions colleagues actually ask: where is the approved version, which folder belongs to this project, and who can change the document? Use a few clear locations based on work rather than the personal preferences of the person who first created the drive.
Keep active work separate from completed projects. Within a project, distinguish working files from documents approved for use. Avoid placing the only approved copy in a private folder that others cannot access when its owner is absent.
Choose names that carry useful information
Agree on a simple naming pattern that includes the project and document purpose. Add a date when it identifies a release or meeting, rather than appending today’s date every time someone opens a file. Use the same date order throughout the team.
For bilingual material, include a consistent language label when there are separate files. Keep the French and English versions together and identify who updates the pair. A translated copy that has lost its link to the original becomes harder to maintain after the first correction.
Share the maintained version
When appropriate, send a link to the shared document instead of a new attachment. Check the recipient’s access before sending it and use permissions suited to the task. Someone who only needs to read the final copy may not need to edit the working file.
Use the tool’s revision history when available, but do not assume every storage service handles versions in the same way. Establish how the team recovers an earlier version and what happens when a file is deleted. Keep the organisation’s separate backup practice in mind.
Archive deliberately
At the end of a project, identify the files that remain useful and move them into a clearly named archive. Follow the organisation’s retention rules rather than keeping or deleting everything automatically. Preserve enough context to explain what the final documents were used for.
Try the system with a colleague who did not build it. Ask them to find an approved document, its other-language version and the current owner. Where they hesitate, change a name or add a short folder note. A filing system succeeds when ordinary questions no longer need a group message.
Keep in mind
- Separate active, approved and archived work
- Use consistent project and language labels
- Check permissions on shared links
- Test retrieval with another colleague