What is a corporate intranet and what does it give your company?

A corporate intranet is the internal digital hub that only your own employees can reach. Announcements, HR documents, the people directory, leave requests and team collaboration all live at a single address. Unlike your public website, an intranet looks inward: it serves the employee, not the customer.

What problem does an intranet solve?

Most companies don't go looking for an intranet as a wish; they arrive at it after a pain has been building for a while. The symptoms tend to be familiar:

• The same announcement is posted to a chat group, sent by email and pinned to a board — and nobody knows who read it.
• Nobody is sure who holds the latest version of the leave form.
• A new joiner spends their first week asking "who do I ask about this?"
• Field and store teams are the last to hear what head office decided.

What these have in common is scatter. The information exists, but not in one place; announcements go out, but their reach is never measured. An intranet closes exactly those two gaps: a single source and measurable reach.

Are a portal, a file server and an intranet the same thing?

No. A file server stores documents but carries no context: it doesn't know which version of a policy is current, who has read it, or who it applies to. A classic corporate portal is usually a list of links — it points employees at other systems instead of finishing the job itself.

A modern intranet completes the work inside itself: the announcement is published, read receipts are collected, a leave request is opened, a manager approves it, the process closes. That is why it helps to think of an intranet not as a "site" but as the place where an employee's working day begins.

What does an intranet typically contain?

Scope varies by company, but the core building blocks are similar:

1. Announcements and news — pinned posts, and critical notices that require acknowledgement.
2. People directory and org chart — who is who, who reports to whom, who is available right now.
3. Document centre — policies, forms and templates, with version tracking.
4. Self-service requests — leave, expenses, IT support, room booking.
5. Culture features — a recognition wall, surveys, an ideas platform, communities.

Our modules page explains what each of these does in detail.

Where does measurable value come from?

The return usually shows up under three headings. First, search time: the minutes an employee spends locating a document or the right person. Second, repetitive HR load: the same question asked dozens of times, the same form chased by hand. Third, reach: whether teams away from a desk actually receive an announcement at all.

The way to measure these is to write down the current state before you launch. How many "where do I find this form?" questions arrive each month? How many days does a critical announcement take to reach the field? Those two numbers are the only concrete ground on which you can discuss the return six months later.

Does a small company need one?

The need grows with information scatter, not with headcount. A 40-person company spread across three sites may need one more than a 120-person company sitting on a single floor. Shift work, field teams and remote working all lower the threshold; we go into who it suits on this page.

Where does an intranet stop and business software begin?

A frequent question is whether an intranet replaces your ERP or HR system. It doesn't. The ERP holds the record itself: payroll, accounting, stock. The intranet is the employee-facing surface of those records — it shows the leave balance, starts the request, carries the approval and reports the outcome.

That distinction produces two practical benefits. Employees don't have to learn ten different interfaces; they start in one place. And master data stays in one system: instead of maintaining its own user list by hand, the intranet matches your corporate directory, so a title change made in the HR system is simply followed.

A good rule of thumb: if a piece of information is maintained separately in two places, it will eventually disagree with itself until an integration exists.

Where should you start?

The most common mistake is switching on every module on day one. What works is starting narrow: announcements, people directory and documents. Once those three have become a daily habit, add requests, recognition and surveys. Our 90-day rollout plan walks through the first three months step by step.

If you are still evaluating options, our selection guide lists the questions worth asking.