Skip to main content

Why is Scheduling 2.0 not displaying jobs or applicants correctly?

Learn what to do if you encounter issues where jobs or applicants do not appear as expected

Written by Terence Cassidy

Why is Scheduling 2.0 not displaying jobs or applicants correctly?

Scheduling 2.0 in Access Recruitment CRM is a powerful tool for managing job schedules and applicant assignments. However, users may occasionally encounter issues where jobs or applicants do not appear as expected. Below are common causes and solutions to these problems.


Common Causes and Solutions

1. Missing Shifts for Jobs

Scheduling 2.0 requires jobs to have shifts assigned in order to display them in the scheduler. If a job does not have any shifts, it will not populate in the scheduling view.

Solution:

  • Add shifts to the job manually or by using a rota template. This ensures that the scheduler has data to display for the selected job.

2. Broad Search Terms for Applicants

When searching for applicants, very broad search criteria can result in Scheduling 2.0 displaying only a subset of matching applicants. This limitation is in place for performance reasons.

Solution:

  • Refine your search by adding additional filters, such as specific skills, locations, or availability. Narrowing the search criteria will help display the most relevant applicants for the position.


Best Practices for Using Scheduling 2.0

To ensure optimal performance and accurate results when using Scheduling 2.0, follow these best practices:

  1. Populate All Necessary Data: Ensure that all jobs have shifts assigned before attempting to schedule.

  2. Use Specific Filters: Avoid overly broad searches when looking for applicants. Instead, use precise filters to narrow down the results.

  3. Regularly Update Data: Keep job and applicant information up-to-date to avoid discrepancies in the scheduler.

By addressing these common issues and following best practices, you can maximize the efficiency and accuracy of Scheduling 2.0 in Access Recruitment CRM.

Did this answer your question?