Stop writing session notes
after the bell rings.

Noteberry

Voice-first session documentation for school-based therapists. Tap a student, speak your notes, walk to the next room with the paperwork done — and the FERPA audit trail attached.

How it works

1
Tap & speak
Open the calendar, see who you've got today, tap a student, hit Record, and talk through the session like you'd describe it to a colleague.
2
AI cleans up
Gemini transcribes the audio, polishes the grammar without rewriting anything, and produces a 3-5 sentence clinical summary in under a minute.
3
Done & filed
Save → the schedule auto-marks complete and the audit log records the disclosure. Export to .docx in one click for the district form.

What's inside

Record & transcribe

Speak your session note. Gemini handles transcription, light grammar polish, and a clinical summary in under a minute.

Schedule & track

Per-student frequency targets, monthly compliance dashboard, and a calendar that shows exactly who needs to be seen this week.

Export & share

One-click DOCX exports for individual sessions, full parental records (FERPA §99.10), or period summaries for district review.

Built for compliance

FERPA-strict access control. Therapists see only the students they're explicitly assigned to. District managers see their district. App admins see everything. Enforced server-side, not by hiding UI.
Append-only audit log. Every read, write, edit, export, and search is recorded with user, timestamp, IP, and resource. Mongoose pre-hooks block update/delete on the audit collection itself.
Parental access export. One click produces a comprehensive DOCX of a student's entire education record, including the audit trail of who has touched it (34 CFR § 99.10).
Soft delete + retention. Sessions and students can be soft-deleted with audit, restored from a review queue, and held per district retention policy before any hard delete.
Multi-tenant from day one. Districts, campuses, classrooms, and per-student therapist assignments — all enforced server-side via a single source-of-truth helper.

Who it's for

Therapists

School-based SLPs, OTs, and counselors who write a stack of session notes between students and want to be done by the time they hit the next bell.

District managers

SPED coordinators who own compliance reporting, frequency tracking, and parental record requests across multiple campuses.

FAQ

How does the FERPA piece actually work?

Every read, write, edit, export, and search of a session note or student record is logged to an append-only audit collection with the user, IP, and timestamp. Therapists are scoped per-student (not per-campus), enforced server-side by a single guard helper. On a parental records request, one click produces a comprehensive DOCX of the student's entire education record — session history, audit trail, and a cover page citing 34 CFR § 99.10.

Where does the audio go?

Audio is captured in the browser via MediaRecorder and posted once to our server, which forwards it to Google's Gemini API for transcription. The audio buffer is discarded immediately after the transcript comes back — we never persist the audio. If you ever want to retain audio (e.g. for evidence), there's a per-session opt-in flag on the SessionNote model that's currently dormant pending a storage decision.

What about Google's data agreement?

Before any real student PII hits the Gemini API in production, your district needs a Data Processing Agreement with Google designating them a “school official” under 34 CFR § 99.31(a)(1). The product owner handles this with the district's legal team — it's a one-time DPA, not a per-deployment task. For demos with fake data you're fine without it.

Can a therapist see another therapist's notes?

No. Therapists are scoped per-student, not per-campus. A district manager explicitly assigns each student to each therapist, and the server-side guard helpers reject any read or write for a student that's not in the caller's assignedStudentIds list. Cross-district reads are blocked the same way for district managers.

What happens to a session if I delete a student?

Students and session notes are both soft-deleted by design. Deleting a student moves them to the trash (visible to district managers via /manage/deleted) but preserves their session history. Restoring a student brings everything back. Hard delete is gated on a separate review queue + retention policy and is tracked separately as issue #17.

Does it work on a phone?

Yes. It's a Progressive Web App — install it from Safari or Chrome on the home screen and it launches full-screen with microphone access (iOS 14.5+). The bottom nav is touch-tuned and recording works one-handed.

What if our roster comes out of an SIS as a Word doc?

Upload it. The roster importer at /manage/import accepts a .docx with a single table (Student Name / Student ID / Campus / Teacher / Frequency), shows you a diff preview, and lets you commit. Idempotent — running the same import twice creates nothing extra. You can opt in to strict mode (rejects unknown campuses) or to soft-delete missing students (off by default because FERPA forbids auto-deletion).

Ready to stop typing notes during dinner?

If your district manager has invited you, sign in. Otherwise, get in touch with them for an invite code.