Weekly Employee Evaluation Template: A Practical Guide

A weekly employee evaluation template is a short, repeatable form for recording an employee’s priorities, progress, specific feedback, and next steps for one workweek. Use the blank template below as a starting point, then adapt its prompts to the role and discuss the notes with the employee rather than treating the form as a scorecard on its own.

What a Weekly Evaluation Is For

A weekly evaluation creates a regular place to connect planned work with what actually happened. It can help a manager recognize completed work, notice obstacles while they are still manageable, and agree on what should happen next. For employees, a clear record can make expectations easier to understand and give them a chance to explain context that may not be visible to a supervisor.

The term “evaluation” does not have to mean a formal rating. Many teams use a few written prompts and a short conversation instead. The most useful level of formality depends on the work: a fast-moving project may benefit from a brief weekly review, while a role with longer work cycles may need a weekly check-in focused on milestones rather than final results.

A weekly document is most useful when it supports ongoing communication. It should not be the only time an employee hears about a concern, nor should a single week’s notes be treated as a complete picture of someone’s performance. A missed target may reflect a changed priority, a blocked dependency, or an unrealistic estimate. The conversation helps distinguish among these possibilities.

How to Use the Template

Complete the form close to the end of the workweek, while examples and decisions are still fresh. The manager can draft the review, the employee can complete a self-assessment, or both can fill in their sections before discussing them together. Agree on one process so that employees know when and how the form is used.

1. Set the scope. Enter the week being reviewed and identify the priorities that were actually agreed upon. If priorities changed, note when and why rather than comparing the employee with an outdated plan.
2. Record observable work. Describe a deliverable, action, or behavior and its result. Separate what happened from assumptions about motivation or personality.
3. Discuss progress and barriers. Ask what helped, what slowed the work, and whether the employee needs a decision, resource, or clearer direction.
4. Agree on next steps. Name the action, who owns it, and a reasonable due date or check-in point. Keep the list short enough to use.
5. Invite the employee’s perspective. Make space for a correction, explanation, or additional context, and record any agreed follow-up.

For instance, “Prepared the client handoff notes and caught two missing setup steps before the transfer” is more useful than “great attitude.” If a planned task was not completed, write what changed and what the next decision is. The goal is an accurate, usable account, not a polished summary that hides uncertainty.

Weekly Employee Evaluation Template

Choosing Fair, Useful Criteria

Choose criteria that relate to the actual responsibilities of the role and can be discussed with concrete examples. A template does not need to assess every aspect of a job every week. A small number of relevant prompts is easier to complete consistently and leaves more room for a useful conversation.

• Results: What work was completed, delivered, resolved, or moved forward?
• Quality: Was the work accurate, clear, complete, or in line with the agreed requirements?
• Reliability: Were commitments and updates handled as agreed, taking changes and dependencies into account?
• Collaboration: What specific communication or coordination helped the work progress?
• Learning and support: What new skill, feedback, or resource would help with upcoming work?

Not every criterion fits every job. A role involving unpredictable requests may be better assessed by how priorities were handled than by counting tasks completed. A project with a long delivery cycle may call for milestone progress and risk identification, not a weekly judgment about whether the final outcome is finished. Discuss expectations in advance so that employees are not surprised by standards introduced after the work is done.

Where a rating scale is used, define its labels. For example, a team might distinguish “on track,” “needs attention,” and “not applicable,” while explaining what evidence belongs under each. These are example labels, not a universal standard. Allow “not applicable” or a written explanation when the week did not provide a fair opportunity to assess a criterion.

Writing Specific Feedback and Ratings

Useful feedback links an observation to an effect or next step. A simple structure is: what happened, why it mattered, and what to continue or change. “The handoff included the updated schedule, so the receiving team could plan its shift without asking for a correction” gives more information than “good communication.” For improvement, identify the work and expectation: “The draft was submitted after the agreed review time; next week, flag a likely delay before the deadline so we can adjust the review plan.”

If you use numbers or labels, explain them in words. A score without an example can feel arbitrary and may conceal differences in how reviewers interpret the scale. Avoid using a rating to summarize several unrelated issues; describe each relevant observation separately. If there is not enough evidence for a meaningful rating, say so instead of guessing.

Balance recognition with development feedback, but do not force an equal number of positive and negative comments. Be honest, proportionate, and focused on work the employee can influence. When a concern is significant or ongoing, raise it directly and clarify the expected change and follow-up rather than relying on a vague weekly note.

Common Problems and How to Avoid Them

• Turning the form into a checklist of activity. A long list of tasks may show busyness without explaining outcomes. Focus on a few agreed priorities and note meaningful progress.
• Rating people on events outside their control. Record dependencies, changed instructions, and unavailable resources. Discuss what the employee could reasonably do and what support is needed.
• Using vague labels. Words such as “professional,” “not proactive,” or “excellent” are hard to interpret without an example. Describe the action and its work-related effect.
• Saving every concern for the form. A weekly review should not be a surprise delivery system for feedback that could have been discussed earlier. Raise time-sensitive concerns promptly.
• Applying different standards across the team. Use the same core prompts and explain role-specific differences. Consistency means comparable expectations, not pretending all jobs have identical outputs.
• Making the process too burdensome. If writing the review takes longer than the conversation can reasonably use, shorten the form. A concise record that is revisited is better than an elaborate form nobody completes carefully.

A further misconception is that a written evaluation is automatically objective. A written record can improve clarity, but it still reflects the reviewer’s observations and choices. Invite the employee to add context, correct factual errors, and identify missing examples. Keep conclusions proportionate to the evidence available for that week.

Weekly Check-Ins Compared With Formal Reviews

A weekly evaluation is usually narrow in time and practical in focus: current priorities, immediate feedback, obstacles, and next steps. A formal performance review generally looks across a longer period and may address broader goals, development, or organizational processes. The exact arrangements vary by workplace, so the weekly form should not imply that it replaces any established review process.

Frequent notes can make later conversations more grounded because they preserve examples instead of relying only on recent memories. However, the notes should still be interpreted in context. A particularly difficult week does not by itself establish a long-term pattern, just as one strong week does not answer every question about sustained performance.

If weekly reviews are being introduced, explain their purpose, who will see the information, and how it relates to other check-ins. Employees should know whether the form is primarily for coaching, coordination, or formal documentation. Clarity about purpose helps prevent a supportive conversation from feeling like an undisclosed scoring exercise.

Privacy, Consistency, and Recordkeeping

Keep the form focused on job-related observations and the actions needed to support work. Avoid unnecessary personal details. Store completed forms only in the appropriate workplace location and limit access to people with a legitimate role in the process, following the organization’s policies for records and retention. Do not promise confidentiality beyond what the workplace can actually provide.

Review the process periodically. Check whether managers are completing forms at a similar cadence, whether the prompts fit the roles, and whether employees understand how to respond. If the same obstacle appears repeatedly, the useful next question may be whether a workflow or resource needs attention rather than whether an individual should simply try harder.

For a situation that requires legal, tax, medical, or financial-planning advice, ask a qualified professional.

Alternatives and Adaptations

A printable table works well when a team wants a simple paper record or a consistent discussion guide. For a less formal approach, use the same prompts as a one-page conversation agenda and write only the agreed actions afterward. A self-review can be added by asking the employee to describe one achievement, one obstacle, and one priority for the coming week.

Adapt the form to the work without losing its core purpose. A project team might replace “tasks completed” with “milestones and risks.” A customer-facing team might note a specific interaction or recurring issue, while avoiding unnecessary identifying details about customers. For work that cannot be judged meaningfully every week, keep a brief check-in but review outcomes over a more suitable period. In every version, make room for context and a clear next step.

Frequently Asked Questions

What should a weekly employee evaluation include?
Include the week covered, agreed priorities, specific progress or outcomes, strengths or concerns supported by examples, obstacles, support needed, employee comments, and next actions. Keep the prompts relevant to the role.

Should a weekly employee evaluation use a rating scale?
Not necessarily. A written summary may be enough for coaching and coordination. If you use ratings, define each label, explain it with evidence, and allow an explanation or “not applicable” when a fair assessment is not possible.

How long should a weekly evaluation take?
There is no single required duration. Keep the form short enough to complete consistently and the discussion long enough to clarify progress, context, and next steps. The amount of detail should reflect the work, not a target number of comments.

How do I evaluate an employee whose work is hard to measure weekly?
Review progress toward milestones, quality of decisions, collaboration, or risks identified rather than forcing a weekly output count. If the work cycle is longer, use weekly check-ins for coordination and assess completed outcomes over an appropriate period.

Can employees add comments to the evaluation?
Yes. An employee comment field gives the person a way to add context, clarify a factual detail, or identify support they need. Agree on how comments are recorded and ensure that disagreement can be noted without treating it as misconduct.

Related

• Subcontractor Invoice Template and What to Include
• St. Jude Donation Receipt Template and What to Know
• State Press Release Template for Gavi Updates