Automatic Candidate Pooling

The Automatic Candidate Pooling feature allows customers to add autopooling criteria to a requisition or requisition template to find candidates in the database who are available and qualified for a job. Managers can then access the autopool results with a single click.

The Automatic Candidate Pooling feature is typically used in decentralized hiring environments, for example in high volume retail and hourly hiring where managers may have to quickly identify candidates on their own without the assistance of recruiters.

For the Automatic Candidate Pooling feature to be available, the feature must be enabled by the system administrator. Users creating or defining autopooling criteria must be granted the required user type permissions, but no permission is required to access the autopool results.

Autopooling criteria can be added to a requisition via the Autopooling Criteria tab (if autopooling criteria were added to a requisition template, they will be inherited by the requisition). This is like a saved search that managers can use to find candidates who are both available and qualified. The following autopooling criteria may include any criteria from the Advanced Search, plus an additional set of basic criteria. For example:

  • Exclude candidates in selection process

  • Candidate's general profile language must match the requisition language

  • Exclude expired job submissions (selected by default)

  • Exclude rejected candidates - Within the last x days

  • Exclude hired candidates - Within the last x days (selected by default)

  • Candidate's place of residence - Within a radius of x kilometers/miles from the primary location of the job opening

  • Submissions must match the following organization-location-job field structure

As a best practice, when defining autopooling criteria:

  • Define autopooling criteria in requisition templates so criteria are inherited as requisitions are created.

  • Define the widest possible set of candidates from the database that would be both qualified and available. This way, no time is wasted on unqualified or unavailable candidates. For example:

    • Set Organizations, Locations and Job Fields to only include candidates from other jobs with overlapping skills and/or who applied to nearby locations. Filter by Organization and Location if appropriate (specific country, specific division, etc.).

    • Exclude candidates being considered in another requisition, who were recently hired, whose submissions have expired.

    • Use the parameter to limit results to candidates who live within X kilometers/miles of the primary location of the requisition.

Once autopooling criteria have been defined and enabled, the system will automatically generate a list of candidates matching the criteria anytime on demand. Only candidates who have applied on another requisition will be considered. This list of candidates is accessible in the requisition-specific candidate list or in the requisition file via the Autopooling icon. A maximum of 300 candidates can be displayed. The user then has the ability to:

  • View candidate files.

  • Match candidates to the current job opening (candidates are moved from the autopool results list to the requisition-specific candidate list, and they can then be moved along the workflow like any other candidate).

  • Match candidates to the current job opening and reject them in a single action (which will remove undesired candidates from continuing to appear in the candidate pool for this requisition; by default this option is disabled).

  • Filter the list of candidates using quick filters defined by the system administrator.

  • Sort the list of candidates by clicking a column heading.

When viewing a candidate file, the user may be able to view the other job applications that the candidate has submitted, depending on the permissions granted.

The user is able to match a candidate to the requisition via the autopooling feature even if the permission to match candidates to a requisition in general was not granted.

The user may also be able to match and reject candidates in one action if the permission was granted. When rejecting a candidate, the manager must specify the qualifiers (motives) and provide comments as required by the workflow.

If configured by the system administrator, the Automatic Candidate Pooling feature may also provide the ability to create optional repooling rules which automatically set a candidate's submission to an Inactive status after X days of inactivity. If the autopooling criteria for other jobs include the criteria to exclude candidates who are in a selection process, candidates who are automatically set to an inactive status will no longer be excluded and thus will be included in pool results.