Employee Performance Report: How to Write One That Gets Results

An employee performance report is a written document that evaluates how well a person has carried out their job responsibilities over a specific period. It typically covers goals met, skills demonstrated, areas for improvement, and a plan for what comes next. When done well, it gives both the manager and the employee a shared record they can act on.

Most managers dread writing these. The report either becomes a vague collection of pleasantries that helps nobody, or a stack of subjective impressions that the employee disputes on sight. Neither outcome is useful.

The difference between a performance report that collects dust and one that actually changes behavior comes down to structure and evidence. This guide walks through what to include, how to write each section, and how to use objective data (including time tracking) so the report reflects what actually happened rather than what you remember happening.

Why employee performance reports matter

Performance reports exist for a practical reason: they create a written record that connects expectations to results. Without them, feedback stays verbal, inconsistent, and easy to forget.

A well-written report does four things. It documents what an employee accomplished during the review period, giving both sides a factual basis for the conversation. It identifies specific skills or behaviors that need development, with enough detail for the employee to act on. It sets measurable goals for the next period, so progress can be tracked rather than guessed at. And it protects the organization legally if performance issues escalate to disciplinary action or termination.

Companies that skip formal performance documentation tend to run into the same problems: managers apply standards unevenly across the team, high performers feel unrecognized because nobody wrote down what they did, and underperformers never receive the clear written feedback they need to improve. When it comes time to make promotion or compensation decisions, there is no objective record to reference, only opinions.

What to include in an employee performance report

A complete performance report covers seven areas. Not every report needs to go deep on all seven, but skipping any of them entirely leaves a gap.

Employee information and review period. Name, job title, department, manager name, and the dates the report covers. This sounds obvious, but missing dates are one of the most common problems in performance files. Without a clear period, neither side can agree on what is being evaluated.

Job responsibilities and expectations. A brief summary of the role’s core duties and any specific goals or targets that were set at the beginning of the review period. This section anchors the rest of the report. If the employee did not know what was expected, the evaluation that follows is unfair.

Performance against goals. The core of the report. For each goal or responsibility, document what was achieved, what fell short, and the context around both. Use specific outcomes, not adjectives. “Closed 47 of 52 assigned tickets within SLA” is useful. “Did a good job with tickets” is not.

Skills and competencies assessment. Rate or describe the employee’s proficiency in the skills that matter for their role. Common categories include technical knowledge, communication, problem-solving, teamwork, and time management. Use examples to support each rating.

Strengths and accomplishments. What the employee did particularly well during the review period. Be specific enough that the employee feels genuinely recognized. “Handled the Q3 client migration with zero downtime and no customer complaints” tells the person exactly what you valued.

Areas for improvement. Where the employee needs to develop. Frame these as forward-looking actions, not character judgments. “Needs to improve response time on urgent tickets from the current average of 4 hours to under 2 hours” is actionable. “Has a bad attitude about urgent work” is not.

Goals for the next period. Two to four specific, measurable goals for the upcoming review period. Each goal should include what success looks like and a timeline. These become the “performance against goals” section in the next review, closing the loop.

Types of employee performance reports

Different situations call for different report formats. The most common types are:

Annual performance review. The standard once-per-year evaluation. Covers the full previous year and typically ties to compensation decisions. Annual reviews work best when they summarize ongoing feedback that was already given throughout the year. If the annual review is the first time an employee hears about a problem, the process has already failed.

Quarterly performance review. A shorter, more frequent check-in that covers the previous three months. Quarterly reviews catch issues earlier and make the annual review less overwhelming because the documentation is already done. Many teams are shifting to quarterly cycles for this reason.

Mid-year review. A single mid-point check between annual reviews. Useful for organizations that are not ready for quarterly reviews but recognize that once a year is not frequent enough.

90-day review. Used during the probationary period for new hires. Evaluates whether the employee is meeting the expectations set during onboarding and whether the role is a good fit. This review has higher stakes than most because it often determines whether employment continues.

360-degree feedback report. Collects input from the employee’s manager, peers, direct reports, and sometimes clients. The advantage is a more complete picture of performance from multiple angles. The challenge is that collecting honest, useful feedback from multiple people takes significant time and coordination.

Self-evaluation. The employee writes their own assessment before the manager writes theirs. Comparing the two reveals gaps in perception. Self-evaluations can be unreliable: some employees undersell themselves as a signal of dissatisfaction, while others overrate their contributions. The value is in the comparison, not in taking the self-evaluation at face value.

Project-based review. Evaluates performance on a specific project rather than a time period. Useful for project-based organizations where an employee’s responsibilities change significantly from one assignment to the next.

How to write an employee performance report: step by step

Step 1: Gather data before you write

The most common mistake in performance reporting is writing from memory. Memories are biased toward recent events (the recency effect) and toward incidents that were emotionally charged. An employee who had one bad week in month eleven may be remembered less favorably than their actual nine months of strong work warrant.

Before you start writing, pull together objective sources: time tracking records, project completion data, customer feedback scores, peer feedback, ticket metrics, attendance records, and any notes you made throughout the review period. The goal is to build the report on evidence, not impressions.

Step 2: Review the previous report’s goals

Start with the goals that were set in the last review cycle. For each goal, document the outcome: was it met, partially met, or not met? If partially met, what percentage was completed and what prevented full completion?

This step is where many performance reports fail. If the previous report did not include specific measurable goals, there is nothing concrete to evaluate against. Going forward, make sure every report ends with clear targets for the next period.

Step 3: Write the accomplishments section first

Start with what went well. This is not about being nice; it is about accuracy. If you write the improvement areas first, the whole report skews negative, and the accomplishments section reads like an afterthought.

Be specific. Instead of “great team player,” write “volunteered to cover three shifts during the April staffing shortage, maintaining the team’s response time at 98% SLA compliance throughout.” Specificity makes the praise credible and gives the employee a clear picture of what behaviors you want to see repeated.

Step 4: Write the improvement areas with actionable language

For each area of improvement, include three elements: what needs to change, what the current state is, and what the target state looks like.

Poor example: “Communication needs work.”

Better: “Client update emails were sent an average of 3 days after project milestones during Q2 and Q3. The target is same-day updates within 4 hours of milestone completion.”

Avoid personality judgments. “Is too slow” is a judgment. “Average task completion time was 6.2 hours against a target of 4 hours” is a measurement that the employee can work with.

Step 5: Set goals for the next review period

Write two to four goals for the upcoming period. Each goal should follow the SMART framework: specific, measurable, achievable, relevant, and time-bound.

Weak goal: “Improve project management skills.”

Strong goal: “Complete the PMP certification by Q2 2026 and lead at least one cross-departmental project by year-end, delivering within 10% of the original budget estimate.”

Step 6: Review for fairness and consistency

Before finalizing, ask yourself: would I say the same things about another employee who did the same work? Performance reports should be calibrated across the team. In cross-manager environments, evaluations should be scored objectively, not argued competitively between managers. If the same performance gets rated “exceeds expectations” in one team and “meets expectations” in another, the system is broken.

Step 7: Discuss the report with the employee

A performance report is not a memo you drop on someone’s desk. Schedule a conversation to walk through it together. Give the employee the written report in advance so they can read it before the meeting. During the meeting, listen as much as you talk. The employee may have context you did not have when writing the report. Document any changes or additions that come out of the discussion.

Example phrases for employee performance reports

Having a bank of clear, professional phrases speeds up the writing process and helps maintain consistency across the team.

Goal achievement

• Exceeded the quarterly sales target by 12%, closing $340,000 against a $303,000 goal
• Completed all assigned onboarding tasks for 15 new hires within the 30-day window
• Delivered the website redesign two weeks ahead of the September deadline
• Met 4 of 5 performance goals for the review period; the remaining goal (certification) is in progress with an expected completion date of March

Communication and teamwork

• Facilitated weekly standups that reduced cross-team miscommunication and cut duplicate work by approximately 20%
• Responded to internal requests within 2 hours on average, the fastest response time on the team
• Took initiative to document tribal knowledge into the team wiki, creating 12 reference articles used by the entire department
• Needs to communicate project delays earlier; three of five project delays in Q3 were not flagged until the delivery date

Technical skills

• Resolved 94% of tier-2 support tickets without escalation, up from 78% in the previous period
• Learned the new CRM system independently and trained three team members during the rollout
• Code review turnaround time averaged 4 hours, consistently within the team’s 8-hour SLA
• Needs to develop proficiency in data analysis tools; current reporting relies on manual spreadsheet processes that are prone to errors

Time management and productivity

• Consistently logged time accurately, with less than 2% variance between estimated and actual hours across all projects
• Managed a workload of 35 active tasks simultaneously while maintaining quality scores above 90%
• Overtime hours decreased from 12 hours per week in Q1 to 4 hours per week in Q3 after implementing personal time-blocking practices
• Needs to improve prioritization of urgent requests; average response time on high-priority tickets was 4.1 hours against a 2-hour target

Leadership and initiative

• Mentored two junior team members, both of whom received positive 90-day reviews
• Identified and proposed a process change that reduced invoice processing time from 3 days to 4 hours
• Volunteered to lead the office relocation project, completing it on schedule with no disruption to client deliverables

Areas for improvement (constructive phrasing)

• Attendance was inconsistent in Q2, with 6 unscheduled absences compared to a team average of 2. A pattern of Monday absences was discussed in the mid-quarter check-in
• Meeting deadlines remains a development area; 3 of 8 deliverables were submitted after the agreed date, with delays ranging from 2 to 7 days
• Needs to delegate more effectively; took on tasks that could have been assigned to junior team members, which contributed to the overtime pattern noted above

Common mistakes to avoid

Writing from memory instead of data. The recency effect means you will overweight the last few weeks of the review period. Pull time tracking records, project data, and customer feedback before you start writing.

Using vague language. “Good communicator” and “needs improvement” tell the employee nothing they can act on. Every statement should include an observable behavior or a measurable result.

Surprising the employee. If the performance report is the first time the employee hears about a problem, the manager has failed, not the employee. Issues should be addressed as they arise. The report documents what was already discussed.

Rating everyone the same. If every person on your team gets the same rating, the system provides no useful information. Differentiate based on actual performance differences.

Skipping the goals section. A report without forward-looking goals is an autopsy, not a development tool. Always end with measurable objectives for the next period.

Making it personal. “You are disorganized” is a character attack. “Task completion rate was 65% against a target of 90%, with missed deadlines on three client deliverables” is professional feedback. Stick to behaviors and outcomes.

How to use time tracking data in performance reports

One of the biggest challenges in performance reporting is gathering objective evidence. Subjective observations are important, but they become much more credible when paired with data.

actiTIME gives managers a data layer for performance reports that most review processes lack. Because every team member logs their time against specific tasks organized in a Customer, Project, and Task hierarchy, managers can pull concrete numbers instead of relying on recall.

The reports most useful for performance evaluations are:

Staff Performance Report. Shows how each person distributes their working hours across tasks and projects. During a performance review, this data answers questions like: Is this person spending their time on the right priorities? Are they spread too thin across too many projects? How does their time allocation compare to what was planned?

Estimates vs. Actual Time Report. Compares the estimated hours for each task against the actual hours logged. If an employee consistently finishes tasks in half the estimated time, that is evidence of strong efficiency. If tasks regularly take twice the estimate, it may signal a need for training, process improvement, or more realistic estimation.

Time Balance and Overtime Report. Shows whether an employee is working their contracted hours, falling short, or regularly logging overtime. Chronic overtime is an early indicator of burnout or workload imbalance. Including this data in a performance report opens a conversation about sustainability, not just output.

Time-Track Report. Provides a detailed log of what was worked on, when, and for how long. Useful when the review discussion gets into specifics about a particular project or time period.

Rather than replacing subjective evaluation, time tracking data supplements it. When a manager writes “consistently meets deadlines and manages workload effectively,” the time tracking data provides the evidence: tasks completed within estimates, balanced weekly hours, no pattern of last-minute overtime spikes.

Start a free 30-day actiTIME trial to see how time tracking data can strengthen your next round of performance reviews.

We reduced payroll processing to 45 minutes per week

actiTIME is very robust, integrated well into your business process, and most important, helps you focus on your business instead of monkeying around with technology. actiTIME has reduced our payroll processing from 4-6 hours per week to 45 minutes per week.

Try actiTIME

FAQ

How do you write a performance report for an employee?

Start by gathering objective data: time tracking records, project outcomes, customer feedback, and notes from throughout the review period. Review the goals set in the previous cycle and document whether each was met, partially met, or not met. Write the accomplishments section first, then areas for improvement with actionable language (what needs to change, the current state, and the target). End with two to four measurable goals for the next period.

What are the 5 key performance indicators for employees?

The most commonly used employee KPIs are quality of work (error rates, customer satisfaction scores, rework frequency), productivity (output volume, tasks completed per period), attendance and punctuality (days absent, pattern of tardiness), goal completion (percentage of objectives met within the review period), and professional development (skills acquired, certifications earned, training completed). The right KPIs depend on the role; a customer support agent’s indicators look different from a software developer’s.

What is the difference between a performance review and a performance report?

A performance review is the full process: gathering data, writing the evaluation, conducting the conversation, and setting future goals. A performance report is the written document that comes out of that process. The report is one component of the review. Some organizations use the terms interchangeably, but the distinction matters because a report without a discussion is less effective, and a discussion without a written record leaves nothing to reference later.