67% of managers regularly avoid or delay giving critical feedback to their employees. That number comes from Leadership IQ’s survey of 689 HR directors and executives, and it almost always gets read as a courage problem.
This post is about the window before that avoidance hardens into a performance improvement plan. A manager notices something in March, again in April, decides in June to address it, and discovers nothing was ever written down. Performance documentation is supposed to prevent that. Instead the first written record of the problem is the PIP itself.
That is a bad place for a problem to appear for the first time. The employee reads a formal document full of dates nobody ever mentioned, and the manager is reconstructing six months from memory into a form HR will keep.
What pre-PIP performance documentation is actually for
Most advice treats documentation as year-round HR hygiene: keep records on everyone, in case you need them. That is a different job. The documentation this post is about has one narrow purpose. It carries you from “I think there’s a pattern here” to “I can show the pattern, and I can show what I already tried.”
Only the second supports a decision; the first is an impression. The second is dates, specific behavior, and specific coaching that changed nothing. A PIP resting on the first reads as a surprise. A PIP resting on the second reads as the next step in a conversation running since June.
Managers stall on these notes because they do not have the sentence, not because they lack nerve.
If you haven’t had the coaching conversation yet, that comes first. Our guide on how to coach an underperforming employee covers the stage before this.
When to start writing it down
The trigger is the second instance of the same specific problem.
Not the first time it happens. One late deliverable is a data point, and opening a file on a data point is how managers end up with records that look like case-building. And not the moment you decide a PIP is likely either, because by then you are writing from memory about things that happened weeks ago, and it shows in every line.
Second instance, same specific problem, similar business impact. Write it the same day if you can, within 48 hours at the outside.
Then keep that cadence for everyone in a comparable situation. A file that starts the week you began to dislike someone is visible as exactly that to whoever reads it later.
What belongs in every entry
Four fields. An entry with all four is still usable months later.
| Field | What goes in it | What to keep out |
|---|---|---|
| Date | The date it happened, and the date you wrote it | ”Last month”, “recently” |
| Specific behavior | What the person did or said, so someone absent could picture it | Labels: careless, dismissive, unmotivated |
| Business impact | What it cost: the delay, the rework, the client who noticed | ”It affects the team” |
| What was said or agreed | What you raised, what they said back, what you agreed next | Your read on whether they meant it |
Keep entries to four or five sentences. The longer a record runs, the more opinion leaks in.
When managers first try to document a concern, we see the same pattern: they write down how the moment felt, not what the person did or said.
The rewrite: five vague notes, and the version that would hold up
The five notes below are composites built from patterns we see across coaching conversations, not transcripts of real employees. The vague versions are close to what managers actually type. The rewrites are what the same manager produced once someone sat next to them and asked, clause by clause, what did you see. Nobody in these examples is a bad manager. They are people trying to be fair with no wording to hand.
Mark, three missed deadlines
“Mark’s been missing deadlines again. Not a great attitude about it either.”
That is the whole entry. Mark is a data analyst who has submitted three deliverables one to two days late in six weeks, each time without flagging the delay in advance. The note captures none of that. It also adds a judgment about his attitude that Mark would dispute and the manager could not evidence.
The rewrite:
On Aug 12, Mark submitted the Q3 dashboard update two days after the agreed deadline of Aug 10, without notifying me in advance. This is the third missed deadline since July 1 (also missed the June 30 and July 21 deliverables). In our Aug 12 1:1, I asked him to flag delays 24 hours ahead going forward. He agreed.
What changed: the dates make the pattern countable instead of asserted, and the agreement is on the record. If Mark misses the next one without a heads-up, the entry after this one is about a broken commitment rather than another late file. That is a much stronger thing to be holding in June. The word “attitude” is gone and nothing went with it.
Rachel, errors the client found first
“Rachel’s reports keep having mistakes. She needs to be more careful.”
“Be more careful” is advice, not a record. It also buries the part that makes this serious, which was never the arithmetic. It is who found it.
The rewrite:
Rachel’s July 28 reconciliation report understated Q2 revenue by $12,000 due to a formula error in the summary tab. A client contact flagged it before we caught it internally. This is the second consecutive month with a calculation error the client found first (also the June 30 report). I reviewed both with her on Aug 1; we agreed she would run a second-pass check before sending client-facing numbers.
What changed: the impact now has a number and an audience. A note that says “mistakes” invites a debate about how serious mistakes are. A note that says a client caught a $12,000 understatement two months running does not invite that debate. The agreed fix is written as a process, so next month’s report either has a second-pass check on it or it doesn’t.
Tom, talking over people in meetings
“Tom can be dismissive of Emily and Sam in meetings. It’s becoming a pattern.”
Dismissive describes a person. It cannot be observed, argued with, or improved against, and it is the first word to fall apart when anyone else reads the file and asks what he actually did.
The rewrite:
In the Aug 5 and Aug 14 meetings, Tom spoke over Emily mid-sentence both times she raised an issue, and moved the meeting on before she finished. Emily raised this with me directly on Aug 15. I discussed it with Tom on Aug 16; he said he hadn’t noticed and agreed to let people finish before responding.
What changed: the same behavior appears twice with dates, the complaint has a named source and a date of its own, and the label is replaced by the thing Tom did that made two people reach for that label. Notice what the rewrite does not do. It does not claim Tom intended any of it. His answer, that he hadn’t noticed, sits in the record as his answer, and it may well be true.
Linda, late to the client call
“Linda’s been late a lot lately.”
Eight words, every one of them contestable. A lot compared to what? Lately meaning when? Late by how much?
The rewrite:
Linda joined the Aug 4, Aug 11, and Aug 18 client calls between 15 and 30 minutes after the 9am start, without messaging ahead on any of the three. I raised it with her on Aug 18; she said her commute had changed and agreed to message the group if she would be more than five minutes late.
What changed: three dated instances instead of “a lot”, and the actual problem gets named. It was never lateness on its own. It was three client calls starting without her while nobody in the room knew whether to wait. The rewrite also records her explanation, which is the part managers leave out most often, and usually the part that makes the entry fair.
David, the commitment that keeps not happening
“David keeps saying he’ll do it and then doesn’t follow through.”
Follow-through is a trait. What you can document is one specific commitment, made on specific dates, and what the shared system shows afterwards.
The rewrite:
In our July 22, July 29, and Aug 5 1:1s, David agreed to update the client status tracker by end of week. As of Aug 8, the tracker had not been updated after any of the three weeks. I showed him the tracker’s edit history in our Aug 8 1:1; we agreed he would update it same-day going forward instead of end-of-week.
What changed: the same commitment is tracked three times, and the evidence is a system log rather than the manager’s recollection. That second part matters more than it looks. In three of the five notes above, the manager is the only witness to what happened, which means the entry is only ever as good as the manager’s credibility. Here the tracker is the witness. Which is why this is the entry David is least likely to dispute, and the one that took the least nerve to write.
Where documentation alone isn’t the answer
Writing it down is the wrong first move in four situations, and the fix differs.
A single incident that has not repeated. Hold it, and do not open a file on one data point.
A drop in performance that lines up with something outside work: an illness, a bereavement, a family situation you half know about. The behavior may be documentable and still be the wrong thing to write up first. Ask what is going on, and loop in HR before starting a record.
Anything that touches a protected characteristic, or that the employee could frame as discrimination. Bring HR in now rather than keep documenting solo and hoping the file speaks for itself. None of this is legal advice: whether a record meets a legal standard depends on your jurisdiction and your company’s policy.
Then there is the concern you cannot get onto the page at all. The person hits their numbers and something about how they work is wrong, and every attempt to write it down comes out as a description of who they are rather than what they did. There is no good note for that one. Writing it anyway makes it worse, because a file of character judgments is the first thing to fall apart when a third party reads it.
Turning the note into the conversation
A file nobody has discussed is not documentation. It is a grievance with dates on it. Every entry above contains a line about a conversation, because the note records one rather than replacing it.
The opening line carries most of the weight. Try: “I want to talk about the tracker updates. Three weeks where we agreed end-of-week, and the edit history shows nothing. Tell me what’s getting in the way.” Dated, specific, ending on a question instead of a verdict. That sentence lives inside constructive feedback as a skill, and the assessment shows how your version of it lands.
Be ready for it to go badly anyway. Reading someone a precisely dated record can feel like surveillance, and the more accurate it is the less room they have to disagree, which some people experience as a trap rather than fairness. The usual way through is the one-on-one itself. If the pattern only comes up once it is already a problem, the record will always read as evidence being collected.
The real reason the note never gets written
Go back to the 67%.
Read as a courage problem, that figure says two-thirds of managers know what to say and cannot make themselves say it. Almost every article on performance documentation assumes that, which is why they all close by telling you to be specific. Nobody ever produced a specific sentence by being told to be specific.
Look at what changed between the vague notes and the rewrites. No manager there learned anything new: they already knew Mark had been two days late three times. What they lacked was wording that puts it on a page without sounding like an accusation or a character reference. SHRM’s documentation guidance lands in the same place: vague language is what undermines a record once somebody outside the conversation reads it.
That is a vocabulary problem. It is also solvable, which the courage reading is not. A manager with five sentence patterns in front of them writes the note the same day. A manager without them waits until the performance improvement plan is already scheduled and the only written record of six months of concern is the document that ends the conversation.
If the sentence is where you get stuck, rehearse it before the next 1:1. Merlin will work through the wording with you inside Slack or Teams.