ATS Pro Development / Bug Reports

Issue:

Candidate activity records currently provide very limited information, making it difficult to establish exactly what happened to a candidate and which specific job or pipeline an activity relates to.

Examples:

We recently had a candidate, Nina Shah, removed from a job pipeline.

However, her activity records only show that she was removed, without identifying which job pipeline she was removed from.

Similarly, her profile shows that she was added to two jobs, but only displays the job titles, without the job reference numbers or locations.

This creates a significant problem when we have multiple vacancies with identical or very similar job titles across different locations.

For example, we may have 10+ Optometrist vacancies nationwide.

How are we supposed to identify which specific vacancy a candidate was added to or removed from?

Having to click on each job individually just to establish its reference and location is inefficient.

It also takes us away from the candidate's profile, potentially interrupting our current work and losing our place.

Expected improvement:

Candidate activity records should provide meaningful, detailed information, including:

• Exact job title.

• Job reference number.

• Job location.

• Specific pipeline involved.

• Clear details of the action performed, including whether a candidate was added, removed, moved or updated.

• Where applicable, the previous and new pipeline stages.

The objective:

Activity records should provide a clear and complete history of everything that happens to a candidate, without requiring recruiters to navigate through multiple screens to establish basic information.

At present, the activity history is too basic to be genuinely useful.

We need proper visibility and traceability, particularly when managing large numbers of candidates and vacancies with identical job titles across multiple locations.