Build Secure K–12 Case Management SaaS

ResolvED HHB — School Case Management and Restorative Practices Software

PROJECT OVERVIEW

I am seeking an experienced full-stack software developer or small team to build ResolvED HHB, a secure, cloud-based SaaS application for K–12 schools and districts.

HHB stands for Harassment, Hazing, and Bullying. The platform will initially serve Vermont schools, with the potential for national expansion.

The software will combine regulatory compliance, investigation management, student support, and restorative practices into one intuitive system.

I am an experienced educational leader with more than 20 years in school leadership and restorative practices. I have developed the product vision and initial workflows and need a technical partner to create a functional, scalable commercial product.

THE PROBLEM

School administrators must navigate complicated legal requirements when responding to harassment, hazing, and bullying complaints. Responsibilities include investigating allegations, documenting evidence, meeting deadlines, communicating with families, determining findings, supporting students, and maintaining records.

Much of this work currently relies on disconnected documents, spreadsheets, and manual tracking.

ResolvED HHB will simplify these processes while emphasizing accountability, student well-being, relationship repair, and prevention.

CORE FEATURES

1. INCIDENT REPORTING AND CASE MANAGEMENT

Secure incident intake forms capturing allegations, involved individuals, witnesses, dates, supporting evidence, and immediate actions. Automatic case identification numbers, searchable records, and chronological activity histories.

2. COMPLIANCE AND GUIDED WORKFLOWS

Configurable workflows aligned with Vermont HHB laws and school policies. Guided procedural steps, deadlines, reminders, required documentation, and notification tracking. Ability to update rules as regulations change and eventually support additional states.

3. INVESTIGATION MANAGEMENT

Structured investigation workspace supporting interview notes, witness statements, confidential evidence uploads, timelines, documentation of allegations and responses, findings, approvals, and investigation report generation.

4. RESTORATIVE PRACTICES AND STUDENT SUPPORT

This is a distinguishing feature of ResolvED HHB.

The platform should provide restorative questions, guided reflection, student support planning, relationship-repair strategies, restorative meeting preparation, agreements, reentry planning, and follow-up monitoring.

Restorative processes must remain separate from legally required investigations, with appropriate safeguards and voluntary participation.

5. DASHBOARDS AND TASK TRACKING

User dashboards showing active cases, assigned responsibilities, case status, upcoming deadlines, overdue tasks, required notifications, and student follow-up activities.

6. COMMUNICATION AND DOCUMENT GENERATION

Customizable templates for family notifications, investigation reports, support plans, restorative agreements, and case closure summaries. Secure document storage and PDF export.

7. REPORTING AND ANALYTICS

Administrative reporting on case volume, investigation timelines, compliance, intervention completion, and recurring concerns, with strong confidentiality protections.

8. USER ROLES AND PERMISSIONS

Different access levels for district administrators, principals, designated HHB employees, investigators, counselors, restorative facilitators, and system administrators.

AI FUNCTIONALITY

I am interested in exploring AI-assisted features, including policy guidance, procedural suggestions, interview question development, document drafting, and restorative reflection resources.

AI should support rather than replace professional decision-making. It must not independently determine findings, credibility, or disciplinary outcomes.

Advanced AI can be developed in a later phase.

TECHNICAL REQUIREMENTS

The application should be a secure, responsive, browser-based SaaS platform.

I welcome recommendations regarding the technology stack, including React, Next.js, Node.js, Python, PostgreSQL, or comparable technologies.

Key requirements:

- Secure authentication and multifactor authentication
- Role-based permissions
- Multi-tenant architecture with district data separation
- Encryption and secure document storage
- Comprehensive audit logs
- Configurable workflows and deadlines
- Automated notifications
- Database backup and recovery
- Accessible, user-friendly interface
- Scalable cloud infrastructure
- Future integration capabilities

The system must support FERPA-related privacy obligations and appropriate security protections for confidential student records.

Initial development must use fictional student data.

MINIMUM VIABLE PRODUCT

The MVP should include secure accounts, school and district setup, incident reporting, guided investigation workflows, deadline tracking, evidence management, report generation, restorative support planning, dashboards, case closure, and basic analytics.

I want a practical, functional MVP rather than every possible feature in the first release.

DEVELOPMENT APPROACH

I prefer a phased, milestone-based engagement:

Phase 1: Discovery, requirements review, user workflows, wireframes, technical architecture, and detailed development estimates.

Phase 2: Interactive prototype demonstrating the primary workflows.

Phase 3: Functional MVP development, including frontend, backend, database, security, and essential features.

Phase 4: Testing, security review, bug fixes, and deployment preparation.

Phase 5: Pilot implementation, feedback, refinements, and future development planning.

I would prefer to begin with a paid discovery phase before committing to full development.

OWNERSHIP AND DELIVERABLES

ResolvED must retain ownership of custom source code, designs, documentation, and intellectual property, subject to agreed third-party licensing terms.

Development should occur in accounts and repositories controlled by ResolvED.

Deliverables include source code, functional application, database architecture, technical documentation, testing, deployment instructions, and knowledge transfer.

IDEAL DEVELOPER

Experience with secure SaaS applications, workflow automation, case management systems, education technology, and confidential data is highly desirable.

I value clear communication, realistic estimates, thoughtful recommendations, and experience working with nontechnical founders.

PROPOSAL REQUIREMENTS

Please include:

1. Relevant experience and examples of similar projects.
2. Recommended technology stack.
3. Proposed development phases and timeline.
4. Estimated discovery and MVP costs separately.
5. Approach to security and data privacy.
6. Individual or team development structure.
7. Source code ownership and handover approach.
8. Anticipated maintenance and hosting costs.

LONG-TERM VISION

ResolvED HHB will initially focus on Vermont but should be designed for expansion into other states.

My vision is to create software that helps school leaders navigate complicated investigations while supporting accountability, compassion, student well-being, and stronger school communities.

I am seeking a collaborative technical partner interested in helping develop a meaningful, sustainable commercial software product.