Enterprises have automated parts of the workforce change process, but the parts are scattered across email, chat, the HCM and a ticket queue, so the control exists while its evidence does not. A national mortgage lender built SOX-audited manager self-service in UKG Pro by settling the delegation matrix before anyone designed a form.
Table of Contents
Almost every enterprise has automated parts of the workforce change process. That is not the problem. The parts are scattered: the request arrives by email, approvals happen in a chat thread, the transaction gets keyed into the HCM, and the IT work is raised as a ticket by whoever remembered. Each step may be automated. The chain is not.
For a small organization that fragmentation is survivable. Where compensation and headcount feed audited financial statements, the control exists but its evidence is scattered across four systems, none of which was designed to hold it.
Manager Self-Service in UKG Pro Serves Two Audiences at Once
The HRIS Director’s problem is intake. Actions arrive in whatever format the leader chose, missing whichever fields they did not know were required. HR operations becomes a translation layer, converting requests into transactions and chasing what is missing. The work is invisible, constant, and impossible to staff for.
We were not processing workforce changes. We were interpreting them.
HRIS Director, national mortgage lender
Internal audit arrives from the opposite direction with an evidence problem. Under Section 404, controls over financial reporting must be documented and testable, and compensation and headcount are direct inputs to those statements. When a pay change was approved in an email thread, the control exists but the evidence is scattered. Auditors do not ask whether the right person approved it. They ask you to demonstrate it, months later, for a sample.
Both problems share one solution: leaders initiate workforce actions inside the system of record, under the organization’s own delegation rules, with the approval chain and audit trail produced as a byproduct rather than reconstructed on request.
The reason this needs building is structural. Employee self-service assumes actor and subject are the same person, so the permission model is simple. A leader initiating a workforce action is working on someone else’s record, the action carries financial materiality, and the authority to approve it depends on position and dollar thresholds, with a path that may involve four sequential parties across HR, finance, and the reporting line. Some actions apply to one employee, others to forty at once. UKG Pro holds the record, the structure, the compensation data, and the effective-dating that makes the transaction correct. What gets added is the leader-facing layer above it.
The Delegation Matrix Comes Before the Forms
The organizations that get this right share one sequencing decision, and it is the whole argument here: define the delegation matrix before anyone designs a screen. Who may initiate a compensation change. At what threshold a second or third approver enters. Which actions require finance rather than only the reporting line. What evidence each step must leave behind.
That matrix is a controls artifact, not a configuration detail, and it usually already exists in the company’s SOX documentation as a delegation of authority. Projects stall when HRIS and internal audit negotiate over form fields instead, because a form is a proposal about authority neither party can approve until the matrix is settled. Once it is explicit, routing and logging are implementation.
What a National Mortgage Lender Built
A large national mortgage lender took this on for its leader population. Working with CloudApper, it built a leader portal embedded directly in UKG Pro, reached through the single sign-on identity leaders already use, so it is not a separate destination with its own credentials.
Free Datasheet
CloudApper Substitute Request & Management Solution for UKG Ready Datasheet
The portal presents structured forms for the actions leaders initiate: team member movement, compensation changes, separations, and requests for new titles. Each submission enters a four-step approval chain, and mass movement is supported so a reorganization follows the same reviewed path as a single transfer. Every step writes to an audit log built for SOX examination rather than troubleshooting. The reorganization case is the one that matters most: a restructure moving a large group across a single weekend produced the same evidence per change as an individual separation, with no compensating control and no side spreadsheet. Where an action has IT consequences, such as access or equipment, the portal opens the ServiceNow ticket automatically rather than relying on someone to remember.
Be precise about the claim. The portal does not automate SOX compliance, and saying so invites an argument the organization will lose. It records the approvals and evidence the existing controls already required, captured inside an authenticated UKG session rather than in email threads. The control did not change. Where its evidence lives did.
The ServiceNow trigger is the detail HRIS teams appreciate most, because forgotten provisioning is how a completed transaction still produces an employee who cannot work on day one. Organizations solving the same problem often approach it through identity provisioning automation tied to lifecycle events, and the reasoning is identical: the system that knows the change happened should be the system that triggers what the change requires.
The difference at audit time is that I am no longer building the evidence. I am retrieving it. Those are completely different amounts of work, and only one of them is defensible.
Director of Internal Audit, national mortgage lender
The lender’s Compensation Manager framed it as a data question, noting that submissions now arrive “complete the first time, because the form will not let them be otherwise.”
What to Require If You Are Scoping This
With the matrix settled, three requirements remain.
Evidence has to be automatic. If producing an audit trail requires anyone to do anything extra, it will be incomplete when it matters. The log should be a consequence of the transaction, capturing the named approver and timestamp at every step, not only the final one.
Mass actions need the same control path. Reorganizations are when discipline slips, because volume invites a bulk load that bypasses review. Mass movement has to be a first-class workflow.
Downstream systems should be triggered, not remembered, which is the difference between a workflow and a checklist. The same instincts drive the questions about how to extend UKG Pro without upgrade exposure and automate workflows without a development cycle, because thresholds change.
What Changes When Delegation Runs Inside the Transaction
For the organization, the return is audit posture and speed at once, which is unusual. Controls normally slow things down. Here the structured path beats the email it replaced, because nothing waits on interpretation.
For HR operations it is a role change. A function that spent its capacity translating requests moves to reviewing exceptions, which is what those people were hired for. Data quality improves too, since structured intake prevents the incomplete position and cost center records that otherwise surface later as reporting problems, and it reduces the archaeology that HRIS admins do when tracing how a field came to hold the value it holds.
“I used to send an email and hope. Now I can see where my request is, who has it, and what happens next. I stopped following up on things, which means I stopped being the reason they moved.”
Team Leader, national mortgage lender
For employees, the effect is the one nobody puts in a business case. A pay adjustment stuck in approval limbo is experienced by the person waiting on it, not the system holding it. Visible status means the change takes effect when it was meant to, and the manager who promised it can say where it stands. That is a retention matter before it is a compliance one.
UKG Pro remains the system of record throughout. What CloudApper added is the layer where actions are initiated, routed, evidenced, and propagated. CloudApper WorkBridge exists for this class of build, and organizations moving away from routing HR actions through external ticketing systems often start with the same question about where manager requests should actually live.
The CloudApper AI Platform for UKG exists for requirements like this one: specific to an organization’s approval structure, materiality thresholds, and control environment, too particular to belong in any platform’s core, and too consequential to run through a mailbox. CloudApper is the process layer that holds the work, on any platform, in weeks rather than quarters. The organizations that move fastest are not the ones with the loosest controls. They are the ones whose controls run inside the transaction instead of alongside it.
If your leaders still initiate workforce changes by email and your audit evidence gets assembled after the request, talk with the CloudApper team about a structured leader portal inside your existing UKG Pro environment.
Project 