Skip to content
English
  • There are no suggestions because the search field is empty.

The approval workflow

How to submit a job for approval, follow it through each level, withdraw the request, and what happens if it is rejected.

How to submit a job for approval, follow it through each level, withdraw the request, and what happens if it is rejected.

If your organisation requires approvals, every new job has to be signed off before it can be set up and published. The person raising the job submits it from the job creation flow, the approval groups sign it off, and the job then moves to Pending Setup. This article covers the submitter's side. Approvers should read "Approving or rejecting a job". Administrators building workflows should read "Setting up approvals for your organisation". "Job statuses explained" covers the statuses a job passes through.

Submitting a job for approval

Admin and HR users can submit any job. A Member can submit a job they are the hiring lead for. Agency users cannot. Only a job in Draft can be submitted. If your organisation has switched off Require approvals for new jobs, there is no Approvals step: the job goes straight from Job Details to setup, and only Admin and HR users can raise jobs.

  1. Go to Jobs and start a new job. Choose how to create it on the Start step, then complete Job Details.
  2. On the Approvals step, choose a Workflow Type. Your organisation may have several. If none exist, the step says "No approval workflows configured. Contact your administrator."
  3. Under Approval Levels, each level shows its name and a badge. Can edit + approve means the approvers at that level can change the job as well as approve it. Approve only means they cannot.
  4. Assign a group to each level. A level with a padlock and the text "The approval workflow decides which group approves this level." is fixed and cannot be changed. Every other level needs a group chosen from Select approval group....
  5. Answer the questions under Approval Justification. Your organisation sets these, and any marked required must be filled in. If one is missed, the job is not submitted and the message lists the fields that are missing.
  6. Select Submit for Approval.

To stop part way, select Save as Draft on the Approvals step. It stores your workflow, group choices and justification answers. Later, open the job from the Jobs list (set the Status filter to Draft or All statuses, as the list opens on Published jobs) and select Continue Draft Job.

A group with no members cannot be used. The step shows "This group has no members. Add members before submitting for approval." next to it, and the submission fails until a System Admin adds someone to the group. A group marked Hidden is not offered in the group list unless the workflow already fixes it on that level.

If required job details are missing, the submission fails with "Job is not ready to publish" and a list of the fields. Go back to Job Details, complete them and submit again.

If your organisation has turned on admin bypass, a System Admin sees an extra switch on the Approvals step: "Admin bypass: skip pending approvals and mark as Approved". Switching it on changes the button to Submit with Admin Bypass. The job goes straight to Pending Setup, nobody is asked to approve it, and the Approval History records that an admin bypassed it. HR users never see this switch.

What happens after you submit

The job moves to Pending Approval. What happens next depends on the Workflow Mode of the workflow type you chose.

  • Cascade. The levels run one after another. Everyone in the group at level 1 is emailed, and only that group can act. Each later group is emailed when the level before it approves.
  • Parallel. Every level's group is emailed at once, and the groups can approve or reject in any order. The job is approved when no level is left waiting. Nobody is emailed as individual levels finish.

In both modes you are emailed when the last level approves and when any level rejects. The email carries the approver's name and their comment or reason.

Approvers are only emailed if they are active users, have email notifications on, and have Approval action needed switched on in their notification settings. If a job is sitting still, ask the approver to check My approvals in the left navigation, which lists every job waiting on them. Approval does not publish anything: after the last level approves the job is in Pending Setup, and it goes live when setup is completed.

Following a job through approval

Open the job and stay on the Details tab. A banner shows Pending Approval and the group the job is waiting on, with a badge such as "Level 1 of 2". In a Parallel workflow it names only one of the groups still to decide, so use the Approval History to see every level.

The Approval History card near the bottom of the page lists every round of approval for the job. For each round it shows who submitted it and when, each level's decision with the approver's name, any rejection reason, the justification answers in the order your organisation set them, and how the round ended: approved, rejected, withdrawn or bypassed.

On a job brought across from the previous system you may also see an Approval History (Vacancy Filler) card with a Legacy record badge. It is read only and kept separate from approvals made in Recruit.

Admin and HR users also see a count such as "3 awaiting approval" beside the Jobs heading.

Changing or withdrawing a request

While a job waits, only approvers whose level is set to Can edit + approve can edit it. In a Cascade workflow that means the current level. In a Parallel workflow it means any level still waiting. For everyone else the Edit option in the job's actions menu reads Edit (blocked during approval). If you need to change something yourself, withdraw the request.

  1. Open the job and scroll to the Approval Actions card.
  2. Select Withdraw Approval Request.
  3. Optionally give a Reason for Withdrawal, then select Withdraw.

The job returns to Draft and the approvers who were still waiting are emailed. Only the person who submitted the request or an Admin can withdraw it. Withdrawal is not possible once the request has been fully approved or rejected.

If the job is rejected

The job goes back to Draft and you are emailed with the approver's reason. When you open the job, a banner reads "This job was previously rejected" followed by the reason, with a View history link to the full record. If it has been rejected more than once, the banner gives the number of times.

Edit the draft, deal with the reason given, and submit it again from the Approvals step. A rejection or withdrawal discards the progress made so far, so the new round starts again at level 1. The earlier rounds stay in the Approval History.