Frequency and Distribution of Performance Evaluations Sample Clauses

Frequency and Distribution of Performance Evaluations. ‌ A. Employee performance evaluations shall be prepared for probationary employees at least every three (3) months during the probationary period. B. For regular full time employees, a performance evaluation shall be completed every year on the employee’s anniversary date (original date of hire into the employee’s current classification). In addition, a performance evaluation may be prepared at any time at the reasonable request of the employee or at the discretion of the employee’s supervisor, when it is deemed to be necessary and appropriate. C. Performance evaluations shall be prepared with a copy to the employee and the employee’s department file. The original shall be forwarded to the Human Resource Department for review and retention in the employee’s official personnel file.
Sample 1Sample 2
AutoNDA by SimpleDocs
Frequency and Distribution of Performance Evaluations. ‌ A. Employee performance evaluations shall be prepared for new hire probationary employees at least every six (6) months during the probationary period and at least every three (3) months for promoted probationary employees. Employees shall be evaluated during a formal training program by daily, weekly, and monthly evaluations until successful completion of the training program. B. For regular full-time employees, a performance evaluation shall be submitted within ten
Sample 1

Related to Frequency and Distribution of Performance Evaluations

  • Performance Evaluations The Contractor is subject to an annual performance evaluation to be conducted by NYCDOT pursuant to the PPB Rules.

  • Performance Evaluation The Department may conduct a performance evaluation of Contractor’s Services, including Contractor’s Subcontractors. Results of any evaluation may be made available to Contractor upon request.

  • Covenants of Performance Measurement No interference. Registry Operator shall not interfere with measurement Probes, including any form of preferential treatment of the requests for the monitored services. Registry Operator shall respond to the measurement tests described in this Specification as it would to any other request from an Internet user (for DNS and RDDS) or registrar (for EPP). ICANN testing registrar. Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. PUBLIC INTEREST COMMITMENTS Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.) Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-discrimination by establishing, publishing and adhering to clear registration policies.

  • Monitoring of Performance Vendor shall continuously monitor and record its performance to ensure that all of Vendor's responsibilities and obligations hereunder are being met and fulfilled. Citizens may conduct programmatic and other administrative contract monitoring during the term of this Agreement. The purpose of this monitoring is to ensure that all of Vendor's responsibilities and obligations are being met and fulfilled. Such monitoring may include on-site visits, report reviews, invoice reviews, compliance reviews, and a review of any other areas reasonably necessary. Vendor acknowledges and agrees that Citizens may also monitor and record Vendor Staff communications to the extent they occur within or are connected to any Citizens’ resource, such as electronic or telecommunications systems.

  • Appropriation of Performance Security (i) Upon occurrence of a Contractor’s Default, the Authority shall, without prejudice to its other rights and remedies hereunder or in law, be entitled to encash and appropriate the relevant amounts from the Performance Security as Damages for such Contractor’s Default. (ii) Upon such encashment and appropriation from the Performance Security, the Contractor shall, within 30 (thirty) days thereof, replenish, in case of partial appropriation, to its original level the Performance Security, and in case of appropriation of the entire Performance Security provide a fresh Performance Security, as the case may be, and the Contractor shall, within the time so granted, replenish or furnish fresh Performance Security as aforesaid failing which the Authority shall be entitled to terminate the Agreement in accordance with Article 23. Upon replenishment or furnishing of a fresh Performance Security, as the case may be, as aforesaid, the Contractor shall be entitled to an additional Cure Period of 30 (thirty) days for remedying the Contractor’s Default, and in the event of the Contractor not curing its default within such Cure Period, the Authority shall be entitled to encash and appropriate such Performance Security as Damages, and to terminate this Agreement in accordance with Article 23.

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