Evaluation Process
A. The immediate supervisor will meet with an employee at the start of their review period to discuss performance expectations. The employee will receive copies of their performance expectations as well as notification of any modifications made during the review period. Employee work performance will be evaluated during probationary, trial service and transition review periods and at least annually thereafter. Notification will be given to a probationary or trial service employee whose work performance is determined to be unsatisfactory.
B. The supervisor will discuss the evaluation with the employee. The employee will have the opportunity to provide feedback on the evaluation. The discussion may include such topics as:
1. Reviewing the employee’s performance;
2. Identifying ways the employee may improve their performance;
3. Updating the employee’s position description, if necessary;
4. Identifying performance goals and expectations for the next appraisal period; and
5. Identifying employee training and development needs.
C. The performance evaluation process will include, but not be limited to, a written performance evaluation on forms used by the Employer, the employee’s signature acknowledging receipt of the forms, and any comments by the employee. A copy of the performance evaluation will be provided to the employee at the time of the review. A copy of the final performance evaluation, including any employee or reviewer comments, will be provided to the employee. The original performance evaluation forms, including the employee’s comments, will be maintained in the employee’s personnel file.
D. If an employee disagrees with their performance evaluation, the employee has the right to attach a rebuttal.
E. The performance evaluation process is subject to the grievance procedure in Article 30. The specific content of a performance evaluation is not subject to the grievance procedure.
F. Performance evaluations will not be used to initiate personnel actions such as transfer, promotion, or discipline.
Evaluation Procedure The procedural requirements set forth in this agreement which conform with and provide specificity to the statutory obligations established by Ohio Rev. Code § 3319.111 and § 3319.112.
Evaluation Procedures The following procedures for employee evaluation shall be utilized for the term of this Agreement:
1. Orientation materials related to evaluation procedures will be provided to all employees by the 10th school day.
2. Employees shall submit to their evaluator a complete listing of proposed objectives, and measurement activities related thereto, to be considered in the annual evaluation by the 25th school day.
3. The evaluator shall have completed by 30th school day annual objective setting conference with employee.
4. The evaluator shall by the 40th school day determine and shall provide the employee with a complete listing of actual objectives from those proposed by the evaluator and employee, and measurement activities from those proposed by the evaluator and employee, and measurement activities related thereto, that will be incorporated in the annual evaluation that the evaluator will prepare for the employee. The objectives and related measurement activities referred to herein shall be in accordance with the employee job description prescribed by the District. The District will make every attempt to have the number of objectives required to be uniform from site to site.
5. Within a reasonable time after the request, the evaluator shall be provided with a written progress report from the employee containing the latter's perception of the progress being made toward the achievement of the objectives prescribed in Item 3, above. During the course of the evaluation period, circumstances may change which may result in the modification of the original standards and objectives. These changes may be initiated by the supervisor or the employee. Agreement of both parties is required.
6. The evaluator, by the 145th school day, shall have conducted classroom observations in order to gather data on employee performance as the evaluator believes to be related to:
A. The actual objectives and measurement activities described in Item 3, above;
B. Other criteria for employee evaluation and appraisal that are established by the District Xxxxx Act Guidelines. At the discretion of the evaluator, tenured teachers may receive only one (1) formal instructional observation per year. Probationary teachers will receive two (2) formal instructional observations per year. Prior to conducting formal instructional observations regarding the teacher's duties related to the instructional objectives herein described, the teacher shall be notified of the observation prior to the beginning of the teacher's actual instructional day. Upon the request of the evaluatee or when, in the evaluator's judgment, additional instructional classroom observations are necessary, such observations may be conducted. Within a reasonable time, an employee shall be provided with a written statement regarding instructional observations that have been conducted. Such written statements shall contain a summary of the instructional activities observed, and any suggestions being made by the observer for possible improvement by the employee to include, but not be limited to, the following:
1) Specific directives for improvement
2) Assistance to implement such directives as
(a) Provisions of additional resources;
(b) Mandatory training programs designed to improve performance to be paid by the District. A final and written report of the achievement of objectives, and measurement information related thereto shall be submitted by the employee to the evaluator by the 140th school day.
7. The evaluator shall prepare a written District evaluation form of employee performance and transmit the evaluation to the employee. The employee may submit a written reaction or response to the evaluation and such response shall be attached to the evaluation and placed in the employee's permanent personnel file which shall be maintained in the District Office. Permanent employees shall be evaluated at least once every other year, and in no event later than 30 days before the last school day scheduled on the school calendar of the current school year. Probationary employees shall be evaluated at least once each year and in no event later than the 150th school day.
8. Employees who meet each of the following conditions shall be evaluated up to every five
Evaluation Cycle Goal Setting and Development of the Educator Plan
A) Every Educator has an Educator Plan that includes, but is not limited to, one goal related to the improvement of practice; one goal for the improvement of student learning. The Plan also outlines actions the Educator must take to attain the goals established in the Plan and benchmarks to assess progress. Goals may be developed by individual Educators, by the Evaluator, or by teams, departments, or groups of Educators who have the similar roles and/or responsibilities. See Sections 15-19 for more on Educator Plans.
B) To determine the goals to be included in the Educator Plan, the Evaluator reviews the goals the Educator has proposed in the Self-Assessment, using evidence of Educator performance and impact on student learning, growth and achievement based on the Educator’s self-assessment and other sources that Evaluator shares with the Educator. The process for determining the Educator’s impact on student learning, growth and achievement will be determined after ESE issues guidance on this matter. See #22, below.
C) Educator Plan Development Meetings shall be conducted as follows:
i) Educators in the same school may meet with the Evaluator in teams and/or individually at the end of the previous evaluation cycle or by October 15th of the next academic year to develop their Educator Plan. Educators shall not be expected to meet during the summer hiatus.
ii) For those Educators new to the school, the meeting with the Evaluator to establish the Educator Plan must occur by October 15th or within six weeks of the start of their assignment in that school
iii) The Evaluator shall meet individually with Educators with PTS and ratings of needs improvement or unsatisfactory to develop professional practice goal(s) that must address specific standards and indicators identified for improvement. In addition, the goals may address shared grade level or subject matter goals.
D) The Evaluator completes the Educator Plan by November 1st. The Educator shall sign the Educator Plan within 5 school days of its receipt and may include a written response. The Educator’s signature indicates that the Educator received the plan in a timely fashion. The signature does not indicate agreement or disagreement with its contents. The Evaluator retains final authority over the content of the Educator’s Plan.
Escalation Process If Customer believes in good faith that Customer has not received quality or timely assistance in response to a support request or that Customer urgently need to communicate important support related business issues to Service Provider’s management, Customer may escalate the support request by contacting Service Provider and requesting that the support request be escalated to work with Customer to develop an action plan.
Evaluation Report The state must provide a narrative summary of the evaluation design, status (including evaluation activities and findings to date), and plans for evaluation activities during the extension period. The narrative is to include, but not be limited to, describing the hypotheses being tested and any results available.
Evaluation Criteria 5.2.1. The responses will be evaluated based on the following: (edit evaluation criteria below as appropriate for your project)
PROGRESS EVALUATION Engineer shall, from time to time during the progress of the Engineering Services, confer with County at County’s election. Engineer shall prepare and present such information as may be pertinent and necessary, or as may be reasonably requested by County, in order for County to evaluate features of the Engineering Services. At the request of County or Engineer, conferences shall be provided at Engineer's office, the offices of County, or at other locations designated by County. When requested by County, such conferences shall also include evaluation of the Engineering Services. County may, from time to time, require Engineer to appear and provide information to the Williamson County Commissioners Court. Should County determine that the progress in Engineering Services does not satisfy an applicable Work Authorization or any Supplemental Work Authorization related thereto, then County shall review same with Engineer to determine corrective action required. Engineer shall promptly advise County in writing of events which have or may have a significant impact upon the progress of the Engineering Services, including but not limited to the following:
A. Problems, delays, adverse conditions which may materially affect the ability to meet the objectives of an applicable Work Authorization or any Supplemental Work Authorization related thereto, or preclude the attainment of Project Engineering Services units by established time periods; and such disclosure shall be accompanied by statement of actions taken or contemplated, and County assistance needed to resolve the situation, if any; and
B. Favorable developments or events which enable meeting goals sooner than anticipated in relation to an applicable Work Authorization’s or any Supplemental Work Authorization related thereto.
Induction Procedures a) The parties to this Agreement acknowledge that it is in the interests of the industry that all new employees and employers on a building project understand their obligations to this Agreement and are introduced to their jobs in a manner which will help them work safely and efficiently.
b) In order to achieve this it is recommended that, in conjunction with the Site Management, Job Xxxxxxx and Safety Supervisor/Safety Committee, new employees and new employers be given an explanation of the following: ⮚ The Rights and Obligations of this Agreement including its disputes/grievance resolution procedures; ⮚ The appropriate issue of work clothing and safety equipment as per this Agreement; ⮚ Safety Rules and Procedures including relevant legislation; ⮚ Superannuation entitlements; ⮚ Long Service Leave provisions; ⮚ Redundancy Pay entitlements; ⮚ Site Emergency procedures; ⮚ Award or Enterprise Agreement rates of pay; ⮚ Site-specific matters such as security, etc. procedures; ⮚ Rights, obligations and benefits of union membership.
c) The induction presentation and material shall have regard to the language skills of the employee/employer.
Negotiation Process (a) If either the Chief Executive Officer of ICANN (“CEO”) or the Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”). Notwithstanding the foregoing, neither the CEO nor the Chair may
(i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014.
(b) Following receipt of the Negotiation Notice by either the CEO or the Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”).
(c) If, following the conclusion of the Discussion Period, an agreement is reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator.
(d) If, following the conclusion of the Discussion Period, an agreement is not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-‐evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website.
(i) The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i).
(ii) The mediator shall conduct the mediation in accordance with the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute.
(iii) Each party shall bear its own costs in the mediation. The parties shall share equally the fees and expenses of the mediator.
(iv) If an agreement is reached during the mediation, ICANN shall post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator.
(v) If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below.
(e) If, following mediation, ICANN and the Working Group have not reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e).
(i) If an Arbitration Notice is sent, the mediator’s definition of issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person arbitrator panel. Each party may modify its Proposed Revisions before and after the Posting Period. The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2.
(ii) No dispute regarding the Proposed Revisions may be submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles 1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6, 7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11.
(iii) The mediator will brief the arbitrator panel regarding ICANN and the Working Group’s respective proposals relating to the Proposed Revisions.
(iv) No amendment to this Agreement relating to the Proposed Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors.
(v) In order for the arbitrator panel to approve either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder.
(f) With respect to an Approved Amendment relating to an amendment proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6.
(g) Notwithstanding anything in this Section 7.7 to the contrary, (a) if Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-‐hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).
