Instantly see where a Candidate is in your procurement process.
Instantly seeing what stage of the recruiting process a Candidate is in helps you quickly identify steps to ensure the process stays on track. Your Beeline workflows can be configured with Candidate Statuses that define transitional onboarding stages. Candidate Statuses give users an at-a-glance summary of the progress and standing of a Candidate or a requisition.
In addition to Candidate Statuses, your workflows can include settings (called Allowed Actions) that limit and direct which actions users can take on a Candidate or a requisition.
TIP: Allowed Actions can be permitted or denied based on a Candidate Statuses.
Candidate Statuses and Allowed Actions help you to track and manage the different steps within your recruiting lifecycle. Plus, you can use Candidate Statuses to help control the Candidate’s experience by ensuring they move through your pipeline quickly.
Main Benefits
- Track and manage the different steps in your Candidate and request lifecycles.
- Ensure your users take the correct actions to smoothly move a Candidate or a request through your onboarding process.
- Set up alternate status with visibility controlled by user role.
- Trigger updates to your worker downloads so onboarding activities for Candidates are terminated, which keeps your automated integrations synchronized.
- Ensure your automated worker upload and download integrations operate smoothly.
Persona
Program Office users.
Action required
Creating Candidate Statuses and Allowed Actions to fit your organization’s onboarding workflows requires a Service Request ticket and Beeline Enterprise configuration.
Alternate statuses
You can also set up alternate statuses and control who see which status based on the user’s role.
For example, you organization might track more details related to approvals that you want to be visible only to your users. Assume you have a Candidate you’re ready to submit an offer to. But a last-minute bill rate increase was received that requires a new approval by your Financial Controller. You have an internal status of Pending Financial Controller Approval but your Supplier sees an Offer Pending Approval status.
Alternate status can be shown on these pages in your Enterprise VMS:
|
|
|
|
|
|
|
|
Available Allowed Actions
| Allowed Action | Description |
|---|---|
| Auto Reject Candidate Approval on Request Filled | Turning on this Allowed Action prevents users from approving a candidate and ensures that additional candidates associated with a request in the status you selected are automatically rejected when the request is filled. For example, your workflow has the Auto Reject Candidate Approval on Request Filled action set to Yes for requests in an Offer Accepted status. Users cannot inadvertently approve an additional candidate on requests in an Offer Accepted status. Including the Auto Reject Candidate Approval on Request Filled action on your workflows ensures that users correctly transition candidates when a request is filled. |
| Cancelled | Candidate was onboarded but then the assignment was cancelled and reopened. |
| Disqualified | Candidate was eliminated during the submittal process by any authorized user, such as the Hiring Manager, Program Office. |
| HM Disqualified | Candidate was qualified by the Program Office eliminated by the Hiring Manager. |
| Interview Activity | Candidate has an interview in progress, or an interview is being scheduled or pending approval. |
| Interview Cancelled | A scheduled interview was called off. |
| Interview Completed | Candidate's interview and evaluation is complete. |
| Interview Pending | Candidate's interview is upcoming. |
| Interview Rejected | Candidate's submitted interview was declined. |
| Interview Requested | An interview with the Candidate has been asked for. |
| Interview Required | An interview with the Candidate is compulsory. |
| Interview Scheduled | Candidate's interview has been planned. |
| MSP Disqualified | Candidate was eliminated during the submittal process by the Managed Service Provider. |
| Offer Accepted | Supplier consented to the submitted offer. Generally, an onboarding process must occur before an assignment is created. During the onboarding process, the candidate may still be disqualified. |
| Offer Pending Final Approval | An offer was proffered but is waiting for acceptance. |
| Offer Pending Supplier Acceptance | An offer was submitted to the Candidate and is waiting for the Supplier’s response. |
| Offer Rejected | Supplier declined the submitted offer to the Candidate. Additional offers can be made, if desired. |
| Offer Withdrawn | An offer was submitted but was retracted. |
| Onboarded | Candidate was onboarded, and an assignment was created. |
| Pending Background Checks | Supplier accepted an offer, but background checks aren’t completed. |
| Pending Confirmation | Candidate is Pending Final Confirmation from the Hiring Manager. This step can be turned off based on your configuration. |
| Pending Onboarding | Candidate is waiting for the Program Office to start onboarding. |
| Pending Onboarding Processing | Candidate is waiting for the Program Office to handle onboarding data. |
| Pending Submissions | Candidate proffered to a requisition. |
| Prevent Cancel Request | Turning on this Allowed Action prevents users from cancelling a request with candidates in the status you selected. For example, your workflow has the Prevent Cancel Request action set to Yes for requests in an Offer Accepted status. Users cannot inadvertently cancel requests in an Offer Accepted status. Including the Prevent Cancel Request action on your workflows ensures that users correctly transition candidates before a request is closed or cancelled. |
| Qualified | Candidate was reviewed and approved by the Program Office. |
| Qualified - Interview Activity | |
| Ready for Offer | Hiring Manager has chosen the Candidate and is ready for an offer. |
| Rejected | Candidate was eliminated outside the workflow because the Reject button was used. |
| Submitted | Indicates that the candidate has been submitted to the client for review. Usually this means that the MSP has been notified and they can now review and screen the candidate. |
| Withdrawn | The Candidate was pulled by the Supplier. Generally, because the Candidate is no longer available or was submitted inadvertently. |
Documentation release: Beeline Enterprise | Q1 2024