Off Limits Employment History

The Off Limits logic checks the relation between an Account and a Contact by leveraging Employment History records. Employment History records associate an Account with a Candidate A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider., and related data is also added (job A job (vacancy, position, role) is an opening for which a customer's client needs a placement. title, start date and end date of the job etc).

Employment History records are created in the system in the following scenarios:

• When a CV is parsed in the Org
• When a Closing Report Fifth Stage of Job placement flow, a Candidate that reaches the Closing Report Placement stage has been assigned to a job. In Bullhorn Recruitment Cloud, a 'Closing Report' is a record that captures all the information related to the newly filled position (name of Candidate, position, salary, start date, which recruiter gets credit for the hire etc.) is created in the Org. Please note that in this scenario, the Employment History ‘Start Date’ is copied from the Closing Report’s ‘Start Date’ field and can be a value in the future. If that’s the case, even if a Closing Report record and an Employment History record are created for the assignment, the Employment Record will only be marked as ‘Current’ when the date specified in Start Date is reached.

Manually

The Off Limits calculation engine determines the current Company A Company is the organization where the contact works. This can also be called the Client. (Account) of a candidate by checking the value in the ‘Account’ field on the Employment History record associated to that candidate that meets the following criteria:

• ‘Current’ checkbox= True
• ‘Verified’ checkbox= True

For example, to determine which Contacts A contact (or client contact) is the person who the recruiter is working with at a Company. In Talent Rover a Contact can be either a Client Contact or a Candidate Contact. Both types of Contacts are stored in the same object (Contact). are to be Off Limits because they are employees of the Account ‘Acme’, the Off Limits engine will look for all Employment History records with the following data:

• ‘Account’ field=Acme
• ‘Current’ checkbox= True
• ‘Verified’ checkbox= True

‘Current’ Account checks in Off Limits logic

• As part of the Off Limits engine calculations/recalculations, Bullhorn Recruitment Cloud code looks for a Contact’s ‘Current’ Account in the following cases:
• Account policy: to determine which Contacts are to be Off Limits because they are current employees of the Account nominated in the policy
• Contact policy: no reason to check for current Account when a Contact policy is created
• Successful Candidate policy: for the SC The Support Contact (Account Contact, AC/SC, SC, AC) is the person who can contact Bullhorn Support at a particular company., current Account= Closing Report’s Account. Any change to the current Account results in the Candidate no longer being Off Limits, so this is checked as part of Off Limits calculations.
• ATS Stage policy: to determine if the Contact that the policy applies to should be excluded from becoming Off Limits based on the ‘internal Candidate rule’ (ie Internet Explorer is an out of date browser provided by Microsoft. Use Chrome!: the Candidate is a current employee of the open Job’s Account)
• Job Role A job (vacancy, position, role) is an opening for which a customer's client needs a placement. policy: currently no checks for current Account
• Job policy: to determine if the Contact/s that the policy applies to should be excluded from becoming Off Limits based on the ‘internal Candidate rule’ (ie: the Candidate/s named on the policy become off limits for all Jobs A job (vacancy, position, role) is an opening for which a customer's client needs a placement. except their Company jobs but including their Company's jobs named in the policy)
• Please note that in the current implementation, only in the case of Successful Candidate and Job policies the ‘current’ account checks cover (1) Account Hierarchy (2) Billing Account/Billing Account Hierarchy.

Employment History ‘Current’ checkbox

This is the logic used to identify the ‘current’ job leveraging Employment History:

• Exclude everything with a Start Date in the future
• Exclude everything where the End Date is in the past
• If the End Date is in the future - mark as Current
• If the End Date is blank - mark it as Current only if there is a Start Date
• If End Date is a string like ‘present’ - mark it as Current only if there is a Start Date

There can be more than one ‘Current’ Employment History record for the same Candidate

Employment History ‘Verified’ checkbox

‘Verified’ is unchecked by default and when the Employment History record is created as a result of parsing. Users can check it manually to validate that data has been reviewed and is correct (especially that the correct Account was selected)