RESIDENCE COMMUNITY STANDARDS GUIDELINES Sample Clauses

RESIDENCE COMMUNITY STANDARDS GUIDELINES. Residence is a diverse community of distinct individuals from many different backgrounds. In order to maintain a comfortable living environment and to protect individual rights within the residence, we have developed a set of guidelines outlining the types of behaviour that are acceptable and the types of behaviour that are unacceptable. Residents are expected to use reasonable foresight in ensuring their actions do not place the safety or well-­‐being of themselves or others at risk. Unacceptable behaviour is any behaviour which contravenes these guidelines. Ignorance, anger, alcohol or substance abuse will not be accepted as an excuse, reason, or rationale for failing to follow these standards. These behaviours can be identified and addressed by anyone in the residence community. Unacceptable behaviour may come to the University’s attention in a variety of ways, including observation by Residence staff, Security Services, Facilities Management staff, Food Services staff, or other students, or through photo, Internet, social media, mobile device, or video evidence. Anything posted online which comes to our attention (e.g., Facebook, YouTube, and Twitter) will be used as evidence in an investigation. Unacceptable behaviour within residence can be documented by: Residence Life Staff, Facilities Management or any other University staff including contractors who work in the residences, Security Services, and the Winnipeg Police Department. These regulations are an important part of this Contract and are meant to ensure that Community Standards are met. Violation of Residence Community Standards, or actions that contribute to or facilitate the violation of any of the following regulations, are a breach of this Contract and may result in disciplinary action. The University will not accept ignorance, anger, alcohol or substance use as an excuse, reason, or rationale for violating Residence Community Standards. The regulations fall into two classes:
Sample 1
AutoNDA by SimpleDocs

Related to RESIDENCE COMMUNITY STANDARDS GUIDELINES

  • Residence Community Living Standards The Residence Community Living Standards (“RCLS”) forms a part of this Agreement. It details the rights, responsibilities, and privileges of Residents as well as the residence conduct process. Each Resident is responsible for reading, understanding, and adhering to the terms outlined within the RCLS. The Manager and the Institution may amend the terms of the RCLS from time to time and may post the amendments in the Residence. Failure to abide by the RCLS may result in eviction from Residence and termination of this Agreement as per the violations and sanctions outlined in the RCLS, and as stated in section 8.01(d). The RCLS can be found online at: xxx.xxxxxxxxxxxxxxxxx.xx

  • Information Technology Accessibility Standards Any information technology related products or services purchased, used or maintained through this Grant must be compatible with the principles and goals contained in the Electronic and Information Technology Accessibility Standards adopted by the Architectural and Transportation Barriers Compliance Board under Section 508 of the federal Rehabilitation Act of 1973 (29 U.S.C. §794d), as amended. The federal Electronic and Information Technology Accessibility Standards can be found at: xxxx://xxx.xxxxxx-xxxxx.xxx/508.htm.

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

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

  • Management; Community Policies Owner may retain employees and management agents from time to time to manage the Property, and Owner’s agent may retain other employees or contractors. Resident, on behalf of himself or herself and his or her Guests, agrees to comply fully with all directions from Owner and its employees and agents, and the rules and regulations (including all amendments and additions thereto, except those that substantially modify the Resident’s bargain and to which Resident timely objects) as contained in this Agreement and the Community Policies of the Property. The Community Policies are available at xxxxx://xxxxxxxxxxxxxx.xxx/policies.pdf or on request from the management office and are considered part of this Agreement.

  • Health and Safety Standards Contractor shall abide by all health and safety standards set forth by the State of California and/or the County of Xxxxxx pursuant to the Injury and Illness Prevention Program. If applicable, Contractor must receive all health and safety information and training from County.

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

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

  • Standards Compliance DNS. 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”).

  • Standards for Network Elements 1.8.1 BellSouth shall comply with the requirements set forth in the technical references, as well as any performance or other requirements identified in this Agreement, to the extent that they are consistent with the greater of BellSouth’s actual performance or applicable industry standards.

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