Overview

This article includes frequently asked questions about processing child job applications.

  1. Why are some applications not appearing on my child job?
  2. How can I reserve an application for my child job so it can’t be moved onto a different job? 
  3. What is a pipeline boundary?
  4. What is an unveiled bucket?


1. Why are some applications not appearing on my child job?

  • Applications that match the categories of the child job will automatically appear in the bucket they are in on the pipeline
  • If an application is not appearing on the child job, it will be because the categories the candidate selected don’t match the categories that the child job is filtering on. Check the filtering on the job details page. You may need to adjust the category selections on your child job or talk to the candidate about selecting another category value if they want to be considered for a work type (as an example), but have not yet selected it.


2. How can I reserve an application for my child job so it can’t be moved onto a different job?

  • Applications that are still on the pipeline and could be actively being considered for other jobs, appear on the top line of the child job before the boundary, they are simply a suggested/matched talent pool
  • Applications that are reserved for a specific child job appear on the bottom line before the boundary
  • When using an action with a bucket move on an application on the top line (when viewing the application from list view), you will be presented with an option to select if the application should be considered for all pipeline jobs (default option and will keep the application on the top line and available for all child jobs) or only the child job that you are looking at. If you choose the second option, the application will move down onto the bottom line and will be reserved for the child job i.e. not available on the pipeline until you move them to a declined, withdrawn, rehire, or another terminal bucket in your process excluding "Hired".


3. What is a pipeline boundary?

  • The last bucket an application can be moved to on a pipeline. After this bucket, the application must be moved to the child job to be processed further
  • You can identify a boundary as the numbers in the bucket goes from two rows to one row
  • If you're viewing a pipeline role, actions that move an application past the boundary cannot be used
  • When viewing a child job, candidate applications prior to the boundary that match the profile categories of the child job will be represented as numbers on the top row. If you have moved an application down onto a child job prior to the boundary, you will see a number on the bottom row prior to the boundary. If applications are on the bottom row or past the pipeline boundary they will not be visible on the pipeline and cannot be considered for other child jobs until they have either been moved to a decline, withdrawn or rehire bucket.


4. What is an unveiled bucket?

  • If you don’t want candidates to know they have been put forward for a child job, the first (or first few) buckets past the boundary can be veiled (hidden) so the candidates can’t see they have been put forward for the role. 
  • If they move into an unveiled bucket, when they log into their candidate profile on the careers site, they will be able to see their application for the child job