Mastering ServiceNow HRSD

What is ServiceNow HRSD?

ServiceNow Human Resources Service Delivery (HRSD) is a module that digitizes and automates HR processes — from onboarding to offboarding — giving employees a consumer-grade self-service experience and giving HR teams a streamlined case management system.

ServiceNow was founded in 2003. Over time, it evolved from pure IT service management (ITSM) into a comprehensive enterprise platform covering HR, legal, finance, and customer workflows.

Required Plugins

HRSD Application Navigator Modules (after plugin install)

• HR Administration — Case creation config, services, COEs, SLA
• Case Management — All HR cases (open, in progress, closed)
• HR Tasks — Tasks created within cases
• HR Knowledge — Articles available to employees and agents
• HR Reports — Dashboards and metrics
• Employee Center — Portal configuration

When the HRSD plugin is installed, a set of out-of-the-box roles is automatically created. Every action in HRSD — viewing cases, creating configs, managing services — is controlled by these roles.

Core HRSD Roles

Role vs Group

In ServiceNow HRSD:

• A Role defines what a user can do (permissions/access).
• A Group defines who gets work assigned to them (assignment groups).

Role Hierarchy (Inheritance)

Higher roles inherit the permissions of lower roles. An HR Admin can do everything a Case Writer or Basic user can do.

Steps to Assign HR Role to a User

One of the most commonly confused concepts in HRSD is the difference between a User Profile and an HR Profile.

Why Do We Need HR Profile?

The HR Profile stores confidential employment data that should not be visible in the standard sys_user table. It also acts as a centralised data source when HR cases are created — the case automatically pulls employee information from the HR Profile.

HR Profile Sections

Auto-Creation of HR Profile

By default, when a new user is created in ServiceNow (via LDAP sync or manual creation), HRSD can be configured to automatically create an HR Profile for that user using a Business Rule. This is especially useful in organisations with large-scale LDAP imports.

Steps to Manually Create HR Profile

An HR Case is the core record in HRSD. It tracks an employee's request or issue from creation to resolution. Every HR service interaction generates an HR case.

Types of HR Cases

HR Case Fields (Key)

HR Case States

Or: Work in Progress → Closed Incomplete (if unresolvable) / Closed Cancelled (if employee withdraws).

Ways to Create an HR Case

A Center of Excellence (COE) is a logical grouping of HR services, teams, and cases around a specific HR functional area. Think of it as an "HR Department within the HR Department."

Why COE?

Large organisations have many HR functions. A COE ensures that a payroll query goes to the Payroll team, a benefits question goes to the Benefits team, and a talent question goes to Recruiting — all automatically, without manual routing.

Common COEs

COE Configuration Steps

HR Case Configuration controls how the HR Case form looks and behaves when an agent creates a case. This is where you define what fields appear, what tabs exist, and how the case form is structured.

Two Key Configuration Areas

Tabs in Case Creation Configuration

1. Employee Information Tab

Controls what employee data is pre-populated on the case when an agent selects the Subject Person. You can add or remove fields pulled from the HR Profile.

2. Case Creation Tab

Controls the main case form fields — what the agent fills in when creating the case. You can add custom fields, reorder sections, and set mandatory fields.

Form Sections

Within each tab, you can create multiple sections to organise fields logically:

• Employee Details — name, employee ID, department
• Request Details — specific fields for the service
• Notes — additional comments

Steps to Configure Case Creation Form

A Service Level Agreement (SLA) is a commitment to resolve or respond to an HR case within a defined time period. HRSD uses the same SLA engine as ITSM.

Types of SLA

SLA Target Types

SLA Definition Configuration

An HR Service is the specific offering that defines the request-to-fulfilment process for a particular type of HR request. Every HR case is associated with exactly one HR Service.

Key HR Service Fields

Fulfillment Types — The Most Important Decision

Steps to Create an HR Service

HR Lifecycle Events are the most powerful HRSD feature. They automate complex, multi-step, multi-department HR processes — like onboarding a new hire or processing a transfer — by automatically creating a parent case and multiple child cases across different COEs.

What is HR Lifecycle Management?

It is a framework designed to automate and manage complex HR processes that span multiple tasks, departments, and even external systems. When an HR Lifecycle Event is triggered, it orchestrates everything automatically.

Lifecycle Event Components

Steps to Create a Lifecycle Event

HR Templates

HR Templates allow you to automatically populate fields on a case or HR Task form. When a case is created using a particular HR Service, the template can pre-fill fields — saving agents time and ensuring consistency.

HR Templates can be configured for:

• HR Services
• HR Catalog Items (Record Producers)
• HR Service Activities
• Lifecycle Event Activities

HR Criteria

HR Criteria defines the audience for HR content — who can see, access, or have created an HR case or service. It's the access control mechanism for HR Services in the Employee Center.

What HR Criteria Controls

• Who can see an HR Service in the Employee Center
• Who can create an HR case for a service
• Which Lifecycle Event activities apply to an employee
• Which Knowledge Articles are visible to which employees

HR Criteria Configuration Fields

Steps to Create HR Criteria

An HR Record Producer is a Service Catalog item that, when submitted by an employee through the Employee Center (portal), creates an HR case. It is the self-service form that employees fill out to raise HR requests.

Record Producer vs Regular Catalog Item

Record Producer Structure

Steps to Create an HR Record Producer

// Producer Script
current.hr_service = '<sys_id of Address Change HR Service>';
current.short_description = 'Address Change Request';
current.u_new_street = producer.new_street;
current.u_city = producer.city;
current.u_effective_date = producer.effective_date;

HR Service Activity

When an HR Service uses the Service Activity fulfillment type, it automatically generates HR Tasks — sequential or parallel steps that agents must complete to resolve the case.

Configuring Service Activities

E-Signature in HRSD

HRSD supports collecting digital signatures from employees or managers as part of case fulfilment. This is commonly used in Lifecycle Events (e.g., signing a leave agreement, receiving a separation document).

E-Signature Flow

Configuring E-Signature

Transfer Case

The Transfer Case feature allows an HR agent to move an existing HR case to a different COE or HR Service when the initial routing was incorrect, or the case scope has changed.

Transfer Types

Transfer Case Configuration

The Transfer Case button in the UI is controlled by a UI Action and a Script Include. The glide modal popup is configured via UI Builder or script. You can control which fields appear in the transfer dialog (e.g., new COE, reason for transfer, new assignment group).

Bulk Case Creation

Bulk Case Creation allows HR Admins to create multiple HR cases simultaneously for multiple employees — extremely useful for mass HR events like onboarding a new cohort or annual benefits open enrolment.

When to Use Bulk Case Creation

• 50 new hires joining on the same date — create 50 onboarding cases at once
• Annual open enrolment — create benefits review cases for all 5,000 employees
• Mandatory policy acknowledgement — create sign-off cases for entire department
• Merit cycle — create performance review cases for all managers

Steps for Bulk Case Creation

The Employee Center Pro (ECP) is the modern self-service portal for employees — replacing the older HR Service Portal. It goes beyond service delivery to include employee communications, engagement tools, content publishing, and communities.

Employee Center Pro vs Employee Center

Key ECP Concepts

Browse Experience

The Browse Experience is the main navigation structure of the ECP. It controls how services, knowledge, and content are organised and displayed to employees.

Mega Menu

The Mega Menu provides a rich, multi-column navigation dropdown when employees hover over a category — similar to modern e-commerce sites. Configured in ECP Portal Administration → Mega Menu.

Content Publishing & Campaigns

HR can publish announcements, news, and targeted content campaigns to specific employee segments. Example: Publish "Open Enrolment Reminder" to all US employees during October.

Employee Communities

Peer-to-peer discussion forums within the ECP. Example: "New Hire Community" where recent joiners share tips and ask questions of each other.

ECP Configuration Workflow (Admin to Employee)

HR Reports and Dashboards

ECP includes built-in HR dashboards accessible to HR managers. Key metrics:

• Case volume by COE and service
• Average resolution time vs SLA target
• SLA breach rate by team
• Employee satisfaction (CSAT) scores
• Open case aging report
• Top 10 most-requested HR services

HR Notifications

Notifications in HRSD are automated messages (email, SMS, push) sent to employees, managers, or HR agents when HR case states change or specific events occur.

Common HR Notification Triggers

Steps to Create an HR Notification

Subject: Your HR Request Has Been Received – ${number}

Hi ${opened_for.first_name},

Thank you for contacting HR. Your request has been received and a case has been created.

Case Number: ${number}
Request Type: ${hr_service.name}
Submitted: ${opened_at}
Expected Resolution: ${expected_resolution_date}

You can track your case status at: ${portal_url}

Best regards,
Acme HR Team

Inbound Email Actions

Inbound Email Actions (also called Inbound Actions) automatically process emails sent to a ServiceNow monitored email address (e.g., hr@acme.com) and create or update HR cases.

How Inbound Email Actions Work

Inbound Action Configuration

// Create HR Case from inbound email
var hrCase = new GlideRecord('sn_hr_core_case');
hrCase.initialize();
hrCase.short_description = email.subject;
hrCase.description = email.body_text;
hrCase.hr_service = '<sys_id of General Query service>';
hrCase.opened_for = email.origsys_id; // match email to user
hrCase.insert();

Key HRSD Roles Summary

Fulfillment Type Decision Tree