Where is the current travel expense regulation? Who is responsible for a specific technical question? And which message affects your own location? Such questions seem small, but they repeat themselves in everyday company life. An employee portal can create a common entry point. Its value depends on whether information is maintained reliably and everyday tasks actually become easier.

An intranet is therefore more than an internal website with news. It can connect knowledge, documents and operational processes. At the same time, the scope must fit the organization. A cluttered platform with lots of unused features can create the same clutter as the shelves it was intended to replace.

Start with the most important search and work tasks

Before designing, you should observe what questions employees regularly ask. Often it involves contact persons, binding documents, applications or current organizational information. These tasks form a more resilient basis than the desire to recreate as many well-known portal functions as possible.

Different perspectives are helpful: new employees, long-standing specialists, managers and people without a permanent office workplace. You don't necessarily need the same home page. Nevertheless, there should be a common basic structure. An individually adapted interface must not lead to colleagues using completely different terms for the same binding information.

Personalization needs understandable rules

A personal home page can prioritize information by location, role, or team. This is helpful if it makes relevant content easier to access. However, the assignment must be comprehensible. Employees should be able to tell whether they are seeing all messages or just a selection. Important company-wide communications must not disappear through unclear filters.

Personalization should also not be confused with excessive data collection. Many adjustments can be derived from existing tasks and authorizations. Additional behavior profiles are not automatically necessary for this. If personal usage data is evaluated, the purpose, legal basis and, if applicable, operational co-determination must be examined separately.

News with editorial responsibility

A news area needs more than one publishing function. Those responsible for content, target groups and validity should be determined. A message about a short-term change does not have to continue to occupy the same space after it ends. Recurring categories and understandable titles help identify relevant information.

Not every message should trigger an email or push message. Otherwise, another channel will be created whose content will remain unread. A tiered approach can distinguish important organizational notices from general news. It must be clear which channel is mandatory and how employees without regular screen access can be reached.

Treat documents as curated knowledge

A portal shouldn't just wrap an existing folder structure in a new design. Title, responsibility, version and validity are important for central documents. A clear summary can help find the right content. Outdated versions must be recognizable or removed from the normal search without uncontrollably deleting the necessary evidence.

A search function benefits from structured information. Categories, keywords and meaningful file names can make finding things easier. When scanning, it is important to check whether there is any text that can be searched. In addition, the search must not display content that the person requesting does not have permission to view. This applies to both results and preview texts.

Keep the employee directory up to date

Telephone number, subject area and organizational assignment can help with collaboration. However, not every personal detail belongs in a generally accessible directory. The required scope should be coordinated with the tasks and data protection requirements. Photos are also not automatically required standard information.

The source of care is particularly important. If a telephone number is managed manually in several systems, discrepancies quickly arise. Integration can make sense if data responsibility and updates are regulated. In the event of departures or role changes, access and directory entries must be adjusted in a timely manner. A nice profile with outdated responsibilities defeats the purpose.

Internal forms as complete processes

Holidays, equipment or training requests can be recorded using forms. The actual benefit comes from the further process: review, responsibility, decision and feedback. Employees should be able to see their processing status instead of having to ask again by email after sending.

A fictitious equipment request could require different approvals depending on the amount and cost center. Substitutions, rejections and subsequent changes must be taken into account. It is also important that an application is not considered completed just by sending an email. The binding status should remain traceable in the system. Further considerations are discussed in the article Process automation.

Apply roles and rights to content

A login only protects entry. Afterwards, it must be checked for documents, processes and administrative functions who is allowed to access them. Roles can represent general tasks and take additional assignments such as team or location into account. The more complex the model becomes, the more important it is to have understandable rules and tests.

Permissions should also apply to direct file URLs. A hidden menu does not prevent access to an unprotected file. For particularly confidential information, storage, downloading and logging must be considered separately. The practical test therefore also includes an attempt to access a known process with a different role.

Include mobile and barrier-free use

Not all employees work on a large screen. A portal for workshops, field service or changing workplaces requires suitable access and operating concepts. This not only affects layout, but also device availability, registration and connection. A long release form may need to be designed differently on the smartphone than at the desk.

Clear labels, keyboard usability and sufficient contrast help different user groups. Content should remain readable even with larger fonts. Specific tasks are suitable for acceptance: finding a regulation, identifying a responsible person and correcting an application with missing information. Such tests reveal problems that pure function lists do not capture.

Introduction as an editorial and organizational project

Of course, a portal is not only used through a circular email. Those responsible must maintain content and use the intended processes themselves. A limited, well-managed scope often makes sense when starting out. Existing information channels should be deliberately replaced or demarcated so that no contradictory versions remain in parallel.

Feedback is graded based on actual tasks. Which search query often does not lead to the desired result? Where do additional questions arise? Which information is out of date? Measurements should be data-efficient and with a clearly defined purpose. The number of page views alone says little about whether people were able to complete their task successfully.

Distinguish binding content from exchange

A portal can contain both informal news and binding regulations. This content should be treated visibly differently. A team discussion does not replace an approved policy. Conversely, a short message does not have to go through the same complex approval process as a company-wide procedural instruction.

For binding documents, information on validity, responsible body and replaced version helps. When making changes, it should be clear whether a typographical error has simply been corrected or a technical rule has been adjusted. Employees can then better assess whether they need to change their approach. A mere list of recent uploads often does not convey this meaning.

Another question concerns accessibility in the event of an outage. What information is needed if the portal is currently unavailable? Emergency contacts or operational backup procedures should not reside exclusively in the affected system. The information concept must take the actual working environment into account and, if necessary, provide for other protected means of provision.

At the start, a small editorial team can check central content together with specialists. Duplicate and contradictory versions will be cleaned up before they are adopted. A recurring inspection date will then be set. This creates a knowledge base whose reliability does not solely depend on the attention of individual, particularly committed people.

A joint start with clear care

A good employee portal combines current information, discoverable knowledge and traceable processes. Its quality arises from a suitable content model and binding responsibility. Technology can make this work easier, but cannot completely replace it.

Ours fictitious employee portal shows a possible interface with messages and quick access. For a concrete implementation, GRITTMANN would first record the most important internal tasks, sources of care and authorizations. From this, a manageable initial scope can be developed that can offer verifiable benefits in everyday life.

Sources and further documentation

Technical basics and additional information from the respective editors. Links last checked on 06.10.2026.