When configuring Advanced Analytics, which applicant statuses do NOT need to be mapped?

Comprehensive and Detailed In-Depth Explanation:

Mapping applicant statuses in Advanced Analytics (AA) tracks candidate pipeline progression for reporting. Let’s identify exceptions:

Option B (Invited to Apply): Correct. This pre-application status (e.g., an email invitation) isn’t part of the pipeline and thus doesn’t require mapping.

SAP Documentation Excerpt: From the Advanced Analytics Guide: “‘Invited to Apply’ does not need to be mapped in Advanced Analytics, as it represents a pre-application status outside the candidate pipeline.”

Reasoning: An “Invited to Apply” email from careers.bestrun.com isn’t tracked until the candidate applies, so it’s excluded from AA’s status set in Admin Center > Advanced Analytics Configuration.

Practical Example: For “Best Run,” an invite sent on February 1, 2025, isn’t mapped.

Option C (Forwarded): Correct. This internal recruiter action (e.g., forwarding a profile) isn’t a candidate-facing status.

SAP Documentation Excerpt: From the Advanced Analytics Guide: “‘Forwarded’ is an internal recruiter action and does not require mapping in Advanced Analytics, as it is not a candidate-facing pipeline status.”

Reasoning: Forwarding a candidate to a hiring manager in Recruiting Management doesn’t affect the candidate’s journey, so it’s omitted from AA mapping.

Practical Example: For “Best Run,” a “Forwarded” action on March 1, 2025, isn’t tracked.

Option A (Auto Disqualified): Incorrect. This pipeline endpoint (e.g., rejected by ATS) must be mapped for complete reporting.

Option D (Withdrawn by Candidate): Incorrect. This key status (e.g., candidate opts out) requires mapping to reflect pipeline drop-off.