How to Write a Teacher Up Without Giving Them the Ammunition to Grieve It

Formal documentation of a teacher’s performance or conduct is one of the most legally consequential things a principal does. It is also one of the most commonly done badly — not because principals are careless, but because most of them were never taught what good documentation actually requires. They learned on the job, often in the middle of a situation that had already escalated, and the gaps in their documentation became the vulnerabilities in the process.

This post is the guide you needed before you needed it. If you are reading it in the middle of a situation — it is still useful. Start now. Late documentation is better than no documentation. Just do not pretend it was written in real time if it was not.

A poorly written write-up does not just fail to hold — it becomes the teacher’s defense. Every vague phrase, every opinion stated as fact, every undocumented conversation that you reference is a door their union rep will walk through.

The Four Non-Negotiables of Documentation That Holds

First: it must be factual. Documentation that holds is a record of observable events — what happened, when, where, who was involved, what was said or done. It is not an interpretation of what the behavior means about the person. ‘Ms. Jones was rude to the student’ is an interpretation. ‘On October 14th at approximately 10:20am, Ms. Jones raised her voice at a student, stating: [specific words]. The student put their head down and did not respond for the remainder of the period.’ That is documentation.

Second: it must be specific. Dates, times, locations. Specific behavior, not categories of behavior. Not ‘Ms. Jones has been consistently unprofessional’ — that tells a grievance panel nothing. ‘On September 22nd, October 5th, and October 14th, Ms. Jones [specific behavior on each date]’ — that tells them exactly what the record shows.

Third: it must be contemporaneous. Written as close to the event as possible. The credibility of documentation diminishes with time. Notes written the same day carry more weight than notes written two weeks later trying to reconstruct what happened. Get in the habit of writing the five-sentence record before you close your computer on the day something occurs.

Fourth: it must be communicated. Documentation that sits only in your file is less powerful than documentation the teacher has received and acknowledged. After a formal conversation, send a written summary. ‘This is a record of our conversation on [date]. Here is what was discussed. Here is the expectation. Here is the follow-up date.’ That email, received by the teacher, creates a record that both parties share.

What Invites a Grievance

Vague language: ‘unprofessional behavior,’ ‘inappropriate attitude,’ ‘failure to meet expectations.’ Without specifics, these are characterizations that a union rep can challenge as subjective.

Skipped steps: documentation that references prior conversations that were never themselves documented. If you are now writing formally about a pattern, the record needs to show the informal conversations that preceded it. If those conversations were not documented at the time, the formal write-up appears to be the first communication of the concern — which significantly weakens the case.

Opinion and inference: ‘It is clear that Ms. Jones does not respect students.’ That is a conclusion, not an observation. Stick to what can be seen, heard, or measured.

The Write-Up Template That Works

Date and time of the documented event. Location. Description of what was observed — factual, behavioral, specific. Impact on students or colleagues. Previous communications about this concern, if any, with dates. Expectation going forward. Consequence if the behavior continues. Follow-up date.

That is the structure. It is not complex. What makes it strong is the discipline to stay inside it — to write only what can be verified, to resist the temptation to characterize, and to be consistent in applying it regardless of who the teacher is or how long they have been there.

The process is what protects the standard. Build the process.