A Checklist for SharePoint Intranet Design

A SharePoint intranet checklist: hub site architecture, task-oriented navigation, content ownership, the permission model, search, Teams integration and post-launch maintenance.
Technical summary
Technology
SharePoint Online, Viva Connections, Microsoft Search
Topic
Intranet planning
Level
Start
In this article10 sections

Most SharePoint intranet projects start with a beautiful home page design and end a few months later with news that isn’t updated, ownerless pages and a menu nobody opens. The problem isn’t SharePoint but the questions left unanswered before launch. The checklist below gathers, in order, the items most often skipped in the field, from information architecture to the permission model and from search to post-launch maintenance.

1. Purpose and user tasks

Don’t move on to home page design before putting in writing what the intranet is for. In the meeting everyone says “a communication portal”; but one person pictures an announcement board, another a document repository and another a forms center. These three expectations don’t fit on the same home page.

  • Are the intranet’s three main purposes written down (e.g. official communication, access to policies and forms, entry to internal services)?
  • Have the 15–20 tasks employees do most often been listed (leave requests, expense forms, finding who to call, reading policies)?
  • Have the different needs of field, office and management users been identified?
  • How will success be measured (active users, announcement read rate, form usage, search success)?

When building the task list, ask employees directly, not department managers. The manager says “our procedures should be visible”; the employee asks “where’s the leave form?” The first screen of the home page should answer the second question.

2. Information architecture

Modern SharePoint uses a flat site structure and hubs that group these sites, instead of the classic subsite hierarchy. Each department or project has its own site, and through hub association they share common navigation, theme and search scope. The advantage of this structure is flexibility: when the organization changes, sites don’t move; only the hub association changes.

  • Has the hub site structure been decided? The main intranet hub, department/location sites and associations.
  • Is navigation designed around tasks rather than the org chart? Has it been tested in employees’ own words with card sorting?
  • Have communication sites (publishing) been separated from team sites (collaboration)?
  • Have page and news templates, content types and metadata been defined?

The mistake we see most often in the field is a menu that’s an exact copy of the org chart. Only HR knows the path “Human Resources > Payroll and Benefits > Forms”. Employees type “expense” or search for “form”. Menu labels should be written with the words that come out of card sorting tests; menus deeper than two levels are hardly ever used.

3. Content and ownership

The technical setup is done in a few weeks. Keeping the content current is work that goes on for years. A page without an owner is out of date within six months.

  • Does every site and page have a content owner?
  • Has an inventory of content to migrate been taken, and have old and duplicate items been weeded out?
  • Has a publishing and review schedule been set?
  • Will policies and procedures be published from a controlled document library?

Run the content inventory with a simple table: source location, content owner, decision (move / rewrite / archive / delete) and target site. Copying the “Shared” folder on the network drive as it is isn’t an inventory; it moves the same mess to the new platform and pollutes search results from day one.

4. Permission model

The basic rule of an intranet permission model is simple: everyone reads, few people write. When edit rights are spread to every department, it becomes impossible to track who changed what.

  • Is read access broad and edit access narrow?
  • Are permissions granted through Entra ID or Microsoft 365 groups instead of individuals?
  • Has the use of broken inheritance (unique permissions) been kept to a minimum?
  • Has an external sharing policy been set by site type?
  • Has showing content to the relevant groups with audience targeting been planned?

Inheritance broken one by one at folder or file level turns into a structure that can’t be audited a few years later. If confidential content is needed, open a separate site and grant permissions at site level. Audience targeting isn’t a permission mechanism; it only shows or hides content, it doesn’t block access. Explain this distinction to content editors from the start.

Before setting up the intranet, define the limits on guest and external partner access within the framework of SharePoint and OneDrive external sharing security.

If users can’t find what they’re looking for in the menu, they turn to search. If search comes back empty too, they close the intranet and go back to asking by phone.

  • Have recommended results (bookmarks) and acronyms been defined for Microsoft Search?
  • Has unnecessary or old content been cleaned up so it doesn’t pollute search results?
  • Are people cards and organization information correct in Entra ID (job title, department, manager)?

People search is one of the most-used functions of an intranet, and it takes its data directly from Entra ID. If there are users with an empty job title or a wrong manager field, their people card looks wrong too. Clean up the directory data before launch. This prevents more complaints than the home page design does.

6. Teams and mobile

  • Will the intranet be offered inside Teams with Viva Connections?
  • Will important announcements also be shared in Teams channels?
  • Have page layouts been tested on mobile devices; do field employees have accounts and licenses?

In most organizations, the app employees keep open all day is Teams. Bringing the intranet into Teams with Viva Connections, instead of confining it to a separate browser tab, removes a barrier to use. On the field staff side, the technical problem is usually licensing: mobile access can’t be provided for a shared tablet account or an employee without email until an identity and licensing plan is in place.

7. Processes and forms

  • Which forms will be built with Microsoft Forms, and which with Lists or Power Apps?
  • Have forms that need approval been connected to Power Automate approval flows?
  • Is there an entry point from the intranet to the helpdesk portal for IT requests?

The practical distinction is this: Microsoft Forms for one-off surveys and simple information gathering; Microsoft Lists for requests that need records and status tracking; Power Apps for processes that need conditional fields, multi-step screens and external data. Teams that start with Forms and later face the question “what’s the status of this request?” end up having to move the form to Lists. Choose the right tool from the start.

8. Launch and adoption

  • Have content editors been trained; are publishing rules written down?
  • Have launch communications and management support been planned?
  • Will usage statistics and feedback be collected for the first 30 days?
  • Have checks for broken links, old content and ownerless pages been scheduled?

Launch isn’t the close of a project; it’s the start of operations. Site usage analytics show which pages aren’t being opened; these pages are either in the wrong place or unnecessary. In a quarterly review, ownerless sites, pages belonging to employees who have left and expired announcements should be cleaned up.

Common mistakes

Moving the entire network drive to the intranet, making the menu the same as the org chart, giving every department full edit rights and not defining content ownership after launch are the most common mistakes. These mistakes lower search quality, create permission chaos and lead users to abandon the intranet.

Add two more items to these. The first is putting too many web parts on the home page: when news, events, birthdays, weather, a social feed and quick links are all on the same screen, none of them get read. The second is giving departments permission to create sites without defining a tenant-wide theme and site design; within a few months, every site you come across has a different color and a different menu. Visual consistency is achieved from the start with a site creation template, not afterwards.

Frequently asked questions

How many hub sites are needed?

In most mid-sized organizations, a single main hub (the intranet) and, if needed, a few hubs for department or location groups are enough. Hubs should reflect how users look for information, not the org chart.

What should be used as the intranet home page?

The tenant’s root site can be set up as a communication site and made the main hub; with Viva Connections, the same entry point is also reachable from within Teams.

What will happen to our old classic SharePoint pages?

They can be converted to the modern experience, or the content can be moved to new sites. Valuable content should be separated out and the old content archived.

To apply the checklist to your organization and build the intranet together, see our SharePoint intranet and employee portal service.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Web

We build and maintain corporate websites, WordPress and CMS platforms, intranet and SharePoint portals, document management, and form and approval workflows, and keep them secure and up to date.

Knowledge Center

Other articles