Latest Release Version 3.16.0 26th August 2026
junipa
Student Plans Tamsin Ravenscourt Case notes
Pip Bellhaven Grammar RC
TR
Tamsin Ravenscourt
STU-40817 · Year 8 · form 8C · enrolled 2023
Level of adjustment
Substantial
Category
Cognitive
Basis
Diagnosed
Plan status
Active · Fully Signed
Viewing as
Learning Support Coordinator Classroom Teacher
READ_STUDENT_CASE_NOTES READ_SENSITIVE_STUDENT_CASE_NOTES

The list below is what a classroom teacher's own screen returns from the server. Nothing is hidden by the browser; the projection happens before the response is sent, so the text of a sensitive note never reaches this device.

Case notes

6 records · newest first 4 readable 2 withheld
  • Rohan Delacroix Learning Support 04 Aug 2026

    Reader and scribe worked well again in the half-yearly. Tamsin used the full extra time and finished the extended response, which she has not managed unaided before.

    Linked evidence · TEACHER_FILE_NOTES
  • Author withheld Sensitive 22 Jul 2026
    Content withheld.
    You do not have READ_SENSITIVE_STUDENT_CASE_NOTES.
    What the server returned for this row
    uid
    null
    redacted
    true
    sensitiveCaseNote
    true
    recordedDate
    2026-07-22
    studentUID
    STU-40817
    relatedEvidenceUID
    present
    created
    2026-07-22 15:41
    noteText
    absent
    The record exists and is dated. Only the words are gone.
  • Nadia Farrow Classroom Teacher, English 09 Jul 2026

    Chunked instructions are holding up in the novel study. Tamsin works steadily when the task is given in three parts on the board rather than read out in one go.

    Linked evidence · ADJUSTMENT_NOTED_IN_PLANNING
  • Author withheld Sensitive 27 Jun 2026
    Content withheld.
    You do not have READ_SENSITIVE_STUDENT_CASE_NOTES.
    uid null redacted true recordedDate 2026-06-27
  • Elowen Bright Classroom Teacher, Science You wrote this Sensitive 12 Jun 2026

    Tamsin asked to leave the practical early and told me why. I have recorded the reason here and let the year adviser know the same afternoon.

    Linked evidence · TEACHER_FILE_NOTES Readable to you because you are the author, not because of a privilege
  • Rohan Delacroix Learning Support 30 May 2026

    Phone call with Marguerite Ravenscourt about the semester review. She is happy for the literacy group to continue on Tuesdays and asked for the reading list a week ahead.

    Linked evidence · DOCUMENTED_MEETING

Two of the six rows are sensitive notes this teacher cannot read. They still occupy their place in the sequence, dated and marked, so the history reads as continuous. Ownership is checked before privilege, which is why the note of 12 June is legible to its own author while carrying the same sensitive marking as the two that are not.

Mentioning a colleague

Staff picker, opened by typing an at sign in the note body
Reader worked well again in the half-yearly. @Nad
Staff 8 results maximum
  • NF Nadia Farrow Classroom Teacher, English
  • NW Nadia Wrenfield Classroom Teacher, Mathematics
  • EB Elowen Bright (You) Classroom Teacher, Science
  • RD Rohan Delacroix Learning Support
Mark as sensitive

Two staff share a first name, so the picker shows the role beside each to tell them apart. The current user's own entry is marked, because staff do mention themselves by habit and the result is a notification that goes nowhere.

What the server does with that mention
  1. The note is re-read from the database. The note the browser sent is not trusted.
  2. The sender's authority over that note is confirmed.
  3. The recipient's own right to read it is confirmed independently. You cannot mention a colleague into seeing something they have no right to see.
  4. A sensitive note's notification carries no preview text, and is never included in an email even at a school that has turned message content on.
What the notification carries
Ordinary note
Rohan Delacroix mentioned you on Tamsin Ravenscourt
Reader worked well again in the half-yearly.
Sensitive
Rohan Delacroix mentioned you on Tamsin Ravenscourt
No preview. Open the record to read it.

Both notifications name the sender and the student, because a recipient has to know why they are being called in. Only the second withholds the words, and only the second stays out of email entirely.

The check runs on the server for the plain reason that the browser is not a source of truth about who may read what. A mention is a permission decision, so it is made where permissions live.

The same note, two surfaces

Why the record and the roster behave differently
This record

Shown, dated, withheld

A sensitive note the viewer cannot read still appears as a dated, redacted row. A support teacher needs to know there is history here worth asking about, and an audit trail with invisible gaps in it is not an audit trail.

Class roster

Not shown at all

On a shared class roster the note is not shown at all, not even as a count, and authorship is not an exception there. A row that appears for one teacher and not another on a shared screen tells the room something about the student.