TU Exception Request Tool (ERT)

Transcription

1 TU Exception Request Tool (ERT) AUGUST 28, 2007 MSN TRAINING UPDATE Target Audience All MSN Support Agents Introduction Over the past two years, we ve encountered several paycheck issues mostly due to late submission of OT Forms and Leave Request Forms. Digging deeper, we found out that several issues exist that contribute to this, ranging from forms not being available, to team managers not being available to approve, to forms being lost as they passed from one department to another. To give Agents more power to ensure accurate paychecks, the Application Development team has created the Exception Request Tool (ERT). This will allow agents to submit requests for Overtime and Leaves from their workstations directly to the workforce group and to check the status at their convenience. This tool will be used for all Leave requests and most OT exceptions. What s Important Exception Request Tool (ERT) is an online tool which allows its users to submit requests for Overtime and Leaves and check each request status at their convenience. The ERT can be accessed by going to the site Overtimes All Overtime requests for phone time should be processed through the ERT. The agent concerned should fill out the online form. Leaves The ERT has no connection to employees attendance standing. Medical certifications to excuse an absence, LWOP requests, Emergency Leave, Maternity Leave, and Force Majeur situations will still be handled by your supervisors and HR through existing processes. Planned leaves should still be filed 2 weeks in advance. PROCEDURE: 1. Get your username and password from your team manager. Your username will usually be your NCO Employee ID. 2. To get started, go to and sign in. 3. Select the type of request you d like to submit and fill out the form. There are 3 main actions that you can do: File an Overtime File a Leave View My Requests o Edit Request o Delete Request Sign in Screen: Enter your username and password. This should be given by your team manager.

2 The Home Page: You can file an OT, a leave or check the status of your leave request and the OT you filed. Overtime Button: The screenshot below shows a successfully filed overtime. Employees must properly fill out all required fields with accurate information. Date and time should be in Manila. Additionally, military time should be used. A calendar at the bottom part of the page is available for convenience. Employees must also add comments in the Comments field (for example, OT Approved by TM XYZ). Correct Reason must also be properly selected.

3 Leave Button: The screenshot below displays a properly filled out Leave request form. Fields to be populated are, the Queue (the line of business you support), the Date/s (the date/s when the leave is applied for), the Reason (reason for applying for a leave), and Comments (additional information about the leave applied for). A reference number will be displayed at the bottom of the page once a successful leave request or overtime exception has been filed: View My Requests Button: This takes you to a page where you can view the status of your requested Leave and the Overtime exceptions you have filed. Aside from viewing, you can also delete and edit your filed Leaves and Overtime Exceptions here. See screenshot below:

4 First, click on the reference number of the request that you want to either delete or edit. On the next page, the Edit and Delete buttons will be available for you select. Make the necessary changes to the form if you would like to edit it and then click the Submit Changes option. Simply click on Delete if you want to delete the whole request. NOTE: It is highly important that leaves and overtime exceptions be filed on the right time and with the most accurate information as this prevents inappropriate delays. For any questions or concerns regarding the Exception Request Tool (ERT), approach your team manager. When is it Effective Information in this Training Update should be disseminated to all target audiences immediately. References NCO Memorandum dated August 24, 2007 (from the Application Development Team) Code

5