Performance Management

Performance Management

Help employees understand expectations, improve performance and reach meaningful goals. Explore practical guidance for performance reviews, feedback, goal setting and performance improvement.

Popular topics:
Performance reviews • Feedback • Goals • Coaching • Performance improvement • Documentation

How to Conduct an Employee Performance Review: A Complete Guide for Managers

Category: Performance Management
Reading time: 12–15 minutes
Last updated: September 2026

An employee performance review should be more than a form completed once a year.

A well-run performance review gives managers and employees dedicated time to discuss accomplishments, expectations, challenges, development, goals, and ways to improve. It can also help employees understand how their work contributes to broader business objectives.

A poorly managed review can have the opposite effect. Employees may leave confused about expectations, surprised by feedback, or uncertain about what they should do differently.

The difference is usually not the form itself. It is the quality of the conversation.

This guide explains how to prepare for, conduct, document, and follow up on an effective employee performance review.

Free Resource: Download the HROfficials Employee Performance Review Template and use it to structure your next review conversation.

What Is an Employee Performance Review?

An employee performance review is a structured conversation between an employee and manager about the employee’s work, performance, goals, development, and expectations.

Depending on the organization, a review may be:

  • Annual
  • Semiannual
  • Quarterly
  • Project-based
  • New-hire or probationary
  • Promotion-related
  • Development-focused

Some companies combine formal reviews with more frequent informal check-ins.

The exact process should fit the organization’s size, culture, type of work, and management style.

The purpose should be clear:

Understand performance, provide useful feedback, recognize contributions, address gaps, and establish clear next steps.

Why Performance Reviews Matter

A thoughtful performance review can help both employees and managers.

Employees can gain:

  • Clearer expectations
  • Recognition for accomplishments
  • Useful feedback
  • Development opportunities
  • Better understanding of priorities
  • Support for career growth

Managers can gain:

  • A structured opportunity to discuss performance
  • Better understanding of employee challenges
  • A record of goals and development discussions
  • Greater clarity about support and training needs

Organizations can gain:

  • Better alignment around goals
  • More consistent management practices
  • Improved employee development
  • Better identification of skill gaps
  • More useful workforce information

A performance review should not be the only time an employee receives feedback.

When managers save every piece of feedback for one annual conversation, the review can become overwhelming and less useful.

A better approach is:

Regular check-ins + ongoing feedback + periodic formal reviews

How Often Should Performance Reviews Be Conducted?

There is no single schedule that works for every company.

Possible approaches include:

Annual Review

One formal review each year.

Simple, but it can create too much pressure around one conversation.

Semiannual Review

Two formal reviews each year.

This gives managers more opportunities to adjust goals.

Quarterly Review

A formal conversation every three months.

Useful for fast-changing environments.

Continuous Feedback

Regular one-on-one conversations supplemented by a formal review when appropriate.

For many organizations, a combination works well.

For example:

Weekly or biweekly one-on-one

plus

Quarterly goal review

plus

Annual formal performance review

The ideal schedule depends on the organization and the type of work.

Before the Performance Review

The quality of a review depends heavily on preparation.

Don’t schedule the meeting and start thinking about the employee’s performance five minutes beforehand.

Prepare in advance.

Step 1: Review the Employee’s Job Description

Start with the actual role.

Ask:

  • What are this employee’s primary responsibilities?
  • What outcomes are expected?
  • What skills are required?
  • What does successful performance look like?

If the job has changed significantly since the description was created, update your understanding before evaluating the employee.

An employee should generally be evaluated against responsibilities and expectations that are actually relevant to their role.

Step 2: Review Previous Goals

Look at the goals established during the previous review or planning period.

For each goal, determine whether it was:

Completed

Partially completed

Not completed

No longer applicable

Changed because of circumstances

Do not automatically label an unfinished goal as poor performance.

Ask what happened.

Perhaps:

  • Priorities changed
  • Resources changed
  • The employee was assigned different work
  • A project was delayed for reasons outside the employee’s control
  • The original goal was unrealistic

Performance reviews should consider context.

Step 3: Review Specific Examples

Avoid vague statements such as:

“You have done a good job.”

or:

“You need to communicate better.”

Instead, gather specific examples.

For example:

“During the customer migration project in March, you identified a reporting problem before launch and worked with the operations team to correct it.”

Specific examples make feedback easier to understand and act on.

Step 4: Review Employee Accomplishments

Give the employee an opportunity to identify accomplishments.

Ask:

What are you most proud of accomplishing during this review period?

This can reveal contributions managers may not have seen directly.

Review:

  • Completed projects
  • Revenue or cost impact where relevant
  • Customer outcomes
  • Process improvements
  • Quality improvements
  • Team contributions
  • New skills
  • Certifications
  • Leadership activities

Don’t focus only on large projects.

Consistent execution of core responsibilities matters too.

Step 5: Identify Performance Gaps

Before the meeting, identify areas where performance is below expectations.

For each issue, ask:

  1. What happened?
  2. What was expected?
  3. What evidence supports the concern?
  4. Has the employee previously received feedback?
  5. Does the employee have the resources and training needed?
  6. What improvement is expected?
  7. How will progress be measured?

This makes the conversation more objective.

Step 6: Prepare Development Opportunities

A performance review should not only ask:

“How did you perform?”

It should also ask:

“How can you grow?”

Consider:

  • Training
  • Stretch assignments
  • New responsibilities
  • Mentoring
  • Job shadowing
  • Certifications
  • Leadership opportunities
  • New projects

Not every development opportunity needs to be expensive.

Sometimes the best development opportunity is meaningful work.

Step 7: Give the Employee Time to Prepare

Tell employees in advance:

  • The purpose of the review
  • What will be discussed
  • Whether they need to complete a self-assessment
  • Whether they should prepare accomplishments or goals
  • How long the meeting will last

Don’t surprise someone with an annual review conversation.

The Employee Self-Assessment

A self-assessment can help employees reflect before the conversation.

Useful questions include:

Accomplishments

What accomplishments are you most proud of?

Challenges

What challenges affected your work?

Skills

What skills have you developed?

Support

What support would help you be more successful?

Goals

What would you like to accomplish next?

Development

What skills would you like to strengthen?

The purpose is not to create extra paperwork.

It is to encourage reflection and create better discussion.

Step 8: Schedule the Meeting Properly

Choose a time when you won’t be interrupted.

Avoid squeezing a performance review between two unrelated meetings.

A typical review might take:

30–60 minutes

More complex roles may need longer.

Choose a private setting appropriate to the workplace, whether the meeting is onsite or virtual.

How to Start the Performance Review

The opening tone matters.

Begin with context and purpose.

For example:

“I’d like to use today’s conversation to review your accomplishments, discuss what’s going well, talk through areas where we can improve, and agree on your priorities for the next review period.”

This makes the purpose clear.

Then invite the employee to start.

“Before I share my feedback, how do you feel the past review period went?”

Listening first can provide valuable context.

A Five-Part Performance Review Structure

A simple structure is:

1. Accomplishments

What went well?

2. Performance

How does current performance compare with expectations?

3. Challenges

What is getting in the way?

4. Development

What should the employee learn or improve?

5. Goals

What should happen next?

This keeps the conversation balanced.

Discuss Accomplishments First

Recognition should be specific.

Instead of:

“Great job this year.”

Try:

“You took ownership of the new customer reporting process and reduced the time required to prepare the monthly report.”

Then explain the impact.

“That gave the team earlier visibility into the numbers and reduced last-minute corrections.”

Specific recognition tells the employee what behavior should continue.

Discuss Areas for Improvement

This is often the most difficult part of a performance review.

Use a clear structure:

Situation

Describe what happened.

Behavior

Explain what the employee did.

Impact

Explain the effect.

Expectation

Explain what should happen going forward.

Example:

“During the last two project handoffs, the documentation was incomplete. That caused the receiving team to spend additional time clarifying information. Going forward, I need the handoff checklist completed before each project is transferred.”

This is much more useful than:

“You need to be more organized.”

Focus on Behavior and Results

Avoid making broad statements about personality.

Instead of:

“You’re not a team player.”

Try:

“During the last project, you often completed work independently without updating the rest of the team. That made it harder for others to coordinate their work. I’d like you to provide status updates during the agreed team checkpoints.”

The second version focuses on observable behavior.

Ask Questions During the Review

A review should be a conversation, not a lecture.

Useful questions include:

About Performance

What do you think went particularly well?

What would you do differently?

About Challenges

What obstacles affected your performance?

Is there something you need from me that you aren’t currently getting?

About Development

What skill would you most like to develop?

What type of project would challenge you in a useful way?

About the Manager

How can I better support you?

About the Future

What would you like to accomplish during the next review period?

These questions can turn a one-way evaluation into a collaborative planning conversation.

How to Give Constructive Feedback

Good feedback should be:

Specific

Relevant

Timely

Respectful

Actionable

Instead of:

“Your communication needs work.”

Say:

“In team meetings, I’d like you to provide a brief status update on your projects and raise risks earlier so the team has more time to respond.”

Now the employee knows what to change.

How to Give Positive Feedback

Positive feedback should also be specific.

Instead of:

“You’re a great employee.”

Say:

“You consistently respond to customer issues quickly, and your documentation has made it easier for other team members to understand the history of each case.”

Then explain why it matters.

“That consistency has helped improve the team’s response time.”

Recognition is most useful when employees understand exactly what behavior or result was valuable.

What to Do When Performance Is Below Expectations

Sometimes a review confirms that an employee is not meeting expectations.

Don’t minimize the problem.

But don’t turn the discussion into a personal attack.

Clarify:

The expectation

What should the employee be doing?

The current situation

What is happening instead?

The evidence

What specific examples demonstrate the gap?

The impact

Why does the gap matter?

The improvement required

What needs to change?

The support

What training, resources, or management support will be provided?

The timeline

When will progress be reviewed?

For serious or persistent performance issues, the employer should follow its established policies and procedures and obtain appropriate HR or legal guidance when necessary.

Performance Improvement Plans

A Performance Improvement Plan, commonly called a PIP, may be appropriate in some circumstances when an employee has significant performance concerns.

A useful plan should clearly identify:

  • Performance concern
  • Expected standard
  • Required improvement
  • Specific actions
  • Available support
  • Measurement method
  • Review dates
  • Consequences or next steps consistent with company policy

A PIP should not be used simply as a vague warning.

It should establish a clear path toward improvement.

Not every performance problem requires a formal PIP. Organizations should apply their processes consistently and seek appropriate HR or legal guidance for complex situations.

Setting Effective Performance Goals

A performance review should end with clear next steps.

One commonly used framework is SMART goals:

Specific

Clearly define what needs to happen.

Measurable

Identify how progress will be assessed.

Achievable

The goal should be reasonably attainable given available resources and circumstances.

Relevant

Connect the goal to the employee’s role and organizational priorities.

Time-bound

Establish a timeframe.

Weak goal

Improve customer service.

Stronger goal

Reduce average customer response time to the department’s established target by the end of the next quarter while maintaining required quality standards.

The exact target should reflect the role and organization’s actual metrics.

Example Performance Goals

Customer Service

Improve response-time performance while maintaining customer service quality standards.

Sales

Achieve the agreed quarterly sales target while maintaining required customer retention standards.

HR

Complete onboarding documentation for new employees within the organization’s established turnaround time.

Operations

Identify and implement two process improvements that reduce avoidable processing delays during the next review period.

Management

Conduct regular one-on-one meetings with direct reports and document agreed development priorities.

Goals should be customized rather than copied from a generic list.

Career Development During the Review

Performance and career development aren’t exactly the same thing.

Someone can perform their current role exceptionally well without necessarily being ready for a promotion.

Discuss both separately.

Ask:

What type of work would you like to learn?

What responsibilities interest you?

What skills do you want to build?

What experience would prepare you for your next career step?

Then identify realistic actions.

For example:

Development Goal

Develop presentation skills.

Action

Lead one team presentation each month for the next quarter.

Support

Manager provides feedback after each presentation.

Success Measure

Employee can independently present project updates to stakeholders.

Don’t Promise Promotions During a Performance Review Unless They Are Actually Approved

Employees may ask:

“Am I ready for a promotion?”

Answer honestly.

If a promotion has been approved, explain the relevant details.

If it hasn’t:

“Let’s discuss the responsibilities and skills required for the next level and identify the experiences you need to build toward that goal.”

Don’t create an implied promise through vague language.

How to Close the Meeting

End with a summary.

Review:

  • Main accomplishments
  • Key improvement areas
  • Development priorities
  • New goals
  • Support needed
  • Follow-up dates

Ask:

“What are the most important takeaways you’re leaving with?”

Then:

“Is there anything we haven’t discussed that you think is important?”

Finally, agree on the next check-in.

Document the Performance Review

After the conversation, document the key points.

Include:

  • Review date
  • Employee name
  • Manager
  • Review period
  • Accomplishments
  • Performance observations
  • Agreed goals
  • Development actions
  • Follow-up dates
  • Appropriate employee comments

Keep documentation factual and professional.

Avoid emotional statements such as:

“Employee doesn’t care.”

Instead:

“Employee missed three agreed deadlines during the review period.”

Then provide relevant context.

Employee Comments

Give employees an opportunity to add comments to the review.

They may:

  • Agree with the assessment
  • Provide additional context
  • Clarify circumstances
  • Identify support needs
  • Comment on goals

The employee’s perspective is valuable even when it differs from the manager’s.

What Managers Should Avoid

1. Surprises

Don’t introduce serious performance concerns for the first time during an annual review if they should have been addressed earlier.

2. Recency Bias

Don’t evaluate an entire year based mostly on what happened last month.

Review the full period.

3. Favoritism

Use the same standards for employees performing comparable roles while accounting for legitimate differences in responsibilities and circumstances.

4. Personality Judgments

Evaluate behavior and results rather than labels.

5. Vague Feedback

“Do better” isn’t an action plan.

6. Comparing Employees

Focus on the employee’s responsibilities and expectations rather than saying:

“You’re not as good as Sarah.”

7. Rating Everything as Outstanding

If everyone receives the highest rating regardless of performance, the rating system loses meaning.

8. Talking Too Much

Managers sometimes spend the entire meeting giving feedback.

Listen.

9. Ignoring Context

Consider changes in priorities, resources, role expectations, and circumstances.

10. Failing to Follow Up

A performance review without follow-up is often just paperwork.

How to Make Performance Reviews More Effective

Keep the Conversation Ongoing

Don’t wait until review day to discuss important issues.

Use regular one-on-ones.

Make Goals Visible

Keep goals accessible throughout the review period.

Provide Specific Examples

Evidence is more useful than general impressions.

Encourage Employee Input

Employees should have opportunities to explain challenges and propose ideas.

Track Progress

Schedule follow-ups.

Separate Performance From Personality

Evaluate what the employee does and achieves.

Focus on the Future

The most valuable question after discussing the past is:

What should happen next?

Performance Review Questions for Managers

Use these questions during the conversation.

Accomplishments

  1. What accomplishment are you most proud of?
  2. Which project had the greatest impact?
  3. What contribution do you think was most valuable?

Performance

  1. Which responsibilities are going particularly well?
  2. Where do you think you can improve?
  3. What obstacles affected your performance?

Development

  1. What skill would you like to strengthen?
  2. What type of work would you like more exposure to?
  3. What support would help you grow?

Management

  1. How can I better support you?
  2. Is there anything I could do differently as your manager?

Future

  1. What are your most important goals for the next review period?
  2. What would you like to accomplish in the next six months?
  3. What resources do you need to achieve those goals?

Simple Employee Performance Review Template

Employee Information

Employee: __________________________

Position: __________________________

Manager: __________________________

Review Period: _____________________

Review Date: _______________________

1. Key Accomplishments

What did the employee accomplish during the review period?

2. Performance Strengths

What does the employee consistently do well?

3. Areas for Improvement

What specific behaviors, skills, or results need improvement?

4. Goals

GoalMeasureTarget Date

5. Development Plan

Skill to develop: __________________________

Development action: ________________________

Support needed: ___________________________

Target date: ______________________________

6. Employee Comments

7. Manager Comments

8. Follow-Up

Next check-in date: ________________________

Additional notes: __________________________

Performance Review Rating Scale

If your organization uses ratings, define them clearly.

5 — Exceptional

Performance consistently and significantly exceeds expectations.

4 — Exceeds Expectations

Performance frequently exceeds the expected standard.

3 — Meets Expectations

Performance consistently meets the expected standard.

2 — Needs Improvement

Performance sometimes falls below expectations and requires improvement.

1 — Does Not Meet Expectations

Performance consistently falls below the required standard.

Not every organization needs numerical ratings. A narrative-based system may work better for some businesses.

If ratings are used, managers should understand what each rating means and apply the definitions consistently.

A Better Way to Think About Performance Reviews

Instead of viewing the process as:

Manager evaluates employee

think of it as:

Manager + employee review performance + solve problems + plan next steps

That shift matters.

The purpose isn’t to “win” the conversation.

The purpose is to make expectations clearer and help the employee and organization move forward.

The HROfficials Performance Review Checklist

Before the Meeting

☐ Review job description

☐ Review previous goals

☐ Gather examples

☐ Review accomplishments

☐ Identify performance concerns

☐ Prepare development opportunities

☐ Review employee self-assessment

☐ Schedule private meeting

☐ Give employee preparation time

During the Meeting

☐ Explain the purpose

☐ Discuss accomplishments

☐ Ask employee for perspective

☐ Review performance against expectations

☐ Give specific feedback

☐ Discuss challenges

☐ Discuss development

☐ Establish goals

☐ Agree on support

☐ Set follow-up date

☐ Allow time for questions

After the Meeting

☐ Document discussion

☐ Finalize goals

☐ Record employee comments

☐ Share appropriate documentation

☐ Schedule follow-up

☐ Monitor progress

☐ Provide ongoing feedback

Final Thoughts

A good performance review should leave the employee with greater clarity than they had before the meeting.

They should understand:

What am I doing well?

Where do I need to improve?

What does my manager expect?

What support is available?

What should I accomplish next?

The best performance review systems don’t rely on one annual conversation.

They create a rhythm of:

Expectations → Feedback → Support → Goals → Follow-up

When those conversations happen consistently, the formal review becomes a summary of an ongoing process rather than a stressful surprise.

And that is usually where performance management becomes genuinely useful.

Download the Free HROfficials Employee Performance Review Template

Need a simple structure for your next employee review?

Download the HROfficials Employee Performance Review Template and use it to organize:

  • Employee accomplishments
  • Performance strengths
  • Areas for improvement
  • Goals
  • Development plans
  • Manager comments
  • Employee comments
  • Follow-up actions

[DOWNLOAD THE FREE PERFORMANCE REVIEW TEMPLATE]

Frequently Asked Questions

How often should employees receive performance reviews?

There is no universal schedule. Organizations may use annual, semiannual, quarterly, or ongoing feedback approaches. Many companies combine regular manager check-ins with periodic formal reviews.

What should be discussed during a performance review?

A performance review can cover accomplishments, performance against expectations, challenges, feedback, development, goals, support needs, and future priorities.

Should performance reviews include ratings?

They can, but ratings aren’t required. If ratings are used, organizations should define the scale clearly and train managers to apply it consistently.

What should I do if an employee disagrees with the performance review?

Listen to the employee’s explanation and review any specific evidence they provide. Clarify expectations and document the employee’s perspective appropriately. Follow your organization’s review and escalation procedures.

Should negative feedback be included in an annual performance review?

Relevant performance concerns should be addressed honestly and specifically. However, significant problems generally should not be saved exclusively for an annual review. Employees should receive appropriate feedback when issues arise so they have a meaningful opportunity to improve.

What is the difference between a performance review and a performance improvement plan?

A performance review is a broader assessment and development conversation. A Performance Improvement Plan is a more formal document that may be used in certain situations to address specific performance deficiencies, expected improvements, support, timelines, and follow-up.

Should employees be allowed to comment on their performance review?

Giving employees an opportunity to provide comments can add context and encourage a two-way conversation. Organizations should follow their established documentation process.

Disclaimer

This article provides general HR information for educational and planning purposes and is not legal advice. Performance management, documentation, discipline, compensation, termination, discrimination, accommodation, and related employment practices can be subject to federal, state, and local requirements. Organizations should obtain appropriate professional advice for legally sensitive situations and follow their applicable policies and procedures.

How to Document Employee Performance Issues: Complete Guide for Managers

Category: Performance Management
Reading time: 12–15 minutes
Last updated: September 2026

When an employee isn’t meeting expectations, good documentation can help managers communicate clearly, track improvement, and maintain an accurate record of what was discussed.

Poor documentation can create the opposite problem.

Statements such as:

“Bad attitude.”

“Not reliable.”

“Doesn’t care.”

don’t explain what actually happened.

Effective documentation focuses on specific behavior, expectations, dates, impact, employee response, and next steps.

This guide explains how managers and HR professionals can document employee performance issues clearly, objectively, and consistently.

Free Resource: Download the HROfficials Employee Performance Documentation Template to record performance concerns, coaching conversations, expectations, action plans, and follow-up dates.

What Is Employee Performance Documentation?

Employee performance documentation is a written record of relevant workplace performance concerns, feedback, expectations, coaching, goals, and follow-up.

It can document:

  • Missed deadlines
  • Quality problems
  • Attendance issues
  • Failure to follow established procedures
  • Communication concerns
  • Customer-service issues
  • Productivity concerns
  • Performance discussions
  • Coaching
  • Training provided
  • Improvement expectations
  • Follow-up meetings

Documentation should describe what happened rather than simply labeling the employee.

Why Document Employee Performance Issues?

Documentation can serve several practical purposes.

1. Clarify Expectations

Written documentation gives employees a clear understanding of what is expected.

2. Support Coaching

Managers can use documented examples to discuss performance constructively.

3. Track Progress

Documentation makes it easier to see whether performance is improving.

4. Maintain Consistency

A documented process can help managers apply expectations more consistently.

5. Preserve Important Information

People change roles, managers change, and memories fade. A factual record can preserve relevant information.

6. Support Formal HR Processes

When appropriate, documentation may become part of a broader performance-management process.

Documentation should not be created simply to “build a case” against an employee. It should accurately reflect the organization’s legitimate management process.

The Most Important Rule: Document Facts, Not Conclusions

Compare these two statements.

Poor

John has a bad attitude and is not committed to his work.

Better

On September 3, John did not attend the required 9:00 a.m. team meeting and did not notify his manager. On September 5, he missed the 2:00 p.m. project deadline without providing an update.

The second version gives you information that another manager could actually evaluate.

Ask yourself:

Could someone who wasn’t present understand what happened from my notes?

If the answer is no, the documentation probably needs to be more specific.

What Good Documentation Includes

A useful performance record generally answers:

Who?

Who was involved?

What?

What happened?

When?

When did it happen?

Where?

Where did it happen, when relevant?

What was expected?

What standard, deadline, policy, or instruction applied?

What was the impact?

What happened because of the performance issue?

What did the employee say?

What explanation or context did the employee provide?

What happens next?

What expectations, support, or follow-up were established?

This framework creates a practical record without unnecessary speculation.

Step 1: Identify the Specific Performance Issue

Don’t start by writing:

“Employee is underperforming.”

Identify the actual concern.

Examples:

  • Missed a project deadline
  • Made repeated data-entry errors
  • Failed to complete required training
  • Did not follow the documented process
  • Failed to respond to customers within the established timeframe
  • Frequently arrived after the scheduled start time
  • Submitted incomplete reports

The more specific the issue, the easier it is to address.

Step 2: Describe the Expected Standard

An employee cannot reasonably be expected to meet a standard that has never been communicated or established.

Document what the employee was expected to do.

For example:

The weekly inventory report is due every Friday by 3:00 p.m.

or:

Customer inquiries received through the support system should be acknowledged according to the department’s established response standard.

or:

Employees are expected to follow the documented expense-reporting procedure.

The expectation should be connected to an established job responsibility, policy, procedure, goal, or instruction where applicable.

Step 3: Record the Date

Dates matter.

Instead of:

“This has been happening for a while.”

write:

“The issue occurred on August 14, August 21, and September 2.”

Specific dates make the record much more useful.

Where relevant, include:

  • Date
  • Time
  • Meeting
  • Project
  • Location
  • Related document or system record

Don’t add details that aren’t relevant.

Step 4: Describe What Happened

Use neutral language.

Example

On September 2, the employee submitted the weekly report at 5:18 p.m. The stated deadline was 3:00 p.m. The report was missing the sales-summary section.

Avoid:

“The employee clearly wasn’t taking the deadline seriously.”

The second statement is an assumption about intent.

You generally don’t know what the employee was thinking.

Document what you can establish.

Step 5: Explain the Work-Related Impact

A performance issue matters because it affects work.

Explain the impact when it is relevant.

For example:

Because the report was incomplete, the manager could not finalize the weekly department summary until the following morning.

Or:

The missed deadline required another team member to complete the remaining work.

Or:

The incomplete customer record caused the next team to repeat information-gathering steps.

Impact gives context.

Step 6: Record Previous Feedback

If the issue has been discussed previously, document that fact.

Example:

During the August 15 one-on-one meeting, the manager reviewed the expectation that weekly reports be submitted by 3:00 p.m. and reminded the employee to communicate potential delays in advance.

This creates a record of the communication.

Don’t write:

“I’ve told him a hundred times.”

That’s emotional and imprecise.

Instead:

“The expectation was reviewed during the August 15 and August 29 one-on-one meetings.”

Step 7: Give the Employee an Opportunity to Respond

Documentation should not assume that the manager has the complete story.

Ask:

“Can you walk me through what happened?”

Then record the relevant response.

Example:

The employee stated that the reporting system was unavailable for approximately two hours and that they did not realize the report had to be completed by 3:00 p.m.

Now the manager can investigate whether the system issue and communication gap were relevant.

Listening doesn’t mean accepting every explanation automatically.

It means considering relevant information before deciding what happens next.

Step 8: Document Support Provided

If the employee needs help, record what support was offered.

Examples:

Manager reviewed the reporting procedure with the employee.

Employee was provided access to the updated training guide.

Manager offered weekly check-ins for the next four weeks.

Employee was referred to the appropriate HR resource for questions related to the policy.

This is important because performance management should generally involve more than simply criticizing a problem.

Step 9: State the Required Improvement

Don’t end the conversation with:

“Try harder.”

Give a measurable expectation where practical.

Example:

Beginning September 9, all weekly reports are expected to be submitted by 3:00 p.m. every Friday and should include all required sections.

That’s much clearer.

Step 10: Establish a Follow-Up Date

A performance conversation should usually have a next step.

For example:

Manager and employee will review progress during weekly one-on-one meetings for the next four weeks.

Or:

Progress will be reviewed on October 1.

The follow-up should be realistic for the issue.

A Simple Documentation Formula

A practical structure is:

Date → Situation → Expected Standard → Observed Behavior → Impact → Employee Response → Support → Required Improvement → Follow-Up

Example:

Date: September 3
Situation: Weekly sales-report submission
Expected standard: Report due by 3:00 p.m. Friday
Observed behavior: Report submitted at 5:18 p.m. and did not include the required regional summary
Impact: Manager could not complete the department report until the following morning
Employee response: Employee stated that they encountered a reporting-system issue
Support: Manager reviewed the system process and provided the IT support contact
Required improvement: Submit complete reports by 3:00 p.m. and notify the manager before the deadline if a technical issue may cause a delay
Follow-up: Review next four reports during weekly one-on-one meetings

This is a strong foundation for a factual performance record.

Examples of Poor vs. Better Documentation

Example 1: Attendance

Poor

Sarah is always late.

Better

Sarah arrived after the scheduled 8:30 a.m. start time on September 2 at 8:47 a.m., September 5 at 8:52 a.m., and September 8 at 8:46 a.m. The attendance expectation was reviewed during the September 5 conversation. Sarah stated that she has been experiencing transportation delays.

The manager can then determine the appropriate next step under the organization’s attendance process.

Example 2: Quality

Poor

Mike’s work is sloppy.

Better

Of the 20 customer records reviewed on September 4, four contained missing required fields. The required fields are identified in the department’s customer-record procedure. The manager reviewed the procedure with Mike and requested that future records be checked against the required-field checklist before submission.

Example 3: Communication

Poor

Emma has terrible communication skills.

Better

During the September 6 project meeting, Emma interrupted two coworkers while they were providing status updates. The manager reminded the team that each participant should be allowed to complete their update before questions or comments are raised. The manager and Emma discussed the communication expectation privately after the meeting.

Example 4: Missed Deadline

Poor

David doesn’t care about deadlines.

Better

The client proposal was due internally by September 5 at noon. David submitted the proposal at 4:20 p.m. The manager had previously discussed the internal deadline during the August 29 project meeting. The delay resulted in a shortened review period before the client submission.

Example 5: Failure to Follow a Process

Poor

Lisa refuses to follow instructions.

Better

The department procedure requires customer requests to be entered into the CRM on the day they are received. On September 3, five requests received that day were not entered until September 4. The manager reviewed the procedure with Lisa and discussed the expectation that future requests be entered according to the established process.

Use Neutral Language

The words you choose matter.

Instead of:

“Lazy”

Use:

“Did not complete assigned tasks by the established deadlines.”

Instead of:

“Unprofessional”

Use:

“Used language during the meeting that did not meet the organization’s communication expectations.”

Instead of:

“Bad attitude”

Use:

“Responded to the manager in a raised voice during the September 4 discussion.”

Instead of:

“Not a team player”

Use:

“Did not provide requested project information to the team by the agreed deadline.”

Instead of:

“Doesn’t care”

Use:

“Did not complete the required follow-up after receiving the assignment.”

Specific descriptions are much easier to understand and evaluate.

Avoid Speculation About Motive

Don’t assume why someone behaved a certain way.

Avoid:

“He missed the deadline because he was lazy.”

You don’t know that.

Instead:

“The deadline was missed by two business days. The employee stated that competing project priorities contributed to the delay.”

Now the record distinguishes:

Observed fact

from

Employee explanation

Document Conversations Promptly

Write notes as soon as practical after an important conversation.

Memory becomes less reliable over time.

Include:

  • Date
  • Main topic
  • Important facts
  • Employee response
  • Agreed expectations
  • Next steps

Don’t try to recreate months of conversations from memory.

For recurring performance issues, contemporaneous documentation is generally more useful than a long retrospective summary.

Keep Documentation Confidential

Performance documentation often contains sensitive employee information.

Store it securely.

Limit access to people who have a legitimate business reason to see it.

Avoid putting sensitive performance records in:

  • Public team folders
  • Shared chat channels
  • General project documents
  • Email threads with unnecessary recipients

Follow your organization’s recordkeeping and privacy procedures.

Separate Performance Notes From Personal Opinions

Managers sometimes write notes such as:

“I don’t trust this employee.”

or:

“She’s probably looking for another job.”

These statements are generally not useful.

Ask:

What workplace fact do I actually need to record?

If you can’t connect the statement to a legitimate workplace issue, leave it out.

Don’t Overdocument Every Minor Issue

Documentation doesn’t mean creating an incident report for every tiny mistake.

Use judgment.

A minor, isolated error may be handled through ordinary coaching.

More formal documentation may be appropriate when:

  • Problems repeat
  • The issue is significant
  • Expectations have been clearly communicated
  • The employee has received coaching
  • The problem affects business operations
  • A formal performance process is underway

Follow your organization’s established practices.

Document Positive Performance Too

Documentation isn’t only for problems.

Managers should also record significant accomplishments.

Examples:

Successfully completed the customer migration project two weeks ahead of the planned schedule.

Received positive customer feedback for resolving a complex service issue.

Trained two new team members on the department’s workflow.

Positive documentation creates a more complete view of performance.

It can also make future performance reviews much easier.

Performance Documentation vs. Disciplinary Documentation

These are related but not necessarily identical.

Performance Documentation

May include:

  • Coaching
  • Feedback
  • Goals
  • Development
  • Expectations
  • Progress reviews

Disciplinary Documentation

May address:

  • Policy violations
  • Formal corrective action
  • Repeated misconduct
  • Serious workplace concerns

Organizations should use their own policies and processes to determine how these records are handled.

What if the Employee Disagrees?

Employees don’t always agree with a manager’s assessment.

That doesn’t automatically mean the documentation is wrong.

Allow the employee to provide their perspective.

For example:

The employee disagreed that the deadline had been clearly communicated and stated that the project instructions had changed on September 1.

Then investigate relevant facts.

If the employee provides information that changes the situation, update the record appropriately.

Avoid turning the documentation into an argument.

What If the Employee Refuses to Sign?

Some organizations ask employees to sign performance documentation.

An employee may disagree with the contents or decline to sign.

Don’t tell the employee:

“Signing means you agree with everything.”

An acknowledgment may simply confirm that the employee received the document, depending on the organization’s process.

Follow your established policy for acknowledgments and refusals.

Document the refusal accurately rather than arguing about it.

When a Performance Problem May Require HR

Managers should consider involving HR or appropriate leadership when:

  • The issue is recurring
  • Previous coaching hasn’t worked
  • Formal discipline is being considered
  • A Performance Improvement Plan may be appropriate
  • The employee raises a discrimination concern
  • The employee raises a harassment concern
  • An accommodation or leave issue arises
  • Retaliation is alleged
  • Termination is being considered
  • The issue involves a serious policy violation
  • There may be significant legal or compliance implications

Don’t wait until the end of a difficult situation to involve HR when your organization’s procedures call for earlier involvement.

Performance Improvement Plans

A Performance Improvement Plan, or PIP, may be used in some situations involving ongoing performance deficiencies.

A useful plan should explain:

Performance concern

What isn’t meeting expectations?

Required standard

What should happen instead?

Action

What does the employee need to do?

Measurement

How will improvement be evaluated?

Support

What assistance will be provided?

Timeline

When will progress be reviewed?

Consequences

What may happen if expectations aren’t met, consistent with applicable policy and requirements?

A PIP should be specific enough that both the employee and manager understand what improvement means.

Not every performance issue requires a PIP.

Example Performance Improvement Documentation

Performance Concern

Three project deliverables were submitted after the agreed internal deadline during the past six weeks.

Expected Standard

Project deliverables should be submitted by the deadlines documented in the project plan.

Required Improvement

All assigned deliverables should be completed by the established deadlines. If an issue may prevent timely completion, the employee should notify the manager as soon as reasonably possible.

Support

Manager will review project priorities with the employee during weekly one-on-one meetings for the next six weeks.

Measurement

Timely completion of assigned deliverables during the review period.

Follow-Up

Progress will be reviewed weekly.

This is more useful than:

“Improve your time management.”

How Long Should You Keep Performance Documentation?

There is no universal retention period that applies to every type of employee record in every organization.

Retention requirements can depend on:

  • Type of record
  • Applicable federal law
  • State law
  • Local requirements
  • Industry
  • Employer size
  • Whether a dispute or investigation exists
  • Internal policy

For that reason, use your organization’s records-retention policy and obtain appropriate professional guidance where necessary.

Don’t delete records simply because an employee has improved if applicable retention requirements or a litigation hold require preservation.

Electronic Performance Documentation

Modern organizations may use:

  • HRIS systems
  • Performance-management software
  • Secure document systems
  • Employee portals
  • Digital forms

The technology doesn’t change the basic principles.

Digital documentation should still be:

Accurate

Relevant

Secure

Objective

Accessible to authorized users

Retained appropriately

Avoid creating a confusing collection of notes across email, spreadsheets, chat messages, and personal files.

Manager Documentation Checklist

Before saving a performance note, ask:

☐ Did I identify the date?

☐ Did I describe what actually happened?

☐ Did I identify the expectation?

☐ Did I explain the work-related impact?

☐ Did I avoid assumptions about motives?

☐ Did I record the employee’s relevant response?

☐ Did I document coaching or support provided?

☐ Did I state the required improvement?

☐ Did I identify the next follow-up?

☐ Is the documentation professional and objective?

☐ Is it stored securely?

If the answer to these questions is yes, the documentation is much more likely to be useful.

A Complete Performance Issue Documentation Example

Employee

John Smith

Position

Operations Coordinator

Date

September 8, 2026

Issue

Late weekly reporting

Expected Standard

The department’s weekly operations report is due by 3:00 p.m. each Friday.

Observed Performance

The reports submitted on August 21, August 28, and September 4 were received after the 3:00 p.m. deadline. The September 4 report was also missing two required sections.

Business Impact

The delay prevented the manager from completing the weekly department summary on schedule and required follow-up work the following morning.

Previous Coaching

The reporting deadline and required sections were reviewed during the August 28 one-on-one meeting.

Employee Response

John stated that he had difficulty prioritizing the reporting work while supporting an urgent customer project.

Manager Response

The manager reviewed priority-setting expectations and asked John to notify the manager when competing assignments could affect a reporting deadline.

Required Improvement

Beginning September 11, weekly reports must be submitted by 3:00 p.m. Friday and include all required sections.

Support

The manager will review the weekly priority list with John each Monday for the next four weeks.

Follow-Up

Progress will be reviewed during the September 18 one-on-one meeting.

This example demonstrates the level of specificity managers should strive for.

A Simple Documentation Template

Employee Information

Employee: __________________________

Position: __________________________

Manager: __________________________

Date: _____________________________

Performance Issue

Describe the issue:

Expected Standard

What was expected?

Observed Behavior

What happened? Include dates and relevant details.

Impact

What was the work-related impact?

Previous Feedback

Has this issue been discussed previously?

Employee Response

What did the employee say?

Support Provided

What training, guidance, resources, or support were provided?

Required Improvement

What needs to change?

Follow-Up

Follow-up date: __________________________

How will progress be measured?

Manager Notes

Employee Comments

Final Thoughts

Good performance documentation isn’t about creating a long file on an employee.

It’s about creating a clear record of the management process.

The strongest documentation follows a simple pattern:

What happened → What was expected → What was the impact → What did the employee say → What support was provided → What needs to change → When will we follow up?

Avoid labels.

Avoid emotional language.

Avoid guessing motives.

Use specific examples.

Document important conversations promptly.

Keep records secure.

And make sure your approach is consistent with your organization’s policies and applicable requirements.

When documentation is accurate and objective, it becomes a useful management tool rather than simply paperwork.

Download the Free HROfficials Employee Performance Documentation Template

Need a simple way to document performance concerns?

The HROfficials Employee Performance Documentation Template includes sections for:

  • Employee information
  • Performance issue
  • Expected standard
  • Specific examples
  • Business impact
  • Previous coaching
  • Employee response
  • Support provided
  • Required improvement
  • Follow-up
  • Manager notes
  • Employee comments

[DOWNLOAD THE FREE PERFORMANCE DOCUMENTATION TEMPLATE]

Use the template as a starting point and adapt it to your organization’s policies and processes.

Frequently Asked Questions

Why is documenting employee performance important?

Documentation helps managers clearly communicate expectations, track discussions and improvement, preserve relevant facts, and support consistent performance-management processes.

What should I write when documenting a performance problem?

Describe the specific event or behavior, the date, the expected standard, the work-related impact, the employee’s relevant response, and the expectations or next steps that were established.

Should performance documentation include my opinion?

Avoid unsupported opinions and labels. Focus on observable behavior, measurable results, established expectations, and relevant context.

Should I document positive employee performance too?

Yes. Significant accomplishments, successful projects, improvements, and meaningful contributions can provide a more complete picture of performance and make formal reviews easier.

Should an employee sign performance documentation?

Some organizations use employee acknowledgments, while others do not. If your organization uses signatures, follow the established process and clarify what the acknowledgment represents. A signature should not be presented as agreement unless that is actually what the process requires.

What if an employee disagrees with the documentation?

Allow the employee to provide relevant context or comments. Evaluate new information objectively and document the employee’s perspective appropriately.

When should a manager involve HR?

HR involvement may be appropriate for recurring or serious issues, formal corrective action, Performance Improvement Plans, termination decisions, complaints involving discrimination or harassment, accommodation or leave matters, retaliation concerns, or other legally sensitive situations.

How long should employee performance records be kept?

There is no single retention period for every type of employee record. Follow your organization’s retention policy and applicable legal requirements, and seek appropriate professional guidance when necessary.

Should performance documentation be kept in email?

Important performance records should generally be stored according to the organization’s document-management and employee-record procedures rather than scattered across personal inboxes. Sensitive information should be stored securely and shared only with authorized individuals.

Disclaimer

This article provides general HR information for educational and planning purposes and is not legal advice. Employment documentation, discipline, performance management, recordkeeping, accommodations, leave, discrimination, retaliation, and termination can be subject to federal, state, and local requirements. Employers should follow their own policies and obtain appropriate HR or legal guidance when circumstances are complex or legally sensitive.

How to Give Constructive Employee Feedback: A Complete Guide for Managers

Category: Performance Management
Reading time: 12–15 minutes
Last updated: September 2026

Giving employee feedback is one of a manager’s most important responsibilities—and one of the easiest to get wrong.

Managers may avoid difficult conversations because they don’t want to discourage an employee. Others may give feedback that is too vague, too harsh, or too focused on personality.

Good feedback does something different.

It helps an employee understand:

What am I doing well?

What needs to improve?

Why does it matter?

What should I do differently?

How can my manager support me?

Constructive feedback should be specific, respectful, timely, and focused on behavior or results rather than personal judgments.

This guide explains how managers can give useful employee feedback in everyday situations, performance reviews, one-on-one meetings, and difficult conversations.

Free Resource: Download the HROfficials Employee Feedback Template to prepare clear feedback, record key examples, and establish follow-up actions.

What Is Constructive Employee Feedback?

Constructive employee feedback is information provided to an employee about their performance, behavior, work habits, or results with the goal of reinforcing effective behavior or helping improve performance.

Constructive feedback can be:

Positive

“Your customer follow-up process has been very consistent, and customers are receiving updates sooner.”

or

Corrective

“The last three reports were submitted without the required summary section. Going forward, the summary needs to be completed before the report is submitted.”

Constructive doesn’t mean negative.

The word constructive means the feedback should help the employee understand what to continue, change, or improve.

Why Employee Feedback Matters

Employees can’t improve something they don’t understand.

Clear feedback can help employees:

  • Understand expectations
  • Recognize strengths
  • Correct mistakes
  • Develop skills
  • Improve performance
  • Build confidence
  • Solve problems earlier
  • Align their work with team goals

Feedback also gives managers an opportunity to recognize good work rather than only speaking to employees when something goes wrong.

A healthy workplace should have both:

Recognition

and

Improvement-oriented feedback

Feedback vs. Performance Reviews

These are not the same thing.

Employee Feedback

Usually happens throughout the year.

Examples:

  • One-on-one conversations
  • Project discussions
  • Coaching
  • Informal recognition
  • Real-time corrections

Performance Review

A more formal assessment of performance during a defined period.

For example:

  • Annual review
  • Semiannual review
  • Quarterly review

A good performance-management system uses regular feedback so that the formal review is not the first time an employee hears about a problem.

Think of it as:

Ongoing feedback → regular check-ins → formal review

The Golden Rule of Feedback

A simple rule is:

Be specific about the behavior, clear about the impact, and practical about what should happen next.

Compare:

Weak

“You need to communicate better.”

Constructive

“During the last two project meetings, the team didn’t receive an update on the client issue until the meeting was nearly over. Going forward, please include project risks in your weekly update so the team can address them earlier.”

The second version tells the employee:

What happened

Why it matters

What to do differently

Step 1: Give Feedback Promptly

Don’t wait three months to discuss an issue that could have been corrected last week.

Timely feedback is usually easier to understand because the situation is still fresh.

For example:

An employee sends an incomplete report.

Instead of waiting until the annual review:

“I’d like to discuss the report you submitted today. Two required sections were missing. Let’s review what was needed and make sure the next report includes them.”

This allows the employee to correct the issue immediately.

Timely doesn’t mean impulsive.

Take enough time to confirm the facts before giving serious corrective feedback.

Step 2: Focus on Behavior, Not Personality

This is one of the most important principles.

Avoid:

“You’re careless.”

Instead:

“There were three data-entry errors in the customer records submitted this week.”

Avoid:

“You’re not a team player.”

Instead:

“The project team requested the updated information on Tuesday, but it wasn’t shared until Friday, which delayed their work.”

Avoid:

“You have a bad attitude.”

Instead:

“During yesterday’s meeting, you responded to a coworker’s suggestion by saying it was a ‘waste of time.’ That communication did not meet our expectations for respectful discussion.”

Behavior can be discussed and changed.

Personality labels usually aren’t useful.

Step 3: Use Specific Examples

General statements create confusion.

Too vague

“Your reports need to improve.”

Specific

“Two of the last four reports were missing the required customer-summary section.”

The employee now knows what needs attention.

Whenever practical, include:

  • Date
  • Situation
  • Specific behavior
  • Result or impact

You don’t need to mention every minor incident.

Use examples that are relevant to the feedback.

Step 4: Explain the Impact

Employees may not realize why a particular behavior matters.

Explain the business, team, customer, or workflow impact.

For example:

“When the report comes in late, the finance team has less time to review the numbers before the client meeting.”

Or:

“When customer notes aren’t entered in the CRM, the next person who handles the account doesn’t have the information they need.”

Impact makes feedback meaningful.

Step 5: Be Clear About the Expected Behavior

Don’t assume the employee knows what you want instead.

Instead of:

“Be more organized.”

Say:

“Please use the project tracker for all active assignments and update the status by 4:00 p.m. each Friday.”

Instead of:

“Be more responsive.”

Say:

“Please acknowledge internal requests within the department’s established response timeframe, even if you need additional time to complete the request.”

The employee needs a practical target.

Step 6: Ask for the Employee’s Perspective

Feedback should be a conversation.

After explaining the issue, ask:

“How do you see the situation?”

or:

“What got in the way?”

or:

“Was there something I wasn’t aware of?”

You may discover:

  • Unclear instructions
  • Conflicting priorities
  • Missing resources
  • Training gaps
  • System problems
  • Unrealistic deadlines
  • Communication issues

Listening doesn’t mean avoiding accountability.

It means making sure you’re working with the full picture.

Step 7: Ask Before Assuming

Suppose an employee misses an important deadline.

Don’t start with:

“You clearly didn’t prioritize this.”

Try:

“I noticed the deadline was missed. Can you walk me through what happened?”

The employee may explain a legitimate obstacle.

Or they may identify a preventable problem.

Either way, you have better information.

Step 8: Make Feedback Actionable

Feedback should answer:

What should the employee do next?

For example:

Problem

Customer responses are frequently delayed.

Feedback

“Several customer inquiries have been answered later than our team standard. Going forward, please review the customer queue at the start of each workday and flag any requests that may require additional support.”

Follow-up

“Let’s review the response-time report together next Friday.”

That’s actionable.

The SBI Feedback Model

A simple feedback framework is:

S — Situation

When or where did it happen?

B — Behavior

What did the employee do?

I — Impact

What effect did it have?

Example:

Situation: “During Tuesday’s team meeting…”

Behavior: “you interrupted Maya three times while she was presenting…”

Impact: “which made it difficult for her to complete the update and disrupted the discussion.”

Then add:

Next step: “Going forward, please let the speaker finish before responding.”

The classic SBI structure can be adapted to both positive and corrective feedback.

A Four-Part Feedback Formula

For HROfficials readers, an even easier formula is:

Situation

What happened?

Behavior

What did the employee do?

Impact

Why did it matter?

Next Step

What should happen going forward?

Example:

“During yesterday’s customer meeting, you answered a question before confirming the information with the product team. The customer received incorrect information, which we later had to correct. Going forward, please confirm uncertain product details before providing an answer.”

Simple, specific, and actionable.

How to Give Positive Feedback

Positive feedback deserves the same level of specificity as corrective feedback.

Instead of:

“Good job.”

say:

“You identified the customer billing error before the invoice was sent and worked with finance to correct it. That prevented a larger customer issue.”

Then:

“Please keep using that review process.”

This tells the employee exactly what behavior produced the positive result.

Recognition vs. Praise

These aren’t quite the same.

Generic Praise

“You’re awesome.”

Specific Recognition

“You stayed late to complete the system migration, documented the remaining issues, and made the handoff easier for the support team.”

Specific recognition is more informative because the employee knows what contribution was valuable.

How to Give Corrective Feedback

Corrective feedback doesn’t need to sound harsh.

Use a calm structure:

“I want to discuss something that needs to improve.”

Then:

“Here’s what I’ve observed.”

Then:

“Here’s the impact.”

Then:

“Here’s what I need going forward.”

Then:

“What is your perspective?”

Finally:

“Let’s agree on the next step.”

This provides clarity without turning the conversation into a confrontation.

Example: Missed Deadline

Avoid

“You need to take deadlines seriously.”

Better

“The client report was due internally on Thursday at noon, but it was submitted Friday afternoon. That reduced the time available for review before the client deadline. Going forward, I need the internal deadline met, or I need advance notice if something is going to prevent that.”

Example: Poor Communication

Avoid

“You don’t communicate well.”

Better

“During the last project, the team wasn’t informed about the supplier delay until the delivery date had already passed. Going forward, please notify the team as soon as a significant delay becomes likely.”

Example: Quality Problems

Avoid

“You need to be more careful.”

Better

“Four of the last 25 records contained missing required fields. Please review each record against the checklist before submitting it.”

Example: Meeting Behavior

Avoid

“Stop being rude.”

Better

“During today’s meeting, you interrupted two coworkers while they were speaking. Please allow the speaker to finish before responding.”

Example: Employee Is Doing Well

Avoid

“Great work!”

Better

“Your weekly project updates have consistently identified risks before they affected the deadline. That has helped the team address problems earlier.”

How to Give Feedback When an Employee Becomes Defensive

Some employees become defensive when receiving criticism.

Don’t respond by becoming defensive yourself.

You can say:

“I understand that you see it differently. I’d like to hear your perspective.”

Then listen.

If you still believe the expectation is clear, return to the workplace issue.

“I understand your concern. Regardless, the expectation going forward is that the report is submitted by the established deadline.”

Don’t argue about personality.

Don’t try to force the employee to say:

“You’re right.”

The objective is clarity and improvement, not agreement on every point.

What If the Employee Gets Emotional?

Employees may become upset during difficult conversations.

Remain calm and respectful.

You can say:

“I can see that this is difficult to hear. Let’s take a moment.”

Give the employee reasonable space to respond.

Do not make assumptions about why they’re upset.

If the conversation raises medical, disability, leave, harassment, discrimination, retaliation, or another legally sensitive concern, follow the organization’s appropriate procedures and seek HR or legal guidance as needed.

How to Give Feedback to a High Performer

High performers need feedback too.

Avoid assuming:

“They’re doing great, so there’s nothing to discuss.”

Instead, explore:

  • What can they do even better?
  • What responsibilities would develop them?
  • What obstacles can you remove?
  • What skills do they want to build?
  • How can they contribute to team development?

Example:

“Your project delivery has been excellent. The next opportunity I’d like to explore is helping you build your presentation skills by leading the next two client updates.”

How to Give Feedback to a New Employee

New employees need more frequent guidance.

Don’t wait for a formal review.

Give feedback around:

  • Role expectations
  • Work quality
  • Communication
  • Priorities
  • Team norms
  • Training

Make the feedback educational.

For example:

“You’re getting the process down well. One adjustment: please document the customer interaction before moving to the next case. That helps the next team member pick up the account without needing to ask you for details.”

How to Give Feedback During a One-on-One

A good one-on-one can be a natural place for regular feedback.

Try:

What went well?

“What are you proud of this week?”

What could improve?

“What would you do differently?”

Manager feedback

“I noticed…”

Employee perspective

“How do you see it?”

Next step

“What should we change next week?”

This makes feedback part of normal management rather than a special event.

How to Give Feedback During a Performance Review

A formal performance review should not contain surprises.

Use information already discussed throughout the review period.

Start with:

Accomplishments

Then:

Strengths

Then:

Areas for improvement

Then:

Development

Then:

Goals

For more information, see the HROfficials guide:

How to Conduct an Employee Performance Review

When Feedback Becomes Formal Performance Management

Not every piece of feedback requires formal documentation.

However, more structured performance management may be appropriate when:

  • A problem is repeated
  • Improvement does not occur
  • The issue is significant
  • Expectations have been clearly communicated
  • Formal corrective action may be necessary

At that point, managers should follow the organization’s established performance-management process.

See the HROfficials guide:

How to Document Employee Performance Issues

Keep Feedback Objective

Use evidence wherever possible.

Instead of:

“You never meet deadlines.”

Try:

“Three of the last six assigned deliverables were submitted after the agreed deadline.”

Instead of:

“Customers don’t like dealing with you.”

Try:

“The customer survey included three comments concerning the tone of recent communications.”

The second examples are much easier to evaluate.

Avoid the Feedback Sandwich

Some managers use this formula:

Positive → Negative → Positive

For example:

“You’re a great employee, but your work is late, but overall you’re doing a great job.”

This can make the actual feedback unclear.

If an issue matters, discuss it directly and respectfully.

For example:

“Your work quality is strong. I also need us to address the recurring deadline issue. Three recent reports were submitted late, and I’d like us to establish a process that helps you meet the deadlines consistently.”

You can recognize strengths without hiding the issue inside compliments.

Avoid “Always” and “Never”

Words like:

Always

Never

Every time

Everyone

usually make feedback less precise.

Instead of:

“You’re always late.”

say:

“You’ve arrived after your scheduled start time three times in the past two weeks.”

Specific is better.

Don’t Compare Employees

Avoid:

“Why can’t you work like Maria?”

This creates defensiveness and shifts attention away from the employee’s actual responsibilities.

Instead:

“The expectation for this role is…”

Then evaluate the employee against the requirements of their job.

Don’t Give Feedback in Public

Corrective feedback should generally be handled privately.

Public criticism can embarrass employees and damage trust.

Recognition can often happen publicly when appropriate, but even recognition should respect the employee’s preferences and workplace culture.

Don’t Give Feedback When You’re Furious

If you’re angry, pause.

Ask:

“Am I responding to the behavior, or am I reacting emotionally?”

If necessary, take time to gather facts and plan the conversation.

A manager’s emotional reaction can easily turn a manageable issue into a larger conflict.

Use a Feedback Preparation Checklist

Before giving significant feedback, ask:

☐ What specifically happened?

☐ When did it happen?

☐ What expectation applies?

☐ What impact did the behavior have?

☐ What evidence do I have?

☐ Have I separated facts from assumptions?

☐ What do I want the employee to do differently?

☐ What support might be helpful?

☐ Is this feedback appropriate for me to handle?

☐ Does HR need to be involved?

☐ When should we follow up?

Employee Feedback Examples by Situation

SituationLess EffectiveConstructive
Late work“You need to be more responsible.”“The last two reports were submitted after the agreed deadline. I need future reports submitted by the established deadline.”
Poor communication“You don’t communicate.”“Please provide project updates when a deadline or customer commitment may be affected.”
Quality issues“You’re careless.”“Three of the last 15 records contained missing required fields.”
Meeting behavior“You’re rude.”“You interrupted two speakers during today’s meeting. Please allow each person to finish before responding.”
Strong performance“Good job.”“Your early identification of the reporting error prevented a larger problem.”
Initiative“Great attitude.”“You identified the scheduling problem and proposed a solution before it affected the customer.”

How to End a Feedback Conversation

Don’t simply say:

“Okay, thanks.”

End with clarity.

Ask:

“What are you taking away from this conversation?”

Then confirm:

Expected change

Support

Timeline

Follow-up

Example:

“So we’re agreed that reports will be submitted by 3:00 p.m. Friday, and you’ll let me know in advance if a problem threatens the deadline. We’ll review progress during our next two one-on-ones.”

Now both sides know what happens next.

Document Important Feedback

Not every routine comment needs formal documentation.

For significant performance conversations, however, maintain appropriate records consistent with the organization’s process.

Document:

  • Date
  • Issue discussed
  • Specific examples
  • Employee response
  • Expectations
  • Support provided
  • Follow-up date

See:

How to Document Employee Performance Issues

for a deeper guide.

Keep sensitive employee information secure and accessible only to people with an appropriate business need.

How to Build a Feedback Culture

A strong feedback culture doesn’t mean managers criticize employees constantly.

It means people regularly discuss:

What is working?

What isn’t working?

What should we change?

What support is needed?

Build feedback into:

  • One-on-one meetings
  • Team meetings
  • Project reviews
  • Performance reviews
  • Training
  • Recognition
  • Career conversations

The more normal feedback becomes, the less intimidating difficult conversations tend to feel.

The Manager’s Feedback Formula

When you’re unsure what to say, remember:

1. Be specific

What happened?

2. Be objective

What can you actually establish?

3. Explain the impact

Why does it matter?

4. Listen

What is the employee’s perspective?

5. Set expectations

What should happen next?

6. Offer support

What will help?

7. Follow up

When will you review progress?

That’s constructive feedback.

A Complete Constructive Feedback Script

Use this framework when you need to address a performance problem:

I’d like to talk about something I noticed and make sure we’re clear about expectations.

During [specific situation/date], I noticed [specific behavior]. The expectation is [specific expectation], and the impact was [specific impact].

I’d like to hear your perspective. Can you walk me through what happened?

[Listen and clarify.]

Going forward, I need [specific behavior or result].

To help with that, we can [specific support/training/process].

Let’s check in again on [date] to see how things are going.

Do you have any questions or concerns about what we’ve discussed?

Constructive Feedback Script for Positive Recognition

I wanted to recognize something you did particularly well.

During [specific situation/project], you [specific behavior]. That resulted in [specific positive impact].

Your approach to [specific skill/behavior] made a difference because [reason].

Please keep doing that, and I’d like to see you continue building on this strength.

Final Thoughts

Great employee feedback doesn’t have to be complicated.

It needs to be clear, specific, respectful, and useful.

When a manager says:

“You need to improve your communication.”

the employee may leave wondering what that actually means.

When a manager says:

“During the last two project meetings, the team didn’t receive an update about the supplier delay. Going forward, please let the team know as soon as a significant delay becomes likely.”

the employee knows exactly what needs to change.

That’s the difference between vague criticism and constructive feedback.

Use specific examples.

Focus on behavior and results.

Explain the impact.

Listen to the employee.

Set a clear next step.

Offer appropriate support.

Follow up.

And remember that feedback isn’t only for problems.

Recognize excellent work.

Celebrate meaningful progress.

Help employees understand their strengths.

Use feedback as an ongoing management tool—not just something that happens once a year.

Download the Free HROfficials Employee Feedback Template

Want an easy way to prepare and document employee feedback?

The HROfficials Employee Feedback Template can help managers organize:

  • Situation
  • Observed behavior
  • Positive or corrective feedback
  • Business impact
  • Employee response
  • Expected change
  • Support provided
  • Follow-up date
  • Manager notes

[DOWNLOAD THE FREE EMPLOYEE FEEDBACK TEMPLATE]

Use the template as a starting point and adapt it to your organization’s policies and management practices.

Frequently Asked Questions

What is constructive employee feedback?

Constructive feedback is specific information about an employee’s behavior, performance, or results that helps reinforce effective behavior or improve areas that need attention.

How often should managers give employee feedback?

Feedback should happen regularly rather than being reserved for annual reviews. The frequency depends on the role and situation. Regular one-on-one conversations provide natural opportunities for ongoing feedback.

How do you give negative feedback without hurting an employee?

Focus on specific behavior or results rather than personality. Explain the impact, clarify expectations, listen to the employee’s perspective, and identify a practical next step.

Should feedback always be positive?

No. Effective management requires both recognition and appropriate corrective feedback. Avoiding legitimate performance concerns can allow small problems to become larger ones.

What should I do if an employee disagrees with my feedback?

Listen to the employee’s explanation and consider relevant information they provide. You do not need the employee to agree with every point, but you should make sure expectations are clear and that the discussion is fair and based on relevant facts.

Is constructive feedback the same as a performance review?

No. Feedback is an ongoing management activity. A performance review is a more formal assessment conducted over a defined period. Regular feedback should reduce the likelihood of surprises during a formal review.

Should corrective feedback be documented?

Important or recurring performance concerns should generally be documented according to the organization’s established process. Documentation should be factual, objective, and appropriately secured.

What if an employee becomes emotional during feedback?

Remain calm and respectful. Give the employee an opportunity to respond and avoid making assumptions about their emotions. If the conversation raises a potentially protected workplace issue, follow your organization’s appropriate procedures and seek HR or legal guidance as needed.

What is the SBI feedback method?

SBI stands for Situation, Behavior, Impact. It encourages managers to identify the situation, describe the observed behavior, and explain its impact. A fourth step—agreeing on the next action—is often useful for practical performance conversations.

Disclaimer

This article provides general HR information for educational and planning purposes and is not legal advice. Employee feedback, performance management, discipline, documentation, accommodations, leave, discrimination, retaliation, and termination can be subject to federal, state, and local requirements. Employers should follow their applicable policies and obtain appropriate HR or legal guidance when circumstances are complex or legally sensitive.

Scroll to Top