How to Write a Behavioral Observation (With Examples)

A behavioral observation is not a summary of how someone made you feel.

It's a record of what you saw and what you heard — specific, factual, and grounded in the moment it occurred. Written well, it's one of the most useful tools a manager has. Written poorly, it creates more problems than it solves.

Here's exactly how to do it right.

What Makes an Observation Behavioral

The word behavioral is doing real work here. It means the observation is rooted in observable action — not inference, not interpretation, not feeling.

Behavioral: what the person said, did, wrote, or failed to do. Not behavioral: what you think they meant, how they came across, what their attitude suggests.

The distinction matters because behavioral observations are defensible. They can be corroborated. They can be reviewed by HR, legal counsel, or a third party. Interpretations can't — they just invite argument.

The Four Elements of a Strong Observation

Every behavioral observation should answer these four questions:

Where did it happen? The setting matters. A team meeting, a 1:1 conversation, an email exchange, a client call, a shared workspace. Different contexts carry different weight and may be subject to different standards.

What specifically was said or done? This is the core of the observation. Use direct quotes where possible. If you can't quote directly, describe the action as precisely as you can. Avoid paraphrase that softens or editorializes.

When did it happen? Date and approximate time. The same day is always better than a week later. Memory distorts fast, and contemporaneous notes carry more credibility.

Is this part of a pattern? Note whether this is the first time you've observed this behavior or whether it follows a prior incident. One data point is a note. Multiple data points are a pattern. The distinction matters for what comes next.

Examples: Before and After

Before (not behavioral): Marcus was rude and unhelpful during the client meeting. He clearly doesn't take this seriously.

After (behavioral): During the October 22nd client meeting, Marcus interrupted the client twice mid-sentence and responded to a direct question about project timelines by saying he didn't have those numbers without offering to follow up. The client asked again at the end of the meeting and received the same response.

Before (not behavioral): Priya has been disengaged lately and her attitude is affecting the team.

After (behavioral): In the past three weekly team meetings on October 9th, 16th, and 23rd, Priya did not contribute to discussion despite being directly asked for input twice in each session. In the October 23rd meeting she left 10 minutes early without notifying anyone.

Notice what changed. The after versions don't make claims about character or attitude. They describe what happened, when, and in what context. A third party reading those observations can assess them on their own merits.

What to Leave Out

Personality labels. Difficult, toxic, unmotivated, passive-aggressive, lazy — none of these are behavioral. They're judgments. Leave them out entirely.

Demographic references. Age, gender, race, religion, national origin, disability status — these should never appear in a behavioral observation under any circumstances. Even a casual reference creates legal exposure.

Inferred motivation. She did it on purpose. He's trying to undermine the team. She doesn't care about her job. You don't know this, and stating it as fact is both inaccurate and legally risky.

Second-hand information. I heard from someone that is not an observation. If you didn't witness it directly, note that clearly or don't include it.

When to Write It

The same day. Always the same day if you can.

Memory is unreliable. The specific words that were said, the exact sequence of events, who was present — these details fade within hours. A two-sentence note written the day of the incident is worth more than a detailed reconstruction written two weeks later, and it will hold up better if the record is ever reviewed.

If you must write after the fact, note the date of the incident and the date you logged it. Don't present a delayed observation as contemporaneous.

Building a Habit

The managers who document most effectively aren't the ones who write the most. They're the ones who write consistently.

A brief, specific observation logged regularly builds a record that reflects reality accurately over time. It captures the good alongside the concerning. It shows what support was offered, what conversations were had, what changed and what didn't.

That record is what makes performance conversations productive, performance reviews fair, and disciplinary actions defensible.

Let the System Handle the Structure

Knowing what to write is one thing. Building the habit of writing it — in plain language, without the subjective drift that makes records problematic — is another.

Phineas handles the structure so you can focus on the observation. Write what you saw in plain language. Phineas flags subjective language, suggests behavioral framing, and tracks entries over time so patterns become visible before they become crises.