ICIMS Requisition Approval Not Working: 7 Causes and Fixes

We get this call more than almost any other: “ICIMS requisition approval not working, the hiring manager says they never got anything, and the req has been sitting for a week.” Nine times out of ten the platform did exactly what it was configured to do. The gap is in how the approval was started, who is in the chain, or what happened to the email on its way to the approver.

This guide walks through the seven causes we see most often across mid-market and enterprise ICIMS instances, in the order we check them. Each one has a diagnostic you can run yourself and a fix that stops it from recurring. If you are still building your approval chains, start with our ICIMS requisition approvals setup guide and come back here when something stalls.

How ICIMS requisition approval actually routes

Before diagnosing anything, it helps to know what ICIMS does when a requisition goes out for approval. Approvers are attached to the requisition in a specific order, and ICIMS notifies them one at a time, in that order. The second approver does not hear anything until the first approver acts.

Each approver receives a Job Approval Request email with a link. That link opens an approval screen where they can review the details and description, add a comment, and click Approve or Decline. Approvers who are logged in also see the requisition under Jobs Pending My Approval on their dashboard.

Everything about the chain is visible on the requisition’s Approval tab: who is in it, who has acted, and who the requisition is waiting on right now. That tab is where every diagnosis in this post begins.

Cause 1: The approval was never started

Problem. The recruiter or hiring manager built the requisition, added approvers, and clicked Save. Saving stores the requisition. It does not route it. The button that routes it is Save & Begin Approval (or the equivalent “begin approval” action in your configured requisition form), and ICIMS customer guides we reviewed call this out explicitly: clicking Save alone will not start the process.

Impact. The requisition looks finished to the person who created it, so nobody follows up. Days later someone asks why the job is not posted.

Example. A new recruiter creates twelve requisitions in their first week. Eight route correctly. Four sit untouched because they were saved and closed before the approval action was clicked.

Fix. Open the requisition and check the Approval tab. If it is empty or shows no pending approver, reopen the requisition, confirm the approver list, and start the approval. To stop it recurring, add “start the approval” to the recruiter checklist and build a saved job search for requisitions in a draft-style status older than two business days. Review it every morning.

Cause 2: The chain is waiting on an earlier approver

Problem. Because ICIMS notifies approvers in sequence, the person who escalates (“I never got the approval email”) is often third or fourth in the chain. They have not received anything because the second approver has not acted. Vacation, a full inbox, or an approver who no longer holds the role all produce the same symptom.

Impact. The requisition ages while three people each assume it is with someone else. Time to fill takes the hit before a single candidate has applied.

Fix. The Approval tab shows exactly which approver the chain is waiting on. Contact that person directly. If they are out, replace them with their delegate on the Approval tab (your user group needs permission to edit approvers) and the chain resumes from that step. For visibility across the whole instance, build the Jobs Pending Approval By Current Approver search that ICIMS documents in its Community, save it, and pin it to the TA operations dashboard.

Cause 3: The approval email is in quarantine or spam

Problem. The Job Approval Request email was sent, but the approver’s mail gateway held it. ICIMS approval emails contain action links, and secure email gateways treat unfamiliar senders with action links as suspicious. This is the same family of issue we cover in ICIMS email notifications not working, but approvals are where it hurts most because a single missed message halts the whole chain.

Impact. Approvers who never see the request cannot act. New executives and newly created approver mailboxes are the most common victims because their mail rules have not been tuned yet.

Fix. Confirm the approver can still act from inside ICIMS: Jobs Pending My Approval on their dashboard does not depend on email at all. Then look at the approver’s status on the Approval tab: ICIMS marks an approver Unable to Contact when the email has not reached the recipient, and Notified when it was sent but not yet viewed. Ask IT to check the quarantine log for the approver’s mailbox and to allow mail from the address your instance sends approval requests from. ICIMS does not publish a sender allowlisting or SPF and DKIM procedure in its approval documentation, so treat this as an email gateway task on your side rather than an ICIMS setting. Once the mailbox is clear, click Resend on the Approval tab. And do not have anyone forward the email: ICIMS warns that the link and approval buttons let the recipient approve the job without logging in, so the message should not be forwarded or CCed.

Cause 4: A link scanner approved or declined it first

Problem. This one surprises people. The Approval tab shows an approver approved (or declined) at 6:02 a.m., but the approver swears they never opened the email. Microsoft documents that Safe Links in Defender for Office 365 rewrites URLs in email and that URLs without an established reputation are detonated asynchronously in the background. Other email security products behave similarly. When a scanner follows a one-click Approve or Decline link, the action reaches ICIMS as if a person clicked it. ICIMS customers have raised exactly this pattern for offer approval emails on the ICIMS Community, and it applies to requisition approvals the same way.

Impact. Requisitions get approved without review, or declined without a reason. Both are worse than a delay, because the audit trail now shows a decision nobody made.

Fix. Two options, and we recommend doing both. First, have IT add the ICIMS approval URLs to the Safe Links policy’s “Do not rewrite the following URLs” list (or the equivalent exclusion in your gateway) so the links are not followed during scanning. Second, train approvers to act from the approval screen inside ICIMS rather than from the email link. The email becomes a notification, and the decision is always a deliberate click behind a login.

Cause 5: The approver record is inactive or incomplete

Problem. Approvers are ICIMS user records. When someone leaves, changes role, or was created without an email address on their profile, the chain still routes to them. An inactive record cannot act. A record with a wrong or missing email never receives the request.

Impact. This is the classic org chart drift problem. The approval list was built around a finance director who left in March, and every requisition for that department has been waiting on a person who no longer works there.

Fix. Open the stalled approver’s user profile and check that the record is active and the email address is correct. Replace them on the Approval tab if needed. Then fix the source: every approval list that named the departed user needs updating, not just this requisition. We run this as a standing item in an ICIMS system audit, because stale approvers are one of the most common findings and one of the cheapest to fix.

Cause 6: A decline stopped the chain and nobody resumed it

Problem. An approver clicked Decline, perhaps with a comment like “change the title to Senior.” The approval stops. The Approval tab marks that approver as Rejected, and ICIMS automatically notifies the approval initiator, the job owner, and the job creator. Approvers later in the chain, who are emailed one at a time in list order, have not been reached yet. The recruiter makes the edit, saves, and moves on, without resuming the approval.

Impact. The requisition now reads as edited and complete, but it is not in approval and it is not approved. It sits until someone notices the job never posted.

Fix. Check the Approval tab for a Rejected status. If there is one, confirm the requested change was made, then click the Resume Approval button on the Job Profile Approval tab and click OK on any confirmation screens. (Reset Approval is a different button: ICIMS documents it for sending an already approved job back through the chain.) Coach approvers to use comments for minor edits and reserve Decline for genuine rejections. Where your process allows it, an approver can approve with a comment and the recruiter can make the edit after, which keeps the chain moving.

Cause 7: The approval screen shows no details or no buttons

Problem. The email arrived. The approver clicked the link. The approval screen loaded, but the job details were missing, or there were no Approve and Decline buttons to click. ICIMS documents the cause: incorrect HTML in the job description (or any other field that supports HTML content) prevents that field from displaying on the approval screen and prevents the Approve and Decline buttons from displaying. This is not a login group or permission problem. The approval link works without logging in, which is why ICIMS warns against forwarding it.

Impact. The approver assumes ICIMS is at fault, gives up, and the request ages. Support tickets pile up on the admin, and the usual first guess (permissions) sends everyone down the wrong path.

Fix. Open the job’s Job Description tab and clean up the HTML in the description and any other WYSIWYG field (content pasted from Word or a careers page is the usual culprit). Retest with the original approval link. If the buttons still do not display, submit a case to ICIMS Technical Support, which is exactly what the Community article recommends. Login groups still decide who can start an approval and see the Approval tab inside ICIMS, so keep well-structured ICIMS login groups on the same cleanup list, but they are not why an approval screen is blank.

The 10 minute diagnostic checklist

Run these in order. Each step rules out one or more of the causes above, and most stalled approvals are explained by step three.

How to keep approvals moving

Fixing one requisition is a ten minute job. Keeping ICIMS requisition approval not working off your ticket queue takes a few standing practices.

Review approval lists quarterly. Every departure and every reorg changes who should approve. Put approval list review on the same calendar as your login group and user cleanup.

Name a delegate for every approver. Executives travel. Finance closes the books. When the delegate is known in advance, replacing a stalled approver takes one minute instead of a week of chasing.

Make aging visible. A saved search for requisitions pending approval for more than three business days, reviewed every morning by TA operations, catches every cause in this post before a hiring manager has to escalate.

Decide where approvals happen. Email links are convenient. Approving inside ICIMS is auditable and immune to scanners. Pick one, document it, and train to it. The same discipline applies to offer approvals, which we cover in our ICIMS Offer Management setup guide.

Give the system an owner. Most approval stalls we see trace back to nobody owning the approval configuration after go-live. If your admin is stretched, ICIMS managed services covers approval list maintenance, notification health, and the morning aging review as part of a flat monthly engagement. Approval delays feed directly into time to fill, and the measured results on our ICIMS ROI page show what happens when that friction is removed.

Frequently asked questions