SharePoint without the sprawl

Somewhere in your SharePoint there is a folder called "New Folder (2)" and inside it is a file called "FINAL v3 USE THIS ONE.xlsx". Nobody knows if it is actually the final version. Three people have edit access who left the company last year. This is normal. Almost every SharePoint we walk into looks like this, because SharePoint makes it easy to create things and hard to notice you should not have.

The good news: SharePoint sprawl is not a personality flaw of your team. It is the predictable result of skipping three decisions at setup. Make those decisions now, even years late, and the mess stops growing.

Decision 1: sites follow teams, not projects

The most common failure mode is one giant site with one giant document library, organized by an ever-deepening folder tree. The second most common is the opposite: a new site for every project, forever, until you have 200 sites and nobody knows which ones are alive.

The structure that holds up is one site per long-lived function: Operations, Finance, HR, Sales, and one for company-wide stuff like the handbook and templates. Projects get folders (or document sets) inside the site of the team that owns them, not their own site. A site is a permission boundary and a search scope. A folder is just a folder. If a thing needs its own permissions and its own lifespan, it earns a site. Otherwise it does not.

Keep folder depth shallow. Two or three levels is the practical limit. Past that, people stop navigating and start dumping files at whatever level they landed on. Also, deep paths break things: SharePoint has a real limit around 400 characters for the full file path, and synced deep folders hit it constantly.

Decision 2: permissions go to groups, never to people

This is the one that bites hardest. When someone clicks Share on a folder and picks a coworker's name, SharePoint quietly breaks permission inheritance on that folder. Do that a few hundred times over a few years and nobody on earth can answer the question "who can see our payroll files?" We have audited tenants where the honest answer took two days to produce.

The fix is a rule, and the rule has no exceptions: access is granted to Microsoft 365 groups, and people are added to groups. "Finance Members" can edit the Finance site. "Finance Visitors" can read it. When Sarah joins accounting, she goes into one group and gets everything she needs. When she leaves, she comes out of one group and loses everything. Offboarding becomes a one-line task instead of an archaeology project.

Turn off casual sharing while you are at it. In the SharePoint admin center, set the default sharing link to "People with existing access" instead of "Anyone" or "People in your organization." Users can still share deliberately; they just stop granting access by accident every time they paste a link into an email.

Decision 3: names and retention are written down

A naming convention does not need to be clever. It needs to exist and fit on one page. Ours usually looks like this:

• Dates go first and go backwards: 2026-07-13 Board Minutes.docx. Files sort themselves.
• Client or project name next, then what the document is: Acme - MSA - Signed.pdf.
• No "final," no "v2," no initials. SharePoint keeps version history automatically. Right-click a file and choose Version history: every save is there, restorable. The moment your team trusts this, the FINAL-v3 disease dies.

Retention is the other half. Old files are not harmless; they are the reason search returns six copies of every template and the reason legal discovery costs what it costs. Decide how long each kind of document lives: seven years for financial records, duration-plus-two for contracts, one year for general working files, whatever your accountant and lawyer say. Then set it up once in Microsoft Purview as retention labels and let it run. Files age out on their own instead of accumulating forever.

Fixing an existing mess

Do not try to reorganize in place while people are working. The order that works:

1. Build the new structure empty: sites, libraries, groups, sharing settings.
2. Move current, active files into it, renaming as you go. This is usually a much smaller pile than you fear. Most of the volume is dead weight.
3. Move everything else into a read-only Archive site. Do not sort it. Search still finds it if anyone ever needs it.
4. Set the old locations read-only for a month, then remove them. If nobody screams in a month, nobody was using it.

How you know it is done right

Three tests. First, ask "who can see the HR site?" and get an answer in under a minute by opening one group's membership. Second, a new hire finds the expense report template without asking anyone, because there is exactly one place it could be. Third, six months later there are no new top-level folders you cannot explain. Sprawl is not something you clean up once; it is something the structure either invites or prevents. Get the three decisions right and the structure does the maintenance for you.