At minimum: payslips and tax documents, leave balance and application, attendance with regularisation, personal and bank detail updates that carry an approval trail, current policy documents, and the reporting line with a searchable directory. Add a manager view for approvals and team visibility. The real test is whether HR's ticket volume for those items falls.
Look at what your HR inbox actually receives over a month and sort by frequency. The list is remarkably consistent: a copy of last month's payslip, how much leave is left, a letter confirming employment for a landlord or a visa, an address change, a bank account change, what the notice period is, who the new reporting manager is, and a correction to an attendance record. None of these needs a human. Each of them is a lookup or a form against data the organisation already holds. Building a portal is really the exercise of moving that specific list out of a queue and onto a page. Start there rather than from a vendor's feature matrix, because a portal that covers eight low-value features and misses the payslip download will not be used twice.
More than a payslip list. Employees need the current payslip, a searchable archive of previous ones, year-end tax statements, and the declarations they are asked to submit each year, with a visible deadline and a status so nobody has to ask whether their submission was received. Add the tax-regime choice where that applies, a view of what has been deducted so far, and a reimbursement or claim path if you operate one. The documents must be downloadable in a format a bank or an embassy will accept, since a screen that displays a payslip but cannot produce a file simply redirects the request back to HR. Where the portal is separate from your [payroll software](/payroll-software), confirm the archive survives a payroll vendor change, because losing historical payslips is a recovery job nobody budgets for.
Not as a free edit. Split the fields by consequence. Contact number, emergency contact and personal email can update immediately with a confirmation, because a wrong value there is inconvenient rather than dangerous. Address, marital status, dependants and identity documents feed statutory records and should go through review with the supporting document attached. Bank account details deserve the strictest path of all: re-authentication, a notification to the employee's registered contact that a change was requested, and an approval before it takes effect. Bank-change fraud through self-service is a real and recurring pattern, and the countermeasure is friction placed precisely where it matters rather than across every field. Whatever the path, keep the previous value and the change record rather than overwriting, so a disputed salary transfer can be reconstructed.
The balance first, because that is what people came for, followed by the ability to apply, the status of anything pending, and the team calendar so someone can see who else is already off before requesting a date. Show the accrual and what will lapse at reset. On attendance, show the current period's record, flag missing punches while there is still time to correct them, and provide the regularisation route directly rather than pointing at a separate system. This section is where a portal earns its adoption, since it is the one people visit monthly rather than annually. Make sure the rules displayed match the ones configured in your [leave management](/leave-management-software) setup, because a portal that shows a balance the payroll calculation disagrees with destroys trust in both.
Managers are the second audience and they are usually served worse than employees. They need a single queue of everything awaiting their decision - leave, attendance corrections, detail changes they are asked to endorse, timesheets - rather than four notifications from four modules. They need their team's leave calendar for planning, visibility of who is out today, and the reporting line beneath them. They need to act from a phone, because approvals that require a desktop are the reason requests sit for days. Deliberately limit what else they see: performance and pay information belongs in different tools with different permissions, and bundling it into the approval screen creates an access problem you will have to unpick later. A delegation setting for when a manager is away is the small feature that prevents most approval backlogs.
Two things employees hunt for constantly. First, current policy documents - leave, travel, expenses, code of conduct, the holiday calendar for their location - with a version and an effective date so nobody argues from a superseded copy. Second, a directory that answers who does what: name, role, location, reporting line, work contact, and enough structure to navigate an unfamiliar department. Add letter generation for the common requests, since an employment confirmation letter produced on demand removes a whole category of tickets. Keep the directory scoped to work information only; personal contact numbers and addresses should not be browsable by the organisation, and the difference between a work directory and an [employee database](/employee-database-software) is exactly this boundary.
Measure the thing it was built to change. Count HR tickets for each category on the list before launch, then count them again after a full cycle. If payslip requests have not fallen, either people cannot find the download or they do not know it exists, and both are fixable. Track login frequency alongside ticket volume, because a portal used once a year at declaration time is not doing the job even if it technically contains everything. Watch the manager approval queue age too, since a growing backlog signals a mobile or notification problem rather than an unwilling manager. Adoption problems in self-service are almost always findability, notification or trust, and each has a different fix, so diagnose before adding features nobody asked for.
Pitch N Hire is an applicant tracking system built for recruiters and hiring teams. If this answer described something you want to run properly, the ATS is where it lives.
Free for 1 user · No credit card · Talk to a real hiring expert
Get a personalized walkthrough of Pitch N Hire on your own roles and workflow. No slides, no obligation.
Prefer to talk? Book a demo · Talk to sales · View pricing
Free 1-user plan · No credit card · Talk to a real hiring expert
See your true cost-per-hire and how much Pitch N Hire could save you — our free Recruitment ROI Calculator gives you the numbers in under a minute. No signup required.
Open the free ROI calculatorPrefer a tailored walkthrough on your real roles? Drop your work email:
★ Free 1-user plan · No spam · Talk to a real hiring expert
