In a company with 35 employees, an employee portal can sound excessive. Yet every month the office manager answers the same questions: Where is the current expenses policy? Who orders a laptop? Was the sickness notification received? Company size does not prevent information loss. It merely makes the loss more personal
Monday, 9:06 a.m.: a question starts travelling
A new employee needs access to a project drive. They ask their manager, who forwards the request to IT. IT needs a cost centre and confirmation. Two days later there are four emails and no unambiguous status. A portal does not fix this by sending another message. It needs a structured request with an owner, required information and a visible next step
This is the useful perspective for a small business: the portal is not an internal homepage. It is a shared queue for recurring work and a dependable place for current information
Search before navigation
Employees rarely know the organisation structure as well as the people who designed the menu. They search for “working from home”, not “policy for mobile service delivery”. Good internal search understands everyday wording, synonyms, document titles and concise answers. Results show an owner and review date so that nobody mistakes a five year old rule for current policy
Many questions do not deserve a PDF at all. A clear page with an answer, scope and contact is easier to maintain and works better on a phone. Attachments remain useful for forms or signed originals
Three work streams are enough to begin
Internal requests
IT access, purchasing and certificates each receive a short form. Every request gets an identifier, category, deadline and responsible group. Personal data is collected only when the work requires it
Onboarding
Tasks depend on role and start date. The manager, HR and IT see their outstanding items; the new employee sees only the relevant steps. Dependencies are explicit: an account cannot be created until the name and start are confirmed
Current knowledge
Policies and instructions have an owner, audience and review date. If the owner leaves, responsibility must be transferred. Otherwise the portal ages in exactly the same way as a shared drive
SSO reduces accounts, not governance
Signing in through the existing identity provider reduces extra passwords and enables central offboarding. Every application still has to decide which group may view or trigger which action. Broad roles such as “employee” and “administrator” are inadequate for HR files, pay information and health data
Logging should cover sensitive access without becoming surveillance of ordinary work. The purpose, access and retention of logs must be clear. An employee portal processes trust related data; unnecessary activity profiles damage that trust
When a small portal becomes too large
The common mistake is to digitise every department at once. The result is eight forms, three unfinished knowledge areas and a dashboard nobody needs. Start with one process that repeats frequently. After four weeks, ask: Which questions disappeared? How long did requests remain unowned? Which searches returned no result?
Those search gaps are an editorial task list. If twenty people search for “parental leave” and find nothing, the search engine is not the main problem
A practical boundary test
A small business may not need a portal while information changes rarely, requests remain manageable and one person can reliably cover them. A portal becomes more likely when knowledge depends on individuals, onboarding repeatedly misses steps or confidential requests sit in unprotected inboxes
The article on an onboarding portal explains the dependency model for larger starting processes. In an employee portal, however, professionalism does not begin with feature breadth. It begins with one current answer and one request whose owner is always known