Absence Management System (AMS) Project & System Introduction County of Los Angeles October 2011.

Absence Management System (AMS)Project & System Introduction

County of Los Angeles

October 2011

2

Our Time Together Today

About the AMS Project About the LeaveLink® Tool How LeaveLink® Works System Demo Questions/Discussion

3

How did we get here?

Since 2009, the County focused on improving program administration:• The number of open leaves has declined • DHR has developed and distributed policy guidelines and

conducted training by department• Monitoring has increased for leaves identified via manual

reports

In 2009, FMLA regulations changed, expanding the notification and tracking requirements and making administration more complex, as the CA regulations did not change. This represents a significant challenge to the County.

To build upon the success to date and improve the effectiveness of leave management, we will be implementing a tool and approach that can provide

better administration, tracking and reporting on leaves of absence throughout the County.

4

About the AMS Project

Decision Support Software

(LeaveLink®)Ensures

compliance & consistency,

reduces administrative

burden

PortalCurrent technology provides single

point of entry for managers, supervisors and employees; efficient interface for manager/department

POs is easily implemented

Program Stewardship

Establishes and maintains best

practice and policies and workflows.

Crafts system “rule sets” from

policies

5

About LeaveLink®

LeaveLink® is a decision support software system owned by Absentys

Absentys is a highly specialized consulting and technology company dedicated to helping employers achieve the benefits of Integrated Absence Management (IAM)

LeaveLink® is 100% web-deployed

Federal and state leave laws are pre-loaded

County policies will be entered (including union rules)

6

More About LeaveLink®

LeaveLink® features include:

Hierarchical user permissions (different types of users have different functionality)

Workflow for users with system- and personnel-generated task lists

Supports fulfillment requirements (e-mail and paper notifications)

A robust reporting portfolio

Integration with other systems (incoming and outgoing feeds)

How it will work…

The system is ‘pre-populated’ with basic information on all employees, and leave policies, to help establish eligibility for leaves.

Employees apply for leave by contacting their department (same process they use today).

The system user at the department uses LeaveLink® to pull up the employee and add information about the requested leave.

The system helps the user make eligibility determinations, and generates the appropriate paperwork (the leave packet).

The user enters information into LeaveLink® as leave events occur (for example, when the medical certification is received, when the employee returns to work)

As needed, system users can run reports that summarize leave information, at the individual level, or for groups of employees, or by leave type, or time period, etc.

7

The system is ‘pre-populated’ with basic information

8

Employees apply for leave by contacting their department just as they do today

9

When there is a need for leave…….

…employees might call…. come in person….

…or drop off paperwork…. or mail it in….

…or send an e-mail to get the leave started.

However it starts, it’s a trigger for action by the department to initiate the leave process

to comply with the law

The system user at the department uses LeaveLink to pull up the employee and add information about the requested leave

10

11

12

The system helps the user make eligibility determinations….

13

Sample: same leave, but approved (no prior leaves taken)

14

…. and generates the appropriate paperwork (the leave packet)

15

The user enters information into LeaveLink as leave events occur

16

Update screen when medical certification is received

17

Approval panel after review of

medical certification

18

Actions populate the audit

trail.

19

The audit report can be

generated summarizing

the entire case.

20

At return to work, the administrator documents fitness for duty, restrictions and

acceptance back to work.

21

Task screens help administrators keep track of activities related to leaves – some are system-generated based on workflow dates, others can be

created by the administrators and their leave management team.

As needed, system users can run reports

22

23

Reports of individual employee leaves

24

Reports that provide pattern analysis

25

Reports that summarize by multiple parameters,

including duration of leave.

26

Reports that summarize leave types

27

Reports that summarize leaves over time

28

Reports that provide detail per department, or work group

29

Questions?

https://qa.leavelink.com.

https://qa.leavelink.com

https://qa.leavelink.com.