Start free trial Watch 4 min video Book a demo
Holidays & time off

Event Authorisation Workflow – Backup Approver

ApprovalsCalendar

Installing this workflow tells Sense to send every event request to the employee's line manager and a secondary approver at the same time, rather than in sequence. Either one can approve or reject it, so a request never sits waiting on a single person's availability.

Install workflow Book a demo

How it works

Set your Secondary Approver field then let Sense notify both approvers at once

  1. To use the Event Authorisation Workflow – Backup Approver, simply add a Secondary Approver field to the Job Details screen using Screen Designer, populate it for each employee, and undeploy the default event authorisation workflow.

  2. Then, every time an employee submits an event request, Sense will automatically notify their line manager and secondary approver at the same time.

  3. If either one approves or declines, then the employee is emailed the outcome, and the approver who didn't action it gets a confirmation email too.

See pricing

More holidays & time off workflows

See all holidays & time off workflows
Event Authorisation Workflow – Dual Approval (Manager & Admins)Route every event request to the line manager first, then on to admins only once they approve, so two people sign off before the employee hears the outcome. ApprovalsCalendar Event Authorisation Workflow – Dual Approval (Manager & Secondary Approver)Send event requests to the line manager first, then a named secondary approver for the final sign-off, so two people approve before the employee is emailed. ApprovalsCalendar Event Authorisation Workflow – Dual Approval (Primary Approver & Manager)Send event requests to the employee's named primary approver first, then their line manager for the final say, emailing the employee once both have decided. ApprovalsCalendar

Common questions

What kicks this workflow off?

An employee submitting an event request from their calendar.

Who approves the request?

The line manager and the secondary approver, notified at the same time. Only one of them needs to act.

What happens once one of them makes a decision?

The employee gets an email confirming the outcome, and the approver who didn't action the request also receives a confirmation email.

What if an employee has more than one job role?

All the managers and secondary approvers across their roles receive the request, but only one approval is needed overall.

How is this different from the Reroute Approver workflow?

Reroute sends the request to one named approver instead of the manager. Backup Approver sends it to the manager and a secondary approver together, so whichever one is available can act.