Skip to content

Multi-level hiring approvals: who must say yes before a candidate moves forward

In a chain, the branch manager likes a candidate and head office has never met them. Approval rules per stage, named approvers in a fixed order and a rule that any “no” stops the card make hiring accountable without making it slow.

By Wameed compliance teamZATCA and e-invoicing

5 min read

In short: Wameed lets each stage of a hiring pipeline requireapprovals. The default pipeline hasthree levels (Screening, Interview, Offer, one approval each). A stage can requireN approvals from anyone with the approve permission, ornamed approvers (a quorum of N of M), or named approversin order, each notified when it is their turn. A cardcannot skip a stage until its quorum is met,any approver’s “no” rejects the application, and moving a card back voids the votes at that stage and later ones. Everything is recorded in the timeline.

Hiring decisions are expensive and sometimes hard to reverse. Approvals put the right people in the loop without a stack of emails.

When approvals help

  • Chains, where branch managers recruit and head office or a regional manager signs off.
  • Sensitive roles: those with cash, stock, customer data or supervision.
  • Salary above a band, requiring finance sign-off.
  • Owner-managed shops, where the owner wants to meet every final candidate but not read every CV.
  • Reducing bias: several independent opinions beat one.

If you are a three-person shop, you may need none of this. Keep it light.

The building blocks

Required approvals per stage

Each stage has a number of approvals required before a card can movepast it. The default pipeline:

StageApprovalsTypical approver
Applied0None
Screening1Recruiter or HR
Interview1Hiring manager
Offer1Owner or regional manager
Hired0The final decision

That is three levels of acceptance out of the box.

Who may approve

Three modes:

  1. Anyone with the approve permission at the branch, until N have voted.
  2. Named approvers, a quorum: for example 2 of these 3 people.
  3. Named approvers in order (sequential): level one first, then level two, and so on. Each is notified when it is their turn, and everyone named must approve.

Optionally, the cardadvances automatically when the quorum is met.

The rules that make it safe

  • A card cannot move forward past a stage until its quorum is met, and cannot skip a stage.
  • One vote per approver per stage.
  • Only named approvers can vote where names are set; in order where sequential.
  • A vote requires the approve permission.
  • Any “no” rejects the application. Reopening restores the card where it stood, and the “no” stays on the record, so a fresh decision must come from someone else.
  • Moving a card back voids the votes at that stage and every later one. They are kept for the record, struck through, but must be given again.
  • Entering Hired needs the approve permission.
  • Creating the staff member needs the staff permission too, so approving a hire is not the same as creating a person.

Designing your approval chain

A single shop

Screening (owner), Interview (owner), Offer (owner). One person, three records. Auto-advance can keep it quick.

A growing chain

  • Screening: HR or branch manager, one approval.
  • Interview: hiring manager and a peer, two approvals from named people.
  • Offer: regional manager, then finance if the pay is above a band, sequential.

A chain with a sensitive role (cashier supervisor, stock controller)

Add asecond named approver at the Interview stage from outside the branch, so no one hires alone into a role that handles money.

Keeping it fast

Approvals fail when they sit in someone’s inbox. To stop that:

  • Notifications go to the next approver, in their language, when it is their turn.
  • A “waiting on you” badge shows on the card, and the inbox follows the turn.
  • Set a service level: approvers answer within 48 hours.
  • Use auto-advance where the vote is a formality.
  • Review the stage times to find the bottleneck.

Records and fairness

The application screen shows each approval level, who the named approvers are, how each voted (voided votes struck through), and the full timeline. That gives you:

  • A defensible record of why someone was or was not hired.
  • Fairness checks: are the same criteria applied to each candidate?
  • Training evidence for new hiring managers.

Keep rejection reasonsinternal; they are never shown to the candidate. Confirm your legal position on discrimination and record-keeping with your adviser. Seerecruitment and the careers page.

Mistakes to avoid

  • Too many levels for a small business.
  • Approvers who are on leave. Name a substitute.
  • Letting a “no” be overridden quietly. Reopen it on the record.
  • Moving a card back to “fix” an approval problem and then forgetting the votes are voided.
  • Hiring first, approving later.

Frequently asked questions

Can an approver skip a level?

No. A card cannot move past or skip a stage until its quorum is met.

What happens if someone says no?

The application is rejected. It can be reopened and the “no” stays on record.

Can approvers be named people?

Yes: a quorum of N of M, or in a fixed order.

Who can create the staff member?

Someone with approve permission for the hire and the staff permission to create people.

  • #اعتماد التوظيف
  • #موافقات متعددة المستويات
  • #سير عمل التوظيف
  • #قرار التوظيف
  • #hiring approvals
  • #multi-level approval workflow
  • #recruitment governance

Share this article

Ask about your own shop

Thirty minutes on your products, your tax setup and your hardware — not a slide deck.

Keep reading