Explanation of terms
Reasons for entry are defined per onboarding and help to keep track of the recruitment reasons: Replacement for an existing position, a newly created position or vocational training. They enable detailed task planning per reason and improved analytics of onboarding processes. This allows you to recognise what onboarding is primarily used for and evaluate performance based on the link between tasks due and reasons for joining.
Configuration
In the menu on the page Reasons for Entry you can create a new reason via + Create .
See also Create and edit reasons for entry
Behaviour in the system
-
Permissions
The Permissions to create, edit and delete reasons for entry are included in the Onboarding - Administrator (Standard) role in the delivery. However, it can also be added to any other role. -
Association with task packages
In task packages, you can choose for which reason for entry this should be selected. If you have maintained different reasons for entry, you can put together a completely separate task package with different task templates for each reason, which will guide the onboardees through their own onboarding process. -
Standard reasons for entry when the system is delivered
- New Employment
- Return After Parental Leave
- Return After Long Term Sickness
- Takeover After Training/Study
- dir="ltr">Internship
- Vocational training
- Job Change
- Other
- Return from Sabbatical
- Company Change
- Job Location Change
- Branch Change
- Temporary Employment
-
Order of entry reasons
Once you can select reasons for entry from a list, they are sorted as shown on the page Reasons for Entry. It therefore makes sense to press and drag them so that frequently used reasons are at the top.
If you click on the icon next to the entry reason, hold it down and drag it to the desired position, you can change the order. -
Naming
The name of the reason for entry should be immediately understandable for all colleagues. -
Renaming of entry reasons
All reasons for entry can be renamed. However, as the internal name always remains the same, this ensures that existing connections with external tools always work properly. -
Solving entry reasons
Almost all reasons for entry can be deleted. Only the entry reason with a cogwheel symbol (similar to this ) cannot be deleted, only renamed, as a reason must remain in the system.
If deleted, the reason is removed from the list of entry reasons and can no longer be selected for new onboardings and as a preselection in the task packages. However, the reason is retained in existing onboardings until it is deleted. It will continue to be listed in reports. -
Report
The oData reporting interface is used to output the reasons for entry for each onboarding.
You can use this to identify, for example, what you mainly use onboarding for and analyse whether there is a connection between overdue tasks and the entry reasons and thus deduce which ones are going particularly well.
How our customers use this
Some of our customers fundamentally revise the reasons for entry in order to do justice to the company's own way of labelling recruitment types. They rename existing reasons accordingly, delete those provided by us in the standard system or add new ones. Special designations such as voluntary service, interim management and the like can also be realised.