Clark County School District

Las Vegas, Nevada Grades 6-12 Digital Courseware

RFP 26024BDC

This RFP consists of 35 pages

Revision Date January 20, 2026 RFP due date: March 5, 2026 at 1:00 p.m.

Questions due by: February 5, 2026

Table of Contents

RFP 26024BDC

Part 1 Overview of the Project

Part 2 Interpretation

Part 3 Schedule and Submittal Instructions

Part 4 Proposal Presentation and Response Part 5 Scope of Work and Technical Requirements Part 6 Proposal Evaluation and Award Part 7 Special Conditions Part 8 General Conditions Part 9 Definitions and Acronyms Part 10 Agreement Part 11 Submittal Forms – Provided as separate documents at:

https://ccsd.bonfirehub.com Proposal Submittal Form

Public Disclosure Form

Customer Reference Form

Supplier Federal 2 CFR 200 Certifications Form

Supplier Application/Update Form

W-9

Supplier Contact List Designation Form

Amendment 1 Data Sharing Amendment

Attachment A to Amendment 1 - Schedule of Data

Attachment B to Amendment 1 - Certificate of Data Destruction Return

Appendix A – Pricing Sheet

Appendix B – Systems Matrix

Part 1: Overview of Project The Clark County School District, herein referred to as District, is accepting proposals for a comprehensive catalog of online courses to meet the credit recovery needs for students throughout the District in Grades 6–12.

Part 2: Interpretation

All questions about this Request for Proposal must be submitted electronically Euna Procurement (formerly named Bonfire)) at https://ccsd.bonfirehub.com on or before the required due date. Answers to the questions will be provided to all Plan Holders of the RFP in Euna Procurement in accordance with the RFP schedule of events.

Any deviation from this policy or attempt to directly contact or influence any Clark County School District employees or his/her representatives may result in disqualification of the Respondent. Any oral communications will be considered unofficial and non-binding on the District.

Part 3: Schedule and Submittal Instructions Schedule of Events:

3.1 Cancellation: The District reserves the right to cancel this RFP, in whole or in part, at any time during the solicitation process and prior to the RFP due date. This solicitation of proposals does not obligate the District to award a contract, nor does any liability attach to the District for the issuance of this document.

3.2 Collusion: Any evidence of agreement or collusion among Respondents and prospective Respondents acting to restrain freedom of competition by agreement to bid a fixed price or otherwise, shall render the proposals of such Respondents void.

3.3 Cooling Off Period: Per District Regulation 4371, the District may not enter into any contract, agreement, or consulting arrangement directly or indirectly, with any employee or former employee for a period of one year from the date of termination of employment other than as a member of a bargaining unit, or as a substitute employee, unless (1) there is full disclosure of the nature and extent of the employee’s or former employee’s interest in the matter, and (2) the contract is noticed and acted upon in an open session before the Board of School Trustees and approved by a majority of the Board of School Trustees.

The Respondent is hereby put on notice, by this condition, that it is his/her responsibility to disclose any relationship or affinity with a Board of School Trustee or an authorizing official in writing to the Director of Purchasing and Warehousing. Failure to properly disclose a relationship shall result in termination of the purchase contract and may jeopardize the Respondent’s future business dealings with the District.

3.4 Cost to Prepare and Submit Responses: All costs incurred in the preparation and submission of responses to the RFP shall be the responsibility of the Respondent.

3.5 Disclosure: Advance disclosures of any information to any particular Respondent, which gives that particular Respondent any advantage over any other interested Respondent in advance of the opening of the bids, made or permitted by a member of the District or an employee or representative thereof, shall void all proposals of that particular bid solicitation or request.

3.6 Interpretations, Corrections and/or Changes: Any interpretation(s), correction(s), or change(s) to this RFP will be made by Addenda. Interpretations, corrections or changes to this RFP made in any other manner will not be binding and Respondent(s) shall not rely upon such interpretations, corrections or changes. Addenda will be available in Euna Procurement (formerly named Bonfire) at https://ccsd.bonfirehub.com. It is the responsibility of the Respondent, prior to submitting a response to the RFP, to determine whether all addenda have been received and are included in the RFP response.

3.7 Issues/Complaints Regarding Requirements and Specifications: Any Plan Holder may submit complaints to the Buyer I prior to responding to the RFP if the Plan Holder believes the RFP unduly constrains competition or contains criteria that are inadequate or improper. The complaint must be on or prior to the deadline for submission of questions as indicated in the Schedule of Events. The District reserves the right to modify requirements, support specifications, or both. Should the Plan Holder complaint identify a justifiable change(s), an addendum detailing the modifications shall be released. Issues/complaints shall be submitted in writing and addressed to the appropriate Buyer I as defined on the front page of this document.

3.8 Late Proposals: Proposals received after the due date and time will not be considered and will be returned unopened to the sender. Regardless of the method used for delivery, Respondents shall be wholly responsible for the timely delivery of submitted proposals.

3.9 Preparation: Proposals should be prepared in such a way as to provide a straightforward, concise delineation of capacities to satisfy the requirements of the RFP. Expensive bindings, color displays, promotional materials, etc., are not necessary or desired. Emphasis should concentrate on conformance to the RFP instructions, responsiveness to RFP requirements, and on completeness and clarity of content. All proposals and accompanying documents become the property of the District.

3.10 Prompt Payment Discount: Prompt payment discount shall be defined as the amount of discount offered by the Respondent to the District if payment is made within a specified time frame. Terms of payment or cash discounts that require payment in less than 15 calendar days shall not be considered in the proposal evaluation.

3.11 Proposal Modification/Open Offer: Proposals may be modified or withdrawn prior to the established opening date by delivering written notice to the Director of Purchasing. Proposals which are not withdrawn before opening shall be considered firm for a minimum of 120 calendar days after the date of proposal opening in order to allow the District to evaluate and consider award. Respondents may submit proposals any time prior to opening date and time. Proposals must be received in their entirety by the deadline for submission and the opening date noted above.

Should a Respondent recommended for award withdraw their proposal, or if an awarded Respondent should breach the contract, that Respondent may be deemed non-responsible for a period of up to two (2) years.

3.12 Proposal Opening: Proposal information shall not become public record until after an award recommendation has been made and posted publicly on Euna Procurement at https://ccsd.bonfirehub.com prior to the Board of School Trustees voting on the recommendation.

3.13 Proprietary Information: The District is a public entity as defined by state law and as such, it is subject to the Nevada Public Records Law (Chapter 239 of the Nevada Revised Statutes). Under that law, all of the District’s records are public records (unless otherwise declared by law to be confidential), and are subject to inspection and copying by any person. Respondents are advised that after an award recommendation has been made by the Director of Purchasing, the complete content of all proposals will become a public record and nothing contained in the proposal will be deemed to be confidential. Respondents should not include any information in its proposal that is proprietary in nature or that they would not want to be released to the public. Proposals should contain sufficient information to be evaluated without reference to any proprietary information.

3.14 Proposal Delivery Instructions: The District strongly prefers electronic proposal submission via Euna Procurement at https://ccsd.bonfirehub.com. Proposals will be evaluated using Euna Procurement. Any hard copy (including flash drives) proposals received will be uploaded into Euna Procurement. The District accepts no responsibility or liability for either the Respondent’s errors and/or omissions in its proposal or errors committed by District staff in uploading submissions to Euna Procurement.

For hard copy proposals, submit proposals and mark boxes/envelopes plainly as indicated below:

4212 Eucalyptus Avenue, Bldg. #7

Las Vegas, NV 89121 For: Grades 6-12 Digital Courseware

3.15 Respondent’s Representation: Respondent is certifying that by submitting a proposal it has read and understands the proposal documents and that the proposal is made in accordance with all applicable laws.

3.16 Responsibility for Improper Identification or Submission: No responsibility will attach to the District, or any official or employee thereof, for the pre-opening of, post-opening of, or the failure to open a hard copy proposal not properly addressed and identified. Proposal delivery by facsimile and/or e-mail, IS NOT ALLOWED.

Part 4: Proposal Presentation and Response

4.0 General:

a. Faxed or emailed Responses are not acceptable.

b. Submitting a Response via Euna Procurement (formerly named Bonfire): The District strongly prefers electronic proposal submission via Euna Procurement. Respondent’s may register with Euna Procurement and access this RFP at https://ccsd.bonfirehub.com. Proposals will be evaluated using Euna Procurement. Any hard copy (including flash drives) proposals received will be uploaded into Euna Procurement by District staff. The District accepts no responsibility or liability for either the Respondent’s errors and/or omissions in its proposal or errors committed by District staff in uploading submissions to Euna Procurement.

c. Submitting a Hard Copy Response: If a Respondent chooses not to submit a Response via Euna Procurement, the Response must be mailed or delivered in a sealed envelope with the RFP number clearly displayed on the outside of the envelope.

1. Respondent must submit one original proposal response with cost information and a copy of the original response without cost information. Clearly label each response accordingly as “original” and “copy”. Label and index binders with appropriate section and sub-section numbers as referred to herein. Number each page individually and provide a table of contents.

and

2. Electronic Media Submission Requirements: Submit one flash drive complete with proposal response and cost information. Submit a second complete electronic version without cost information. Both electronic versions are to be submitted in either Microsoft Word or Adobe PDF. Submit as a single file as opposed to multiple files copied to the flash drive. Please affix a label to the flash drive which clearly identifies the name of the responding firm.

4.1 General Submittal Information: Respondent shall complete the following forms and submit the completed forms as part of its proposal. Forms are available as individual attachments in Euna Procurement.

a. Submittal Form

b. Disclosure Form

c. Customer References

d. Supplier Federal 2 CFR 200 Certifications Form

e. Supplier Application/Update Form

f. W-9

g. Supplier Contact List Designation Form

4.2 Respondent Experience and Personnel: The Respondent must include in the proposal a description of its company, including the organization’s experience and history with providing services to similar organizations. The Respondent shall provide the following information:

a. Historical background on individual or firm making proposal.

b. Description of the division of Respondent’s firm that provides these services.

c. List of individuals who will manage this project and his/her professional qualifications including resumes.

4.3 Contractor and Subcontractor Listing: Submit the names, addresses, phone numbers, and applicable licenses of all firms that will provide services in conjunction with the performance of this agreement.

4.4 Loss of Agreement and/or Inability to Fulfill Requirements: If the Respondent has had an agreement terminated, or has a pending termination, or a settlement to avoid litigation or termination for default during the past five years, all such incidents must be described. Termination for default is defined as notice to stop performance due to the Respondent’s non-performance or poor performance, and the issue was either: (a) not litigated; or (b) litigated and such litigation determined the Respondent to be in default.

a. The Respondent shall submit full details of all terminations for default, settlements, or pending terminations experienced in the past five years including the other party's name, address, and telephone number. The Respondent shall also present its position on the matter. The District shall evaluate the facts and, at its sole discretion, may reject the Respondent’s response if the facts discovered indicate that completion of an agreement resulting from this RFP may be jeopardized by selection of the Respondent.

b. If the Respondent has experienced no such settlement or terminations for default in the past five years, and it has no pending terminations, it must affirmatively declare so.

4.5 Scope of Work and Technical Response: Describe the approach to be taken including, but not limited to, how the project will be organized, number and types of staff involved.

4.6 Scheduling: Provide a schedule of events that clearly indicates the time sequence for tasks that are required to perform major components of the Work. Express these tasks in daily durations, example: survey activity five working days, etc.

4.7 Cost Appendix: Using Appendix A, Pricing Sheet, provide the following cost information and other as prompted therein:

a. Schedule of fees applicable to this effort to achieve the desired results. Itemize costs as related to significant events that are identified in the Respondent’s schedule and indicate a grand total. Costs must include all materials, supplies, etc., to accomplish Work.

b. If applicable, all equipage, parts, etc. are to be included F.O.B. destination and freight shall be included in the price of the item.

c. Rate chart applicable for potential expansion of Work.

d. Non-local firms are to indicate estimated travel expenses applicable to this effort.

e. Respondent must provide an hourly and/or daily rate for future services.

f. Define unit of measure, as applicable.

4.8 Verbal Presentation/Oral Interviews: The District reserves the right to require any or all Respondent(s) to either make a presentation that illustrates its abilities relative to this effort and/or attend an interview session to gauge its suitability to provide services for this project. If so requested, the Respondent(s) shall make its personnel available within ten calendar days of request. No cost allowance shall be permitted for this requirement.

4.9 Additional Information: Respondent(s) may provide additional information that is relevant to this proposal for consideration. Additional information response shall be limited to two pages or less.

Part 5: Scope of Work and Technical Requirements

5.1 General: The Clark County School District, herein referred to as District, is accepting proposals for a comprehensive catalog of online courses to meet the credit recovery needs for students throughout the District in Grades 6–12. The District shall support these courses using teachers within the District and is not requesting access to external teachers to support classes being offered.

5.2 District Background: The District has partnered with suppliers for credit recovery through an RFP since 2014. Historically, the District has procured credit recovery programs and services through a competitive RFP, with the selected Supplier’s program implemented districtwide for all middle and high schools. This RFP does not obligate the District to implement the awarded program on a districtwide basis and may allow use at the school, grade, or program level, as determined by the District. All purchases resulting from this RFP shall be processed through the District’s Purchasing Department.

5.3 Existing District Equipment and Systems: The following information is provided as an overview of the District’s current technology platform. The proposed solution shall be able to interface and work in harmony with the existing District infrastructure, which is defined below.

The District's technology infrastructure is built upon a Gigabit Ethernet (GbE) wide area network (WAN) serving 376 schools and all administrative offices. The District supports over 100,000 desktop and notebook computers, 350,000 Chromebooks, and nearly 700 file servers in various physical, virtual, or cloud-hosted configurations. File and print services are provided for all schools and administrative offices with Microsoft Windows servers utilizing Microsoft Active Directory for authentication. All classrooms support one-to-one connectivity over a combination of wired and Wi-Fi connections. The typical local area network (LAN) infrastructure is 100 Mbps Ethernet to the desktop and utilizes Wi-Fi versions 5 or 6. District schools and offices share 80 Gbps access to the Internet.

The District uses Google Workspace for Education as a collaborative environment. All staff and students have access to Google.

Students may be participating through a distance learning model and working from home using various internet connectivity options such as cable modems or hotspots.

5.4 Provision of a Complete and Operational System: The Supplier shall furnish a turn-key system that is completely operational within the District's existing infrastructure (see Section 5.3), whether or not all items and/or tasks reasonably necessary to make the system operational are specified by the District. No cost allowances shall be permitted for items not specified by the District.

5.5 System Functionality and Features: This section is an overview of the District’s requirements for the proposed system functionalities and features with specific requirements. The requirements are specified as “mandatory”, “highly desirable”, and “desirable”. By submitting a proposal, the Respondent is certifying that its proposed program meets all mandatory requirements. Any proposal that does not meet the functionalities labeled “mandatory” may be rejected and not considered for award. Appendix “B” provides requirements response instructions for each section.

Respondents shall complete the matrix in the order that it is presented. Additionally, several sub-sections of Part 5.5 require the Respondent to submit answers to specific queries. Whenever prompted, Respondent shall provide answers and submit them in the appropriate matching section in its proposal response.

5.5.1 General Requirements: Listed below is an overview of the District’s requirements for this section.

a. Respondent’s proposal shall offer a data-rich, user-friendly student view, teacher view, and administrative view. (Mandatory)

b. Scaffolding and lesson structure to support learners shall be pedagogically sound and lesson structure shall be consistent among and throughout courses and clearly defined. (Mandatory)

c. Courses shall offer a high level of interactivity and multi-modal learning opportunities, including a balance between text, video, and student manipulations/interactivities. (Mandatory)

d. Academic vocabulary for content area courses shall be explicitly provided to students. (Mandatory)

e. Assessment questions by course shall demonstrate a variety and appropriate percentage at each level of Depth of Knowledge. (Mandatory)

f. Content shall be aligned to the Nevada Academic Content Standards (NVACS) and learning objectives and based on the National Standards for Quality Online Learning from Quality Matters and the Virtual Learning Leadership Alliance, with a focus on issues of curriculum and assessment at the individual course level. (Mandatory)

g. Adjustments to course content shall be made within one calendar year (365 days) of changes to NVACS content standards. (Mandatory)

h. Respondent’s system shall be functional and operational based on the requirements stated herein on or prior to the District’s go-live date of July 1, 2026. Failure to do so shall result in penalties as stated in Part 7.5 of this RFP. (Mandatory)

5.5.2 System Integration Requirements: The Respondent’s system shall: be, consist of, support, and/or provide the following:

a. Capable of using the District standard username for students (prior to the “@” sign in student District email addresses) as the unique student identifiers. Currently, the District standard username for students consists of the student’s first name (up to 5 letters), followed by a period, followed by a unique identifying number. (Mandatory)

b. Support for Application Programming Interface (API): Infinite Campus (IC), the District’s Student Information System (SIS), supports API integration (IMS Global 1.2) via the Schools Interoperability Framework (SIF). A designated District resource with SIF expertise will handle all configurations and manage the SIF connections. (Desirable)

c. Roster student data through Clever, IMS Global 1.2 API, or Canvas (Mandatory)

d. Single sign-on with Clever is required. (Mandatory)

e. Support batch upload of users from .txt, .csv, .xls, and/or .xlsx file formats for rostering students at the district level. Batch uploading shall be available as needed. (Mandatory)

f. Able to integrate with Infinite Campus the District’s student information system and Canvas the District’s Learning Management System for rostering and grade passback. This includes the parent portal, which would include LDAP authentication using Microsoft Active Directory on Windows Server 2022. The Supplier, in conjunction with District staff, shall participate in a requirements gathering process to develop a solution with IC. Once there is an understanding of the request, IC shall provide the District with a proposed solution and estimate for the Work. If the District accepts the proposal the solution shall be scheduled and delivered. Specific components for integration shall include (1) account activation, (2) account provisioning, (3) course section creation, (4) student enrollment into sections, (5) grade/transcription of final grade, (6) completion of course information and (7) SSO for staff. (Mandatory)

5.5.3 General System Requirements: A comprehensive progress monitoring software shall meet the following technical requirements for digital or online components in order to be considered:

a. Program Software is accessible from any Internet-enabled device, including but not exclusive to personal computers, laptop computers, Chromebooks, tablets, Macs, iPads, and smartphones.

b. Curricular and Instructional Materials in digital or online formats support single sign-on (SSO) using the Security Assertion Markup Language (SAML) or Lightweight Directory Access Protocol (LDAP) against the District’s Active Directory (AD) environment for all students and staff.

c. Software supports rostering and single sign-on through a Clever integration.

d. Software is compatible with all modern Internet browsers, including but not exclusive to: Microsoft Edge, Internet Explorer, Chrome, and Safari, using default installation settings and without additional system hardware or software components required on end-users’ devices.

e. Respondents shall have the ability to configure a nightly (or more frequent) transfer of student data.

f. For digital or online assessments, the assessment system shall support automated transfer of student assessment data. If a direct connection is not possible, the system shall allow assessment data to be readily imported into Unify using at least one of the following file formats: CSV (comma-delimited) or TSV (tab-delimited). The Respondent shall provide the applicable technical requirements and recommended configurations necessary to fully implement and utilize the digital or online curricular and instructional materials, including but not exclusive to:

i. Hardware requirements;

ii. Operating system requirements;

iii. Software requirements;

iv. Browser-specific requirements;

v. Network and security requirements;

vi. Licensing models; or

vii. Copyright and fair use guidelines.

5.5.4 General Assessment Software Requirements: The Supplier’s system shall meet the following requirements:

a. Web-based, digital content to meet the credit recovery needs of students in Grades 6–12.

b. System capacity must support a minimum of 30,000 concurrent users with a response time of no more than three seconds.

c. Include an online platform for the administration of progress monitoring tools and data reporting.

d. The platform must allow teachers the ability to create progress monitoring schedules that measure a student’s growth and performance, yielding rate of improvement, and level of performance data/graphs.

e. The progress monitoring system must allow data sharing with school staff and District personnel.

f. The assessment system must be user friendly for students in Grades 6–12, and educators.

5.5.5 Gradebook Requirements: The Respondent’s system shall: be, consist of, support, and/or provide the following:

a. Export the gradebook to .csv, .xls, .pdf and/or .xlsx no less than three times per year based on the requirements for the State of Nevada. Specifically, this includes the following: (Mandatory)

i. The legal name of the student and student ID is included in the electronic learning management system.

ii. Evidence of the student’s progression in the course for each week that the student is enrolled in the course is documented in the electronic learning management system.

iii. The time that the student spends in the program is recorded by the electronic learning management system.

b. The gradebook data shall be archived by the Supplier on a rolling three-year basis. (Mandatory)

c. Provide teachers with the ability to allow assignments to be replaced, skipped, or deleted at the course level. (Desirable)

d. A global setting to override the ability for teachers to customize content, allowing assignments to be created, replaced, skipped, or deleted at the course level. (Highly Desirable)

e. Skip, delete, and add teacher/school/District-generated assignments within the course content and to the gradebook at the District level. (Mandatory)

f. Teachers shall be able to add assignments within the course content and to the gradebook, including the ability to add teacher-generated assignments. (Desirable)

g. Enter up to four-character alphanumeric fields into the gradebook, to match approved Nevada attendance codes. (Desirable)

h. Teachers, schools, and authorized District staff shall be able to set weights for assignments. (Highly Desirable)

i. Teachers, schools, and authorized District staff shall be able to set weights for assignment categories. (Highly Desirable)

j. Provide a cumulative student grade including only the assignments that have been attempted. (Highly Desirable)

k. Ability to apply minimum “F” by allowing no grade entered for attempted assignments to be less than fifty (50) percent. (Highly Desirable)

l. Provide the ability to flag assignments that have not been turned in as “Late” without a score/value attached. (Highly Desirable)

m. Provide standards-based reporting using a 4-1 scale at the elementary level and 4-0 scale at the secondary level. (Highly Desirable)

n. Provide the ability to have grades passback automatically into the District student information system. (Highly Desirable)

5.5.6 Global Administration Role & Permission Requirements: The Respondent’s system shall: be, consist of, support, and/or provide the following:

a. Support the functions and types of user roles for the following: (Highly Desirable)

i. Global Admin: able to view class, student, course, school, and District level data; make structural changes to course gradebooks; add content to courses; generate reports at a multi-school, school, teacher, course, or individual student level.

i. Teacher: able to view class and student level data, enter grades for assignments, make structural changes to the gradebook, add content to courses, generate reports at a course or individual student level.

ii. Teacher Assistant: able to view class and student level data, enter grades for assignments, and generate reports at a course or individual student level; however, is unable to make changes to courses or gradebook structure.

iii. Mentor/Observer: able to view class and student level data and generate reports at a course or individual student level; however, is unable to make changes to courses or the gradebook.

b. Customize user roles, allowing for specific rights to be given to individuals and/or user groups as required. (Desirable)

c. Set default rights for user roles at both school admin and global admin levels. (Highly Desirable)

d. Global admin and school admin users, within their login context, shall be able to access any course at a teacher view level, allowing view of the course content and interactions between the teacher and students. (Desirable)

e. Global admin, school admin, teacher, teacher assistant, and mentor/observer users, within their login context, shall be able to access any course at a student view level, allowing view of the course content and interactions between the student and the teacher. (Desirable)

f. Archive interactions between the student and teacher. (Mandatory)

5.5.7 Reporting Requirements: The Respondent’s system shall be, consist of, support, and/or provide the following:

. Generate reports of the following types with the data fields as listed: (Highly Desirable)

i. Class Attendance/Activity Report (whole class, teacher-level access and higher) given a selected date range to include the following:

a) Student name, student username/ID, course name, first access to course within date range, last access to course within date range, number of assignment submissions within date range, number of logins within date range, time online in course within date range, current grade in course, number of total page views within date range, page views by date within date range. (Respondent shall provide sample report)

ii. Student Attendance/Activity Report (single student, mentor-level access and higher) given a selected date range to include the following:

a) Student name, student username/ID, course name, first access to course within date range, last access to course within date range, number of assignment submissions within date range, number of logins within date range, time online in course within date range, current grade in course, number of total page views within date range, page views by date within date range. (Respondent shall provide sample report)

iii. Multi-Class Attendance/Activity Report (school admin-level access and higher) given a selected date range to include the following:

a) Student name, student username/ID, course name, first access to course within date range, last access to course within date range, number of assignment submissions within date range, number of logins within date range, time online in course within date range, current grade in course, number of total page views within date range, page views by date within date range. (Respondent shall provide sample report)

iv. Class Activity Report (school admin-level access and higher) given a selected date range to include the following:

a) Student name, student username/ID, course name, first access to course within date range, last access to course within date range, total number of page views within date range, page view access by area of course by class within date range, page view access by area of course by student within date range, number of student logins within date range, student time online within date range, current grade. (Respondent shall provide sample report)

v. Reports available within the interface, or upon request, to monitor the following teacher actions:

a) Content removal, course modification, grade modification, and notes. (Mandatory)

b) Aggregate/disaggregate reports at varying levels, including District, Region, multi-school, school, class, multi-teacher, teacher, multi-student, and student levels. (Highly Desirable)

c) Export reports in multiple file formats, including .csv, .xls, .xlsx, and .pdf. (Mandatory)

d) Archive and access course/student activity for the last five years. (Highly Desirable)

e) Maintain access to student activity for two years after contract expiration. (Mandatory)

f) Export student data to .csv format within six months after contract expiration. (Mandatory)

g) Record, maintain, and report attendance-related course data in support of the District’s compliance with Nevada pupil accounting requirements under NAC Chapter 387, and applicable distance education statutes and regulations, including NRS 388.820 through 388.874 and NAC 388.800 through 388.860. At a minimum, each course shall record the enrollment (EN) date, days of student activity, the number of days the student was active in the system prior to course completion, and the number of instructional hours required to complete course activities. (Mandatory)

h) Accurately record the login date and time of each student, each day, and in each course. (Mandatory)

i) Generate a historical login summary for each student for each course. (Highly Desirable)

j) Generate a historical activity summary of time spent for each student for each course. (Highly Desirable)

k) Generate a log of users that accessed the records for a particular student including time, date, and the changes made for audit trail purposes. (Highly Desirable)

5.5.8 Dashboard Data Requirements: The Respondent’s system shall: be, consist of, support, and/or provide the following:

a. Student login dashboard shall display current progress in course based on assignments completed and learning objectives mastered, for all courses in which the student is enrolled. (Mandatory)

b. Teacher login dashboard shall display current progress of students by course based on assignments completed and learning objectives mastered, for all courses which the teacher is assigned. (Mandatory)

c. Student login dashboard shall display current progress in course based on the assignments that should be completed and required learning objectives as calculated by the start date of the course, for all courses in which the student is enrolled. (Mandatory)

d. Teacher login dashboard shall display current progress of students in course based on the assignments that should be completed and required learning objectives as calculated by the start date of the course, for all courses which the teacher is assigned. (Mandatory)

e. Student login dashboard shall include alerts for upcoming assignments and overdue work. (Highly Desirable)

f. Teacher login dashboard shall include alerts for student work needing to be teacher-scored, for all courses for which the teacher is assigned. (Highly Desirable)

g. Ability for students to access a pacing guide that assists the learner in identifying when lessons and units are expected to be completed by date and adjusts to student or teacher choices in personalized blended learning. (Highly Desirable)

5.5.9 Course Design Requirements: The Respondent’s system shall be, consist of, support, and/or provide the following:

a. At a minimum, provide courses outlined in 5.10.1 and 5.10.2 for credit recovery in Grades 6–12). (Mandatory)

b. Ensure that all courses offered shall be on the Nevada Department of Education (NDOE) Distance Education Approved Course Provider List prior to execution of any contract. (Mandatory)

c. Ensure that all courses offered for grades 6-12 shall be semester courses (Mandatory) and quarter classes (Highly Desirable).

5.5.10 Alignment to Standards and Course Design Requirements: The Respondent’s system shall: be, consist of, support, and/or provide the following:

a. All content is aligned with the Nevada Academic Content Standards (Mandatory)

b. All content is aligned with District Regulation 6150: Instructional Materials including supplemental materials. (Mandatory)

c. Provide learning with a focus on equity, accessibility, and fair representation of all demographics of people without denigrating any particular group, belief, or culture. Professional learning provided under this agreement shall not lay blame nor villainize any groups regardless of their belief system, structure, historical viewpoint, race, ethnicity, national origin, culture, or reinforce stereotypes of any group or subgroup and shall not arise from political messaging. All professional learning must be research-based and contain citations or be verifiable upon request. (Mandatory)

d. Provide lessons and messaging that empowers all people and groups without discrimination while furthering equity, diversity, justice and fairness. The messaging must avoid fault-based language and shall not blame any group or subgroup for their messaging, culture, or politics. No blame or fault shall be assigned for any prior misconduct or historical event and no specific group or subgroup based on nationality, race, place of origin, or heritage may be disparaged. No political messaging will be allowed and all lessons must be based on verifiable facts, research, and data. (Mandatory)

e. Align course sequencing to District pacing or change course sequencing. (Mandatory)

f. Read vocabulary words to students. (Highly Desirable)

g. Translate words and/or pages. Please list languages available for translation. (Highly Desirable)

h. Convert text to speech for students. (Highly Desirable)

i. Ability for students to highlight and markup text, including the ability to maintain notes and highlights in a digital notebook feature for future reference. (Desirable)

j. Calculator functions within math, and other courses as appropriate, for student access. (Desirable)

k. Map references for student access in social studies courses. (Highly Desirable)

l. Extension activities at higher Depth of Knowledge. (Highly Desirable)

5.5.11 Assessment Requirements: The Respondent’s system shall: be, consist of, support, and/or provide the following:

a. Allow settings for mastery to be set globally at a District level by course by category. (e.g. allowing tests, quizzes, and teacher-scored activities to all be set at different mastery percentages.) (Mandatory)

b. Teachers shall not have the ability to override the system mastery level as set by the school. (Highly Desirable)

c. Allow default number of resets allowed on assessments to be preset at the District and the school level. (Highly Desirable)

d. Allow students to have the ability to repeat assignments and/or that teachers are able to assign additional practice at the same depth of knowledge when students do not meet mastery. (Desirable)

e. Provide the ability to make comments on student assessments at both the teacher and student level. (Highly Desirable)

f. Courses include embedded worksheets and/or study guides as study aides for students. (Highly Desirable)

g. Lock assessments for proctored testing. (Mandatory)

h. Allow answer keys to any worksheets or study aides to be included within the system and accessible at the teachers, school, and District levels. (Mandatory)

i. Embedded rubrics using a 4-1 scale at the elementary level and a 4-0 scale at the secondary level shall be included within the system and accessible at the teachers, school, and District levels for all teacher-scored assessments. (Highly Desirable)

j. For middle and high school content proposals (grades 6-12), credit recovery use is necessary (Mandatory):

i. System/courses shall possess the ability for unit pre-test and/or diagnostic test prior to beginning a unit. (Mandatory)

ii. System shall have the ability to create an individualized learning path for student, based on the level and areas of mastery in the diagnostic pre-test. (Mandatory)

5.5.12 Parent Access Requirements: The Respondent’s system shall: be, consist of, support, and/or provide the following:

a. Provide parent logins or the ability to receive reports to view student progress. (Highly Desirable)

b. Support integrated push data for parent logins, meaning the ability to load parent information and create logins through batch uploads or API. (Highly Desirable)

5.5.13 Calendaring Requirements: The Respondent’s system shall: be, consist of, support, and/or provide the following:

a. Set custom calendars for course completion for an entire class (e.g. semester-based courses) at a school and teacher level. (Mandatory)

b. Set custom calendars for course completion for individual students (e.g. rolling enrollment) at a school and teacher level. (Mandatory)

5.5.14 Messaging and Communication Requirements: The Respondent’s system shall: be, consist of, support, and/or provide the following:

a. In compliance with District Regulation 4100 on messaging and communication (Mandatory)

b. Support threaded discussions within system/courses. (Desirable)

c. Support live District teacher-student chat. (Desirable)

d. Allow teachers to use shared whiteboard with students within live chat. (Desirable)

e. Allow for teachers to instant message students within system. (Desirable)

f. Create groups for student collaboration. (Desirable)

g. Provide written feedback directly on assignments. (Highly Desirable)

h. Provide functionality within system/courses for all messaging and communication to be contained within the system without requiring use of an external email address. (Highly Desirable)

i. System shall not require an external email account for students, such that an outside teacher/student email is not required for student-teacher communication. (Highly Desirable)

j. Schools with established email accounts for students shall be able to use the existing email addresses, if an external email address is required within the system. (Desirable)

k. Allow users at the school and District levels to have the ability to view communications between students and teachers in order to monitor for instructional supervision. (Highly Desirable)

l. Allow users at the teacher, school, and District levels to have the ability to view communications between students, in order to monitor for appropriate behavior. (Highly Desirable)

m. Allow users at the teacher, school, and District levels to disable student to student communication, if the functionality exists within the system. (Highly Desirable)

5.5.15 End User Access Requirements:

a. Web-based, cloud-hosted

b. SSO via Microsoft Entra SSO / Clever

c. Grade passback into the student information system is highly preferred, but not required.

d. Role-based rostering

e. Mobile functionality

f. Must be compatible with the following operating systems (OS): Chrome OS, iOS (Apple), Windows 11 and above

5.6 License, Support and Hosting Requirements: The Supplier’s system shall consist of and/or provide the following:

a. Licensing: The Respondent shall submit its licensing option(s) to the District for review and evaluation (i.e. per student, per course, per semester; annual per student unlimited courses; per course, per subject, per grade site license; campus license, concurrent per seat users etc.). The Supplier’s system shall have the flexibility of allowing the District or Supplier to host the application in their respective data centers. Fees for years one, two, and three shall be fixed. Fees for years four through ten shall be fixed; however, such fees may include an increase to offset inflation, subject to District approval, based on the Consumer Price Index (CPI) for All Urban Consumers, U.S. City Average, All Items, Not Seasonally Adjusted. The District shall not consider fee submissions that are predicated on variations of volume. No fees shall be paid until successful implementation of the system.

i. If the Respondent’s licensing model is predicated on a per-seat and/or per-student basis the license fee shall be waived for any student/course enrollment which is abandoned within 28 calendar days after the initial registration/login.

ii. How does the Respondent define enrollment in terms of licensing fees?

b. Warranty: The warranty period shall begin when the District determines the system has been successfully implemented and is fully operational for its intended use. The warranty period shall be one (1) year from that date. The warranty start date shall be established by the District and documented through issuance of a District Purchase Order. During the warranty period, the Supplier shall provide all services necessary to keep the system fully operational and in compliance with the requirements of this RFP at no cost to the District, including, but not limited to, the following:

i. Routine bug patches and fixes within thirty (30) days of release.

ii. Updates and upgrades within thirty (30) days of release.

iii. Technical support to include telephone hotline service with guaranteed response time of no more than four (4) hours.

iv. On-site support for error resolution situations.

b. Maintenance/Support: A post-warranty itemized yearly cost for an ongoing maintenance agreement as defined in the warranty section. Respondent shall identify a fixed cost for a period of not less than nine years.

i. Respondent shall fully support and provide updates to the system offered for no less than ten years post “go live” acceptance by the District. Respondent shall submit a letter certifying compliance with this requirement.

ii. Software releases shall be scheduled systematically with appropriate copies, download options and documentation made available to the District.

iii. District-wide technical support for all users. The District requires support from 6:00 a.m. to 9:00 p.m. PST. Please describe toll-free phone, email, and live chat support for each specific user (student, teacher, and administrator) during these hours.

iv. The Respondent shall provide comprehensive and timely help desk support to District management, users, and/or technical/support staff. The Respondent shall describe its proposal for supporting users after they have received their initial training and begin to use the new system. Describe the support plan in detail. How many staff will be deployed at the Help Desk to support the District? What consulting resources will be provided to the District for end-user support during this time?

v. Describe how support calls are initiated, including who may place calls from the District, and the type of and number of Supplier support lines available.

vi. If available, describe the online work order tracking system for clients.

vii. Respondent shall describe what other support is available for problems.

c. Hosting: The Respondent’s system shall provide/support the following:

i. A comprehensive, customizable data retention program that the District can configure for each service or functional unit as needed.

ii. Data is maintained and stored in a secondary redundant remote secure location(s) in the continental United States.

iii. Dedicated hosting option (vs. multi-tenant).

iv. Comprehensive backup strategy with off-site disaster backup.

v. Processes to cleanse equipment and storage location(s) including backups and storage of data as part of asset lifecycle management as well as termination of contract.

vi. Backups are managed by the same Supplier the service is being purchased from.

vii. Data and derivatives are owned by the District; use or access to the data is also limited to the District. The Supplier shall not use the data for purposes other than to directly support this effort.

viii. A process and associated controls that insure separation of District data and security information or logs from its other service customers.

ix. Data is transmitted using Secured Sockets Layer protocol or other industry standard encryption technique which exceed standard.

x. Supplier has data loss prevention or content filtering mechanisms in place.

xi. Complete back-up shall be accomplished on a daily basis with a guarantee that no more than one full day of data shall be lost regardless of the cause.

5.7 Problem Resolution Requirements: The Supplier shall provide the following:

a. Notification: The District shall report problems and defects to the Supplier by telephone, fax or email from 6:00 a.m. to 6:00 p.m. PST. For Severity Level 1 errors or defects, the District shall, in addition to any notification by any other means, notify the Supplier by telephone. Supplier shall, without cost to the District (other than the fees for Maintenance Services), resolve all errors/issues as defined herein. Historical outage reports for at least the previous year including a record of outage and downtime for the platform shall be submitted. An expectation of total downtime and outages shall not exceed one percent (0.1%) of the total operational time for a calendar year.

b. Problem Classification: The District shall make an initial nonbinding classification of each problem or defect and will report such problem or defect to Supplier based on the criteria set…