Nevada Department of Education - request-for-information-30DOE-S4039 amendment 1.pdf
PDF 293 KB Posted
- Solicitation number
- 30DOE-S4039
- Issued by
- Nevada
About this file
This is a Request for Information (RFI) issued by the Nevada Department of Education through the Nevada State Purchasing Division for an Anonymous School Safety and Tip Management Platform to support the SafeVoice Nevada initiative. The RFI seeks qualified vendors capable of providing a modern, cloud-based platform enabling students, parents, school staff, mental health providers, and law enforcement agencies to securely report and manage anonymous safety concerns and threats. The platform must support unlimited administrative users, participating schools and Local Educational Agencies across Nevada, and unlimited tip submissions without performance degradation. The RFI specifies requirements for multi-channel tip intake via web browsers, iOS and Android mobile applications, and telephone; media attachments up to 100MB; two-way anonymous communication portals; customizable workflow statuses; automated duplicate detection; real-time dispatch notifications via email and SMS; comprehensive audit trails; and robust reporting capabilities with export options in PDF and CSV formats. The response deadline is October 19, 2026, at 2:00 PM PST, with questions due by October 9, 2026, at 4:00 PM PST and answers posted by October 15, 2026. This RFI will not result in a contract award; rather, aggregated information will be used for budget justification or to develop a subsequent solicitation.
Vendors must provide detailed cost models including one-time implementation and setup fees, recurring subscription or licensing fees, ongoing maintenance and support costs, and optional service rates. All responses must be submitted through nevadaepro.com with technical and cost information submitted separately and flagged as confidential. The platform must comply with Nevada Revised Statutes 603A and Nevada Administrative Code 242.110, align with CIS Critical Security Controls and NIST Special Publication 800-53 (Revision 5), and achieve a minimum GovRAMP Core certification status with higher sensitivity data requiring GovRAMP Authorized or Provisionally Authorized verification. Vendors must disclose their experience providing similar services to state or federal government entities, current active contracts, data residency and hosting locations, infrastructure controls, and any security incidents or data breaches within the past three years. All data, databases, logs, and backups must be hosted within the continental United States in compliance with the State Cloud Services Policy S.5.06.01.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Nevada Department of Education - request-for-information-30DOE-S4039.pdf | ||
| Quote Instructions.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Nevada State Purchasing Division Department of Administration 515 E Musser St Ste 300 Carson City, NV 89701 purchasing.nv.gov nevadaepro.com
Revised 2024-11 Page 1 of 5
Request for information
Date October 5, 2026
Solicitation number 30DOE-S4039
Single point of contact name Kaylene Hoyt
Single point of contact email ndecontracts@doe.nv.gov
Requesting agency Nevada Department of Education
Request for information title Anonymous School Safety and Tip Management Platform
Response deadline date and time October 19, 2026, 2:00 PM PST
This request for information (RFI) is available at nevadaepro.com as a bid solicitation.
Table of Contents
1. Applicable regulations governing procurement
2. Project overview
3. Scope of work
4. Cost
5. Timeline
6. Submission checklist https://purchasing.nv.gov/ https://nevadaepro.com/
Page 2 of 5 Request for information
1. APPLICABLE REGULATIONS GOVERNING PROCUREMENT
1.1. All applicable Nevada Revised Statutes (NRS) and Nevada Administrative Code (NAC) documentation can be found at: www.leg.state.nv.us/law1.cfm.
1.2. Vendors are advised to review Nevada’s ethical standards requirements, including but not limited to NRS 281A, NRS
333.800, and NAC 333.155.
1.3. This solicitation is a request for information (RFI) only. It is not a solicitation for bids or proposals. No contract award will result from this RFI. Aggregate information from this RFI will be analyzed and may be used as budget justification or to develop a subsequent solicitation.
1.4. All information received in response to this solicitation is considered confidential business information by the
Administrator of the Nevada State Purchasing Division of the Department of Administration. This solicitation will not lead to evaluation or award pursuant to NRS 333.335(7), so responses remain confidential.
1.5. GovRAMP NOTICE: Effective July 1, 2026, all new contracts containing a cloud component will include risk assessment requirements aligned with the GovRAMP program, which is based on NIST SP 800-53 (Revision 5). By submitting a response, vendors acknowledge they are responsible for reviewing and understanding the applicable GovRAMP requirements. Please refer to the GovRAMP link below for additional information and project-specific requirements. https://govramp.org/
2. PROJECT OVERVIEW
The Nevada Department of Education (NDE) is seeking information on qualified vendors who can provide a modern, cloud-based, anonymous tip acquisition and management platform to support the state’s SafeVoice Nevada initiative.
The platform will serve as the primary technology infrastructure for students, parents, school staff, mental health providers, and law enforcement agencies to securely report, route, and manage anonymous safety concerns and threats.
2.1. Requesting agency background
2.1.1. Pursuant to NRS 388.1323 the Nevada Department of Education’s (NDE) Office for a Safe and Respectful Learning
Environment is required to maintain a 24-hour, toll-free, statewide hotline and internet website by which any person can report a violation of the provisions of a safe and respectful learning environment. The NDE established the SafeVoice program to comply with the statutory requirement, which allows individuals to anonymously report any type of threat to the safety or well-being of students. These reports are received through the SafeVoice website, mobile application, or telephone line, which are then disseminated to schools through the SafeVoice support center that is operated by the Department of Public Safety’s Investigation Division. Although the Department of Public Safety operates the SafeVoice support center, NDE staff provide overall management of the SafeVoice program, and school administrators investigate reports. According to data collected by the Department of Public Safety, the SafeVoice program has received a total of 53,676 tips from January 2018 through December 2024. Additionally, the Department of Public Safety indicates that the range of tips varied from bullying, complaints on school staff, cyberbullying, suicide threats, depression and anxiety, harassment, assault, endangered children, and threats to school.
3. SCOPE OF WORK
3.1 The selected vendor will provide an end-to-end software platform, branded mobile applications, system implementation, continuous technical support, and comprehensive administrator training.
3.1.2 General & Security Requirements
• User Access & System Capacity: The platform must support an unlimited number of administrative users, participating schools/Local Educational Agencies (LEAs), recipient contacts, and tip submissions across the State of Nevada without performance degradation.
http://www.leg.state.nv.us/law1.cfm https://www.leg.state.nv.us/NRS/NRS-281A.html https://www.leg.state.nv.us/NRS/NRS-333.html#NRS333Sec800 https://www.leg.state.nv.us/NRS/NRS-333.html#NRS333Sec800 https://www.leg.state.nv.us/nac/nac-333.html#NAC333Sec155 https://www.leg.state.nv.us/NRS/NRS-333.html#NRS333Sec335
Page 3 of 5 Request for information
• Anonymity Protection: The platform must strictly protect the identity of tipsters from all system users, including law enforcement and administrative staff. Robust exception-handling workflows must exist solely for cases of verified system misuse, abuse, or imminent danger (e.g., first-person self-harm, false reporting).
• IP Address Retention: To support investigations of system abuse or life-safety emergencies, incoming tip IP addresses must be captured, securely stored, and retrievable within the system for a minimum of 72 hours.
• Branding: Web and mobile applications must feature custom branding for SafeVoice Nevada and support future branding and interface updates.
• Access Control: The platform must support granular, role-based security permissions for Multi-Disciplinary Teams (MDTs), including customizable "Do Not Disturb" timeframes and emergency override capabilities.
3.1.3 Functional & Technical Requirements
A. Tip Submission & Acquisition
• Multi-Channel Intake: Support secure tip intake via web browsers, iOS and Android mobile apps, and direct phone calls.
• Media Attachments: Enable tipsters to attach photos, audio, and video files (supporting file sizes up to 100MB per file).
• Manual Entry: Allow authorized staff and law enforcement personnel to manually log phone-in tips or walk-in reports into the system.
• Encryption & Protocols: Enforce HTTPS/TLS encryption for all data in transit and at rest, delivering immediate, automated receipt confirmations to tipsters.
• Two-Way Dialogue: Provide a secure, password-protected portal allowing tipsters to communicate anonymously with triage staff and law enforcement, as well as upload supplementary files post-submission.
B. Tip Management & Workflow
• Automated Logging: Apply immutable date/time stamps upon initial tip creation across all channels (web, app, manual entry).
• Triage & Stat using: Feature customizable tip status workflows (e.g., open, pending, triaged, closed), priority tagging, and administrative options to clear inadvertently flagged tags.
• Duplicate Detection: Automatically scan incoming tips for matching metadata (names, aliases, locations, addresses) and flag linked or duplicate entries.
• Integrated Trauma Alerts: Include an integrated module or API connection capability (similar to Handle with Care) allowing law enforcement to log traumatic student event alerts directly to schools.
C. Notifications & Distribution
• Real-Time Dispatch: Instantly dispatch urgent tip notifications via email and SMS to designated Multi-Disciplinary Team contacts across schools, law enforcement, and mental health providers.
• Broadcast Alerts: Provide the ability to send customized, non-tip operational notifications, updates, and emergency alerts to specific schools, districts, or contact groups.
• Receipt Verification: Track, confirm, and audit when notification recipients open tips and log final case dispositions.
D. Search, Audit, & Reporting
• Audit Trails: Maintain comprehensive, unchallengeable audit logs tracking all record views, edits, status updates, transfers, and user actions with associated User IDs and date/time stamps.
• Reporting Engine: Provide a robust reporting tool capable of filtering data by date range, category, location (city, county, school district), and disposition status.
• Export Options: Support scheduled and on-demand report exports in standard formats, including PDF and CSV.
3.1.3 Deliverables & Required Services
Page 4 of 5 Request for information
• Software Platform & Branded Mobile Apps: Complete deployment, hosting, and ongoing maintenance of iOS and Android mobile applications via official app stores, alongside a secure web application platform.
• Data Governance & Access: Ensure NDE/SafeVoice administrative staff retain full ownership and access to the system database for reporting, compliance, and advanced analytics.
• Training & System Support: Deliver live and recorded online training modules for administrative users, accompanied by ongoing technical support and SLA-backed maintenance throughout the contract term.
• Resource Repository: Provide a digital library hosting marketing materials, student curriculum/lessons, posters, and video content to support statewide awareness and adoption.
3.1.4 State of Nevada Security Requirements
• Regulatory Framework Alignment: The architecture, deployment, and ongoing operations must strictly comply with Nevada Revised Statutes (NRS) 603A and Nevada Administrative Code (NAC) 242.110. Additionally, security measures must align with the CIS Critical Security Controls, NIST Special Publication 800-53, and the state-mandated GovRAMP cybersecurity standards.
o Include whether your recommended solution can meet these security controls.
• Cloud & Infrastructure Governance: Cloud-based architecture and deployments must map directly to the State Cloud Services Policy S.5.06.01. The proposed solution must achieve a minimum of GovRAMP Core status, while higher sensitivity data requires GovRAMP Authorized or Provisionally Authorized verification.
o Is your recommended solution able to meet the GovRAMP compliance?
• Please list any state or federal government entities for which you have provided similar services, including details on all current active contracts.
o Name of the agency/system o Scope of services provided o Current active contract status and performance period
• Please provide technical specifications for your proposed solution, including:
o Hosting Platform & Architecture: Identify the underlying platform and architecture (e.g., cloud-native, SaaS, self-hosted, AWS, Azure, on-premises).
o Data Residency & Storage: Specify the exact geographic locations (e.g., Continental US, Canada, UK, or other regions) where all collected data, active databases, logs, and system backups are hosted.
o Infrastructure Controls: Describe any regional failover locations or sub-processors involved in hosting customer data.
• Please disclose whether your organization or any associated cloud environments have experienced a security incident, data breach, or unauthorized access within the last three (3) years. If yes, please provide:
o The date and nature of the incident o The scope of data or systems impacted o Remediation steps taken and measures implemented to prevent recurrence
4. COST
4.1. Please provide a detailed cost model for the proposed services, including an itemized breakdown of:
• Implementation & Setup Fees: One-time onboarding, configuration, migration, and training costs.
• Recurring Fees: Subscription, licensing, or hosting fees (e.g., annual, monthly, or per-user rates).
• Ongoing Maintenance & Support: Tiered support options, SLA levels, or unexpected maintenance fees.
• Optional Services: Rates for custom enhancements, specialized training, or professional services.
5. TIMELINE
5.1. All questions shall be submitted using the bid Q&A feature in nevadaepro.com by the deadline below.
5.2. The following represents the proposed timeline for this project.
Page 5 of 5 Request for information
5.2.1. All times stated are Pacific Time (PT).
5.2.2. These dates represent a tentative schedule of events.
5.2.3. The State reserves the right to modify these dates at any time.
A. Deadline for questions ................................................................................... No later than 4:00 pm on 10/09/2026 B. Answers posted .................................................................................................................. On or about 10/15/2026 C. Submission deadline ...................................................................................... No later than 2:00 pm on 10/19/2026
6. SUBMISSION CHECKLIST
6.1. This section identifies the information requested and how to respond.
6.1.1. Information should be submitted as a quote through nevadaepro.com.
6.1.2. Technical information and cost information should not be included in the same attachment.
6.1.3. All attachments should be flagged as confidential in nevadaepro.com.
6.1.4. Additional attachments may be included.
| 1. Applicable regulations governing procurement |
| 1.1. All applicable Nevada Revised Statutes (NRS) and Nevada Administrative Code (NAC) documentation can be found at: www.leg.state.nv.us/law1.cfm. |
| 1.2. Vendors are advised to review Nevada’s ethical standards requirements, including but not limited to NRS 281A, NRS 333.800, and NAC 333.155. |
| 1.3. This solicitation is a request for information (RFI) only. It is not a solicitation for bids or proposals. No contract award will result from this RFI. Aggregate information from this RFI will be analyzed and may be used as budget justification o... |
| 1.4. All information received in response to this solicitation is considered confidential business information by the Administrator of the Nevada State Purchasing Division of the Department of Administration. This solicitation will not lead to evaluat... |
| 1.5. GovRAMP NOTICE: Effective July 1, 2026, all new contracts containing a cloud component will include risk assessment requirements aligned with the GovRAMP program, which is based on NIST SP 800-53 (Revision 5). By submitting a response, vendors ac... |
| 2. Project overview |
| 2.1. Requesting agency background |
| 2.1.1. Pursuant to NRS 388.1323 the Nevada Department of Education’s (NDE) Office for a Safe and Respectful Learning Environment is required to maintain a 24-hour, toll-free, statewide hotline and internet website by which any person can report a viol... |
| 3. Scope of work |
| A. Tip Submission & Acquisition |
| 4. Cost |
| 4.1. Please provide a detailed cost model for the proposed services, including an itemized breakdown of: |
| Implementation & Setup Fees: One-time onboarding, configuration, migration, and training costs. |
| Recurring Fees: Subscription, licensing, or hosting fees (e.g., annual, monthly, or per-user rates). |
| Ongoing Maintenance & Support: Tiered support options, SLA levels, or unexpected maintenance fees. |
| Optional Services: Rates for custom enhancements, specialized training, or professional services. |
| 5. Timeline |
| 5.1. All questions shall be submitted using the bid Q&A feature in nevadaepro.com by the deadline below. |
| 5.2. The following represents the proposed timeline for this project. |
| 5.2.1. All times stated are Pacific Time (PT). |
| 5.2.2. These dates represent a tentative schedule of events. |
| 5.2.3. The State reserves the right to modify these dates at any time. |
| A. Deadline for questions No later than 4:00 pm on 10/09/2026 |
| B. Answers posted On or about 10/15/2026 |
| C. Submission deadline No later than 2:00 pm on 10/19/2026 |
| 6. Submission checklist |
| 6.1. This section identifies the information requested and how to respond. |
| 6.1.1. Information should be submitted as a quote through nevadaepro.com. |
| 6.1.2. Technical information and cost information should not be included in the same attachment. |
| 6.1.3. All attachments should be flagged as confidential in nevadaepro.com. |
| 6.1.4. Additional attachments may be included. |
File details come from the government source that posted it. Updated .