ServiceNow HRSD Health Check

What a Health Check Engagement for HRSD Covers

An HRSD health check engagement evaluates how well your human resources service delivery system is working. Assessment covers whether employee lifecycle processes are automated or still manual: onboarding, role changes, offboarding. Data quality is audited: are employee records complete and current? Do organizational structures accurately reflect your business? Workflows are reviewed: do approvals work smoothly or do requests sit pending? The assessment identifies what is working well and where problems create friction for HR teams and employees.

Based on findings, recommendations address improvements to automate manual processes, improve data quality and streamline workflows. The health check length depends on scope and results in a prioritized roadmap for improvement, addressing both quick wins and strategic changes.

Typical Starting Problems and Organisational Data Issues

Many organisations use HRSD as a ticketing system rather than a true HRIS. Employee data is scattered: core employee records in one place, organizational structure in another, position information in spreadsheets. New hire onboarding is partially manual: HR creates records in HRSD and manually notifies IT, facilities and other teams to provision access. Role changes require manual updates in multiple places. Offboarding is incomplete: some access is revoked, some is forgotten, accounts linger long after departure.

Data quality suffers because there is no authoritative source. Manager details are outdated in the organization structure. Job titles are inconsistent because someone changes them in their profile but HRSD is not updated. Salary grades are stored elsewhere and not synced to HRSD. This fragmentation makes reporting difficult and introduces errors in automated workflows.

Employee Lifecycle Assessment

The assessment traces the employee lifecycle: hiring, onboarding, career progression and offboarding. At each stage, the assessment determines whether the process is efficient. Hiring: are job requisitions tracked, are offers managed in HRSD or elsewhere, how are candidates routed? Onboarding: are new hires added to HRSD, is equipment requested automatically, are access requests triggered, how many manual handoffs occur? Role changes: when an employee changes roles, how is the change recorded, what downstream systems are updated, are there delays? Offboarding: when an employee leaves, what triggers the offboarding process, how comprehensive is it, how quickly is it completed.

The assessment also evaluates whether the employee lifecycle is integrated with business systems. When someone is hired, payroll should be notified. When someone changes roles, their cost centre should be updated. When someone is offboarded, their access should be revoked across all systems. Many organisations perform these updates manually, missing integration opportunities.

Data Quality and Organizational Structure

Employee records are audited for completeness: what percentage have required fields filled, what percentage have outdated information. Organizational structure accuracy is assessed: does the hierarchy in HRSD match the organizational chart, are manager assignments correct, are reporting lines up-to-date. Data consistency is checked: are fields like department, cost centre and location used consistently or do different parts of the org use them differently.

Data sources and ownership are identified. Employee name comes from payroll. Job title might come from an HR management system. Organizational structure might be maintained manually. Phone numbers might come from a directory. When data comes from multiple sources, synchronisation is important. When one source is out-of-date, others are stale too. Recommendations address consolidating data sources where possible and establishing synchronisation for those that cannot be consolidated.

Workflow and Approval Process Evaluation

Key workflows are traced: leave requests, expense approvals, training approvals and so on. For each workflow, measurement includes: how often is it used, what is the average approval time, what percentage complete successfully versus are abandoned. Slow or high-failure workflows should be simplified. Bottlenecks are identified: approvals assigned to people who are busy or out-of-office, approval criteria that are unnecessarily strict, or information gaps that require back-and-forth clarification.

Mobile and self-service capabilities are also assessed. Can employees view and update their own information? Can they request leave and track requests? Can managers access their team data and approve requests from mobile devices? Limited self-service means HR handles routine requests that could be automated.

Integration with Payroll and Finance Systems

HRSD is effective when tightly integrated with payroll and finance. Employee data in HRSD should feed payroll so there is one source of truth for compensation. Cost centre assignments should flow to finance systems for expense allocation. Organizational changes should update GL accounts. Many organisations maintain separate HRSD and payroll systems with manual reconciliation, creating data inconsistency and extra work. Assessment identifies integration opportunities and recommendations address approaches to tighten the connection.

Recommendations and Roadmap

Health check recommendations typically include automating core lifecycle processes, improving data quality, integrating HRSD with payroll and other systems and streamlining workflows. Recommendations are prioritised by business impact. Quick wins like assigning approvals to the right people or fixing stale organizational data can be implemented quickly. Strategic improvements like automating onboarding might require multiple system changes and take longer to implement. We develop a roadmap that balances quick value with long-term capability.

Check each data field against the system that should own it

HRSD data problems often do not announce themselves as data problems. They show up as an approval that routes to a manager who left in the spring, an onboarding task routed to a group that has been dissolved, or a leave report that disagrees with payroll by a few days’ worth of entries. Each of these traces back to a field whose true owner was never written down. A useful health check starts by listing the fields that drive workflow and reporting, then asking which system is the source for each one, and whether HRSD reads it, copies it or overwrites it.

Field group	Typical source	What goes wrong when HRSD is not clear	Check during the health check
Reporting line and manager	HR information system or directory	Approvals route to a person who no longer manages the employee	Compare approver on five recent requests with the current org record
Job title and job profile	Position records	Titles drift between profile, HRSD and access groups	Count mismatches between title in HRSD and title in the source
Location and cost center	Finance or facilities master data	Reports split headcount across two versions of the same site	Check whether any location exists twice under different codes
Employment status	HR information system, updated by lifecycle events	Leavers keep open tasks and access requests	Trace one recent leaver through every open task and request

Reconciling without overwriting good data

Once the owner of each field is known, decide how a mismatch is corrected. Automatic overwrite is tempting but dangerous when the source itself is wrong, because it spreads an error faster. A safer approach is to flag mismatches into a review queue, let an HR administrator decide which side is right, and record the decision against the field. Keep the queue small by fixing the upstream rule that produced the mismatch, rather than clearing the same mismatch repeatedly.

1. Export the fields in scope from HRSD and from each source system on the same date.
2. Match records on a stable identifier, not on name, because names change and duplicate names are common.
3. Classify each mismatch as a timing difference, a missing record, or a conflicting value.
4. Fix timing differences by reviewing the synchronization schedule, and fix conflicting values by settling the owner decision.
5. Re-run the comparison after the fix and confirm the same mismatch does not return on the next cycle.

An illustrative case of a stale approver

Consider an HR team that receives a steady trickle of complaints about leave requests stuck in a queue. The approval chain looks correct when inspected one request at a time. A comparison of the approver field against the current reporting line shows that a group of managers changed roles during a restructure, and the synchronization that updates manager relationships ran only for new hires. The cause is an integration rule, not a workflow, and the fix changes the sync scope. The lesson for the health check is that a reviewer who samples only recent records will miss errors that affect older employees, so the sample should include a set of employees who changed role during the last reorganization.

What a healthy HRSD data set looks like in practice

Healthy data is boring. Managers see the people they manage in their requests. Reports on headcount agree with the figures that finance uses, within the tolerance HR has agreed. Leavers disappear from active task lists on the day they leave. When an HR administrator opens an employee record, the fields they need are current without a call to another team. If the team still checks a spreadsheet before answering a question about an employee, the platform has not yet earned that trust.

When the data problem is bigger than HRSD

Some findings point to a source system that is itself unreliable. Duplicate employee identities across two HR systems, or position records that were never migrated, cannot be fixed inside HRSD. In that situation the health check should say so plainly, and the next step is a data remediation project upstream. Forcing HRSD to paper over the gap will make each workflow fragile in a different way.

Frequently asked questions about HRSD data health

Which field should we check first?

Start with the reporting line, because it drives approvals, notifications and access decisions. A wrong manager affects more processes than any other single field.

Can an automated rule correct mismatches safely?

Only where the source is known to be authoritative and the rule has been tested against a set of known errors. Otherwise, route mismatches to a person.

How often should the comparison run?

Set the cadence by how fast the data moves. Organisations with frequent restructures need more frequent checks than those with stable structures.

Who should own the mismatch queue?

An HR administrator with authority over the source data, supported by the platform team. Ownership by the platform team alone tends to push decisions onto people who do not know the business meaning of the field.

Next step

For a broader view of how HR records should flow between systems, the onboarding integration patterns describe the common flows, and the guide to offboarding controls covers the controls for the offboarding handover, which involves HR, IT, security and facilities.