A good self-evaluation explains what you delivered, why it mattered, and what you will improve next. For an international team, it also makes visible the work that happens while your manager is offline: a clear handoff, a documented decision, or a problem solved without another meeting.
These self-evaluation examples are for employees at startups working across countries and time zones, and for founders who want more useful review conversations. They cover achievements, areas for improvement, and next-period goals. All scenarios and numbers are illustrative, not Shor customer results. Replace them with evidence from your own work.
How to write a self-evaluation
Start with the expectations you and your manager agreed at the beginning of the review period. Then gather project outcomes, feedback, and examples of decisions you owned. Look across the whole period, including work that never became a launch announcement.
Use this structure for each important point:
Action + evidence + impact + next step.
For example: "I created a support handoff checklist. In the following month, tickets returned for missing context fell from 12 to 4. That gave the next shift more time to solve customer issues. Next quarter, I will test the checklist with our second support team."
Describe your contribution accurately. If three people delivered a project, explain your part instead of claiming the whole result. Where several things changed at once, say your work contributed to the outcome rather than claiming it caused all of it.
If you do not have a reliable metric, use something observable: a decision document the team adopted, a completed migration, feedback on a demo, or a process another person can now run. Never invent a percentage to make an answer look stronger.
Achievement and delivery examples
1. Delivering against an agreed goal
"I delivered the reporting dashboard by our agreed September deadline. I owned the data model and release checklist, while design and engineering teammates handled the interface. The operations team now uses it for its weekly review instead of combining three spreadsheets."
2. Improving quality
"I reviewed the causes of reopened support tickets and rewrote our troubleshooting instructions for the two most common issues. Reopened tickets in those categories fell from 18 in July to 9 in August. I will keep checking the trend as ticket volume changes."
3. Explaining a missed target
"I completed 8 of the 10 planned customer interviews. I underestimated recruitment time and raised the risk too late. For the next research cycle, I will begin recruiting a week earlier and review response rates with my manager before the schedule becomes tight."
Async communication examples
4. Making updates actionable
"I changed my weekly updates to include completed work, blockers, and decisions needed, with an owner and deadline for each request. Teammates in other time zones can now respond without first asking what I need from them. I will ask the team which parts of the update they actually use."
5. Writing decisions down
"I documented the options and tradeoffs for our new onboarding flow before the planning meeting. Two colleagues who could not attend added feedback in the document, and their suggestions changed the final scope. I will use the same approach for the next cross-team decision."
6. Improving unclear messages
"Some of my requests lacked enough context for colleagues to act while I was offline. I will include the desired outcome, supporting links, and a specific question in each handoff. In our next retrospective, I will ask whether follow-up questions have decreased."
Teamwork across time zones examples
7. Creating reliable handoffs
"I introduced a handoff note with the current status, next action, and escalation owner for open customer issues. During the last release, the next shift continued work on all six priority tickets without waiting for me to come online."
8. Planning around availability
"Before scheduling the launch, I checked team availability and local holidays with each project owner. We moved one approval earlier and assigned a backup reviewer. The release went ahead on the agreed date without asking colleagues to work during planned leave."
9. Reducing dependence on meetings
"I relied too much on live discussions to resolve routine questions, which made progress depend on a narrow overlap window. Next month, I will trial written proposals for routine decisions and reserve calls for issues that remain unresolved after feedback."
For founders planning team coverage, our guide to where to hire remote employees covers location and hiring costs. For a review, assess how someone worked within the agreed overlap hours, rather than rewarding permanent availability.
Ownership and reliability examples
10. Raising risks early
"When a dependency threatened our release date, I flagged it with two options: reduce scope or move the launch. The team chose the smaller release before we committed to customer communications. I then tracked the deferred work through completion."
11. Following through
"I took ownership of the action items from our onboarding retrospective and closed all five by the agreed dates. I added the updated instructions to the team handbook so the improvements did not depend on someone remembering the meeting."
12. Setting realistic commitments
"I accepted two urgent requests without explaining the effect on my existing commitments. One planned task slipped by three days. I will make the tradeoff explicit when new work arrives and agree which deadline changes before committing."
Problem-solving and initiative examples
13. Fixing a recurring problem
"I traced repeated import failures to inconsistent date formats and added a validation step before processing. In the next four weekly runs, that failure did not recur. I documented the fix and the remaining edge cases for the team."
14. Testing a smaller solution
"Before proposing a new tool, I tested a shared intake form with one team for two weeks. It captured the information we had been collecting through follow-up messages. We adopted the form and postponed the tool purchase until we have a clearer need."
15. Asking for help sooner
"I spent too long investigating an issue alone because I wanted to bring a finished answer. Next time, I will agree an investigation time limit with my lead and share what I have tried, what I know, and the specific help I need when I reach it."
Feedback and collaboration examples
16. Applying feedback
"My manager said my project summaries buried the main decision. I began opening each summary with the recommendation and moving background below it. In our last review, she confirmed that the revised format made the action needed clearer."
17. Handling disagreement constructively
"When design and engineering disagreed on the release scope, I wrote down the customer need, constraints, and two workable options. We agreed on a smaller first release and a follow-up usability check. That gave both teams a clear decision to work from."
18. Making room for other perspectives
"I sometimes answered questions before quieter teammates had a chance to contribute. I will share discussion prompts in advance and invite written feedback afterward, so participation does not depend on speaking quickly in a live call."
Leadership and mentoring examples
19. Helping a new colleague become independent
"I paired with our new teammate on their first two releases and documented the checks we used. They ran the third release independently, with me available for questions. I will update the guide based on the steps they found unclear."
20. Delegating with clear ownership
"I delegated the next customer workshop with a written outcome, budget, and decision boundaries. The owner planned and ran it without needing approval for every detail. I stayed available for escalations and reviewed the results afterward."
21. Removing a leadership bottleneck
"Too many routine approvals still depend on me, especially when I am offline. This quarter, I will agree which decisions team members can make independently and name a backup for those that still need review. We will revisit the boundaries after the first month."
Growth and development examples
22. Applying a new skill
"I learned the reporting tool well enough to build and validate our weekly operations report. A teammate checked my first two reports, and I now produce them independently. Next, I want to learn how to investigate changes in the underlying data."
23. Building role knowledge
"I joined four customer calls and grouped the questions customers asked before signing up. I used those notes to revise the onboarding checklist with the support team. I will check whether the revised checklist answers those questions in the next onboarding cycle."
24. Setting a measurable development goal
"I need more practice presenting recommendations to senior stakeholders. Next quarter, I will lead two project readouts, request feedback on clarity and decision readiness, and review that feedback with my manager before the third presentation."
A self-evaluation template you can copy
Use the sections below in your team's review document. Follow your employer's format and length requirements if it already has them.
Review period and role: [Dates, role, and any material change in responsibilities.]
Agreed priorities: [The two or three outcomes you were working toward.]
Results and contribution: I [action]. The evidence is [result, work artifact, or feedback]. My contribution was [specific ownership], working with [other contributors]. This mattered because [impact].
How I worked with the team: I helped colleagues make progress by [handoff, documentation, feedback, or coordination example]. The observable result was [evidence].
What did not go as planned: I [missed commitment or behavior to improve]. The effect was [impact]. I learned [lesson] and will change [specific action].
Next-period goals: By [date], I will [outcome]. We will assess progress using [evidence] and check in on [date].
Support I need: To deliver this, I need [priority decision, access, training, feedback, or help removing a blocker] from [person or team].
Keep the finished review selective. A few well-supported examples give your manager more to discuss than a long list of tasks.
How founders can make international team reviews useful
Share expectations before asking employees to assess themselves. Use the same role expectations and review period for comparable work, and give everyone time to prepare written answers before the conversation.
Look for outcomes and the work that enabled them. A colleague who documents a decision while you are asleep should not need to repeat it in a meeting to receive credit. Equally, a high message count or late-night reply is not evidence of strong performance on its own.
Discuss constraints as well as individual choices. Missing access, unclear priorities, and unavailable reviewers are problems to fix, not details to leave out of the review. Close the conversation with agreed goals, support, and a follow-up date.
Where Shor fits
Shor supports international hiring and payments through contractor contracts and payments, employer of record (EOR) employment, and payroll for companies with their own local entities. This guide is a review resource you can use in your existing team process; it does not require a performance-review feature in Shor.
For an employee hired through an EOR, keep the review focused on the role's agreed goals and work with the relevant employment contacts when a decision needs a formal employment change. Our guide to what EOR employment means explains that arrangement, and the EOR onboarding timeline helps founders plan the start of the relationship.
FAQ
What should I write in a self-evaluation?
Explain your main results, your contribution to shared work, one or two areas to improve, and your next goals. Support each important point with a specific example. Include the support you need from your manager to deliver those goals.
How do I describe achievements without sounding boastful?
State what you did and the evidence for its impact. Name collaborators and separate your contribution from the team's overall result. "I owned the release checklist for a launch delivered by four people" is more useful than either taking all the credit or hiding your contribution.
What if I have no metrics for my work?
Use observable evidence, such as an adopted document, a completed project, a colleague who can now run a process independently, or specific feedback. Explain why it mattered. Do not manufacture a number or imply causation you cannot support.
How should I write about an area for improvement?
Describe the behavior, its effect, and what you will change. Add a way to check progress. "I raised a deadline risk too late; next cycle I will flag dependency delays at our weekly check-in" gives you and your manager something concrete to follow up on.
What makes a remote employee's self-evaluation different?
Include the work that may be less visible to a manager in another time zone: written decisions, handoffs, early risk reporting, and helping others work independently. Assess those contributions against agreed expectations, rather than hours online or response speed outside working hours.