iCIMS Requisition Approvals Setup: A Consultant’s Complete Guide

Hiring approvals are the part of iCIMS that everyone touches and almost no one configures intentionally. The recruiter opens the requisition, types in five names from memory, clicks Save, and then wonders why three days later it is still sitting in Pending Approval. iCIMS requisition approvals setup, done well, replaces all of that guesswork with a system that picks the right people, routes them in the right order, and tells you the second one of them is sitting on it.

This is the post we wish someone had handed us before our first iCIMS implementation. Every section is written from the configuration choices we make on real client builds, the iCIMS Community guidance our consultants reference daily, and the five mistakes that cause the most rework after go-live.

What iCIMS requisition approvals actually are

An iCIMS requisition approval is the gate that sits between “the recruiter has opened a job” and “the job is posted to the career site.” It pauses the requisition, routes it to a list of people who need to bless it (a hiring manager, finance partner, HR partner, VP, sometimes a Compensation team), and only releases the requisition into the open hiring workflow once those approvals come back.

iCIMS supports four flavors of approval that share the same underlying engine: Job (requisition) approval, Candidate approval, Offer approval, and iForm approval. The mechanics are similar across all four. We are focused on Job approval here because it is the one that touches every open role, every quarter, in every iCIMS instance.

Sequential vs parallel approval lists

Before you click anything in the configuration, decide which routing model you want. iCIMS gives you two, and the wrong choice is the most common reason a requisition takes 11 days to approve a 4-day search.

Most mid-market and enterprise teams we work with land on a hybrid: sequential for the spend approval chain (because Finance does not want to weigh in until the manager has actually committed), parallel for the compliance acknowledgements. iCIMS lets you use both by creating two different approval lists tied to different points in the lifecycle.

A quick rule of thumb

If the second approver could rationally say “I want to wait and see what the first approver decides,” use sequential. If the second approver does not care what the first approver does, use parallel. Easy.

Step-by-step iCIMS requisition approvals setup

Here is the order we walk every iCIMS requisition approvals setup through. Skip a step and the chain works in one test scenario but breaks the second a real recruiter tries to open an unusual role.

Configuring approver search and filters

The Approver Search is the dropdown that appears when a recruiter is adding people to the approval list on a specific requisition. Out of the box, it shows every active user in iCIMS, which is usually wrong. Recruiters end up adding someone in HR who hasn’t approved a job in two years, or worse, an approver who has since changed roles.

The fix lives in Configuring Approver Searches. You can scope the search results by login group, by user attribute, by job title, or by department. We typically configure three levels of approver search:

• Manager-tier: only people in the “Hiring Manager” login group plus their direct supervisors
• Finance-tier: only people in the “Finance Partner” login group, scoped by business unit
• Executive-tier: a small, named list of VP and above approvers, often pulled from an HRIS sync

This pairs neatly with the work we cover in our iCIMS login groups setup guide, because login groups are the source of truth for almost every approver search filter.

Minimum Approvers Required: how to use it well

The Minimum Approvers Required setting is the iCIMS feature that quietly saves dozens of stalled requisitions every quarter. The pattern is simple: add more approvers than you actually need, set the minimum to the number you need, and the requisition moves the second the threshold is hit.

Where this shines:

• Finance pool approval. Five Finance partners, any three sign off. PTO and travel do not stop hiring.
• HR partner coverage. Three HRBPs cover one business unit. Any two need to acknowledge. A vacation does not block the chain.
• VP redundancy. Two co-VPs, either one can approve. Common in matrixed reporting structures.

Login groups, workflow rules, and the approval chain

Approvals do not live in a vacuum. Three pieces of iCIMS configuration have to agree for the chain to actually work:

This is the part that bites teams who configured approvals before workflow rules. We see it almost every time we run an iCIMS system audit: the approval list works, every approver signs, and the requisition just sits there forever because the workflow rule was scoped to the wrong login group or never built. If your post-approval status is not changing, start with our diagnostic on iCIMS workflow rules not triggering, that fixes about 70% of these cases on day one.

Stalled approvals, escalation, and recall

Picture this: a recruiter opens a requisition on Monday. The hiring manager approves Tuesday. Finance is on PTO until next Wednesday. The requisition sits in pending approval for nine days. The role is now late, the candidate pool is cooling, and the recruiter is doing their job in a Slack DM.

iCIMS does not have a native time-based escalation feature for the Job Approval list out of the box. Here are the four patterns we configure when teams need real escalation:

1. Saved search + weekly email. Build a saved search called “Jobs Pending Approval > 5 Days.” Email it to the TA Ops lead every Monday. This is the cheapest pattern and works for most mid-market teams.
2. Workflow rule recall. Build a workflow rule that lets a TA Ops admin click a button to recall the approval, edit the list, and re-initiate. This is the manual override.
3. Approver delegation. Train approvers on how to use iCIMS’ delegation feature so PTO is not a hard block. (This is a behavioral fix more than a configuration fix.)
4. Auto-launch action surfaces stalled reqs. An auto-launch action attached to a status check can prompt a recruiter to act on a stalled approval. Not “true” automation, but a visible reminder.

5 most common iCIMS approval mistakes

Every iCIMS instance we audit has at least two of these five. Knock them out and your iCIMS requisition approvals setup will outperform 80% of mid-market deployments.

1. Save vs Save & Begin Approval

The recruiter clicks Save instead of Save & Begin Approval. The requisition is created, the approvers are listed, but nothing was sent. We see this most often with new recruiters who were trained on the legacy flow, or in instances where the button label was customized in confusing ways.

Fix: rename the buttons in your training materials so it is impossible to confuse. Build a saved search called “Requisitions in Pending Approval With No Approval Activity” and check it weekly.

2. Approval list attached to the wrong job template

The Director-tier approval list got attached to the VP-tier job template. The requisition routes to people without the spend authority. Finance bounces it. The recruiter starts over.

Fix: audit your job templates quarterly. One template, one approval list, one spend authority tier. If you have a hundred templates and only three signing tiers, your template library is too big.

3. Approver search not scoped, recruiters add the wrong people

The recruiter types “Smith” and adds the first Smith they see, who happens to be a contractor in a different business unit. The chain now includes someone with no authority. The requisition goes nowhere.

Fix: configure approver searches so the dropdown only shows eligible approvers. Pair this with login group hygiene so the search has clean inputs to filter against.

4. Login group misalignment between approver and post-approval workflow rule

Every approver signs off. The workflow rule that moves the requisition to “Open” is scoped to the “TA Admin” login group. None of the approvers are in that group. Nothing happens. The requisition sits.

Fix: every workflow rule that fires post-approval should either be scoped to a system or service user that is always in the right login group, or scoped to a group that always contains at least one approver. Test with a real approver, not a TA Ops account.

5. No escalation pattern at all

The chain works perfectly when everyone is at their desk. The minute one approver goes on PTO, the entire requisition stalls and TA has no visibility. Hiring managers escalate over Slack. The system goes around itself.

Fix: build the saved search, build the weekly email, and document the recall process. Even a basic escalation pattern eliminates 90% of the “the system is broken” perception that builds when one approval stalls.

Where this fits in the bigger iCIMS picture

Approvals are one node in a much larger system. They depend on login groups, they feed workflow rules, they generate notifications, they get reported on through saved searches, and they ultimately end up in the leadership reports we cover here. If you are seeing approval chaos, the fix is rarely “fix approvals in isolation.” It is usually “fix the approval list, then fix the upstream login groups, then fix the downstream workflow rule.”

The teams that get the most leverage out of their iCIMS investment treat the approval chain as a standing audit point. Quarterly review. Spot-check three random recently-approved requisitions. Time them end to end. If anything took more than three business days, dig into why. That single discipline is the cheapest intervention we know to keep iCIMS requisition approvals working as the company grows.

Frequently asked questions