Skip to content
Nextal Help

Job reasons

Where to find it
Configuration → ATS settings → Job → Reasons tab
Who can use it
Administrators with settings access
Direct URL
https://app.nextal.com/conf/admin/settings/ats/jobSettings

Job reasons are short codes or labels that explain why a job was opened or closed. When a recruiter closes a requisition, they can tag it with a reason — for example, “Hired inside application”, “Hired outside application”, “Not enough candidates”, “Budget restriction”. Those reasons flow into reporting, where hiring managers can see at a glance why positions were closed.

The Reasons tab. All reasons are managed in a single list.

How reasons are used

Reasons are available when a recruiter closes or updates a job. The selected reason is stored on the job record and appears in reporting, where teams can see how many jobs closed for each reason.

Common reasons include:

  • Hired inside application — the role was filled through the ATS pipeline
  • Hired outside application — the role was filled without using the ATS application flow
  • Not enough candidates — insufficient applicants to make a hire
  • Budget restriction — hiring was paused or cancelled for budget reasons

Adding a reason

  1. Go to Configuration → ATS settings → Job and open the Reasons tab.
  2. Click Add new value.
  3. Enter a label.
  4. Click Save.

Editing and deactivating

Click the edit action on any reason to rename it or toggle it Active/Inactive. Deactivate reasons that are no longer applicable — they will no longer appear as options in the job form, but historical jobs that used them retain the value for reporting.

There is no delete action for reasons — a reason can only be deactivated or reordered.

Tips

  • Keep reasons mutually exclusive. If two labels mean the same thing, consolidate to one — duplicates skew reporting counts.
  • Match your workforce-planning taxonomy. If your finance team tracks headcount under specific categories, align reason codes to those categories so ATS data and workforce-planning data stay in sync.
  • Add reasons before they are needed. A recruiter mid-closure who cannot find the right reason will pick the closest approximation — which pollutes analytics. Audit the list before each planning cycle.
  • Deactivate, do not delete. Deactivated reasons keep history intact while preventing future misuse.