Organizing shared cloud files around the work
Choose a shared filing structure, test retrieval and permissions, and tidy cloud records without losing history or ignoring retention obligations.

A shared cloud folder needs a structure people can understand when they’re saving a document and when they’re looking for it later. Adding storage capacity won’t resolve inconsistent naming or competing copies.
Start with one team’s real files and improve that structure before reorganizing the whole business.
Agree on the filing unit
Choose the primary grouping that fits the work: client, project, department or another established business record. Write down where the current working copy belongs.
Give the area a business owner who can resolve uncertain cases. Explain where cross-team documents go so people don’t create a second “official” copy in another department.
Use the OneDrive and SharePoint guide if ownership of the storage location itself is unresolved.
Test naming and retrieval
Use a small set of meaningful folder and document names. Include the identifier or date people need, with a consistent date format where dates are useful.
Ask several staff members to save and retrieve representative documents. Include a new employee and an infrequent task.
Choose folder depth from those tests. There isn’t a universal requirement for three levels or ten files before a folder may exist. Metadata and search can complement folders when the platform supports them.
Keep access boundaries visible
Check who can read, edit and share at the destination. A clear folder name won’t keep anyone out.
Separate areas with materially different access needs using the platform’s supported permission model. Test with a representative account, including an external collaborator where relevant.
Use labels people can read. Colour may help recognition, but it shouldn’t be the only way to distinguish a restricted or archived area.
Pilot moves before making them broadly
Check links, permissions, metadata and version history with harmless test documents. Tell staff where the working copy will move and when they should stop editing the old one.
Microsoft’s SharePoint move and copy guidance distinguishes the commands: Move to carries document history, while Copy to copies only the latest version when history exists.
Verify the result in your platform and destination. Downloading a file and uploading it again loses its version history and can change its metadata.
Review archives and deletion separately
Identify closed work, duplicates and abandoned drafts with their owners. Check retention requirements and any hold before you delete anything.
An archive should remain findable by the people who need it. One enormous archive folder can reproduce the original problem.
Record cleanup decisions and use the recovery process if something moves incorrectly. Sync and version history won’t give you the independent backup coverage the business may need, so check that separately.
Maintain the structure
Include a short filing example in onboarding and give staff a way to flag unclear names or missing destinations. Review recurring problems after project changes.
Expand the pilot only after people can find their records and the access and retention checks work. Our Microsoft 365 service can help connect the filing structure with the tenant’s supported controls.


