HR Service Requests: Building an Employee Service Portal with Humand
October 14, 2026
At 8:40 on a Monday morning, an HR coordinator opens her inbox and finds eleven messages that all start the same way: "Hi, could you help me with something?" One employee needs an employment certificate for a bank. Another wants an advance on this month's salary. A third asks for a laptop charger, a fourth for access to a shared folder, a fifth for a leave letter signed by two managers. Three more are follow-ups to requests sent last week. Two arrived on WhatsApp, one as a voice note. By noon she has answered six of them, lost track of two, and discovered that a request from the previous Thursday was approved by a manager in a chat thread that nobody else can see.
Nothing in that morning is dramatic. No system failed and nobody was careless. Yet it is the daily reality of HR service requests in a large share of companies: a steady flow of small, routine, person-to-person transactions, handled through whatever channel the employee happened to use. The cost does not appear as a line in the budget. It appears as lost hours, slow answers, repeated questions and a quiet loss of trust in the HR team.
Every HR request has the same hidden anatomy. Someone has a need. They look for the right person, the right form and the right channel. They send the request. Someone reads it, decides whether it is complete, asks for missing information, finds an approver, waits for the approval, performs the action and tells the employee it is done. Seven or eight handoffs for a task that, from the employee's side, is a single question: "Can you give me this?"
When those handoffs travel by email, chat and paper, three costs build up. The first is handling time. Each request is read several times by several people, and each missing detail triggers another round of messages. The second is waiting time. A request sits unseen in a shared mailbox, or in a manager's personal chat, or on a desk, and the employee has no way to know where it is. The third is rework. Employees ask again, HR searches for the earlier message, and the same data is typed into a spreadsheet by a person who did not write the original request.
None of these costs is large on a single request. The problem is volume. A company with a few hundred employees generates certificate requests, advance requests, equipment requests, access requests and leave letters every single week, and the HR team absorbs them on top of recruiting, payroll support and employee relations. The administrative load grows faster than headcount, and the people best placed to work on retention and development spend their days answering "where is my request?"
We have written before about how fragmented HR work drains budgets and attention. Requests are the most visible symptom, because every employee touches them and every employee remembers how it felt.
Most organizations do not have one process for HR requests. They have a collection of habits. Certificates are requested by email to a specific person. Equipment goes through the facilities contact. Loans and advances need a signed paper form and a visit to the finance office. Access requests go to IT through a different channel. Office supplies are ordered through a manager who keeps a spreadsheet. Each habit made sense when it started, and each one works as long as the right person is in the office and remembers the steps.
The trouble starts at the boundaries. A request for a new employee's equipment and system access touches HR, IT and a manager at once, and no single person owns the whole journey. An advance on salary needs an approver in the business and a person in payroll, and the employee is the only one who knows both parts exist. When a person is on leave, requests addressed to that person stop moving, and nobody knows they have stopped.
Three failure patterns repeat across companies of every size.
The first is the invisible queue. If requests arrive in personal inboxes and chats, there is no list of what is open. HR cannot see its own workload, and managers cannot see what is waiting on them. The second is the unclear owner. A request that needs three people is, in practice, owned by none of them. The third is the missing record. When the approval happened in a chat message and the action happened in another system, there is no single place that shows who asked, who approved, who acted and when.
These patterns are not a people problem. They are the predictable result of running a service operation without the basic structure of one: a single front door, a defined path for each type of request, and a visible status. IT teams learned this lesson years ago, which is why service catalogs are now moving into non-IT departments. HR is the next obvious place for the same discipline.
Speed is the cost employees notice. Exposure is the cost leadership should notice. Many HR requests carry real consequences: a salary advance is a financial commitment, an equipment loan is an asset leaving the building, an access grant is a security decision, and a leave letter or a certificate is a document with legal weight in many countries.
Consider what an internal audit or a labor dispute asks for. Who requested this? When? Who approved it, and did that person have the authority to do so? What exactly was approved? Was the employee informed? If the answers live in a manager's phone, a forwarded email and a handwritten note, producing them becomes an investigation rather than a lookup. Even when everything was done correctly, the company cannot show it.
Signed documents sit in the same category. A request for a certificate or a letter often ends with a signature, and the way that signature is captured matters. We covered the compliance side of this in our article on digital signature in HR. The principle applies equally to requests: a process that captures the request, the approval and the signed output in one place is a process you can defend.
A service portal is not a new place to put the same chaos. It is a different operating model for routine requests, built on four ideas that work regardless of the software behind them.
The first idea is a single front door. Employees do not need to know which person or department handles a request. They open one place, browse what they can ask for, and choose. The catalog names each service in the employee's own words: "Employment certificate," "Salary advance," "Laptop replacement," "Access to a system."
The second idea is a structured form. Instead of a free-text message that may or may not contain what HR needs, the form asks for the right information once. Dropdowns replace ambiguity, required choices replace back-and-forth, and the request arrives complete. For a certificate, that may be the type of certificate and its purpose. For a loan or advance, the amount requested and the reason. For equipment, what is needed and for whom.
The third idea is a defined path. Each type of request follows a known route: who receives it, who must approve it, who performs the action. The path is the same every time, which makes the process teachable, measurable and improvable. When something needs to change, such as a new approver or an added step, it changes in one place.
The fourth idea is visible status. The employee can see the request, follow it and receive an update when something happens. This single feature removes the largest category of HR contact: the follow-up question. A significant part of any HR inbox is people asking whether something has been received. When they can see the answer, they stop asking.
Our article on self-service portal adoption goes deeper on what makes employees actually use a portal instead of going back to email. The short version: the portal has to be easier than the habit it replaces, and it has to work on the device people already use.
If you measure where HR requests spend their time, the answer is rarely "being worked on." Most of the elapsed time is waiting for an approval. The employee asked on Monday, the manager saw it on Wednesday, answered on Thursday, and HR acted on Friday. The actual work took ten minutes. The calendar time was five days.
Approvals stall for ordinary reasons. The approver does not know a request is waiting. The approver is traveling, on leave or in a meeting. The approver needs context that was not in the original message. The request needs two or three people, and each one waits for the previous one. Or the request was sent to a group, and each member assumed someone else would answer.
Good process design attacks each of these. Name a substitute for every approver, and make the approver part of the request itself, so a notification reaches them where they already work. Put the context into the form, so they do not need to ask. Decide in advance which requests need one approver and which need several. For those that need several, decide whether all must agree or whether the first response is enough. That last choice is a business decision, and it matters more than most teams realize. A request for office supplies rarely needs the same rigor as a salary advance, and treating them identically either slows the simple one or weakens control on the serious one.
Our look at manual time-off requests in distributed teams shows the same dynamic in its sharpest form. Leave is only one kind of request, but it demonstrates how much value sits in a clear path and a fast approval.
Humand's Service Management module puts this model into practice. Employees reach a Service Portal, browse a full service catalog and use smart filters to find what they need. They can report issues and track tickets, request office supplies and work tools such as protective equipment, request loans including salary advances and equipment, download certificates, update profile details and find answers to company questions about benefits, policies and safety procedures. They can also submit and follow vacation, payroll, equipment and access approval requests.
Requests start with forms. Humand's smart forms include checkboxes, buttons and dropdown menus, and they can auto-fill and sign documents. Administrators decide who can complete each form, by segment or individually. Each submitted form reaches the right agent as a centralized request, so the employee does not need to know who handles what. When HR needs a new type of service, administrators define it and set up its form in a few steps, which means the catalog can grow as the organization finds new recurring requests.
Workflows and approvals sit on top of the forms. Humand lets administrators start requests, define approvals and automate steps in every process. When a request needs several approvers, it can be set so that the first approver to respond decides the step. Once that response arrives, the pending responses from the other approvers are cancelled automatically, so a request does not wait for people whose answer no longer matters. Administrators monitor and trace each workflow from one centralized panel, which gives HR a single view of where requests stand.
On the other side of the portal, agents work from a centralized workspace with custom views and smart filters, and they can assign tasks to the right people from the panel. Agents can be organized into groups and Help Desks, and coordinators oversee all agent groups and manage tickets as needed. Agents see how many updates are available in the request list and choose when to refresh, so the page, the filters and the sort order stay in place while they work.
Notifications keep everyone informed. Humand sends notifications for status changes, assignments, comments, approvals and tasks, and each notification links directly to the request. Each type can be switched on or off for push alerts and for the Notification Center, so people receive what is useful to them.
The Service Portal and the Agent Workspace run on web and mobile, on iOS and Android, with the same functionality. That matters for HR requests, because many of the people who submit them and many of the people who approve them are not sitting at a desk. Humand supports single sign-on and several languages, including English, Spanish and Portuguese, which suits teams that operate in more than one country.
Finally, Humand's insights show key metrics such as case volume, resolution time and employee satisfaction, which helps HR spot trends and bottlenecks. The module also sits next to other Humand capabilities that touch the same journeys: digital document management with electronic signatures, time-off and leave management with configurable policies, digital employee files, payroll receipt distribution and company policy management.
Latin America adds particular conditions to this problem, and the best designs account for them from the start.
The first is the channel. In many companies across the region, WhatsApp is the real HR service desk. Employees message a person they know, and that person answers from their phone. It is fast and human, and it is exactly why the model breaks as the company grows: no queue, no owner, no record, and a dependence on one person's availability. We looked at this pattern in our article on outgrowing WhatsApp for internal communication. A portal does not need to remove the personal touch. It needs to give requests a place to live, so the personal touch goes into solving the problem instead of locating it.
The second is the workforce. Large parts of the regional workforce work in stores, factories, warehouses, clinics and field operations. They do not have a corporate laptop, and they often do not have a fixed schedule. A portal that works only from a desktop excludes them. For these employees, the mobile experience is the only experience, and it determines whether the process is used at all.
The third is proof of employment. Certificates of employment, income letters and similar documents are requested constantly in Latin America, for banks, landlords, visas and public agencies. They are repetitive, high-volume and low-complexity, which makes them an ideal first candidate for a structured request. The same applies to salary advances and personal loans, which are common benefits and carry a financial approval that deserves a clean record.
The fourth is multi-country operation. A company with employees in Mexico, Colombia, Chile and Argentina has different rules, different documents and different approvers in each country. A single catalog with permissions and forms that differ by group of employees lets HR keep one process while respecting local differences. Language matters too: Spanish for most employees, Portuguese for Brazil, English for regional leadership.
The largest benefit of a structured request process is not speed. It is visibility. Once requests flow through one system, HR can answer questions that were impossible to answer from an inbox.
How many requests do we receive per month, and of which types? Which request types take longest to resolve? Where do requests wait the longest, in approval or in execution? Which approvers respond fast and which slow the process down? Which requests are repeated because the first answer was unclear? Are employees satisfied with how their requests were handled?
Start with three to five request types that are frequent, simple and painful today, such as employment certificates, salary advances, equipment requests and leave letters. For each one, name the approver and a substitute and decide what the form must collect. Then launch to a limited group, watch what happens and adjust. Within a few weeks you will know which forms confuse people, which approvals are slow and which requests were missing from the catalog. Add request types gradually, driven by the volume you see in the data rather than by a long list agreed in a meeting.
A few operating practices make the difference, and they belong to the HR team, not to the software. Agree on a target response time for each type of request and publish it, so employees know what to expect. Review open requests weekly, with a short routine for anything that has waited longer than the target. Decide who steps in when a request is stuck. Keep the catalog tidy by removing request types nobody uses. None of this is complicated. It is the difference between a portal that is launched and a service that is run.
Before assuming your current process is fine because nothing has visibly broken, run it through a few honest questions.
Isn't this a small problem compared to bigger HR priorities?
Individually, yes. Collectively, no. Routine requests consume a large share of HR hours and shape how every employee perceives the HR function. Reducing that load frees time for the priorities that leadership cares about, and it improves the first impression of HR across the whole company.
Our employees prefer to talk to a person. Won't a portal feel cold?
The goal is not to remove people from the process. It is to remove the searching, the repeating and the waiting. Employees still talk to HR about situations that need judgment. For a certificate or an equipment request, most people prefer a fast, visible answer over a conversation. A portal gives the human conversation more room, not less.
We have many request types and each is different. Can we really standardize them?
You do not need to standardize everything at once. Start with the frequent, simple ones, and let the data show you where the exceptions are. Most organizations find that a small number of request types account for the majority of volume. Forms can differ widely while the front door and the visibility remain the same.
What about people without a corporate computer?
This is the strongest argument for choosing carefully. Any platform you consider must work well on a phone, for submitters and for approvers. Humand's Service Portal and Agent Workspace work on iOS, Android and web with the same functionality, which is why it fits workforces that are not desk based.
Will managers actually use it for approvals?
They will if approving is easier than the alternative. That means a notification that links directly to the request, enough context to decide without asking, and a clear rule for who else can approve. Managers rarely resist approvals. They resist hunting for them.
Does this replace our HR system?
No. A request process sits alongside systems of record such as payroll and employee files. Its job is to handle the journey from need to resolution. Humand's Service Management module works next to its other modules for documents, leave, employee files and payroll receipts, so the request and the record stay close together.
HR service requests rarely fail in one dramatic moment. They fail through accumulation: a message unseen, an approval delayed, a document that cannot be found, an employee who stops asking. Each instance is small, and together they define how employees experience the company and how much of HR's week disappears into administration.
The fix starts with structure, not with software: a single front door, a form that collects what is needed, a defined path with named approvers and substitutes, and a status that the employee can see. Once that model is clear, the choice of platform becomes a question of fit for your workforce, your countries and your devices. For many organizations in Latin America, an option that works on both web and mobile, such as Humand, is a strong candidate, because it covers the catalog, the forms, the approvals and the agent workspace in one module.
If you want to know where your own HR requests lose the most time, book a conversation with our team. We will walk through your current process, identify the three request types where a structured path pays back fastest, and show you how to measure the result.
