Specifications include, but are not limited to: File/Data Submission & Storage: CSI monitors school performance and compliance through various submissions from each of its 43 schools. Submissions typically take the form of data submitted within an email, documents, spreadsheets, and sometimes hyperlinks. The solution should have built in file storage capability for easy retrieval by CSI and school user (based on permissions). Project Management Workflow: CSI manages several projects that require materials to be submitted, reviewed by select CSI staff, feedback/follow up to the school contact, and final evaluation/confirmation of the submission. (Ex: see our annual Organizational Submissions and Audits process and our Charter School Renewal Application process.) The solution should provide project management functionality, including setting deadlines for school users and setting deadlines for CSI reviewers; email notifications to select CSI staff when data is submitted by a school, and email notifications to select school staff when feedback is provided or an evaluation is completed by CSI staff. Dashboard/Report: CSI regularly reports back to schools on school compliance/performance against expectations. The solution should provide real-time feedback via CSI and school-facing dashboards that summarize and report on information such as school tasks/upcoming deadlines, submitted documentation, school performance (compliance). Additionally, the solution should offer an ability to publish annual reports. (Ex: see the school performance report CSI annually publishes for each school, known as the CSI Annual Review of Schools (CARS) Report. Contact Management: The solution should have the ability for select CSI users (based on permissions) to add, update, and deactivate school-level contacts. Ideally, the solution would also have the ability for select school users (based on permissions) to also add, update, and deactivate school-level contacts at their assigned school. Additionally, given we have users that might work with multiple schools, a user should have the ability to be assigned to multiple roles or permissions for multiple schools. Communication: CSI regularly communicates with school and network staff and school board members. The solution should allow CSI users to communicate with users meeting a specified criteria (users identified as ‘school leaders’ at any school, for example). Ideally, such communication should be able to take place within the system and/or result in an email distribution list that can be extracted and used. Roles and Permissions: CSI does not send all communications through one school contact but through various school contacts. Each CSI department requires a school level staff member identified as the main point of contact. Therefore, each school typically has between 5-15 staff members identified as contacts for various responsibilities. The solution must allow CSI to control the permissions for each user role in order to ensure the control of data viewing and modification, and prevent all users from accessing all data. The solution must allow certain CSI staff control over roles and permissions that would allow multiple users within a school access to various components on the system(i.e. all users within one school shouldn’t see all submissions from that school.) Security: Some school submissions to CSI include student- and staff-level data and therefore system security is a high priority. The solution should have leading industry recognized security meeting FERPA and other privacy requirements to ensure protection of student and staff level data. Security specifications must be made available for CSI to share with school stakeholders. Training and Support: Training and troubleshooting support on use of the product should be available for CSI staff with administrative accounts. Live customer service support should be available to those staff members during normal business hours. A dedicated support representative would be preferred, but not required.