Introduction
Renewals is the tool to help you keep track of which Candidates need new projects. It shows the Placements a Candidate has in a selected period and will show if the hours of these Placements add up to the expected hours per week for this Candidate. Save your favorite filters and show them in a Dashboard widget, to make sure you are always in time to start looking for new (or more) Placements for your Candidates.
General
The Renewals module is based on a simple principle: in the Candidate detail, you fill the field ‘hours per week’. Here you put the number or hours you would expect this Candidate to be on Placements. For example “32” if they have a contract for 32 hours per week. When you create a Placement for this Candidate, you fill the hours per week* they will work on that project, for example 24. The Renewals module will show you a list of Candidates that have Placements in a selected period. For each Candidate you will see a summary line with for o.a. the available hours per week and the nearest end date, calculated based on the combined Placements. For more details click to extend the ‘tree’ and see a line per Placement for this candidate, with more details per Placement. For our example Candidate we will now see ‘24/32’ at ‘hours on Placement’ and ‘8 hours’ at ‘available’.
Please note that Renewals is not a planning-tool; it will not show exact days that the candidate is or is not available, and will not take into account things like holidays.
*)In a Placement you can fill hours per day, week or month. When you use day or month, the Renewals module will calculate the hours per week. Keep in mind that when you use ‘per month’, Renewals will calculate hours per week as if each month will have 4.33 weeks. When you plan to use the Renewals module, you get the most precise results when also using ‘per week’ in the Placement.
Dependencies
Renewals is always used in combination with the Placements module.
Activation
Activation of the module is done by OTYS. If you have no acces yes, request via a support ticket. Key users can then activate the module for individual users with setting ‘Go! Renewals - Enable for user’ (SE2851) or add rules for this setting to ABAC. Please keep in mind you can only work with the Renewals module if you also use ‘Placements’.
Configuration
Not much configuration is needed for this module. For optimal use, please consider the following options:
Make changes to the list view in the module if needed. Please note the options here are intentionally limited; this module is to help you spot which Candidates need new Placements. All details about the Placement, Candidate and other related entities can be found in the relevant modules.
Setup (global) filters for easy acces to the most relevant information for your flow
Add one or more Renewals widgets you your Dashboards to have a quick list at hand without clicking to the module
The ‘hours per week’ field in the Candidate is a bit “hidden” in the default candidate view; in a sub-tab of the staffing-tab, in the ‘Salary/costs’ widget which has a lot of fields. You can include ‘Hours per week’ in an Interactions form, and put it in a widget on a more accessible tab. Ask our Support team for help with configuration of the interaction form if you don’t know your way around that feature.
In the Placements module, you can add an ‘hours per week’ column to the listview
In a Placements widget on your Dashboard, you can also add an ‘hours per week’ field to the view
Usage
Setup filters to create relevant overviews for your organisation. In the right panel, via ‘Add criterium’, you find an extended list of options to combine. Commonly used options are:
Placement period. This is the same filter as ‘Date range’ in the left panel.
Search mode (‘On placement’, ‘On or previously on placement’ and ‘Not on placement’)
‘Candidate owner’, ‘Customer Owner’ and ‘Placement owner’
‘My Favorite candidates’. Favorites is based on the star-icon in the header of the Candidate detail. Note: ‘Favorites’ are personal; you can not filter for the favorites of an other user.