Appendix A – HRIS File Sample Clauses

Appendix A – HRIS File. Each Board shall provide to the Trustees of the ETFO ELHT directly, or provide authorization through its Insurance Carrier of Record to gather and provide to the Trustees, the following information within one (1) month of notification from the Trustees. The following information shall be provided in the formats agreed to by the Trustees of the ETFO ELHT and the employer representatives:
Sample 1Sample 2Sample 3See All (137)
AutoNDA by SimpleDocs
Appendix A – HRIS File. Each Board may choose to provide to the Trustees of the Education Sector ELHT directly, or provide authorization through its Insurance Carrier of Record to gather, the following information within one (1) month of notification from the Trustees. The following information shall be provided in the formats agreed to by the Trustees of the Education Sector ELHT and the employer representatives:
Sample 1Sample 2Sample 3See All (134)
Appendix A – HRIS File. Each Board may choose to provide to the Trustees of the OECTA ELHT directly, or provide authorization through its Insurance Carrier of Record to gather, the following information within one (1) month of notification from the Trustees. The following information shall be provided in the formats agreed to by the Trustees of the OECTA ELHT and the employer representatives:
Sample 1Sample 2Sample 3See All (105)
Appendix A – HRIS File. Each Board may choose to provide to the Trustees of the OSSTF ELHT directly, or provide authorization through its Insurance Carrier of Record to gather, the following information within one (1) month of notification from the Trustees. The following information shall be provided in the formats agreed to by the Trustees of the OSSTF ELHT and the employer representatives:
Sample 1Sample 2Sample 3See All (92)
Appendix A – HRIS File. Each Board shall provide to the Trustees of the ETFO ELHT directly, or provide authorization through its Insurance Carrier of Record to gather and provide to the Trustees, the following information within one
Sample 1Sample 2Sample 3See All (14)
Appendix A – HRIS File. Each Board may choose to provide to the Trustees of the ELHT directly, or provide authorization through its Insurance Carrier of Record, to gather, the following information within one (1) month of notification from the Trustees. The following information shall be provided in the formats agreed to by the Trustees of the ELHT and the employer representatives:
Sample 1Sample 2Sample 3See All (12)
Appendix A – HRIS File. Each Board may choose to provide to the Trustees of the Education Sector ELHT directly, or provide authorization through its Insurance Carrier of Record to gather, the following information within one
Sample 1Sample 2Sample 3See All (8)
AutoNDA by SimpleDocs
Appendix A – HRIS File. Each Board may choose to provide to the Trustees of the OSSTF ELHT directly, or provide authorization through its Insurance Carrier of Record to gather, the following information within one
Sample 1Sample 2Sample 3See All (4)
Appendix A – HRIS File. Each Board may choose to provide to the Trustees of the ETFO ELHT directly, or provide authorization through its Insurance Carrier of Record to gather, the following information within one (1) month of notification from the Trustees. The following information shall be provided in the formats agreed to by the Trustees of the ETFO ELHT and the employer representatives: complete and accurate enrolment files for all members, member spouses and eligible dependents, including: names; benefit classes; plan or billing division; location; identifier; date of hire; date of birth; gender; default coverage (single/couple/family). estimated return to work dates; benefit claims history as required by the Trustees; list of approved pre-authorizations and pre-determinations; list of approved claim exceptions; list of large amount claims based on the information requirements of the Trustees; list of all individuals currently covered for life benefits under the waiver premium provision; and member life benefit coverage information. APPENDIX II TO THE ETFO EDUCATION WORKERS MOS MEMORANDUM OF AGREEMENT BETWEEN The Council of Trustees’ Associations (hereinafter called ‘CTA’) AND The Elementary Teachers’ Federation of Ontario (hereinafter called the ‘ETFO’) AND The Crown Re: Bill 115 Litigation ETFO, the CTA and the Crown agree that the contents of the Memorandum of Settlement dated November 27, 2015 cannot be relied upon by the Crown in respect of any argument that the Charter challenge to Bill 115 is moot or by any party to this memorandum with respect to any argument of breach of section 2(d) of the Charter in that application. However, the contents of the Memorandum of Settlement dated November 27, 2015 may be referred to with respect to the issue of damages or remedy arising from any finding of a breach of the Charter, without prejudice to any argument on these issues which may be raised by any party‎. This clause shall be deemed not to be a precedent for any future agreements. APPENDIX III TO ETFO EDUCATION WORKERS MOS LETTER OF UNDERSTANDING BETWEEN The Council of Trustees’ Associations (hereinafter called ‘CTA’) AND The Elementary Teachers’ Federation of Ontario (hereinafter called ‘ETFO’) AND The Crown
Sample 1

Related to Appendix A – HRIS File

  • Employee File 27.01 Upon request to their immediate supervisor, employees are entitled to read, review and be provided with one (1) copy of any document in their human resources file at a mutually agreed time. The Senior Union Official, or designate, with the written authority of the employee, shall be entitled to review the employee's human resource file in the workplace, in order to facilitate the investigation of a grievance. The employee or the Senior Union Official, as the case may be, shall give the Employer seven (7) days' notice prior to examining the file. Employees shall have the right to rebut in writing any document, including but not limited to disciplinary notices and evaluations, in their human resources file. Such rebuttals, other than grievances, shall be attached to the document and placed in the personnel file.

  • Separate Grievance File All documents, communications and records dealing with the processing of a grievance shall be filed in a separate grievance file and shall not be kept in the personnel file of any of the participants.

  • Confidentiality and Safeguarding of University Records; Press Releases; Public Information Under this Agreement, Contractor may (1) create, (2) receive from or on behalf of University, or (3) have access to, records or record systems (collectively, University Records). However, it is expressly agreed that University will not provide to Contractor, and Contractor will never seek to access, any University Records that contain personally identifiable information regarding any individual that is not available to any requestor under the Texas Public Information Act, Chapter 552, Texas Government Code, including “directory information” of any student who has opted to prohibit the release of their “directory information” as that term is defined under the Family Educational Rights and Privacy Act, 20 USC §1232g (FERPA) and its implementing regulations. [Option (Include if University is a HIPAA Covered Entity and University Records are subject to HIPAA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Health Insurance Portability and Accountability Act and 45 CFR Part 160 and subparts A and E of Part 164 (collectively HIPAA) are addressed in Section 12.26.] Contractor represents, warrants, and agrees that it will: (1) hold University Records in strict confidence and will not use or disclose University Records except as (a) permitted or required by this Agreement, (b) required by Applicable Laws, or (c) otherwise authorized by University in writing; (2) safeguard University Records according to reasonable administrative, physical and technical standards (such as standards established by the National Institute of Standards and Technology and the Center for Internet Security [Option (Include if Section 12.39 related to Payment Card Industry Data Security Standards is not include in this Agreement.):, as well as the Payment Card Industry Data Security Standards]) that are no less rigorous than the standards by which Contractor protects its own confidential information; (3) continually monitor its operations and take any action necessary to assure that University Records are safeguarded and the confidentiality of University Records is maintained in accordance with all Applicable Laws and the terms of this Agreement; and (4) comply with University Rules regarding access to and use of University’s computer systems, including UTS 165 at xxxx://xxx.xxxxxxxx.xxx/board-of-regents/policy-library/policies/uts165-information-resources-use-and-security-policy. At the request of University, Contractor agrees to provide University with a written summary of the procedures Contractor uses to safeguard and maintain the confidentiality of University Records.]

  • APPENDIX F Appendix F, HBITS Processes and Forms, attached hereto, is hereby expressly made a part of this Contract as fully as if set forth at length herein. The Parties agree that the processes and forms set forth in this appendix may be updated as necessary, such as to facilitate the development of a web portal or other automated systems. OGS reserves the right to make changes to these processes and forms without seeking the prior written approval of the Department of Law or OSC, however, OGS agrees that any such changes shall comply with the terms and conditions of this Contract and not be material or substantive in nature. The Parties agree that detailed instructions for the completion of these forms shall be set forth in the “How to Use” document presented on the OGS web site or as part of the web portal or other automated system. Form 8, Monthly Report, shall be submitted electronically in Microsoft Excel 2007 or higher format, which will be separately provided by OGS.

  • Root-­‐zone Information Publication ICANN’s publication of root-­‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • Appendix H Appendix H, Contractor’s Insurance Requirements, attached hereto, is hereby expressly made a part of this Contract as fully as if set forth at length herein. The Contractor shall maintain in force at all times during the terms of the resultant Contract, policies of insurance pursuant to the requirements outlined in Appendix H – Contractor’s Insurance Requirements.

  • Account Ownership/Accurate Information You represent that you are the legal owner of the accounts and other financial information which may be accessed via Mobile Banking. You represent and agree that all information you provide to us in connection with Mobile Banking is accurate, current and complete, and that you have the right to provide such information to us for the purpose of operating the Mobile Banking service. You agree to not misrepresent your identity or your account information. You agree to keep your account information up to date and accurate.

  • Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!