Your HR Service Delivery Model Guide

Modern HR operations have moved far beyond administrative tasks.  In most organizations today, HR teams are responsible for the entire employee lifecycle, from recruitment and onboarding to benefits administration, performance reviews, and everyday employee concerns. As organizations grow, teams expand, locations increase, and employee expectations change, delivering these services consistently and efficiently becomes an operational challenge. Without a structured approach, HR teams often fall back on emails and manual tracking, leading to delays, inconsistencies, and limited visibility into how things are handled.

To address this challenge, organizations adapt and implement HR Service Delivery Models. HR service delivery refers to how HR services are structured, managed, and delivered to employees, combining roles, operational processes, and supporting systems to ensure timely and reliable support.

These models help organizations structure HR teams, route employee requests more effectively, and scale operations as the workforce grows. In many organizations, this translates into a structured flow where employee requests move through defined stages from submission to resolution. While broader HR transformation initiatives and detailed process improvements are outside the scope of this article, understanding the underlying delivery models provides a useful foundation.

This article focuses on major HR service delivery models used to structure modern HR operations. Each model comes with its own logic, strengths, and trade-offs. Understanding them helps HR teams and business leaders make informed decisions about how to structure HR to meet their specific business needs.

Summary of key HR Service Delivery Model concepts

The following table summarizes the HR service delivery models covered in this article.

Centralized & decentralized HR service delivery models

Before choosing a service delivery model, HR leaders must make a fundamental decision about how centralized HR should be. The decision shapes everything downstream, from how policies are enforced to which tools actually support how your teams work. Every delivery model discussed later in this article sits on top of this structural foundation.

In a centralized setup, HR activities like policies, payroll, and employee support are owned and managed by a single team. As a result, policies remain consistent, and costs are easier to control. Whereas in a decentralized setup, those same responsibilities live within business units or regions, making HR more responsive to local context but taking a hit on standardization.

The following table highlights a side-by-side comparison between the two approaches:

In practice, purely centralized or decentralized models are rarely chosen for several reasons. In most cases, organizations strike a balance between the two. 

Full centralization can feel bureaucratic, while full decentralization leads to silos. Centralized HR also starts to break when the organization scales rapidly. A single HR team cannot always respond quickly to local needs, and as a result, decision-making slows down. Decentralized HR, on the other hand, tends to create inconsistency, leading different units to follow different policies with no standardization.

Centralized vs Decentralized HR service delivery model

Most mature HR organizations adopt a mix of both (hybrid), where the core is centralized, and execution is local. Policy, compliance, and compensation frameworks are usually designed centrally, while onboarding, engagement, and day-to-day employee support happen close to the team.

For IT leaders picking an HR tool, this is worth paying attention to because the tooling has to flex both ways. A tool that only supports one global workflow will frustrate regional teams. One that lets every unit build its own rules will recreate the silos the company is trying to avoid. The better question is whether the tool can hold shared policies, SLAs, and data at the top while still letting local teams set up what they need underneath.

A simple test is to look at how routing and SLAs are handled in the tool you're evaluating. Can a request be routed to the right local HR group based on the employee's region, while still sitting under a global SLA? Platforms like Freshservice are designed around this kind of split, where routing, approvals, and forms can vary locally but policies, SLAs, and reporting stay consistent at the top. If a tool needs a fully separate setup per region to do the same thing, it isn't built for both worlds.

Ulrich Model

Proposed by Dave Ulrich in the 1990s, the Ulrich Model is still the most widely used HR operating framework today. A 2023 HR Operating Model Report by the Talent Strategy Group surveying over 200 companies worldwide found that the three-pillar system continues to dominate how organizations structure HR globally.

The model splits HR into three groups that each do very different work, which is why it's often called the three-legged stool.

The point of this split is that each group does what it does best. Shared Services keeps operations running, HRBPs focus on the business, and CoEs build the programs. Though at the operational level, the three are closely linked and work together on almost everything. Despite three groups handling different aspects of a single workflow, the employee sees a single process from the outside.

HRBPs typically work directly with business leaders to identify people-related challenges, but depend on Shared Services for execution and on CoEs for policy frameworks and expertise. For example, an HRBP-led initiative, such as workforce planning, usually draws on CoE-designed frameworks and is supported by Shared Services, which handles data, documentation, and follow-through.

Many organizations implement this model by centralizing routine HR tasks, assigning clear roles for HRBPs and CoEs, and using tools like HR portals or service desks to deliver support. It works well, particularly in larger organizations that need to scale HR support without losing strategic focus.

This approach is important in situations such as performance cycles or grievance handling. For instance, sensitive conversations, such as PIP (performance improvement plan) discussions, often require HRBP involvement, while documentation and follow-ups are managed through shared services.

Ulrich model structure showing Shared services, HRBP, CoE

The Ulrich Model needs a platform that can support three very different kinds of work inside the same system. 

• Shared Services needs a ticketing setup with SLAs, automations, and a self-service portal. 

• HRBPs need visibility into requests linked to their business units without having to manage the queue themselves. 

• CoEs need a way to publish policies, templates, and knowledge that both of the other groups can pull from. 

If your chosen tool treats HR as a single generic queue, the model will likely collapse back into a single team handling tickets. A good way to test this during evaluation is to ask how a single employee request moves through the tool when it needs input from all three groups. If it takes manual handoffs and email chains, the tool is not built for this model.

The tiered  HR service delivery model

If the Ulrich model is about the role structure, the tiered model is about request routing. The two aren't mutually exclusive, and most organizations run both simultaneously.

The idea behind the tiered model is simple: not every employee question needs a specialist. For instance, a question about leave balance should not land on the same queue as a complex grievance, and the fastest way to keep HR efficient is to match the request to the right level of support.

In a tiered service delivery model, HR services are delivered through a layered system, starting with self-service and moving towards strategic HR support as needed. As a result, the model helps you manage request volumes more effectively while ensuring that higher-level HR support is engaged only when needed. The payoff shows up in how much work never reaches an agent in the first place.

Most organizations set their service delivery structure in four layers, as listed below, though the numbering varies across use cases.

• Level 0- Self Service: Employees access basic information through FAQs, knowledge bases or HR portals.

• Level 1- HR Service Desk: Handles common queries and requests through tickets, emails or calls.

• Level 2- HR Specialists: Picks up anything that needs deeper knowledge or judgement, such as policies or employee relations.

• Level 3- Strategic HR Support: Deals with sensitive and high-impact matters requiring senior HR involvement, like succession planning, workforce restructuring.

The escalation path matters as much as the levels themselves. When level 0 resolves a query through self-service, it never reaches the HR desk. When level 1 handles it, specialists stay free for complex cases. This load distribution is exactly what makes the model efficient, allowing HR teams to spend less time on routine queries and more time on issues that require human judgment.

Tiered HR service delivery model from self-service to strategic HR

For IT leaders, this is the model where tooling decides whether the design holds. A tiered setup needs three things to work end-to-end.

1. A self-service portal that employees actually use, which means good search, a clean interface, and content that stays current. 

2. A ticketing system underneath it that routes requests to the right tier with clear SLAs and visible ownership. 

3. And a knowledge base that both employees and agents pull from, so the same answer doesn't get written five different ways.

When evaluating a tool, a useful test is to trace a single request end-to-end. Does it start as a self-service search, convert into a ticket if the employee doesn't find the answer, route to the right tier with the right SLA, and close with a knowledge article that feeds back into Level 0?

The Hub-and-Spoke Model

There are many organizations operating across multiple regions or business units that deal with complex consistency issues in HR workflows without restricting local autonomy. The Hub-and-Spoke model is built around solving this. 

The hybrid setup discussed earlier answers the question of where HR should sit. A Hub-and-Spoke HR service delivery model answers the next question, which is how a hybrid HR should actually run day to day. It's a specific way of organizing a hybrid structure, with a clear flow of direction from the center out to the regions, and a feedback loop running the other way.

The central HR team (Hub) defines overall strategy, policies, and standards. While local HR teams (Spokes) focus on delivering services and supporting the employees locally. In simple terms, “the hub” sets direction, and “the spoke” executes it within the organization. This helps:

• Balance control with flexibility

• Supports geographically distributed organizations

• Improves responsiveness to local workforce needs

• Allows central team to focus on strategic interventions

This model works well when an organization needs consistency but can’t ignore local needs. For example, policies may remain the same globally but how they are communicated and implemented often differ across teams.

The biggest risk in this model is drift. When the hub and spokes stop communicating, each side starts making decisions in isolation. Organizations that implement this model well typically invest in regular sync points between the two teams, shared tools, and clearly documented boundaries between centrally decided and locally executed work. 

Hub-and-Spoke structure showing central HR hub connected to regional HR teams

The model’s efficiency depends on two key aspects that support your HR workflow. The hub needs a single source of truth for policies, templates, and reporting, so every spoke can work from the same base. And the spokes need the ability to configure local variations without breaking the global structure, which usually means workspace-level customization, local approval flows, and region-specific forms. A good test during evaluation is whether your tool can show the hub a single view of requests and SLAs across all regions, while letting each spoke run its own forms, workflows, and approvals underneath. If regional teams have to stand up separate instances to do their work, the hub loses visibility, and the model quietly falls apart.

Digital HR Service Delivery Model

The previous models are primarily about HR structures,, but the digital model adds a different layer by showing how technology changes how those structures actually operate.

At its core, this model represents a shift from manual, fragmented HR processes to a more integrated, technology-driven approach. Organizations use digital platforms to make HR services more easily accessible, faster to deliver, and more consistent, rather than relying entirely on HR teams.

With this HR service delivery model, employees interact with HR via centralized platforms to access information, submit requests, and track progress. Requests are captured in a structured format and automatically routed through predefined workflows to the appropriate team. This also creates visibility across the process, enabling both employees and HR teams to track request status and identify delays or bottlenecks.

Compared to other service delivery models, this model offers a considerable shift that improves both coordination and visibility. For example, during onboarding, tasks can be automatically assigned, tracked centrally, and completed on time, avoiding the gaps that occur in manual processes. At the same time, HR teams can see where requests are getting delayed or where the process needs improvement.

Getting an overview of the HR helpdesk using Freshservice Team Dashboards

Unarguably, the importance of tool selection for this service delivery matters most. A digital HR stack needs four things working together. 

1. A portal that employees want to use, with good search and a clean interface. 

2. A ticketing engine underneath it that captures, categorizes, and routes requests with clear SLAs. 

3. A workflow automation layer that can orchestrate tasks across HR, IT, finance, and managers without human forwarding. 

4. And a knowledge base that both employees and agents draw from, so answers stay consistent. 

The tools that work well for HR are usually the same ones that work well for IT service management, because the underlying needs are the same. Freshservice brings these four pieces together in one system, which is why the platform is a common choice for both IT and HR teams inside the more than 74,000 companies worldwide.

How to choose the right HR service delivery model

There is no single correct model. The right choice depends on an organization's structure, growth rate, and the way HR services are expected to operate.

• Consider ‘scale’ as the first indicator. Centralized models work for smaller teams. As teams grow, request volume increases, shared services, and tiered support become useful.

• Geographic distribution matters too. If the teams are spread across regions or countries, a centralized model struggles to meet local business needs. This is where the Hub-and-Spoke model can be used, as it allows the organizations to maintain consistency while adapting to local needs.

• Digital maturity is the most important consideration. It affects the feasibility of self-service and automation-driven models. However, without supporting platforms, these models are difficult to sustain.

Most organizations combine elements from multiple approaches rather than relying on a single model. The key is to start with a structure that matches the current scale and complexity, then layer in additional models as the organization grows.

Conclusion

HR service delivery models shape how employees experience HR on a day-to-day basis. While different models define how the work is organized, what ultimately matters is how consistently and effectively that work is delivered.

As organizations evolve, these models become less optional and more essential. However, identifying the right HR service delivery model is only one part of the equation. The real challenge lies in executing these models efficiently at scale, especially as request volumes increase and processes become more complex.

In your digital transformation journey, Freshservice can be your partner by providing a unified system to manage HR requests, automate workflows, and deliver services in a consistent and scalable manner. To know more, request a demo or try it for free.