Parent Communication Log: What to Record and Why
A parent communication log is a dated record of every contact between school staff and a student's parent or guardian, capturing who initiated it, the method used, what was discussed, and what each side agreed to do next. It exists to answer one question reliably months later: what did the school tell this family, and when. That question comes up in attendance and truancy proceedings, special education disputes, grade appeals, behavior referrals, and any conversation that begins with a parent saying no one ever told them. A log that records facts, and only facts, answers it in seconds. A log full of impressions creates a second problem.
The complication most staff never hear about is that a communication log can, depending entirely on how you keep it, become an education record under the Family Educational Rights and Privacy Act, which means the parent has the right to inspect it.
The FERPA question, stated plainly
FERPA is codified at 20 USC 1232g, with implementing regulations at 34 CFR Part 99, enforced by the Student Privacy Policy Office at the U.S. Department of Education. The regulations define an education record at 34 CFR 99.3 as records directly related to a student and maintained by an educational agency or institution, or by a party acting for it. Parents, and eligible students once they turn 18 or enroll in postsecondary education, generally have the right to inspect and review those records.
The same definition carves out exclusions. The one that matters here is commonly called the sole possession exclusion. Under 34 CFR 99.3, records are not education records when they are kept in the sole possession of the maker, are used only as a personal memory aid, and are not accessible or revealed to any other person except a temporary substitute for the maker.
Read those three conditions as a test that must be passed in full, and note how easily a normal school workflow breaks it:
- Sole possession fails the moment the log lives in a shared drive, a team folder, or a student information system other staff can open.
- Personal memory aid fails when the notes are written to be used by someone else, for example to support a referral, a disciplinary decision, or a truancy filing.
- Not revealed to anyone else fails the first time you forward an entry to an administrator, paste it into a referral form, or read it aloud in a meeting.
So a genuinely private notebook a teacher keeps for their own recall can sit outside the definition. A department-wide log in a shared spreadsheet, a log field in the student information system, or notes attached to a discipline referral are maintained by the school and directly related to the student, and should be treated as an education record.
The practical conclusion is not to hide the log. It is to write every entry as though a parent will read it, because in most school systems they eventually can.
What to record: the fields
| Field | What goes in it | Why it matters later |
|---|---|---|
| Date and time | Exact date, and time for calls and texts | Establishes notice and sequence in any dispute |
| Student name and ID | Full legal name plus the system identifier | Prevents misfiling between similar names |
| Staff member | Name and role of the person making contact | Shows who had the conversation, not just the school |
| Parent or guardian contacted | Name and relationship, and the number or address used | Confirms you reached a person entitled to the information |
| Direction | School initiated or parent initiated | Distinguishes outreach from response |
| Method | Phone, text, email, in person, video, letter | Some notice requirements are method-specific |
| Outcome of the attempt | Spoke directly, left voicemail, no answer, message delivered, undeliverable | An attempt is not a contact, and the distinction decides cases |
| Language and interpretation | Language used, and whether an interpreter or translated notice was provided | Federal civil rights guidance expects meaningful access for families with limited English proficiency |
| Topic | Attendance, academics, behavior, health, special education, scheduling | Makes the log searchable and reportable |
| Summary | Two to four factual sentences on what was said | The substance of the record |
| Agreed next steps | Who does what, by when | Turns a conversation into a commitment you can follow up on |
| Follow-up date | The date the next contact is due | Prevents cases from going quiet |
| Attachments | Copies of letters sent, delivery confirmations, message transcripts | Evidence of the notice itself, not just of your note about it |
What to leave out
Everything in the log should be something you would be comfortable reading back to the parent verbatim. Keep out:
- Diagnostic or clinical language. Describe observed behavior, not a suspected condition.
- Judgments about the family. "Mother was uncooperative" is an opinion. "Mother declined the proposed meeting time and asked for an evening option" is a fact.
- Other students' names. Naming another student in this record can create a disclosure problem when it is inspected. Use a neutral reference instead.
- Hearsay and speculation about custody, immigration status, or housing, unless it is a documented fact the school must act on.
- Sarcasm, editorializing, and all caps. Tone survives the years better than context does.
- Transcripts of long calls. Summarize the decisions instead.
Writing a usable entry
A weak entry: "Called mom again about attendance. Same excuses."
A usable entry: "10/14, 3:45 pm. Called Ms. Rivera, mother, at the primary number on file. Spoke directly. Reviewed 6 unexcused absences since 9/22 and the attendance policy notice mailed 10/7. She stated transportation is the barrier on Tuesdays and Thursdays. Agreed: school will send bus route information by 10/17, parent will confirm receipt. Follow up 10/21."
The second version costs a few seconds more and does work the first cannot: it establishes notice, states the facts relied on, records the parent's stated reason without characterizing it, and creates an obligation on both sides with a date attached.
Special education and health raise the bar
For students with an Individualized Education Program, the confidentiality provisions under the Individuals with Disabilities Education Act at 34 CFR 300.610 through 300.626 apply alongside FERPA, and the prior written notice requirements at 34 CFR 300.503 mean certain communications must be documented in a specific written form rather than logged informally. A log entry noting that notice was given does not replace the notice itself.
Health information a school creates and maintains in a student's education record is generally treated under FERPA rather than HIPAA, but school-based health providers can fall under different rules depending on how the service is organized. If your log will hold health details, confirm the treatment with your district privacy officer.
Access, storage, and retention
If the log is an education record, parents may request to inspect it, and 34 CFR 99.10 requires the school to comply within a reasonable period, not more than 45 days after the request. Parents may also ask to amend records they believe are inaccurate or misleading under 34 CFR 99.20, and if the school declines, the parent is entitled to a hearing under 34 CFR 99.21 and may place a statement in the record. Sharing inside the school is generally permitted for school officials with a legitimate educational interest under 34 CFR 99.31(a)(1), if your annual notification defines those terms.
Retention schedules are set by state law and district policy, not by FERPA, and they vary widely. Ask your records officer for the applicable schedule and follow it, and do not keep a parallel personal copy after the official record is disposed of.
Automating the boring half
Most of a log entry is metadata a messaging system already knows: the timestamp, the recipient, the method, the language, and whether the message was delivered. Capturing that automatically leaves staff writing only the summary and the next step, the part that needs a human. It also gives you delivery evidence rather than a recollection.
Two related questions come up as soon as schools move contact to text. Our guide on K-12 parent communication texting covers how to write messages families actually open, and can schools text parents without consent works through the consent rules that govern the channel. Both sit upstream of the log: get the channel right, and the record largely writes itself.
This article is general information, not legal advice. FERPA, state student records law, and district policy interact differently in every jurisdiction and change over time, so confirm your own obligations with qualified counsel or your district privacy officer.
Frequently Asked Questions
What should be included in a parent communication log?
Date and time, student name and ID, the staff member's name and role, the parent contacted and the number or address used, whether the school or the parent initiated it, the method, whether contact was actually made, the language used, the topic, a short factual summary, agreed next steps with owners, and a follow-up date. Attach delivery confirmations and copies of any letters sent.
Is a parent communication log a FERPA education record?
Usually yes, once it is shared. Under 34 CFR 99.3, records directly related to a student and maintained by the school are education records. The sole possession exclusion applies only when notes stay in the maker's sole possession, serve as a personal memory aid, and are not revealed to anyone except a temporary substitute. Shared drives, student information systems, and referrals break all three conditions.
Can parents request to see a teacher's communication log?
If the log qualifies as an education record, yes. FERPA gives parents the right to inspect and review their child's education records, and 34 CFR 99.10 requires the school to comply within a reasonable period not exceeding 45 days after the request. A genuinely private memory aid kept solely by one staff member may fall outside that right, but most logs in practice do not.
How long should schools keep parent communication records?
FERPA does not set a retention period. Retention is governed by state records law and district policy, which vary considerably, and special education records often carry their own schedule. Ask your district records officer for the applicable schedule, follow it consistently, and do not retain personal copies after the official record has been disposed of.
What should you never write in a parent contact log?
Avoid opinions about the family, diagnostic or clinical language you are not qualified to use, the names of other students, speculation about custody, housing, or immigration status, and any sarcasm or editorializing. Write only what you would be comfortable reading aloud to the parent, because if the log is an education record they may eventually read it themselves.
Do text messages to parents need to be logged?
Treat them like any other contact. If the message is directly related to a student and maintained by the school, it can fall within the education record definition regardless of channel. Log the timestamp, recipient, content summary, and delivery status. Most school messaging systems capture that metadata automatically, which is more reliable than reconstructing it later.
Who can see a parent communication log inside the school?
School officials with a legitimate educational interest may generally access education records without parental consent under 34 CFR 99.31(a)(1), but your school must define who counts as a school official and what qualifies as a legitimate educational interest in its annual FERPA notification. Access is not open to all staff by default, and casual sharing outside that standard is a compliance risk.
Does a voicemail count as parent contact?
Record it as an attempt, not a contact, and log it that way. The distinction matters in attendance, truancy, and special education proceedings, where the question is often whether the family actually received notice. Note the number dialed, the time, whether a message was left, and what the message said, then schedule the next attempt.
Make the record a byproduct, not a chore
FRANSiS is an AI powered SMS platform for school communication that captures delivery status, language, and timestamps automatically so staff only write the summary. Its AI Powered Helper drafts replies for staff to review and send. See our K-12 education solutions or contact us to talk through how it fits your student information system.
