HR & employee experience
Employee Self-Service HRIS in the Philippines: A Practical SME Guide
By ElevenOS ··5 min read
An employee self-service HRIS gives staff a direct place to find their own work information and submit requests. For a Philippine SME, the useful starting point is often simple: Where is my next shift? Was my leave request approved? Is my attendance record complete? A portal works well when employees understand their tasks, managers know which decisions belong to them and HR maintains the underlying records. This guide explains how to introduce self-service with clear responsibilities, practical access checks and an onboarding process employees can actually complete.
Published by ElevenOS. Product scope and quotes can change; confirm your requirements with each provider.
In this guide
7 sections
1. Choose the first questions self-service should answer
List the questions your HR team receives repeatedly. Choose a small set that employees can answer from maintained records, such as their published schedule, attendance or leave-request status. Keep questions requiring judgment with a named person. An employee finding a recorded leave balance is a different task from HR deciding how a particular company policy applies.
ElevenOS employee self-service connects employee information, schedules, attendance review and leave requests where permissions allow. Start the rollout around these everyday tasks. If payroll is in scope, add payslip access after the payroll publication process has been verified. A focused introduction gives staff a clear reason to sign in and an understandable first task.
2. Separate employee tasks from approval and maintenance
Employees should know where to view their information, submit a request and raise a record problem. Managers need to know which requests they review, what evidence matters and who handles their queue when they are away. HR owns the maintained employee record, policy setup and the process for resolving questions that exceed a manager's responsibility.
Map one leave request from beginning to end. The employee chooses dates and submits; the assigned reviewer checks coverage and the applicable policy; HR resolves any setup question. Check what the employee sees after approval or rejection. Record the handoff for an unresolved case so submitting a request does not become an invitation to chase several people by chat.
3. Prepare dependable records before inviting staff
Check the employee's identifier, work contact, hire date, department and reporting assignment. Resolve duplicate profiles and inconsistent team names before rollout. Confirm the published schedule and applicable opening leave balances separately. Account access can work while the information behind it is still incomplete, which leaves the employee with a usable login and an unusable answer.
Agree who maintains a change when someone moves teams, becomes a manager or leaves the company. Review the resulting access and schedule assignments as part of that change. If you use payroll, have its owner check the pay setup independently. An employee profile is a foundation for related workflows; it is not proof that every attendance or payroll input is ready.
4. Test access through each person's actual role
Use separate employee, manager and HR accounts with representative test records. Check which profile fields, documents, attendance records and requests each account can reach. Try a record outside the manager's intended team as well as one inside it. An administrator demonstration shows the full workspace, so it cannot establish what a staff member will see after signing in.
For someone who is both an employee and a supervisor, test their personal tasks and team review separately. Confirm that access supports their responsibility without exposing unrelated information. In ElevenOS, visibility and available actions depend on roles and permissions. Have the responsible administrator verify the configured scope before expanding the pilot; do not assume a job title automatically grants the intended access.
5. Verify the first sign-in and first completed task
Sending an invitation is one checkpoint. Delivery, activation, first sign-in and successful use are additional checkpoints. Prepare a short introduction showing how to find a shift, check attendance and submit a sample request in the agreed test environment. Give employees one named contact for account problems and another route for questions about their records if responsibilities differ.
Try the mobile browser workflow on the devices staff use. Where attendance requires location permissions, explain the request and test it at the workplace. Provide instructions for a failed sign-in or unavailable location reading. Use each employee's authorized account instead of sharing a manager login to get through a blocked step. Record unresolved issues before inviting the next group.
6. Explain how work information is used
Give employees a plain-language explanation of the information collected, why the company uses it and who handles corrections. Include attendance location capture where enabled. A clock-in location and ongoing location sharing are separate features and need separate explanations. Follow your company's privacy process, with its responsible owner reviewing the introduction and any questions requiring specialist advice.
Keep sensitive supporting information in the appropriate controlled workflow. Avoid placing salary screenshots, identity documents or detailed personal explanations in group chats when handling a routine request. Agree who reviews document access, how employee departures affect accounts and who owns retention and export decisions. These are operating responsibilities to resolve with your data owner, rather than assumptions created by buying an HRIS.
7. Match the plan and rollout to the work required
ElevenOS Starter includes employee records and self-service, attendance with geofencing, schedules, leave, approvals and basic reports. Growth adds Philippine payroll and payslips, timesheets, recruitment and performance tools. Business adds multi-branch operations. Enterprise integration and identity requirements are scoped separately. Choose by the workflow your team needs and verify the specific responsibilities during a walkthrough.
Pilot with a few employees and their reviewer. Confirm each person can find the intended information, complete a request and understand its result. Review unanswered questions and access issues with HR before expansion. Bring these examples and your employee count to the demo so the proposed rollout covers actual work. Check current pricing and separately quoted implementation services when budgeting.
Frequently asked questions
4 answers
