Approval chains are a key feature of the Works platform that can help your unit and facility more efficiently manage the approval process and budget impacts associated with new staffing requests and extension offers.

Approval chains can be applied to new Staffing Requests and Extension Offers for currently working resources. Approval chains cannot be built for new offers since the staffing request being approved would cover any offers made from that staffing request.

Approval chains work in chronological (level) order. Let's use the images below as an example. As soon as the staffing request was created, Kevin, as the first level approver, would have received an automated email notification with a direct link embedded in the email routing him to the item requiring his approval. The staffing request must first be approved by the 1st Level: Kevin Uranyi. Only AFTER the prior level approver approves the item is the email notification fired off to the next level approver, 2nd Level: Russ Mortland. This is designed to cut down on unnecessary notification emails.

Once both levels have approved the staffing request or extension offer the suppliers will be notified of the approval(s) and will take the appropriate action.
​

One thing to note about approval chains is the levels are prescriptive only and there is no hard-coded delegation. What I mean by that is that anyone with approver access who is associated with the cost center the approval is for can approve each level. This was designed in case an individual was out of office, for example. In the above image if Russ Mortland was out of office then Kevin could approve both levels and not slow down the hiring and sourcing process.