+
+
+ Goal Tracking + Define goals, categories, status, and progress over time. +
+
+ Incident Logging + Capture critical events with consistent workflows and escalation. +
+
+ Auditability + Record who did what and when for sensitive actions. +
+
+ +
+
+

What WIN Is

+

+ WIN supports student success programs by providing a single place to manage student profiles, + goals, case notes, services provided, and critical incident reports—designed around + day-to-day workflows for advisors, mentors, and case managers. +

+
+ Students + Goals + Case Notes + Services + Incidents + Reports +
+
+ +
+

Who Uses It

+
    +
  • Case Managers / Advisors: track goals, document interactions, and follow up.
  • +
  • Program Administrators: monitor outcomes and compliance-ready reporting.
  • +
  • Supervisors: review incidents, approve actions, and ensure accountability.
  • +
+

+ WIN is built for least-privilege access and consistent documentation. +

+
+
+ +
+

Typical Workflow

+
    +
  1. Select a student and review current goals and status.
  2. +
  3. Add or update goals (category, status, progress notes).
  4. +
  5. Record case notes and services provided for that session.
  6. +
  7. If needed, log a critical incident with severity and follow-up actions.
  8. +
  9. Generate reports for program outcomes and internal review.
  10. +
+
+ +
+
+

Core Features

+
    +
  • Student profiles: basic demographics and program context.
  • +
  • Goal management: categories, statuses, and progress visibility.
  • +
  • Case documentation: notes and service tracking aligned to program needs.
  • +
  • Critical incidents: consistent logging, review, and escalation support.
  • +
  • Search & filters: quickly locate students and prioritize follow-ups.
  • +
  • Reporting: outcomes and activity summaries for administrators.
  • +
+
+ +
+

Privacy & Compliance Design

+

+ WIN is intended for environments where student records require careful handling. + The design emphasizes confidentiality, integrity, auditability, and controlled access. +

+
    +
  • Role-based access control: permissions enforced server-side.
  • +
  • Audit logs: track create/update/delete for sensitive records.
  • +
  • Data minimization: collect only what’s necessary for the workflow.
  • +
  • Secure defaults: least privilege and predictable access patterns.
  • +
+

+ See SECURITY.md in the repo for reporting and expectations. +

+
+
+ +
+
+

Project Structure

+
    +
  • api/ — backend services and data access
  • +
  • ui/ — front-end application
  • +
  • SECURITY.md — security reporting and practices
  • +
  • README.md — build/run instructions and overview
  • +
+

+ This landing page is intended for GitHub Pages and project communication. +

+
+ +
+

Getting Started

+
    +
  1. Open the repository and review README.md.
  2. +
  3. Set up the API environment (local config, database connection, secrets).
  4. +
  5. Run the UI and validate core flows: student list → goals → incident logging.
  6. +
+

+ Want to contribute? Open a PR with a clear description, screenshots (if UI), + and notes on security/privacy impacts. +

+ + Go to GitHub + +
+
+ +
+

Roadmap (High-Level)

+
+
+

MVP

+
    +
  • Student list + profile
  • +
  • Goal create/update
  • +
  • Incident logging
  • +
+
+
+

Operations

+
    +
  • Search & filters
  • +
  • Reports & exports
  • +
  • Supervisor review workflow
  • +
+
+
+

Compliance

+
    +
  • Audit log viewer
  • +
  • Retention & access review
  • +
  • Stronger incident classification
  • +
+
+
+

+ Roadmap items should be validated against requirements and stakeholder workflows. +

+
+ +