Administrative Concerns File. In the event that an administrator has a serious concern about a teacher, as defined in Article 8, the administrator may create an administrative concerns file.
Administrative Concerns File Sample Clauses
Related to Administrative Concerns File
Administrative information IV.2.2) Time limit for receipt of tenders or requests to participate Date
Administrative data Before the mobility, it is necessary to fill in page 1 with information on the student, the Sending and the Receiving Institutions. The three parties have to agree on this section to be completed before the mobility. On page 1, most of the information related to the student, Sending and Receiving Institutions will have to be encoded in the Mobility Tool+ (for Capacity Building projects, in the EACEA Mobility Tool).
SUBMISSION OF THE MONTHLY MI REPORT 4.1 The completed MI Report shall be completed electronically and returned to the Authority by uploading the electronic MI Report computer file to MISO in accordance with the instructions provided in MISO.
Administrative Controls The Contractor must have the following controls in place:
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.
Demographic, Classification and Wage Information XXXXXX agrees to coordinate the accumulation and distribution of demographic, classification and wage data, as specified in the Letter of Understanding dated December 14, 2011, to CUPE on behalf of Boards of Education. The data currently housed in the Employment Data and Analysis Systems (EDAS) will be the source of the requested information.
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:
CMI/RAI MDS Report Recognizing the mutual objective of quality resident care, the Employer agrees to meet through the Union Management Committee with the Union as soon as practicable after the receipt of the annual CMI/RAI MDS report. The Employer agrees to provide the Union with staffing levels, and staffing mix information; the impact of related payroll costs on staffing levels and a written notice of the CMI/RAI MDS report for the facility. The purpose of this meeting is to discuss the impact of the CMI/RAI MDS report on the staffing levels in the Home, quality resident care, and provide the Union with an opportunity to make representation in that regard. The parties shall meet as necessary to discuss other changes or workload issues. The parties may invite additional participants to attend the meeting to support constructive review and discussion.
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.
Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.
