Who Are We Talking About?: The Necessity to Identify the Subjects in Performance Review and Employee Evaluation Documentation
- "Talked to her 5/8, 6/2, 9/1 and others re: multiple performance issues."
- "Met with her again regarding the same issues. JT told me he’d had the same conversations."
- "Who wrote these?" The client didn’t know. The performance review documents were found in a file in a desk occupied by one of Rose’s former managers, with "Rose" scrawled on top of the file.
- "Why did she think the performance review documents applied to Rose?" Her response: who else could they be referring to?
- "Who is JT? Is that person still employed?" My client thought that it could be Jane Thatcher, who had died. Or possibly Joanne Taylor, who moved. Maybe John Titus or Jason Thorn, both of whom had worked in Rose’s department.
When your managers document employee behavior or performance, they are writing for a future reader who does not know the players. Nevertheless, that future individual should have no questions about the events in the employee evaluation document, including knowing who wrote it and who it is about.
So that you do not fall into the traps into which this client dived, here is some guidance for how to get it right:
- Sign the employee evaluation or performance review document with your full name and job title: Remember that a future reader might not know who you are, let alone who other players are. Too often internal reports are unsigned, or signed with initials only. This can be especially troubling if the report is typewritten so that there is no handwriting to use as an authorship clue. Past authors have often left the company at the time of a future lawsuit and documents remain unidentified. A typed "signature" is better, but insufficient—anyone can type a name.
- Identify the person the performance review document is about: "I’ve spoken with her repeatedly and still her performance does not improve." "She was late again on Monday." While the author may presume that future readers will understand that a report in Samantha’s file was written about Samantha, that report may be separated from the file in the course of a lawsuit or otherwise. Performance review documents should stand on their own and be understandable without reference to the file in which they were stored or otherwise.
- Identify the people in the employee evaluation report by full name and job titles: Referring to colleagues and co-workers by initials or nick-names may be understood at the time but become incomprehensible in the passing years. Don’t write "BJ told me that Robert turned in the report not only late, but incomplete." State that "Bruce Jay Sanford (BJ), our project manager, told me that ..."
- Do not abbreviate job titles unless generally understood, and even then be cautious: Everyone knows that CFO means Chief Financial Officer, right? Or does it mean "Central Files Officer"? Or "Chicago Facility Operator"? Or "Company Flight Officer"? It could mean anything particular to your business. Always define an abbreviation (especially a job title) the first time it is used in a memo or employee report.
- Do not use "company slang" without explanation: Your copies of sales receipts may be called "pinks," from by-gone, multi-layer invoices, despite the fact that they are no longer pink. Similarly, the action to log them in a customer’s account may be called "Josephing," after a long-gone, long-term employee who performed that function. However, writing an employee up for "failing to Joseph the pinks" will be incredibly confusing to anyone (perhaps even a future company manager not clued into the slang) who later reads that report.