Request a quote
Emergency SectorsCareers About us Blog Get in touch
Long open-plan office with glass walls and colleagues at their desks in the sunlight

Intranet software: what it must do before you choose a product

Intranet software for a smaller organisation has two jobs: showing staff what is going on, and giving them one front door to the systems they need. Keep those two sharp and the choice gets easier. Add the archive, the procedures and the collaboration too, and you get a home page nobody opens.

6 min read Written by the ITproposal team
Short answer

An intranet is the place for organisational news and the front door to the systems staff use. Procedures belong in a knowledge base and work in progress in the collaboration workspace.

Whether an intranet gets used depends mostly on who has to read it and how they sign in. Frontline staff without a desk or laptop shape the choice more than any feature.

The product comes from a vendor and the content from your organisation. Without an editor and a fixed rhythm, any intranet goes quiet within a year.

What an intranet should do in an SME

The word intranet covers almost anything: a shared drive, a wiki, a site full of forms. For an organisation of a few dozen to a few hundred people, a narrower definition works better. An intranet does three things.

  • Organisational news. What is changing, who is starting, what is happening at the other site this week. It replaces the all-staff email.
  • One front door. Links to the rota, the HR portal, the place to report a fault, the business applications. A new starter does not have to ask where everything is.
  • Who is who. A directory with names, roles and how to reach someone.

What does not belong there: procedures someone has to maintain (that is a knowledge base) and files teams are working on (that is the collaboration workspace). They touch the intranet, but they have a different rhythm and a different owner. Merge them and yesterday’s news sits next to a three-year-old procedure, and nobody knows what is still true.

Start with who has to read it

The biggest mistake in choosing intranet software is starting with features. Start with the reader. In an office business everyone has a laptop, an account and a mailbox. In retail, warehousing, care or construction, many people do not, and they are exactly the ones who miss the news.

Four questions that shape the choice more than any demo:

  • How many staff have their own account? And what does it take, in management and licences, to give the rest one?
  • Do they read on a phone? Then the intranet has to work on a phone without zooming, and you need to know whether it is their own phone.
  • Do they share a device? A till, a tablet in the canteen, a PC in the workshop. Signing in and out there has to be quick.
  • Which languages do they speak? An organisation with sites in several countries, or many international colleagues, needs multilingual support built in, not a translate button.

The sign-in decides whether it gets used

An intranet with its own password does not get used. It is that simple. The sign-in should be the same as for the rest of work, with single sign-on on the account people already have. It is also the secure choice: when someone leaves and their account is disabled, they lose the intranet at the same moment. A separate account in a separate system often stays open for months.

For staff without an office account there are roughly two routes: they get a basic account in your existing environment, or the intranet product provides its own access, for example through the app with a code. The first is easier to manage, the second is sometimes easier for shift workers. Write down how such a person is removed again; that is the part most often forgotten on the second route.

How identity, device and applications together make up the workplace is covered in our piece on the digital workplace.

Choosing intranet software: the questions before the demo

A demo shows what looks good. These questions show what still works after a year:

  • Does it connect to the identity you already have? Single sign-on, and groups that update automatically when someone changes team.
  • Can you target news? By site, department or language, without the editor maintaining a list for each post.
  • Does it work as an app and in the browser? With notifications people can switch off per topic; otherwise everyone switches them all off.
  • Where is the data, and who processes it? A staff directory holds personal data; under UK GDPR you need a processing agreement and should know which country it sits in.
  • Can you export the content? If you switch in five years, you want to take the posts and pages with you, not retype them.
  • Who is the administrator? A named person on your side, and at least two, so the intranet is not locked when one of them leaves.

If you already have Microsoft 365, look at what is within reach there before buying a separate product. It is not always the best option, but it is the comparison you should make.

Who fills it, and how often

An intranet is a communications tool, not an IT project. The owner sits in communications, HR or the leadership team, not in IT. IT handles access and keeps the product running; what goes on it and whether it is right is someone else’s call.

What works in a smaller organisation:

  • One editor with a fixed rhythm. Two posts a week that say something beat ten that nobody reads.
  • Departments supply, the editor publishes. Giving everyone write access sounds democratic and produces a noticeboard.
  • An expiry date on news. Anything that will be wrong in three months moves to the archive by itself.

If the product can show who reads what, decide in advance what you do with that. Per-person reading statistics are monitoring of staff, and employees should be told about it before it starts.

Three ways an intranet goes quiet

  • It becomes the archive. Every department puts its documents there because it exists. After a year nobody looks anything up, because the answer sits among twenty old versions. Keep files where they are edited and link to them.
  • Email stays the real channel. If important news also goes to everyone by email, nobody learns to open the intranet. Pick a moment when the intranet becomes the place, and stick to it.
  • Nobody sees the home page. An intranet you have to look for does not get looked for. Set it as the browser home page, as an app on the phone and as a fixed tile on shared devices.

Where our work stops

What we do. We handle the IT side of an intranet: accounts and single sign-on, groups and permissions, access for staff without an office account, the apps on managed phones and shared devices, and the moment a leaver drops off automatically. We are ISO/IEC 27001 certified, and that is how we set up that access too.

What we do not do. We do not supply intranet software and do not choose it for you; the platform comes from a vendor. Nor do we write content or run internal communications: what goes on the intranet, and who decides that, belongs to your organisation. Whether reading statistics need to be discussed with staff representatives is for your own lawyer or HR adviser.

Frequently asked

Questions about intranets

The five we hear most.

What is an intranet?

An intranet is a private website or app for the staff of one organisation. In a smaller business it mainly does three things: brings organisational news, offers one front door to the systems people use, and shows who is who. Only people who sign in with an organisational account can reach it.

What is the difference between an intranet and a knowledge base?

An intranet brings news and points onwards; most of what is on it is old within weeks. A knowledge base holds procedures and answers that someone keeps up to date, with an owner and a review date per article. They can live in the same product, but they have a different rhythm and often a different owner.

Does a small business need intranet software?

Not always. With twenty people on one site, a well kept channel in the collaboration workspace is often enough. An intranet becomes useful once there are several sites, shift work, or staff without an office account who would otherwise miss the news.

How do staff without a laptop get onto the intranet?

Through a basic account in the existing environment, or through access provided by the intranet product itself, usually via an app on the phone. The first is easier to manage because the account ends with the employment. With the second you have to record separately how someone is removed when they leave.

Do you supply intranet software?

No. The intranet product comes from a vendor, and the content and internal communications belong to your organisation. We handle the IT side: accounts, single sign-on, permissions, access for staff without an office account and the apps on managed devices.

Related services

Further reading

What the intranet connects to.

Shall we sort out access to your intranet?

Tell us who needs to read the intranet and on which devices. We will say how accounts, sign-in and leavers can be handled; the product and the content remain your choice.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call