Modernizing HRMS into employee self-service and connected workflows.

The situation

An HR system existed, but employee work was still paper-first.

The organization already used Sage HRMS, primarily as a prerequisite for payroll. That did not make it an employee operating system. Paystubs had historically been mailed. Acknowledgements, data changes, onboarding, offboarding, reviews, and other HR processes depended on paper, email, manual follow-up, or administrative movement between systems.

An early digital photography-consent acknowledgement created a small first phase. The broader opportunity came when Jeremy partnered with the HR manager to examine how employee self-service and governed HR workflows could work across the existing HRMS, accounting, and payroll environment.

The problem was not simply “replace paper.” HR work includes authority, privacy, records, approvals, notifications, audit, and downstream data movement. A form can make intake easier while still producing an unsafe or ambiguous process. The modernization needed to distinguish who could see an event, who could approve it, when a change became official, what moved into payroll, and what record remained afterward.

Platform decision

Choose a connected ecosystem over a separate employee experience.

The organization evaluated Employee Navigator as a separate option. It offered a different employee-facing experience, but it would have introduced another platform boundary beside Sage HRMS, Sage 100, and payroll. Jeremy and HR chose to expand the native Sage ecosystem through Employee Self Service and HR Actions.

The decision favored alignment and governed data movement over adding another disconnected source. It also created a path to improve the system already holding essential employee and payroll information. The tradeoff was that the native environment would still require careful operating design, customization, integration, testing, and adoption work to become useful.

A vendor installed the products and completed basic configuration. Jeremy’s responsibility began around the operating system the organization needed: discovery, platform selection, contract/timeline/milestone coordination, workflow design, customization, embedded user experience, integration, testing, rollout, support, reporting, and the continuing roadmap.

Operating design

Make authority, handoffs, and retained records explicit.

The modernization expanded employee access to HR data, paystubs, acknowledgements, onboarding and offboarding, data-change requests, performance reviews, and other governed processes. Jeremy worked with HR to translate policies and responsibilities into conditional assignments, delegated and multistep approvals, audit history, generated PDF retention, analytics, and approved movement into payroll.

A central design principle was to separate awareness from authority. A leader may need to know that an event occurred without becoming an approver. A reviewer may validate information without owning the final decision. An approved change may move to another system only after the correct record exists. Treating every notification as approval would create both confusion and governance risk.

Another principle was progressive improvement. Electronic paystubs first moved from postal mail to email after Jeremy investigated and configured digital delivery. The later ESS rollout advanced that process again to on-demand employee access. The story is not a single “paperless” moment; it is an operating model becoming more useful in stages.

A concrete workflow

An address change became more than an online form.

Address change is the clearest public example because it shows the full operating chain. An employee can initiate the request through self-service. The HR workflow applies the appropriate review and approval path. The action maintains an audit history and can retain a generated PDF record. After approval, the information updates the HRMS and follows the approved movement into payroll.

The important improvement is not merely digital intake. It is the governed transition from employee request to reviewed organizational record to connected downstream system. Each stage has a purpose and an owner.

Result and continuing ownership

A platform became a governed employee and HR workflow environment.

The defensible outcome is a broader operating capability: employee self-service, accessible pay information, digital acknowledgements, governed data changes, lifecycle workflows, reviews, retained records, reporting, and connected movement into payroll. Approximately 95–100 employees were in organizational scope.

Jeremy continues to create reports and condition-based automations, support the environment, and work with HR on new requirements. Native procedures and workflow conditions help keep authority explicit. Notifications can inform the right people without silently changing who is permitted to approve.

The case demonstrates more than platform selection. It shows a decision that balanced employee experience with system alignment, a vendor partnership with clear ownership boundaries, the translation of HR policy into operating rules, and continuing responsibility after launch.

No recovered evidence supports a public number for active users, workflow volume, hours saved, paper reduction, error reduction, or financial return. Those metrics are not needed to explain the credible change: an existing payroll-adjacent system became a connected self-service and workflow environment with explicit governance and continuing ownership.

Evidence boundaries

What this story proves—and what remains private.

This case supports platform evaluation, business partnership, contract and milestone coordination, workflow architecture, customization, integration, testing, rollout, reporting, support, and continuing product ownership. It shows Jeremy making connected operational and technical decisions without claiming that he performed the vendor’s installation work.

The page does not publish employee, payroll, HR, injury, performance, approval-chain, or production-screen information. Approximate employee scope remains approximate and does not imply verified active use by every employee. No quantified time, error, paper, adoption, or financial savings are asserted.