Skip to main content
All CollectionsCrelate Hire GuidesOnboarding
BETA - Inherited Requirements/Cascading
BETA - Inherited Requirements/Cascading

Onboarding can be complex with requirements being required by specific Clients, per Job, or at the overall Organizational level.

Amanda Krutz avatar
Written by Amanda Krutz
Updated over 3 weeks ago

Crelate’s Inherited Requirements allows for a matrix of Onboarding Checklist Items to be set and combined from each of these areas to ensure compliance.

Example:

  • When hiring employees your firm always requires a Handbook eSignature, I-9, Federal W-4, eVerify and State Tax form.

  • Your client Astral Extractions always requires employees on assignment sign an NDA (eSignature).

  • The Accountant role with Astral Extractions requires an Accounting form (eSignature) be signed during onboarding.

With Inherited Requirements, Crelate can combine these items so that the completed list of requirements would look like:

  • Handbook eSignature

  • I-9

  • Federal W-4

  • eVerify

  • State Tax Forms

  • NDA (eSignature)

  • Accounting Form (eSignature)

Job Specific Checklists

Navigate to Hire | Onboarding of a Job that has specific Requirements.

Opportunity Specific Checklist: Create an ad-hoc set of requirements use Create a template to set the appropriate items.

Additional Global Checklists To Include: Select an existing Global Onboarding Checklist to apply to this role.

Example – all RN Jobs, regardless of Client, require specific eSignature be completed. Creating an Onboarding Checklist with this requirement would allow you to apply and re-use this requirement (or set of requirements) to any jobs as needed.

Checklist Options: Disable Inheritance: Crelate generates the matrixed list of total Onboarding requirements by moving from more specific to more general. When an employee is onboarded for a specific Job, they first are given the Job specific requirements, than any requirements on that Job’s associated Company, then any requirements on that Company’s Parent Company and finally the Default Onboarding Checklist.

Disabling Inheritance precludes any Company or Default Onboarding requirements. This is defaulted to unselected.

Company Specific Checklists

Navigate to Hire | Onboarding of a Company that has specific Requirements.

Company Specific Checklist: Create an ad-hoc set of requirements use Create a template to set the appropriate items.

Additional Global Checklists To Include: Select an existing Global Onboarding Checklist to apply to this role.

Example – many Healthcare companies, require a specific eSignature be completed. Creating an Onboarding Checklist with this requirement would allow you to apply and re-use this requirement (or set of requirements) to any Companies as needed.

Checklist Options:

  • Disable Inheritance: Disabling Inheritance precludes any Parent Company or Default Onboarding requirements. This is defaulted to unselected. Job Specific requirements would still be included.

Default Onboarding Checklist:

General Onboarding Checklists can be created in Settings | Checklists |Onboarding Checklists. Onboarding is a specialty type of checklist allows for Employee Portal access and specialty Items.

One Onboarding Checklist can be set as the Default Onboarding Checklist to be used across onboardings where Inheritance is not disabled.


What's Next?

Did this answer your question?