Skip to main content

Setting and Tracking Job Close Reasons

Record and organize how your jobs are closed

Amogh Balikai avatar
Written by Amogh Balikai
Updated over a week ago

With Recruiterflow's Job Close Reasons feature, you can easily track why jobs are being closed. This helps you gain insights into hiring trends, identify common challenges, and improve your recruiting strategy.

Why Use Job Close Reasons?

Understanding why jobs close helps you:

  • Track hiring outcomes more effectively

  • Identify patterns or bottlenecks in your process

  • Share data-driven insights with clients and stakeholders

How to Set Up Job Close Reasons?

  1. Go to Settings.

  2. Navigate to the Job Close Reasons section. You will see an option called 'Ask for a reason while closing a job'. Simply toggle this option on and select one or more reasons from the list.

  3. Add your custom reasons (e.g., "Role Cancelled," "Budget Issues," "Position Filled Internally").

  4. All added reasons will appear in the list below, along with a count showing how many times each reason has been used.

Recording a Job Close Reason

You can record close reasons in three ways:

  1. From the Jobs Page
    Close a job directly from the Jobs page. You'll be prompted to select a close reason.


  2. When Making a Placement
    When hiring a candidate and choosing to close the job at the same time, you can select the close reason.


  3. Inside the Job Profile Page
    Close a job from the individual job profile page and select the appropriate reason.

Viewing Close Reasons

You can view all recorded close reasons on Settings > Job Settings > Job Close Reasons, you can see the list of reasons along with a count of how many times each has been used.

Tips for Using Close Reasons Effectively

  • Regularly review the counts in Settings to spot trends.

  • Keep your list of reasons up to date to match your current hiring workflows.

Next Steps

Learn more about managing your pipeline:

If you need any help setting this up, feel free to contact our support team :)

Did this answer your question?