INDIVIDUAL SERVICES AGREEMENT (“ISA”) This Agreement shall include an ISA developed for each student to whom CONTRACTOR is to provide special education and/or related services. An ISA shall only be issued for students enrolled with the approval of the LEA pursuant to Education Code section 56366 (a)(2)(A). An ISA may be effective for more than one contract year provided that there is a concurrent Master Contract in effect. In the event that this Master Contract expires or terminates, CONTRACTOR, shall continue to be bound to all of the terms and conditions of the most recent executed ISAs between CONTRACTOR and LEA for so long as CONTRACTOR is servicing authorized students. Any and all changes to a student’s educational placement/program provided under this Master Contract and/or an ISA shall be made solely on the basis of a revision to the student’s IEP or by written agreement between the parent and LEA. At any time during the term of this Master Contract, a student’s parent, CONTRACTOR, or XXX may request a review of a student’s IEP subject to all procedural safeguards required by law. Unless otherwise provided in this Master Contract, the CONTRACTOR shall provide all services specified in the IEP unless the CONTRACTOR and the LEA agree otherwise in the ISA. (California Education Code sections 56366(a) (5) and 3062(e)). In the event the CONTRACTOR is unable to provide a specific service at any time during the life of the ISA, the CONTRACTOR shall notify the LEA in writing within five (5) business days of the last date a service was provided. CONTRACTOR shall provide any and all subsequent compensatory service hours awarded to student as a result of lack of provision of services while student was served by the NPS/A. If a parent or LEA contests the termination of an ISA by initiating a due process proceeding with the OAH, CONTRACTOR shall abide by the “stay-put” requirement of state and federal law unless the parent agrees otherwise or an Interim Alternative Educational Setting is deemed lawful and appropriate by XXX or OAH consistent with Section 1415 (k)(1)(7) of Title 20 of the United States Code. CONTRACTOR shall adhere to all LEA requirements concerning changes in placement. Disagreements between XXX and CONTRACTOR concerning the formulation of an ISA or the Master Contract may be appealed to the County Superintendent of Schools of the County where the LEA is located, or the State Superintendent of Public Instruction pursuant to the provisions of California Education Code section 56366(c) (2).
Acceptable Use Policy Agreement I understand that I must use school IT systems in a responsible way, to ensure that there is no risk to my safety or to the safety and security of the IT systems and other users. For my own personal safety: • I understand that the school will monitor my use of the IT systems, email and other digital communications. • I will treat my username and password like my toothbrush – I will not share it, nor will I try to use any other person’s username and password. • I will be aware of “stranger danger”, when I am communicating on-line. • I will not disclose or share personal information about myself or others when on-line. • If I arrange to meet people off-line that I have communicated with on-line, I will do so in a public place and take an adult with me. • I will immediately report any unpleasant or inappropriate material or messages or anything that makes me feel uncomfortable when I see it on-line. I understand that everyone has equal rights to use technology as a resource and: • I understand that the school IT systems are primarily intended for educational use and that I will not use the systems for personal or recreational use unless I have permission to do so. • I will not try (unless I have permission) to make large downloads or uploads that might take up internet capacity and prevent other users from being able to carry out their work. • I will not use the school IT systems for on-line gaming, on-line gambling, internet shopping, file sharing, or video broadcasting (e.g. YouTube), unless I have permission of a member of staff to do so. I will act as I expect others to act toward me: • I will respect others’ work and property and will not access, copy, remove or otherwise alter any other user’s files, without the owner’s knowledge and permission. • I will be polite and responsible when I communicate with others, I will not use strong, aggressive or inappropriate language and I appreciate that others may have different opinions. • I will not take or distribute images of anyone without their permission. I recognise that the school has a responsibility to maintain the security and integrity of the technology it offers me and to ensure the smooth running of the school: • I will only use my personal hand held / external devices (mobile phones / USB devices etc) in school if I have permission. I understand that, if I do use my own devices in school, I will follow the rules set out in this agreement, in the same way as if I was using school equipment. • I understand the risks and will not try to upload, download or access any materials which are illegal or inappropriate or may cause harm or distress to others, nor will I try to use any programmes or software that might allow me to bypass the filtering / security systems in place to prevent access to such materials.
Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.
Client Agreement 2.1. The Company may unilaterally change any terms of this Client Agreement for any of the following reasons:
ARTICULATION AGREEMENT The original, signed document is kept on file in the Office of Transfer and Secondary School Partnerships. To obtain a copy of the original, signed document, contact the Office of Transfer and Secondary School Partnerships at .
