COMMUNITY STANDARDS PROCESS Sample Clauses

COMMUNITY STANDARDS PROCESS. When a suspected incident occurs, an incident report is written by University staff, security personnel, and/or other witnesses. These reports are then reviewed by Campus Living Management to conduct an appropriate investigation. If the investigation requires further information, Campus Living Management will contact the individual(s) involved through e-mail to set up a meeting. The e-mail will request the individual to book a time to meet with Campus Living Management to discuss the details of the alleged incident. During the meeting, the individual will have the opportunity to give their own statement regarding the incident in question. The individual will receive incident related information and will be able to ask questions that may arise during the meeting. Failure to promptly respond to Campus Living may waive an individual’s right to provide testimony and/or their own version of events. This timeframe may be reduced during circumstances where the safety or wellbeing of an individual or the Residence community is at risk. As a result, all decisions and accompanying sanctions will be determined based solely on the information that Campus Living has previously received. Based on the information obtained during the student conduct meeting, Campus Living Management will decide whether or not the individual was responsible for the incident that violated Campus Living policies. If the individual is found responsible for violating Campus Living policies, they will receive documentation regarding the outcome of the student conduct meeting and any accompanying sanctions. All Residents have the right to appeal the decision in writing to Campus Living within 5 business days of receiving documentation. Students have the choice of pursuing one of two appeal processes; to the Director of Campus Living or the Local Appeals Committee (LAC). See Section 3.6Appeals Processfor more information.
AutoNDA by SimpleDocs

Related to COMMUNITY STANDARDS PROCESS

  • Quality Standards Each Party agrees that the nature and quality of its products and services supplied in connection with the other Party's Marks will conform to quality standards set by the other Party. Each Party agrees to supply the other Party, upon request, with a reasonable number of samples of any Materials publicly disseminated by such Party which utilize the other Party's Marks. Each Party will comply with all applicable laws, regulations, and customs and obtain any required government approvals pertaining to use of the other Party's marks.

  • Security Standards The Provider shall implement and maintain commercially reasonable security procedures and practices that otherwise meet or exceed industry standards designed to protect Student Data from unauthorized access, destruction, use, modification, or disclosure, including but not limited to the unauthorized acquisition of computerized data that compromises the security, confidentiality, or integrity of the Student Data (a "Security Breach"). For purposes of the DPA and this Exhibit G, "Security Breach" does not include the good faith acquisition of Student Data by an employee or agent of the Provider or LEA for a legitimate educational or administrative purpose of the Provider or LEA, so long as the Student Data is used solely for purposes permitted by SOPPA and other applicable law, and so long as the Student Data is restricted from further unauthorized disclosure.

  • OMB Standards Unless specified otherwise within this agreement, the Subrecipient shall procure all materials, property, or services in accordance with the requirements of 24 CFR 84.40−48.

  • Standards Compliance Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).

  • Safety Standards Performance of the Contract for all commodities or contractual services must comply with requirements of the Occupational Safety and Health Act and other applicable State of Florida and federal requirements.

  • Contractor Standards Contractor shall comply with Contractor Standards provisions codified in the SDMC. Contractor understands and agrees that violation of Contractor Standards may be considered a material breach of the Contract and may result in Contract termination, debarment, and other sanctions.

  • Enterprise Information Management Standards Grantee shall conform to HHS standards for data management as described by the policies of the HHS Office of Data, Analytics, and Performance. These include, but are not limited to, standards for documentation and communication of data models, metadata, and other data definition methods that are required by HHS for ongoing data governance, strategic portfolio analysis, interoperability planning, and valuation of HHS System data assets.

  • Compliance with Accessibility Standards All parties to this Agreement shall ensure that the plans for and the construction of all projects subject to this Agreement are in compliance with standards issued or approved by the Texas Department of Licensing and Regulation (TDLR) as meeting or consistent with minimum accessibility requirements of the Americans with Disabilities Act (P.L. 101-336) (ADA).

  • Human and Financial Resources to Implement Safeguards Requirements The Borrower shall make available necessary budgetary and human resources to fully implement the EMP and the RP.

  • Contract Work Hours and Safety Standards Act The following clauses apply to any Federal-aid construction contract in an amount in excess of $100,000 and subject to the overtime provisions of the Contract Work Hours and Safety Standards Act. These clauses shall be inserted in addition to the clauses required by 29 CFR 5.5(a) or 29 CFR 4.6. As used in this paragraph, the terms laborers and mechanics include watchmen and guards.

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