Introducing custom fields; a great way segmenting users, whilst giving more flexibility for setup and analysis.
What can custom fields be used for?
- Benefit Calculations: provide core levels for all or certain employees that can be used in a calculation to set the cost accordingly
- Benefit Reporting: fancy doing more in-depth analysis at the end of a window? Use custom fields to see which departments, teams or offices have highest/lowest takeup
- Recognition Filters: Segment employees and filter their recognition feed to remove the noise. Particularly useful in large organisations that are made up of several smaller companies, or just many offices where employees only know their local colleagues, enabling users to see the recognitions that matter to them and their immediate colleagues.
We plan to integrate custom fields into other parts of the system over time. Comment below if there are any areas of the system you think custom fields would be particularly useful on.
Who can create the custom fields to begin with?
Any client of ours can use custom fields, however, the initial setup is done by YAW. Talk with your account manager if you wish to start using custom fields and they'll be happy to discuss how you could make the most of them within your existing setup. Depending on what you want to use them for, an Implementation Consultant may need to be drafted in to help out!
How many custom fields are available?
At present, there are 5 custom fields available. These are per company, rather than per employee.
What about the upkeep?
Custom Fields have been integrated with our data uploader, and our edit an individual area so you can keep your custom data up-to-date alongside your current joiner and leaver processes, without any extra effort by your administrator on our system.
You can update the information whenever required, however, please note depending on what custom fields are used for, the ramifications of the change could be immediate, or may require further action. Your account manager, or implementation consultant, will explain the requirements for upkeep when implementing the custom fields for you
Disclaimer:
Custom Fields must NOT be used to store Sensitive Personal Data including, but not limited to, racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic or biometric data, data concerning physical or mental health, data concerning sex life or sexual orientation, data concerning any committed or alleged offences. Please check the relevant regulations and contract terms if in doubt.
Comments
0 comments
Please sign in to leave a comment.