PERFORMANCE GUIDE

How to Document Employee Performance: A Practical Manager Guide

A manager-friendly method for replacing vague notes with specific observations, expectations, employee responses, support, ownership, and follow-up.

OdyHR illustrative team readiness workspace showing document and training status
ODYHR · ILLUSTRATIVE PRODUCT WORKSPACE

Important: This guide provides general operational information, not legal advice. Employment requirements vary by location, industry, workforce, and situation. Confirm current requirements with qualified HR or legal professionals.

QUICK ANSWER

What should a manager write in a performance record?

A useful performance record connects five things: the standard that was communicated, the specific fact observed, the work impact, the employee’s explanation, and the next action with an owner and review date.

Download the editable performance documentation log (Word). It includes a blank form and a clearly fictional example for recording an observation, conversation, support, and follow-up.

STANDARDWhat was expected?
FACTWhat happened?
IMPACTWhat did it affect?
RESPONSEWhat did the employee say?
NEXT STEPWhat happens by when?

The goal is not to create a dramatic paper trail. The goal is to give the employee and the next reviewer a clear, accurate account of the work, the conversation, the support offered, and what will be reviewed next.

STEP 01

Start with the job standard or policy

Before documenting a gap, identify the standard the employee was expected to meet. That standard may come from a job description, written procedure, production target, quality requirement, schedule, conduct policy, or an expectation discussed during onboarding.

Avoid creating a new rule after an incident. If the expectation was unclear, document that clarity is needed and communicate the updated standard before evaluating future performance against it.

Consistency check

Ask whether managers apply the same job-related standard and review method to employees doing comparable work. EEOC small-business guidance emphasizes communicating standards, applying them consistently, and using relevant details when explaining evaluations.

Strong documentation begins earlier in the lifecycle. See our employee onboarding checklist for a structure that records expectations, training, access, and early follow-up.

STEP 02

Write observable facts, not labels or assumptions

Document what a person could verify: dates, times, work output, instructions, records, and statements made in a meeting. Avoid character judgments, diagnoses, exaggerations, motives, and words such as “always” or “never” unless the evidence genuinely supports them.

TOO VAGUE

“Jordan is unreliable and has a bad attitude about deadlines.”

MORE USEFUL

“The client report due Friday at 5:00 p.m. was submitted Monday at 9:12 a.m. The manager had confirmed the deadline in the project plan on Tuesday.”

Include the details that help someone understand the event

  • Date, time, location, assignment, or work period involved
  • People present and the source of relevant information
  • The standard, procedure, or instruction communicated
  • The specific result, behavior, or missed requirement observed
  • The operational impact, stated without speculation

STEP 03

Record the conversation and the employee’s response

A performance note should show that the manager discussed the concern, not merely recorded a conclusion. Capture the date, attendees, main points explained, employee response, questions, context supplied, and any disagreement.

If the employee raises a medical issue, accommodation request, discrimination concern, protected complaint, leave question, or another sensitive matter, pause the ordinary manager workflow and involve the appropriate HR or legal resource. Keep access to sensitive information limited to people who need it.

01

Explain the gap

Connect the observable fact to the communicated expectation.

02

Ask for context

Let the employee respond and record the substance accurately.

03

Offer support

Note coaching, clarification, training, tools, or other approved support.

04

Confirm understanding

Record what the employee understood, not whether the employee agreed with every conclusion.

STEP 04

Set a measurable next step and a real review date

“Improve immediately” does not tell the employee or manager what success looks like. Define the expected result, the period in which it will be reviewed, who will check progress, and what evidence will be used.

  • State the specific expected result or behavior.
  • Identify any training, tools, clarification, or manager support.
  • Assign the employee and manager actions separately.
  • Set the next review date and the period being evaluated.
  • Record the outcome when the review occurs.

Close the loop even when performance improves. A dated outcome prevents an old issue from appearing permanently open and shows the employee’s later progress.

EXAMPLES

Weak and stronger performance documentation examples

SituationWeak noteStronger record
Missed deadline“Frequently late with work.”“The August 14 inventory report was due at noon and received at 4:35 p.m. The noon deadline was listed in the weekly plan.”
Quality issue“Careless work.”“Three of 25 completed records omitted the required approval field. The procedure reviewed July 30 requires approval before closure.”
Attendance“Bad attendance.”“The employee arrived after the scheduled 8:00 a.m. start on August 5, 8, and 12. Arrival times recorded were 8:24, 8:17, and 8:31.”

These are fictional writing examples, not automatic conclusions or customer results. Managers should verify facts, consider the employee’s explanation, apply current policy consistently, and obtain the required review before taking action. Attendance observations in particular need appropriate context and review before drawing a performance conclusion.

FROM OBSERVATION TO FOLLOW-UP

A complete fictional performance record

Use the fields below to see how one note develops over time. The employee, work, and outcomes are invented to demonstrate the process.

Fictional record for Casey Morgan, operations coordinator
FieldExample entry
StandardThe weekly stock summary is due Thursday at noon. The manager reviewed the template and deadline with Casey on August 27.
ObservationThe September 3 summary arrived September 4 at 9:20 a.m. The submission record confirms the time.
Work impactThe manager prepared the Thursday order without the West location count and had to review an additional request on Friday.
ConversationSeptember 4: Casey said the West location had not returned its count and Casey was unsure when to escalate. The manager confirmed there was no written escalation cutoff.
SupportThe manager will name a backup contact for each location and explain the escalation route by September 8.
Next stepFor the next three summaries, Casey will flag any missing count by Wednesday at 3 p.m. The manager will respond to the blocker that afternoon.
Follow-up outcomeSeptember 25: all three summaries arrived by Thursday noon. One missing count was escalated on Wednesday and resolved by the manager. Close this follow-up and continue the ordinary check-in routine.

The entry distinguishes verified output from the employee’s explanation, records a manager commitment, and closes the item when the agreed review occurs. It does not assume that every missed deadline calls for discipline.

Include effective work, too

A balanced record can also note: “Casey identified a duplicate supply request during the September 10 review and checked it with the location manager before the order was sent.” Specific recognition helps a later reviewer understand work across the period rather than seeing only problems.

FROM OBSERVATION TO FOLLOW-UP

A complete performance documentation example

This fictional example shows how a manager can connect the facts, conversation and next action.

FieldExample entry
Communicated standardThe weekly inventory summary is due Thursday at 3 p.m.; the manager reviewed that deadline at the September 1 planning meeting.
ObservationThe September 10 summary was received Friday at 10 a.m.
Work impactThe manager used the prior week's figures for Thursday's planning meeting.
Employee responseThe employee said a source report was unavailable and that they had not raised the blocker before the deadline.
Manager supportThe manager will demonstrate the backup reporting process at the next working session.
Employee actionRaise any source-data blocker by noon on the next reporting day and submit the summary by the agreed deadline.
ReviewThe manager will review the next summary and record the outcome at the following check-in.

At follow-up, add a dated note about the actual result. Record improvements as well as remaining gaps. If the expectation was not met, record the facts, the employee's explanation and the next agreed action. Keep a writing example separate from any decision about discipline.

Keep the record findable with consistent file categories and approved access. Explore OdyHR employee document management to see how records connect to the workflow.

MANAGER TEMPLATE

Performance documentation checklist

  1. 01

    Standard: What job expectation or policy applied, and when was it communicated?

  2. 02

    Observation: What specific fact, date, work output, or behavior was verified?

  3. 03

    Impact: What work, customer, schedule, safety, quality, or team outcome was affected?

  4. 04

    Discussion: When did the conversation occur, who attended, and what did the employee say?

  5. 05

    Support: What clarification, training, tools, coaching, or resources were offered?

  6. 06

    Next step: What measurable result is expected, who owns it, and when will it be reviewed?

  7. 07

    Outcome: What happened at follow-up, and is the item closed or still active?

Store notes in the approved employee record with appropriate access. Our employee-file organization guide covers categories and ownership. Use the performance evaluation guide and Word template when it is time to summarize a defined review period.

OdyHR connects evaluations, manager feedback, and follow-up with employee history. Explore performance evaluations in OdyHR.

AUTHORITATIVE REFERENCES

Sources used for this guide

TURN THE CHECKLIST INTO A WORKFLOW

Keep owners, due dates, records, and next steps connected.

TALK THROUGH YOUR WORKFLOW EXPLORE THE INTERACTIVE DEMO