Creating a New SharePoint Site: A Complete Step-by-Step Guide for UK Businesses

Creating a new SharePoint site is one of those tasks that looks deceptively simple from the outside. Log into Microsoft 365, click a few buttons, and within minutes a new site exists. The technical barrier to creating a SharePoint site is genuinely low — which is part of the reason why so many organisations end up with SharePoint environments containing hundreds of sites, most of which are poorly structured, inconsistently named, and largely unused.

The challenge is not creating a SharePoint site. The challenge is creating a SharePoint site that works — that serves a clear purpose, is structured logically, is designed to be used by its intended audience, is governed properly from day one, and integrates cleanly with the broader SharePoint and Microsoft 365 environment it sits within.

This guide is for UK businesses and teams that want to get that right. Whether you are creating a SharePoint site for your HR department, a major project, a company intranet, or an internal knowledge base, the principles and practices covered here will help you build something that does what it is supposed to do — and keeps doing it long after launch.

Why Creating a New SharePoint Site Deserves More Thought Than It Gets

The ease of creating a new SharePoint site is a double-edged sword. In organisations where site creation is ungoverned — where any user can create a site at any time without reference to a naming convention, a template, or a governance framework — SharePoint quickly becomes a sprawling, incoherent environment.

Consider what happens in a typical ungoverned SharePoint tenancy over two years. The marketing team creates a site for a campaign. The project team creates a site for a new initiative. Someone creates a site to replace a shared drive. Someone else creates a site that duplicates an existing one because they could not find the existing one. Sites accumulate with names like “New Site,” “Test,” “HR 2023,” and “Marketing v2.” Nobody knows what belongs where. Search surfaces results from five different places for the same content. Employees stop trusting SharePoint as a source of truth because they never know whether they have found the most current version of what they are looking for.

Creating a new SharePoint site thoughtfully — with clear purpose, consistent structure, appropriate governance, and integration with the existing environment — prevents this outcome. It is worth taking the time to do it properly.


Understanding the Two Main SharePoint Site Types

The first and most consequential decision when creating a new SharePoint site is choosing the right site type. Modern SharePoint offers two primary site types — communication sites and team sites — and they are designed for fundamentally different purposes.

Communication Sites

A communication site is designed for one-to-many publishing. A small number of authors create and publish content that is read by a potentially large audience. Communication sites do not have an associated Microsoft 365 Group or Teams workspace — they stand alone as publishing destinations.

Communication sites are the right choice for:

– Corporate or departmental intranet home pages
– HR policy and procedure libraries
– IT help and support portals
– Company news and announcements sites
– Knowledge bases and reference libraries
– Any site where the primary purpose is distributing information to a wide audience

Communication sites have a richer set of visual layout options than team sites. They support full-width pages, hero web parts, news web parts, and a range of layout templates designed to create polished, editorial-quality pages. If the site you are creating needs to look professional and communicate information effectively to a broad audience, a communication site is almost certainly the right choice.

Team Sites

A team site is designed for collaboration within a defined group. When you create a team site, Microsoft 365 automatically creates a corresponding Microsoft 365 Group — which includes a shared mailbox, a shared calendar, a Planner board, and a Teams workspace. The SharePoint team site is the file storage and page layer for that group.

Team sites are the right choice for:

– Project teams and working groups
– Department collaboration environments
– Any context where a defined group of people need to share, co-author, and collaborate on documents and content
– Internal team workspaces that are not intended for a broad audience

Team sites have a more functional visual profile than communication sites. They are designed for working in rather than reading — with document libraries, lists, and collaboration features taking precedence over editorial design. If the site you are creating is a working environment for a team rather than a publishing destination for an audience, a team site is the right choice.

The Hybrid Approach

Many SharePoint environments use both site types in combination. A department like HR might have a communication site that serves as its public-facing intranet presence — policies, procedures, announcements, and resources for all employees — alongside one or more team sites for the HR team itself, where confidential work, recruitment documentation, and internal processes are managed.

Understanding this distinction before creating a new SharePoint site prevents the common mistake of choosing the wrong type and then trying to use it in a way it was not designed for.


Planning Your SharePoint Site Before You Build It

The biggest investment of time in creating a new SharePoint site well is not in the building — it is in the planning. The decisions made before a single page is created determine whether the site will be useful, navigable, and maintainable.

Define the Purpose

Every SharePoint site should have a single, clearly articulated purpose. Not “somewhere for the team to share stuff” but “the central resource for the Finance team’s month-end close process, including templates, checklists, guidance documents, and a status tracker.” The more specifically you can define the purpose before you start building, the more purposefully you can design the site.

Identify the Audience

Who will use this site? How many people? How technically confident are they? Will they primarily access it from a desktop browser, from Teams, or from a mobile device? What do they need to be able to find, and how quickly? Answering these questions before designing the site’s structure and navigation ensures you are building for the people who will actually use it.

Map the Content

Before creating any pages or document libraries, map the content that the site will contain. What categories of information belong here? What documents, pages, and tools does this site need to house? How do those categories relate to each other — what belongs at the top level of the navigation, what sits beneath it? This content map becomes the blueprint for the site’s information architecture.

Define the Governance Model

Who will own this site? Who will have permission to create and edit content? Who will have read-only access? How will permissions be managed — through individual assignments, through Microsoft 365 Groups, or through a combination? How often will content be reviewed? Who is responsible for keeping it current? These governance decisions are much easier to make before the site launches than to establish retrospectively.

Consider How the Site Fits in the Broader Environment

Creating a new SharePoint site in isolation — without considering how it relates to other sites, whether it should be associated with a hub, and how it will appear in search and navigation — produces sites that work in themselves but do not integrate cleanly with the wider SharePoint environment. Before building, consider whether the new site should be associated with an existing hub, what global or hub navigation should link to it, and whether it duplicates a site that already exists.


Step-by-Step: Creating a New SharePoint Site in Microsoft 365

With the planning complete, the technical process of creating a new SharePoint site is relatively straightforward. Here is how it works in modern SharePoint Online.

Step 1 — Access the SharePoint Start Page

Navigate to SharePoint from the Microsoft 365 app launcher. The SharePoint start page displays your recently visited and followed sites, and provides the option to create a new site.

Step 2 — Click Create Site

The Create site button in the top left of the SharePoint start page initiates the site creation flow. Depending on your organisation’s SharePoint governance settings, you may be prompted to submit a site creation request rather than creating a site directly — this is by design in organisations that have implemented site creation governance.

Step 3 — Choose Your Site Type

You will be offered the choice between a Team site and a Communication site. Based on the purpose you defined in your planning phase, choose the appropriate type. This decision cannot be easily changed after the site is created, so take it seriously.

Step 4 — Choose a Template

Modern SharePoint offers a range of site templates that provide pre-built page structures and content frameworks for common use cases — department sites, project sites, event sites, and others. These templates are a useful starting point but should be treated as a foundation to customise rather than a finished product. Selecting a template that broadly matches your use case saves time in the initial build.

Step 5 — Configure the Site Details

Name your site. The site name determines the URL, so choose it carefully and consistently with your organisation’s naming conventions. A site named “HR” will have the URL /sites/HR — which is clean and predictable. A site named “Human Resources Department New 2024” will have a URL that is long, awkward, and inconsistent with other sites.

Add a site description. This appears in search results and site listings and helps users understand what the site is for without having to visit it.

Step 6 — Configure Privacy Settings (Team Sites Only)

For team sites, you will be asked whether the site should be private — accessible only to named members — or public, accessible to everyone in the organisation. For most team sites, private is the appropriate setting. Public team sites are rarely the right choice — if content should be accessible to everyone, a communication site is more appropriate.

Step 7 — Add Site Owners and Members

Add the people who will own and manage the site. Site owners have full control over the site — they can manage permissions, add and remove members, and delete content. For team sites, you will also add members at this stage. For communication sites, access is managed through page permissions and the SharePoint visitor role.

Step 8 — Apply Sensitivity Labels If Applicable

If your organisation uses Microsoft Information Protection sensitivity labels, apply the appropriate label to the site at creation. The label determines what data classification applies to content stored in the site and what protections are applied to it. For sites that will contain confidential or sensitive information, this is an important governance step that is much easier to apply at creation than to add retrospectively.


Building Out Your SharePoint Site

With the site created, the work of building it properly begins. This is where the planning you invested in earlier pays dividends.

Establishing the Site Navigation

Configure the site navigation to reflect the content map you defined in the planning phase. For communication sites, the top navigation bar is the primary wayfinding tool — keep it to six items or fewer at the top level, with sub-navigation used for secondary content. For team sites, the left-hand navigation provides the structure — again, keep it purposeful and organised rather than allowing it to grow organically into an unnavigable list.

Creating Document Libraries

Document libraries are the primary content storage mechanism in SharePoint. Most sites need at least one document library, and many need several — organised by content type, audience, or process rather than simply reflecting the existing folder structure from a shared drive.

When creating document libraries, resist the temptation to mirror the deeply nested folder structure that most organisations inherit from file servers and shared drives. SharePoint’s metadata and filtering capabilities make deeply nested folders unnecessary. A flatter structure with well-applied metadata — document type, department, status, date — makes content more findable through both navigation and search.

Creating SharePoint Lists

SharePoint lists are structured data tables that can serve a wide range of purposes — project trackers, leave request logs, equipment inventories, risk registers, supplier directories. Lists are one of SharePoint’s most powerful and most underused features. When a site needs to manage structured information rather than just store documents, a SharePoint list is almost always preferable to a document-based approach.

Building Pages

The pages on a SharePoint site are built using a drag-and-drop web part interface. Web parts are modular content blocks — text, images, document libraries, news feeds, quick links, people profiles, and many others — that can be arranged on a page canvas to create the desired layout.

The home page of any new SharePoint site deserves the most design attention. It is the first thing users see and the primary navigational hub for the site. A well-designed home page uses a hero web part to highlight the most important content, a news web part to surface recent updates, a quick links web part to provide direct access to frequently used resources, and a text or image web part to orient users to the site’s purpose.

Configuring Permissions

SharePoint permissions are managed through a hierarchy of permission levels and groups. At the site level, there are typically three default groups — Owners, Members, and Visitors — with Full Control, Edit, and Read access respectively.

For most sites, managing permissions through Microsoft 365 Groups rather than individual SharePoint permissions is the right approach. Adding a user to the Microsoft 365 Group associated with a team site automatically grants them the appropriate SharePoint access. Managing permissions individually — adding named users to SharePoint permission groups directly — becomes unmanageable at scale and creates compliance risks when people leave or change roles.

Row-level permissions — restricting access to specific document libraries, folders, or individual items within a site — should be used sparingly. SharePoint’s performance degrades with complex permission structures, and heavily permissioned sites become difficult to maintain. If content segmentation is a major requirement, separate sites with appropriate top-level permissions are usually a better approach than a single heavily permissioned site.


Associating Your New Site with a Hub

If your organisation uses SharePoint hub sites — and it should — associating your new site with the appropriate hub is an important step that is often overlooked.

Hub association applies the hub’s shared navigation and branding to the new site, integrates its content into hub-level search, and establishes the organisational relationship between the new site and the broader SharePoint environment. A Finance department site associated with the Finance hub appears in Finance hub navigation, surfaces its content in Finance hub search, and benefits from the branding and design consistency that the hub enforces.

Associating a site with a hub requires hub owner or SharePoint administrator permissions. If your organisation has a site creation governance process, hub association is typically managed by the SharePoint administrator as part of that process.


Applying Branding and Design

A newly created SharePoint site, before any branding is applied, looks like a default Microsoft product. For a team site that is primarily used for internal collaboration, this is often acceptable — the priority is function, not form. For a communication site that is part of a company intranet, or any site that represents the organisation to a broader internal audience, branding matters.

Modern SharePoint supports custom branding through the Change the Look settings — allowing custom colour palettes, header layouts, and site logos to be applied. For more sophisticated branding, SharePoint site designs can be deployed by administrators to automatically apply consistent branding and configuration to newly created sites.


Training Site Owners and Content Authors

A new SharePoint site that its owners do not know how to manage is a site that will decay. Before handing over a newly created site, ensure that site owners understand:

How to manage permissions — adding and removing members, adjusting access levels, and understanding the permission inheritance model.

How to create and publish pages — using the web part interface, the page approval workflow if enabled, and the publishing and scheduling options.

How to manage document libraries — creating folders, applying metadata, managing version history, and recovering deleted items from the recycle bin.

How to configure site navigation — adding, removing, and reordering navigation items at the site level.

How to monitor site analytics — accessing the built-in usage data to understand who is visiting the site and what they are engaging with.

This training does not need to be extensive — a one-hour session covering the essentials, supported by written documentation, is usually sufficient for site owners who are reasonably comfortable with Microsoft 365 tools. What matters is that it happens before the site goes live, not after problems have already emerged.


Common Mistakes When Creating a New SharePoint Site

The most expensive mistakes in SharePoint site creation are not the obvious technical errors — it is the architectural and governance decisions that seem minor at the time but compound over months and years.

Choosing the wrong site type. Building an intranet publishing hub as a team site, or creating a project collaboration environment as a communication site, produces a site that fights against its own design. Choose the site type that matches the primary purpose, even if the other type has features that appeal in the moment.

Creating a site without a governance plan. A site with no named owner, no defined membership, no content review schedule, and no permissions management process is a site that will become a problem. Establish governance at creation, not six months later when the problems have already accumulated.

Using deeply nested folder structures. SharePoint is not a file server. Organising content in deeply nested folders wastes SharePoint’s metadata and filtering capabilities and makes content harder to find through search. Design document libraries with a flatter structure and well-applied metadata from the outset.

Over-permissioning. Complex permission structures — with unique permissions on individual items, folders, and libraries across the same site — are a maintenance burden and a compliance risk. Keep permissions as simple as possible, managed at the site or library level rather than at the item level wherever possible.

Not associating the site with a hub. A site that floats disconnected from the hub structure is invisible to users who navigate via the hub, does not benefit from hub branding and navigation, and does not surface in hub search. Always associate new sites with the appropriate hub unless there is a specific reason not to.

Launching without content. An empty site is worse than no site — it communicates to users that the platform is not ready to be trusted. Before launching any new SharePoint site, ensure that the key content areas are populated with accurate, current content that justifies the site’s existence.


Working with NetMonkeys on Your New SharePoint Site

Creating a new SharePoint site well — from initial architecture decisions through to build, governance, and launch — is a more involved process than the simplicity of the technical creation steps suggests. NetMonkeys has built SharePoint sites for UK businesses across a wide range of purposes and sectors, and we bring a structured, experienced approach to every engagement.

Our creating a new SharePoint site service covers the full end-to-end process — requirements gathering, site type selection, information architecture design, build and configuration, permissions setup, branding, training, and post-launch support. 



Conclusion

Creating a new SharePoint site is a straightforward technical task that conceals a genuinely complex set of decisions about architecture, governance, design, and purpose. The organisations that invest in making those decisions carefully — before they start building — create SharePoint sites that serve their users, integrate cleanly with the broader environment, and remain useful and manageable over time.

The organisations that treat site creation as purely a technical task — clicking through the creation wizard and starting to add content without a plan — create sites that work initially and then gradually become problems. The sprawling, inconsistent, underused SharePoint environments that frustrate so many UK businesses are almost always the result of accumulated site creation decisions that were made without sufficient thought.

Getting it right is worth the effort. And if you want expert support in getting it right, NetMonkeys is ready to help.