Effective management of employee related processes
Every organisation needs processes to deal with employee management. For example, sickness, return to work, skill renewal etc. These processes have a sequence of tasks attached to them that have to be performed.
Crown Workflow allows your employee management processes to be set-up and configured within Crown Manager. A typical workflow process contains a set of rules which dictate events and resulting tasks which need to be performed by employees
- Promotes fairness & consistency in application of tasks & processes
- Ensures compliance with legislative requirements
- Alerts users to tasks and activities they need to complete
- Advises users on how to carry out tasks and activities
- Ability to create templates for business processes
- User configurable WORKFLOW rules for your specific business processes including:
- Sickness registrations
- Overtime authorisations
- Expiry of employee skills
- Return-to-work events
- Expiration of employee health exams
- Creation of new employees
- System can send messages:
- By MyMail, Email, or SMS
Events – may be initiated by the normal day-to-day work of a user. For example, if an employee is registered as sick on Crown WMS, Crown Workflow will trigger a sickness process.
Tasks – may be conditional, for instance, the completion of a task by a user may result in none, one or a number of other tasks being created for other users. A task is related to a user and has an actual completion date. The completion date allows management of and alerts users to their overdue tasks.
For example: Sickness Management process
- Crown Workflow alerts a user to perform the first task in the process, on completion of the first task Workflow triggers tasks for users as dictated by your rules.
- Depending on your rules, the Workflow process may contain just a few tasks, or in a complex process many tasks for many users.
- In this sickness example, when the employee returns to work Crown Workflow will trigger when to complete the sickness process.
- Depending on your rules, the completion of this sickness process may then trigger a further Workflow process to manage a “return to work”.
Workflow includes the following automatic event handling:
- Absence (e.g. Sickness).
- Return to Work.
- Skill Expiry.
- Employee Induction.
- Night Worker Health Check (WTR).
In addition to these, Workflow can be configured to manage manually-triggered processes that do not involve events as defined above.
Crown Workflow Configuration
Crown Workflow allows the user to configure a process template. The template is then used to control processes that are triggered to manage real events.
Template Maintenance enables the user to set a wide range of properties on a process, its tasks and the relation between tasks.
These properties include:
- The process name.
- Descriptions of the tasks.
- How real processes can be triggered.
- Who is responsible for each of the tasks.
- When tasks and the process should be completed by.
- If they can be completed automatically by other Crown Manager administration (e.g. maintenance of skill codes, changing of an Overtime Code).
Management of processes in response to real events is carried out via Crown Manager. Icons are provided on various enquires to highlight the employee the tasks are related to and the date on which tasks are due. The Home Page’s outstanding panel includes an entry highlighting the [worst-case] status of outstanding tasks for the user. All of these lead to the new web pages that facilitate management of active processes.
Crown Workflow allows the user to define a standard process as a sequence of tasks. At its simplest, a task is an instruction on what to do. In addition, notes can be added to give greater detail and advice. A task must be the responsibility of either an employee or a supervisor.
Tasks have other properties that the user can configure, for example:
Urgent Date (when the system may prompt the responsible person that the Target Date is approaching).
The user can configure the tasks in any sequence and can include conditional branching and loops. The user can save the process as a template. Templates can be “works-in-progress” or can be published. Only published templates can be used by ordinary users and employees. A template itself is not used directly by employees or supervisors.
Active Processes and Tasks
If a template is linked to an “event”, the system can automatically trigger an active process. “Events” include Return to Work, Absence, Skill Expiry.
Active processes can also be manually triggered based on the latest published template.
When an active process is triggered, the system uses the template to determine the first task(s) and the people responsible for the first task(s) will be alerted to their responsibility.
Full details of the active task and process can be viewed and managed via the MyTaskDetails web page.
- The task information on MyTasks and MyTaskDetails pages will provide enough detail to enable the responsible person to carry out the task. When they have done so, they can mark the task as complete.
- Alternatively, the task may be completed by performing some administrative function elsewhere in the system. For example, adding a skill linkage to an employee may complete a task in a skill expiry process.
- On completion of a task, the system will look to the template to determine what next task should be initiated. If no such task exists, the whole process will be marked as complete.