Workday Business Process Routing: Approvals and Delegation

Workday business process configuration comes down to four decisions: which steps a process needs, who each step routes to, when a step should be skipped or stopped, and who covers for an approver who is away. Get those right in a sandbox with written test cases, and approval routing stays predictable when people, organizations and policies change.

Key takeaways

• Every business process type has one security policy, but it can have a default definition plus organization-specific definitions, and Workday picks the most specific one it finds.
• Approval chains walk up the management hierarchy, so a deep supervisory structure means more approvals unless you add while running or exit conditions.
• Routing restrictions stop initiators, prior approvers and the event subject from approving their own transactions.
• Delegation must be enabled on the business process security policy before anyone can use it.
• Definition changes are effective dated, and in-flight transactions keep the definition that was active when they were initiated.

How does Workday decide which approval steps a transaction follows?

A business process definition is an ordered list of steps. Workday's HCM Core course material explains that steps are labeled with letters and sorted alphabetically, step "a" is always Initiation, and only one step can be the completion step, which is where data is committed. All approval and review steps have to sit before completion, because once data is committed there is nothing left to approve.

Which definition applies depends on the organization involved. Workday looks first for a definition specific to the transaction's organization, then walks up through each superior organization, and finally falls back to the default definition. Inactive definitions and definitions with errors are skipped. An old organization-specific copy can quietly override every change you make to the default, so list every definition for the process type before you edit anything.

Workday recommends default definitions for easier maintenance. If the only difference is one extra approval, an entry condition on the default definition is cheaper to maintain than a second definition.

Which step types should you use for approvals?

The step type determines what the assignee can do, so choose it based on whether the person needs to edit data.

Step type	What the assignee can do	Good fit
Approval	Approve, send back or deny; cannot edit data. A denial denies the whole process	Budget owners, finance sign-off
Action (review)	Review and edit, then submit	HR partner or compensation partner who may need to correct values
Approval Chain	Approval routed up the management hierarchy until the top or an exit condition	Policies that require "two levels above the employee"
Consolidated Approval	One task that combines several approvals for the same worker	Reducing duplicate approvals across subprocesses
To Do and Checklist	Instructions for work done in or outside Workday	Badge requests, equipment, manual payroll setup
Integration	Triggers data transfer to or from another system	Notifying a downstream provisioning or benefits system

Steps that share the same letter run in parallel, and all of them must finish before the next step starts. Use them when finance and HR review a change independently, and tell each reviewer what they are responsible for checking.

How do you control approval chains so they do not run forever?

An approval chain moves up the hierarchy one manager at a time. In a deep structure, a change for a frontline worker can end up in front of a vice president with no context. Workday gives you condition rules to shape that behavior:

• Entry conditions decide whether a step runs at all. They apply to every step type except Initiation.
• While running conditions decide whether the next manager in the chain must approve. They only apply to Approval Chain and Consolidated Approval Chain steps.
• Exit conditions decide when a chain step is complete, for example once it reaches a manager at a certain management level.
• Validation conditions stop the process when data is wrong. They apply to Initiation and Action steps.

A typical pattern is an exit condition that stops at a director level approver, plus an entry condition so the chain only runs above a threshold your policy defines. We cover the mechanics of building and attaching the rules in our guide to Workday step conditions and validation messages, so this article stays on the design questions.

Routing restrictions and self-approval

The Maintain Advanced Routing task lets you exclude the initiator, prior approvers or the event subject from a step. This matters more than it looks. Without it, an HR partner who also manages a small team can initiate a raise for a direct report and then approve it. If restrictions exclude every assigned person, Workday skips the step, so pair restrictions with an alternate security group that picks up the work instead of letting the approval disappear.

Who can be assigned to a step?

Each step is assigned to a security group, and the business process security policy limits which groups are available, so routing is partly a security design question. If the role-based groups behind your routing are messy, routing will be messy too, which is why we recommend reviewing how your Workday security groups are designed before redesigning approvals.

How should delegation work when approvers are out?

Delegation lets a worker hand some or all My Tasks items to someone else for a date range. Workday's documentation lists three prerequisites: delegation enabled on the relevant business process security policy, the Request Delegation Change business process configured, and users granted the Business Process Delegation domain. Tenant settings also control who workers are allowed to delegate to.

Design decisions to make up front:

1. Which processes are delegable. Many organizations allow delegation of time off and expense approvals but not compensation or termination approvals. Decide per process, not globally.
2. Whether delegations need approval. Delegation requests can route for review, which slows urgent coverage, so decide where that control is worth the delay.
3. End dates. A tenant can require end dates. Turn that on so delegations do not outlive the absence they covered.
4. Self-approval through delegation. If routing restrictions apply during delegation, Workday can route to an alternate delegate (by default the delegate's primary manager) so the delegate never approves their own transaction.

Delegates cannot re-delegate tasks they received. Administrators can review history and stop current delegations from the Manage Delegation Settings report, which helps during audits and offboarding.

How do you test business process changes safely?

Business process changes are effective dated, and the initiation date of a transaction determines which definition version it uses. A fix will not help transactions already sitting in inboxes, so plan communications accordingly.

A practical testing sequence:

1. Write the routing matrix first. For each scenario, list the expected approvers in order.
2. Build one condition at a time in a sandbox. Workday's own course guidance recommends this, along with the Rule Tester task for checking condition logic and the Report Fields and Values report for confirming field values on a real event.
3. Test with real personas. In a non-production tenant, initiate transactions as test users who hold the same roles as an HR partner, a manager and a self-service employee. Check that excluded approvers are actually skipped.
4. Test the edge cases. Vacant manager positions, multiple managers on one supervisory organization, a worker who manages their own organization, and a delegation in effect during the test.
5. Check notifications. Confirm custom notifications reach the right people without duplicates.
6. Activate security changes deliberately. Policy edits stay pending until someone runs Activate Pending Security Policy Changes. Include that step in your deployment checklist.
7. Re-test after Workday releases. Add your routing matrix to the regression suite described in our Workday release management testing plan.

Frequently Asked Questions

What is the difference between an Approval step and an Action step in Workday?

An Approval step lets the assignee approve, send back or deny, but not change data, and a denial ends the whole process. An Action step, often used as a review, lets the assignee edit values before submitting. Use Approval for budget or policy sign-off and Action for HR or compensation partners who are expected to correct details before the transaction is committed.

Why did my business process change not apply to a transaction?

The transaction most likely started before your change's effective date, because Workday uses the definition active on the initiation date. Another common cause is an organization-specific definition for that worker's organization or a superior organization, which Workday uses ahead of the default. Check both the effective date and the full list of definitions for that process type.

Can a manager delegate approvals to anyone in Workday?

No. Delegation must be enabled on the business process security policy for each process, users need the Business Process Delegation domain, and tenant setup controls who workers may delegate to. Delegations can also require approval. Many organizations restrict sensitive processes such as compensation or termination so they cannot be delegated at all.

How do I stop someone from approving their own request?

Use the Maintain Advanced Routing task to exclude the initiator, prior approvers or the event subject from a step. If that exclusion removes everyone assigned, Workday skips the step, so add an alternate security group to take over. Then test the scenario with a manager who initiates a change for a direct report.

How many approval levels should a Workday business process have?

There is no universal number. Start from your delegation of authority policy and require the fewest approvers that satisfy it. Add while running or exit conditions to approval chains so they stop at the level that holds authority, and use entry conditions so higher levels only see transactions above defined thresholds.

Next steps for your HRIS team

1. Export every definition for your five highest-volume business processes and flag organization-specific copies.
2. Write a routing matrix for each and get policy owner sign-off.
3. Add routing restrictions and alternate groups wherever self-approval is possible.
4. Review delegation settings: delegable processes, required end dates and approval needs.
5. Test every change in a sandbox and keep the test cases for future releases.

For more configuration walkthroughs, browse our Workday guides.

Last reviewed: October 2026.

Sources

• Business Process Framework, Workday Education
• Advanced Business Process Configurations, Workday Education
• Delegate My Tasks, Workday Documentation