Start from permissions, not from folders
The most useful decision you make in SharePoint is where the permission boundaries sit. Permissions are cleanest at the site and library level, where you grant access to a group once and every file underneath follows. They get messy when you break inheritance on individual folders, because after a year nobody remembers which subfolder has different rules or why the new office manager cannot open a particular quote.
So before you sketch any folder tree, list the groups of people in your business and what they should and should not see. A typical small office ends up with everyone, managers, finance and payroll, and perhaps a client-facing team. Each group that needs different access gets its own library or site. Inside that boundary, everyone with access can see everything, and folders become purely about finding things.
Keep the folder tree shallow
Two or three levels is plenty for most libraries. A layout like Clients, then the client name, then a handful of standard subfolders such as Quotes, Contracts and Correspondence works far better than a structure where people have to click seven times and guess at each step. Deep trees also run into the path length limits that cause sync errors, because every folder name adds characters to the full address of each file.
If you find yourself creating folders by year inside folders by month inside folders by type, consider whether a single column on the library would do the same job. SharePoint can sort and filter by any column, so a flat folder of invoices with a column for financial year is often quicker to search than a nested set of dated folders.
Use a naming pattern everyone can follow
Agree on a file naming pattern and put it at the top of the library as a short note. Something like client or job number, then document type, then a short description, then the date in year-month-day order sorts neatly and makes search far more reliable. For example, 1045 Quote Kitchen Upgrade 2026-03-14 tells you more at a glance than Quote final v3 revised.
Drop version numbers and words like final from file names altogether. SharePoint keeps version history automatically, so there is one file that changes over time instead of many copies with different suffixes. Avoid special characters such as the hash or percent symbols and keep names reasonably short. Both habits reduce errors when files sync to laptops and when people share links.
Metadata columns, used sparingly
Columns let you tag documents with information such as client, status, document type or review date, then build views that filter on them. A practice manager could have a view showing every policy due for review this quarter; a project office could show all contracts awaiting signature. That is genuinely useful, and it is one of the main reasons to use SharePoint rather than a plain file share.
The trap is adding ten required columns that people must fill in on every upload. They will either stop saving to the library or fill every field with whatever is quickest. Start with one or two columns that solve a real problem, make them choice lists rather than free text, and add more only when someone asks for a view that needs one.
Views, pinned links and the home page
Most staff should never need to browse the whole tree. Create a few saved views, such as recently modified, my documents or contracts by client, and pin the most used folders to the site's navigation or to the channel in Teams. Add the library to File Explorer with the shortcut option so it appears alongside people's own files on their laptop.
A simple site home page with links to the five things people open every day removes a surprising amount of friction. The aim is that a new starter can find the leave form, the current price list and the client folder template within a minute of logging in, without asking anyone. If they cannot, the structure is too clever.
Keeping it tidy over time
Libraries decay unless someone owns them. Name a library owner for each site, usually the manager of the team that uses it, and give them the job of archiving finished work once a year and removing folders nobody uses. Moving old client folders into an Archive library with read-only access keeps the working area small and fast to search.
Check sharing as part of that annual tidy. Look for files shared with people outside the business that no longer need access, and for folders where someone has broken permission inheritance without telling anyone. Ten minutes a quarter is far easier than a full rebuild in three years when the library has become as cluttered as the shared drive it replaced.
In short
- Draw permission boundaries first, then design folders inside them.
- Two or three folder levels is enough for most libraries.
- Use one naming pattern and let version history replace v2 and final.
- Add metadata columns only when they power a view people will use.
- Give every library an owner who tidies it once a year.