SharePoint Site Structure Best Practices: A Guide for UK SMEs

When UK businesses migrate from an on-premises Windows file server or basic cloud drive to SharePoint Online, the single most common mistake is attempting a direct lift-and-shift of legacy folder trees. The classic nested drive, where finance files sit five folders deep inside a department directory that nobody has reviewed since 2018, does not translate effectively to Microsoft 365. When you dump twenty years of nested folders into a single SharePoint document library, sync errors multiply, URLs exceed character limits, and permissions become impossible to manage.

Modern SharePoint operates on a fundamentally different philosophy: a flat architecture powered by dedicated sites, hub navigation, and Microsoft 365 Groups. Moving to this model is not just about keeping files tidy. It directly impacts your security posture, employee search efficiency, and readiness for artificial intelligence tools like Microsoft Copilot.

In this guide, we break down the practical steps UK small and medium-sized enterprises (SMEs) must take to design, organise, and govern a clean SharePoint site structure that scales without creating administrative headaches.

Why the Old Nested Folder Model Fails in SharePoint

On a traditional network drive (such as a mapped Z: drive), deep folder structures were the only mechanism available to categorise documents and restrict staff access. An IT administrator would create a top-level share, disable inheritance six levels down on a specific folder, and assign bespoke NTFS permissions to three individuals. Over time, staff moved roles, departments restructured, and nobody knew who had access to confidential client files.

Bringing that exact approach into SharePoint Online triggers immediate technical and operational friction:

• URL Path Length Limitations: Microsoft 365 enforces an overall decoded URL limit of 400 characters for files and folders. Deep folder hierarchies combined with long company, site, library, and file names routinely break this limit, causing sync failures in the OneDrive sync client and blocking document edits.
• Broken Permission Inheritance: Breaking inheritance on subfolders creates unique permission scopes. In SharePoint, having thousands of unique permission scopes severely degrades library performance, complicates audits, and leads to accidental data leakage.
• Poor Mobile and Browser Discoverability: Moving through eight levels of folders on a mobile browser or Microsoft Teams tab is painful for employees. Users quickly give up, save files locally, or create rogue copies.
• Search Degradation: Deep folder paths obscure document context. Without clear site boundaries and descriptive library metadata, Microsoft Search and Copilot struggle to surface relevant information to staff.

Flat Architecture vs Subsites: What Microsoft Actually Recommends

In legacy versions of SharePoint (such as SharePoint Server 2013 or 2016), the standard practice was building deep hierarchies of top-level site collections containing dozens of nested subsites. Modern SharePoint has retired this concept in practice. Microsoft official guidance explicitly advises organisations to adopt a flat architecture, where every distinct business unit, department, or major project receives its own dedicated top-level site collection.

The primary advantage of a flat architecture for a growing business is organisational agility. If your sales and marketing teams merge, or if a business division is sold or restructured, you simply re-link sites to different hub navigation menus in the SharePoint Admin Centre. You do not need to spend weekends moving gigabytes of data between parent and child directories.

The Four Core Site Types for UK SMEs

To keep governance manageable, most UK SMEs with 10 to 250 users only need four primary categories of SharePoint sites:

1. Communication Sites (The Company Intranet)

Communication sites are broadcast vehicles designed for a few authors to share information with a wide audience. Most employees have read-only access. Typical examples include your company home page, staff handbook, health and safety policies, holiday calendars, and brand asset libraries.

2. Team Sites Connected to Microsoft 365 Groups

Team sites are collaborative working spaces designed for internal teams and departments (such as Finance, Human Resources, Operations, or Senior Leadership). Every modern Team site is tied to a Microsoft 365 Group, which provides a shared mailbox, calendar, Planner board, and Microsoft Teams channel. Membership is binary: you are either an Owner or a Member, giving you edit access to team documents.

3. Cross-Functional Project Sites

Rather than dumping client projects into a generic department folder, create lightweight Team sites for specific initiatives (for example, "ISO 27001 Certification 2026" or "ERP System Replacement"). Once the project finishes, the entire site can be set to read-only or archived cleanly without disrupting everyday operational files.

4. External Collaboration Sites

If you regularly collaborate with external accountants, legal advisers, suppliers, or sub-contractors, isolate that work in dedicated external-facing sites. Never enable external guest sharing on your core internal finance or HR document repositories. Creating distinct client portals allows you to apply strict sharing policies without risking internal confidentiality.

Designing Document Libraries: Folders vs Metadata

A frequent debate when restructuring SharePoint is whether to abolish folders entirely in favour of columns and metadata. Metadata (such as categorising a document by Document Type, Client Name, Fiscal Year, or Review Status) makes filtering and sorting exceptionally fast. However, forcing busy staff to fill out six mandatory metadata fields every time they save an email attachment often leads to resistance.

The pragmatic middle ground for UK SMEs is what we call the shallow folder rule:

• No more than one or two folder levels: Use folders strictly for natural high-level grouping (for example, sorting invoices by year: 2025-2026 > Q1).
• Multiple dedicated libraries: Instead of placing every departmental file into the default "Shared Documents" library, create separate libraries for distinct document types (for example, "Customer Contracts", "Monthly Reports", and "Supplier Price Lists"). Each library can have its own retention rules and custom views.
• Selective choice columns: Introduce lightweight choice columns for status tracking (such as "Draft", "Approved", "Archived") where it genuinely helps staff find key records quickly.

Permissions Governance: Keeping Access Simple and Secure

Managing security in SharePoint is straightforward if you adhere to one golden rule: manage permissions at the site level using groups, not at the file level using individual user invitations.

When users click the "Share" button on individual Word documents and type specific colleague names, SharePoint creates custom sharing links and unique permissions. Within six months, your IT team will have no idea who has access to sensitive payroll files. To prevent this security debt:

• Use Microsoft 365 Groups: Add and remove users from the parent security group or Microsoft Teams team. When a staff member leaves or joins the department, updating their group membership automatically corrects their access across all connected sites.
• Limit Site Ownership: Keep Site Owners to two or three responsible individuals per department. Site Owners have permission to adjust structure and share files, while standard staff remain Site Members.
• Disable anonymous link creation: In the SharePoint Admin Centre, prevent users from generating public "Anyone with the link" URLs for internal company sites. Restrict sharing to "Specific people" or "People in your organisation".

Step-by-Step Blueprint for Restructuring Your SharePoint

If your existing SharePoint environment is cluttered, do not attempt to fix everything in an afternoon. Follow this structured remediation plan:

Phase 1: Information Architecture Audit

Map out your current file repository. List every department, identify which directories contain sensitive or confidential data (such as HR, payroll, legal, and director files), and flag redundant or obsolete files for archiving.

Phase 2: Build the New Target Structure

Create modern top-level site collections in the SharePoint Admin Centre based on your audit. Establish your main Hub site (such as "EJK Hub") and connect departmental sites to it to build a shared global navigation bar and unified search scope.

Phase 3: Migrate in Phased Batches

Never move live operational data during peak business hours. Migrate department by department using official tools like the Microsoft SharePoint Migration Tool (SPMT) or Migration Manager. Clean up naming conventions during the transfer.

Phase 4: User Training and Governance Review

Show staff how to access their new document libraries through Microsoft Teams, web browsers, and OneDrive shortcuts (instead of synchronising entire massive libraries locally). Schedule a quarterly permissions review to check for orphaned sites and stale guest accounts.

SharePoint Architecture vs Migration Checklist

Use this practical checklist before initiating any SharePoint structural overhaul or file migration:

For official architectural documentation, review the Microsoft Learn guide to modern SharePoint information architecture.

If you are planning a migration from an on-premises server or an older cloud setup, explore our dedicated SharePoint migration services and our specialised SharePoint consultancy in Northampton to ensure your migration is delivered smoothly and securely.