Quinyx WFM glossary
Absence is an umbrella term which covers all types of absences from work, either planned or unplanned. For example, if someone doesn't show up to work they are absent, but they are not on leave because it was not planned or notified in advance. Read more here.
Sometimes an absence is entered well into the future, before there's a shift for the period. In such cases, no salary-based shift is created during the absence This means the employee will not receive any leave compensation. To counteract this, we have support for the absence schedule which, simply explained, comprises weekly templates which can be selected in the absence dialogue to create salary-based replacement shifts during the absence. Read more here.
Difference types of absences, such as holiday, illness, parental leave, personal day, long-term illness, etc.
Absence type category
Absence types are grouped into different categories. Each category can have different combinations of properties e.g. salary-based, sickness (illness), permission, vacation (holiday), counts as scheduled hours etc.
An agreement can be viewed as a framework defining what rules regarding working hours are applicable to the individual, for example, whether the employee is paid on a monthly or an hourly basis, the employee's working time quota, calculation period, employment level, etc. Read more about agreement templates here.
A process or set of rules that is followed to generate a result such as a forecast or a schedule.
We're currently building REST APIs in Neo.
A shift assigned to a specific employee.
Approving worked hours. Read more here.
A unit other than a home unit. Read more here.
A public holiday when banks and many other businesses are closed for the day. Bank holidays vary by country.
A schedule template that is reusable. Read more here.
Borrowed / lent out
Refers to an employee that is borrowed from or lent out to a different unit.
Refers to a variable that is a calculation between two other variables, either standard or input data.
The dashboard provides you with status updates and visualizations for a selection of Quinyx measures and information. Read more here.
Daybreak means the time of the day that is considered by the system as the end of one day and the start of the next day. We have multiple daybreaks in Quinyx.
Sometimes known as a prediction. Refers to data in the future which is predicted either manually or using internal or external prediction methods. Read more here.
Refers to a method that has been setup to generate a future prediction for a business driver / variable. Read more here.
A Quinyx concept indicating the employee is not supposed to work this day. Read more here.
An employee's primary unit, i.e., the main place an employee works.
Data that is passed to Quinyx from an external system. Read more here.
Leave is any absence from work which is planned (i.e. vacation) or notified in advance (sick leave). It is either applied for by the employee or added to the schedule by the manager.
A leave application is sent from the employee to the manager.
An umbrella term for any user with system role above employee (i.e. login rights Neo).
The agreed base number of hours for an employee as defined in an agreement template. Read more here.
Time worked in addition to normal working hours.
You can use this if an employee doesn't need to punch in and out. Quinyx goes by the employee's schedule and automatically generates punching in/out times which match the scheduled shifts' start and end times.
Salary type rules
These allow you to define rules for extra salary types to be generated when an employee punches time on a specific shift. These rules can be defined on individual shifts in Schedule (but not in Base Schedule) as well as on shift type. Read more here.
An employee shared between two or more units. Read more here.
The schedule view allows you to view and manage shifts and employees. Read more here.
This typically refers to shift work, i.e., 3x8 hour shifts to cover each 24-hour period. Read more about shifts here.
Social cost is the percentage of both net cost and leave compensation combined. Read more here.
A category or type of shift. Examples include Early shift, Late Shift, Reception, etc. Read more about shift types here.
Data which Quinyx masters and is not data from external systems or a calculation between multiple variables. Read more here.
A specific task or action to be done during a shift. Typically scheduled at a specific time during a shift. Read more here.
A container of properties that you can connect to shift types, shifts, or punches. Read more here.
A unique Quinyx term. Time Trackers can be used for tracking vacation balances, time off in lieu or flextime, for example. Read more here.
Unsocial hours payments are an enhanced rate of pay (or supplement) used to reward and incentivize staff for working when others are not (e.g., night shifts, weekends, and bank holidays). Read more here.
An umbrella term for any user of the system, regardless of their system role.
An existing shift currently not assigned to a specific employee.
Refers to a specific KPI or data point related to the business's data. Either generated by Quinyx or by an external system and presented in Quinyx.
Quinyx' own interactive system built to function on a variety of hardware such as computers, tablet, smart devices, and point of sale systems. Read more here. Read more here.
X day shift/Y day shift
X and V Days - Applies to the Finnish workforce, primarily for the Hotel and Restaurant industries. Simply put, if an employee has worked at least 5 days in one week, the employee earns two days off - called X and V day.