We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.
For more information visit our privacy policy.Student Evaluation a. The President of the College or the President’s designee shall be responsible for administering the student evaluation process. b. Student evaluation packets for each class containing instruments and instructions shall be distributed to each faculty member by the first week of December during the fall semester and by the last week in April during the spring semester. c. It is expressly agreed that the faculty member being evaluated shall not be present in the classroom when the student evaluation is being administered and that all instruction to students with regard to such student evaluation shall be included in writing on the instrument, provided further that the designated unit or non-unit professional shall return the student evaluation directly to the President of the College or the President’s designee. The administering of the student evaluation shall be the responsibility of the President of the College or the President’s designee who shall determine who among unit or non-unit professionals shall administer such student evaluation. Student evaluations shall be valid only if signed by the student; provided, however, that faculty members shall not be entitled to the identity of the student responding unless such student evaluation is used as a basis for dismissal or other disciplinary action and such will be communicated to the students. d. The data from the student evaluation shall be tabulated and copies sent to the President of the College or the President’s designee. The raw data shall be retained by the College for a period of one (1) year during which time the faculty member shall have access thereto upon written request. e. The President of the College or the President’s designee shall review the tabulated data and shall forward a data summary to the faculty member by January 23 for the fall semester and by June 15 for the spring semester. f. The faculty member shall have seven (7) working days in which to respond to such data.
Program Evaluation The School District and the College will develop a plan for the evaluation of the Dual Credit program to be completed each year. The evaluation will include, but is not limited to, disaggregated attendance and retention rates, GPA of high-school-credit-only courses and college courses, satisfactory progress in college courses, state assessment results, SAT/ACT, as applicable, TSIA readiness by grade level, and adequate progress toward the college-readiness of the students in the program. The School District commits to collecting longitudinal data as specified by the College, and making data and performance outcomes available to the College upon request. HB 1638 and SACSCOC require the collection of data points to be longitudinally captured by the School District, in collaboration with the College, will include, at minimum: student enrollment, GPA, retention, persistence, completion, transfer and scholarships. School District will provide parent contact and demographic information to the College upon request for targeted marketing of degree completion or workforce development information to parents of Students. School District agrees to obtain valid FERPA releases drafted to support the supply of such data if deemed required by counsel to either School District or the College. The College conducts and reports regular and ongoing evaluations of the Dual Credit program effectiveness and uses the results for continuous improvement.
Student Evaluations Student evaluations shall be completed by the end of the 12th week of the fall semester.
Hot Weather Guidelines For the purposes of site based discussions regarding the need to plan and perform work during expected periods of hot weather, the following issues shall be considered in conjunction with proper consideration of Occupational Health and Safety issues.
HIV/AIDS Model Workplace Guidelines Grantee will: a. implement the System Agency’s policies based on the Human Immunodeficiency Virus/Acquired Immunodeficiency Syndrome (HIV/AIDS), AIDS Model Workplace Guidelines for Businesses at xxxx://xxx.xxxx.xxxxx.xx.xx/hivstd/policy/policies.shtm, State Agencies and State Grantees Policy No. 090.021. b. educate employees and clients concerning HIV and its related conditions, including AIDS, in accordance with the Texas. Health & Safety Code §§ 85.112-114.
Child Abuse Reporting Requirement Grantee will: a. comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse. b. develop, implement and enforce a written policy that includes at a minimum the System Agency’s Child Abuse Screening, Documenting, and Reporting Policy for Grantees/Providers and train all staff on reporting requirements. c. use the System Agency Child Abuse Reporting Form located at xxxxx://xxx.xxxx.xxxxx.xx.xx/Contact Us/report abuse.asp as required by the System Agency. d. retain reporting documentation on site and make it available for inspection by the System Agency.
Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)
General Guidelines Conduct yourself in a responsible manner at all times in the laboratory.
Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.
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/.