Yardi Workflow Approvals: Delegation, Escalation & Staff Changes

A workflow approval is a routing rule that moves a transaction, such as an invoice, purchase order, or lease change, to the right person for sign-off before it posts. When that routing depends on one named person, every vacation, role change, and resignation becomes an operational outage. This post covers the configuration decisions that keep Yardi workflow approvals moving through staff changes: role-based routing, backup approvers, escalation, segregation of duties, and a checklist for offboarding an approver without stranding work in their queue.

Approvals are one piece of the larger discipline of property management workflow automation. This article focuses on the narrower, higher-stakes question inside it: what happens to in-flight approvals when the people in the routing change.

Why Approvals Stall

Approvals stall for one of three reasons: the routing points at a person who isn't available, the routing points at a person who no longer holds the responsibility, or no rule tells the system what to do when the first approver doesn't act. All three are configuration choices, and all three are fixable before they cost you a late fee or a missed vendor discount.

The symptoms are familiar to most operators:

• Invoices sitting unapproved because the approver is out of office
• Emergency purchases delayed waiting for unavailable managers
• Confusion about who should approve after a reorganization
• Items stranded in the queue of an employee who has already left

Role-Based vs. Person-Specific Routing

Route approvals to a role or group whenever the authority belongs to a position rather than an individual. Reserve person-specific routing for approvals that genuinely require a named person, such as a controller's sign-off above a dollar threshold. With role-based routing, a departure becomes a group-membership update instead of a workflow re-engineering project.

The tradeoff runs in both directions. Person-specific routing is precise but brittle: it breaks the day that person changes jobs. Role-based routing is durable but can diffuse accountability if the group is too broad. A pool where any of ten people can approve tends to become a pool where nobody reviews carefully, because everyone assumes someone else looked. Keep approval groups small, keep membership current, and make sure the approval history shows who in the group actually acted.

A practical middle ground for many organizations: role-based routing for routine operational approvals, person-specific routing with a designated backup for high-dollar or sensitive approvals, and a standing rule that every person-specific step must have a named alternate before it goes live.

Backup Approvers and Out-of-Office Coverage

Backup approvers only help if they exist before the absence starts. Configure alternates when the workflow is built, not when the primary approver is already at the airport. Then treat planned absences as a short checklist rather than an improvisation.

• Time-box the delegation: Coverage should start and end on known dates, so authority doesn't quietly persist after the primary approver returns
• Match authority levels: The substitute's approval limit should cover what will actually arrive during the absence, or items above their limit need a defined path
• Brief the substitute: Tell them what volume to expect, which vendors or properties are unusual, and who to ask when something looks wrong
• Confirm mobile access: An approver who can act from anywhere shortens every cycle, absence or not

Thresholds, Escalation, and Segregation of Duties

Approval thresholds, escalation rules, and segregation of duties are the three controls that decide whether your workflow is fast, safe, or both. Thresholds route small decisions to the people close to the work and reserve senior attention for material amounts. Escalation defines what happens when nobody acts. Segregation of duties keeps any one person from controlling a transaction end to end.

On thresholds: set limits that match actual responsibility. If a property manager can commit $2,500 in the real world, a $500 workflow limit just manufactures approval traffic for their supervisor without adding control.

On escalation: every approval step should have an answer to the question "and if they don't act within X days, then what?" Define the escalation path (usually the approver's manager or a designated queue), the timing, and the notification. Escalation that pages someone is a control; escalation that silently reroutes is a surprise waiting for an audit.

On segregation of duties: the person who enters an invoice shouldn't be the person who approves it, and the people who can edit workflow configuration itself should be a short, known list. Auditors reviewing your controls will ask for exactly this, and the approval history is your evidence. Review that history periodically: it will show you rubber-stamp patterns (approvals seconds after submission), delegations that never expired, and steps still assigned to people who changed roles months ago. Duty separation also has to hold in role permissions themselves, not just in routing; our Yardi user security guide covers that broader access model.

Before You Deactivate a User: Handle Their Pending Items

Before deactivating a departing user, inventory every workflow step assigned to them, then reassign or complete their pending approvals, and only then remove access. Deactivating first strands whatever was in their queue, and stranded items don't announce themselves. They surface weeks later as a vendor call about an unpaid invoice.

This is fundamentally a timing problem between HR, IT, and your Yardi administrator. Access removal is usually driven by the termination checklist; workflow reassignment usually isn't on that checklist at all. Add it, and sequence it first.

The Workflow Change and Offboarding Checklist

When an employee changes roles or leaves, work through the workflow impact deliberately:

Role Changes

• List every workflow where the employee appears as approver, alternate, or escalation target
• Update assignments to reflect the new responsibilities, in both directions: remove what they shouldn't keep, add what the new role needs
• Reassign the old role's steps to whoever inherits them, not to a vacancy
• Run one test transaction through each critical workflow after the changes

Employee Departures

• Identify all workflows involving the departing employee, including alternate and escalation assignments
• Clear or reassign every pending approval in their queue before access is removed
• Reassign their approval responsibilities to named successors with appropriate thresholds
• Expire any active delegations pointing to or from them
• Document what changed, and confirm no workflow step now points at a deactivated user

Test Scenarios That Prove Coverage Works

Configuration you haven't tested is a hypothesis. Four scenarios, run with low-value test transactions, will tell you whether your coverage actually holds:

• The vacation test: Activate a delegation, submit a small invoice, and confirm the alternate receives it and their threshold applies
• The escalation test: Let a test item sit past the escalation window and confirm it moves to the right person with a notification
• The departure dry run: Pick a user with active assignments, list what would strand if they left tomorrow, and time how long full reassignment takes
• The audit-trail pull: Retrieve the complete approval history for one transaction, from submission to posting, and confirm it answers who approved what, when, and under whose authority

Where Invoice and AP Approvals Get Specific

Everything above applies to any approval type in Yardi. Invoice approvals add their own layer of routing logic, and if that's your bottleneck, our Yardi PayScan guide covers invoice-specific approval configuration in depth. If you're rethinking the full purchasing-to-payment cycle around those approvals, the Yardi Procure to Pay guide walks through the entire lifecycle from purchase order to payment.

Getting Help

If your Yardi workflows are causing bottlenecks or breaking when staff changes occur, we can help. BC Solutions provides independent consulting support for organizations that use Yardi: our consultants can audit your current workflow configuration, identify the person-specific routing and missing escalations that will fail next, and implement the fixes, while our help desk team handles the day-to-day questions your approvers run into.