If It's Not Documented, It's Like It Didn't Happen
Mention documentation to many managers, and you can almost feel them tense up.
It sounds formal. Legal. Maybe even a little threatening.
And too often, documentation doesn’t start until someone says, “We may need to terminate this employee. What documentation do we have?”
That’s backwards. Good documentation isn’t about building a case against someone. It’s about creating clarity, helping people improve, and making sure important workplace decisions are based on facts rather than memory.
Start before there’s a serious problem
Documentation shouldn’t suddenly appear when an employee is already in trouble.
Some of the most useful documentation is simple:
An email recapping expectations after a conversation
Notes from a coaching discussion
Goals and commitments from a one-on-one
A follow-up date to check progress
Recognition that something has improved
A record of an employee concern and how it was addressed
None of that needs to feel disciplinary.
It simply creates a record of what was discussed and what happens next.
Document the conversation, not your frustration
This is where managers sometimes get into trouble.
“Bad attitude.”
“Not a team player.”
“Doesn’t care.”
“Always difficult.”
Those may describe how a manager feels, but they don’t tell us much about what actually happened.
Good documentation focuses on observable facts instead of:
Sarah has a terrible attitude and is disrespectful.
Try:
During Tuesday’s team meeting, Sarah interrupted two coworkers while they were speaking and responded, “That’s not my problem,” when asked to help resolve the customer issue. We discussed the expectation that disagreements be handled professionally and respectfully.
Now we know what happened, what the concern was, and what expectation was communicated.
Employees should know what you’re documenting
Documentation should rarely contain a big surprise.
If a manager writes three paragraphs about an employee’s performance problem but has never actually discussed the problem with the employee, the documentation isn’t solving much.
The conversation comes first. Be clear about:
What happened?
Why is it a concern?
What needs to change?
What support is available?
When will you follow up?
Then document the important points. That creates accountability for everyone involved.
Documentation protects employees, too
We tend to talk about documentation as something that protects the organization.
It does. But good documentation also protects employees.
It helps ensure they receive clear expectations. It gives them an opportunity to respond. It provides a record of progress. And it reduces the chance that a decision will be based on one manager’s memory, mood, or interpretation of events.
Good documentation can even work in an employee’s favor.
Imagine a new manager believes an employee has always struggled with performance. Previous records show otherwise.
Or an employee was given a specific goal three months ago and has made significant progress toward it. That information matters.
You probably don’t need to document everything
Not every conversation needs a formal memo.
A quick coaching conversation about being five minutes late once probably doesn’t require a three-page write-up.
Use some judgment.
Generally, documentation becomes more important when:
A problem is recurring
Expectations have been discussed previously
Performance or conduct could lead to disciplinary action
An employee raises a significant concern
There is disagreement about what happened
An accommodation, leave, or other employment issue is involved
A decision may need to be explained later
A helpful question is:
If someone asked me about this six months from now, would it matter that I could accurately explain what happened?
If the answer is yes, document it.
And please don’t wait until termination
One of the worst times to discover there is no documentation is when leadership has already decided someone needs to go.
You hear:
“We’ve talked to him a hundred times.”
Maybe you have.
But what was discussed? When? What expectations were set? Did he know his job was at risk? Was he given an opportunity to improve?
Those questions become much harder to answer when nothing was captured along the way.
Documentation doesn’t replace good management. It supports it.
Keep it simple
Good documentation doesn’t have to sound like it was written by an attorney. In fact, it’s often better when it doesn’t.
Capture the facts.
Be specific.
Leave out assumptions and emotionally charged language.
Document what was discussed, what is expected, and what happens next.
Then follow up.
That’s really the goal.
Documentation isn’t about catching people doing something wrong. It’s about creating enough clarity that six months from now, everyone can understand what happened and why.
Comments