Content of File Sample Clauses

Content of File. The personnel file shall remain confidential and shall contain all materials relevant to the member’s employment. The member shall have the right to review the contents of this file and to receive a copy of any documents contained therein. A member shall be entitled to have a representative of the Council accompany them during such a review. At least once every two (2) years a member shall have the right to indicate those documents and/or other materials in their file which they believe to be obsolete or otherwise inappropriate for retention. Those documents which do not involve charges resulting in discipline will be reviewed by an appropriate member of the administrative staff, and, if the administrative staff member agrees, the documents will be destroyed. A disagreement over the question of obsolescence or inappropriateness shall be immediately subject to the grievance procedure and shall be initiated at Level Two. All charges resulting in disciplinary action shall be considered a permanent part of the member’s personnel file and shall not be removed.
AutoNDA by SimpleDocs
Content of File. The personnel file shall be confidential and shall contain the materials relevant to the member’s employment. The member shall have the right to review the contents of this file and to receive a copy of any documents contained therein. A member shall be entitled to have a representative of the Council to accompany him/her during such review.
Content of File. Xxxxx Systems will not be responsible for the authorization, verification or accuracy of the information contained in a Transaction File. Member will reimburse Xxxxx Systems for any loss or expense incurred by Xxxxx Systems as a result of the Transaction File containing errors or inaccuracies or requiring changes not due to Xxxxx Systems’ sole error.

Related to Content of File

  • Database File The Servicer will provide the Successor Servicer with a magnetic tape (in a format reasonably acceptable to the Indenture Trustee and the Servicer) containing the database file for each Contract (i) as of the Initial Cutoff Date, (ii) the Subsequent Cutoff Date, (iii) thereafter, as of the last day of the preceding Due Period on each Determination Date prior to a Service Transfer and (iv) on and as of the Business Day before the actual commencement of servicing functions by the Successor Servicer following the occurrence of a Service Transfer.

  • Malicious Use of Orphan Glue Records Registry Operator shall take action to remove orphan glue records (as defined at xxxx://xxx.xxxxx.xxx/en/committees/security/sac048.pdf) when provided with evidence in written form that such records are present in connection with malicious conduct.

  • Certain Records Any records required to be maintained and preserved pursuant to the provisions of Rule 31a-1 and Rule 31a-2 promulgated under the 1940 Act which are prepared or maintained by the Adviser on behalf of the Trust are the property of the Trust and will be surrendered promptly to the Trust on request.

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • Use of FIIOC’s and FSC's Name The Trust shall not use the name of FIIOC and FSC in any Prospectus, sales literature or other material relating to the Trust or any Fund of the Trust in a manner not consented to by FIIOC and FSC prior to use; provided, however, that FIIOC and FSC shall approve all uses of its name which merely refer in accurate terms to its appointments, duties or fees hereunder or which are required by the Securities and Exchange Commission ("SEC" or “Commission”) or a state securities commission; and further, provided that in no event shall such approval be unreasonably withheld.

  • 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.

  • 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:

  • Data Security and Unauthorized Data Release The Requester and Approved Users, including the Requester’s IT Director, acknowledge NIH’s expectation that they have reviewed and agree to manage the requested controlled-access dataset(s) and any Data Derivatives of controlled-access datasets according to NIH’s expectations set forth in the current NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy and the Requester’s IT security requirements and policies. The Requester, including the Requester’s IT Director, agree that the Requester’s IT security requirements and policies are sufficient to protect the confidentiality and integrity of the NIH controlled-access data entrusted to the Requester. If approved by NIH to use cloud computing for the proposed research project, as outlined in the Research and Cloud Computing Use Statements of the Data Access Request, the Requester acknowledges that the IT Director has reviewed and understands the cloud computing guidelines in the NIH Security Best Practices for Controlled-Access Data Subject to the NIH GDS Policy. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification, the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.

  • AT WEBSITE XXX XXXXXXXXXXXXXXXX.XXX

  • Terms of Use The Clean Energy Council Limited (CEC) owns all intellectual property rights in the Solar PV Sale and Installation Agreement (Agreement).

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