A practical evidence template for your performance review
Updated 19 November 2026 · Published by Look at you go · Editorial policy
Quick answer
A performance review evidence template records what you were responsible for, what you did, what changed and how you can support the claim. Include the date, relevant objective, your contribution, impact and a proof reference. Use it to build a concise self review that separates verified results from estimates, shared achievements and work still in progress.
Copy this performance review evidence template
Use the template below for each meaningful piece of work, not every task you completed. The aim is to give a reviewer enough information to understand your contribution and check the claim without needing a guided tour of your inbox.
You can paste these fields into a document or spreadsheet. Keep the working record more detailed than the version you submit. An appraisal evidence template should help you make judgements about what matters, rather than create a longer list of things that happened.
- Achievement heading: [A plain-English description of the contribution, not just the project name.]
- Date or period: [When the work happened, with an approximate period clearly labelled if necessary.]
- Objective or expectation: [The agreed goal, role responsibility or review criterion this supports.]
- Context: [The problem, need or constraint that made the work necessary.]
- Action: [What you personally did, including decisions, changes or coordination.]
- Impact: [What changed for the team, customer, organisation or quality of the work.]
- Proof: [A dated document, approved result, feedback message or other retrievable reference.]
- Ownership: [What you led or contributed, and what colleagues or partners delivered.]
- Evidence status: [Verified, qualitative, estimated, awaiting confirmation or in progress.]
- Learning and next step: [What you would repeat, change or investigate.]
- Review-ready summary: [A short account connecting the relevant context, action, impact and proof.]
Fill the fields with evidence, not impressive-sounding fog
Start with the objective or expectation. This makes the entry useful to someone assessing your work, rather than merely interesting to someone who was there. If the work was unplanned, say what need it addressed and why it took priority. Do not retrofit every useful contribution into an objective it never served.
For the action field, choose verbs that describe observable work: investigated, drafted, tested, resolved, negotiated or introduced. Words such as supported and helped can be accurate, but need an object and an explanation. What did your support involve? Which decision or deliverable did it make possible?
For impact, separate the output from its consequence. Publishing guidance is an output. Colleagues using that guidance to resolve a recurring problem is a consequence. You may have evidence for the output before you have evidence for the consequence. Record that distinction instead of promoting a hopeful prediction into a result.
For proof, note the document title, date and location, plus what it actually supports. Look At You Go can help you record work accomplishments in a private, dated record through weekly voice or text check-ins. Whether you use an app or a document, keep the link between each claim and its supporting evidence visible.
Illustration: a completed CAIP evidence entry
The following illustration shows how to complete the template using the CAIP Framework: Context, Action, Impact, Proof. It is a fictional example, not a reported result. The contribution is useful without an invented efficiency saving attached to it.
Illustration: An operations colleague notices that customer requests are repeatedly reaching a team without the information needed to handle them. Their contribution is to improve the handover process, not to claim responsibility for the entire customer experience.
The entry below separates what was created from the observed outcome and gives colleagues appropriate credit. You can use the same structure for analytical work, service delivery, project coordination or less visible maintenance work. The full [CAIP Framework](/caip-framework) explains how the elements fit together.
- Objective or expectation: Improve the reliability of customer request handovers.
- Context: Receiving colleagues regularly had to ask for missing information before they could begin work.
- Action: I reviewed returned requests, identified recurring omissions and drafted a handover checklist. I tested it with the receiving team and revised the guidance following their feedback.
- Impact: In the reviewed requests that used the checklist, the required information was present. Receiving colleagues also reported clearer handovers. Wider adoption and longer-term effects have not yet been assessed.
- Proof: The approved checklist, the reviewed request records and dated feedback from the receiving team support these claims.
- Ownership: I led the review and drafted the checklist. Receiving colleagues tested it, and the team lead approved the revised process.
- Learning and next step: Check whether the checklist remains useful across different request types before recommending broader use.
Choose entries that answer the review criteria
Once you have completed your entries, group them under the criteria your employer actually uses. These might cover delivery, quality, collaboration, judgement or development. Keep your employer's wording where it is clear. A reviewer should not have to translate your categories before assessing your evidence.
Choose entries for relevance and strength, not just visibility. A high-profile presentation may matter less than resolving a recurring service problem. Equally, routine responsibilities deserve space when the evidence shows sound judgement, reliability or sustained quality. Not every achievement needs a launch announcement.
Avoid using the same result repeatedly as if it were a collection of separate achievements. You can explain that an entry supports both delivery and collaboration, but keep the underlying result identifiable. Where several entries show a pattern, summarise the pattern and retain the supporting records.
Check for coverage as well as highlights. If a major responsibility has no evidence attached, investigate the gap before deciding it represents poor performance. You may have overlooked the relevant records. For help deciding which categories belong in the submission, see [what to put in your performance review](/resources/performance-reviews/what-to-put-in-your-performance-review).
Turn the evidence into a self review
Your evidence record is the supporting material. Your self review is the readable account. Do not paste every field into the submission unless your employer asks for that format. Lead with the contribution, explain the relevant action and outcome, then point to the proof.
Use this self review template: “To address [context], I [specific action]. This contributed to [supported impact]. [Evidence reference] supports this account. My responsibility was [scope], working with [collaborators]. The next step is [learning or follow-up].” Remove any clause that adds no useful information.
For example, using the fictional handover illustration: “I improved the handover process by reviewing returned requests and developing a checklist with the receiving team. Reviewed requests using the checklist contained the required information, and colleagues reported clearer handovers. The approved checklist, request review and team feedback support this assessment. I led the analysis and drafting; colleagues tested the process.”
Notice that the summary does not claim reduced costs, faster resolution or improved customer satisfaction. Those might be worthwhile questions to investigate, but they are not established by the stated evidence. Clear boundaries make the contribution more credible, not less impressive.
If your draft sounds stiff, simplify the language without removing the substance. [Self evaluation examples](/self-evaluation-examples) can help with phrasing, but the facts must remain yours. Keep the source record so that you can later adapt the same verified achievement for a CV or resume.
Handle missing metrics, shared results and sensitive work
Evidence does not have to be numerical. An accepted deliverable, documented decision, resolved issue or specific piece of feedback can support a useful claim. The important question is whether the evidence establishes what you say it establishes. Praise for your responsiveness does not, by itself, prove that a project met its objectives.
When results are shared, describe both the team outcome and your contribution. Use “the team delivered” for collective work and “I investigated” or “I coordinated” for your part. Be particularly careful with causal language. “Contributed to” is often more accurate than “caused”, especially when several changes happened together.
Treat uncertainty as information to record, not an embarrassment to conceal. If you cannot verify a remembered detail, mark it for checking or omit it from the submitted claim. If work is ongoing, report the completed milestone and current evidence rather than the expected final benefit.
Keep sensitive information within your organisation's rules. A personal evidence record is not permission to copy customer data, confidential documents or restricted internal discussions into another system. Where permitted, use a non-sensitive description and a reference to the authorised source location.
- No baseline: Describe the observed result without claiming an improvement you cannot establish.
- Feedback only: Identify the relevant behaviour or contribution the feedback supports, rather than treating praise as proof of every outcome.
- Conflicting evidence: Acknowledge the limitation and narrow the claim to what the records support.
- Restricted proof: Ask how the evidence can be reviewed through an approved channel instead of reproducing it.
- A missed objective: Record what happened, your responsibility, the corrective action and what remains unresolved.
Check the template before you submit it
Read each summary as if you were a manager unfamiliar with the project. Can you tell what needed doing, what this person contributed and why it mattered? Can you locate the supporting record? If the answer depends on remembering a meeting from months ago, the entry needs a little more context.
Check that dates, ownership and evidence status agree across your records. Remove unsupported adjectives and duplicated claims. Make sure any proposed next step is clearly separate from completed work. Your appraisal should be an account of performance, not a trailer for an especially optimistic sequel.
For the wider process, including organising your material for the discussion, use the [performance review preparation guide](/uk/performance-review). You can also find reusable formats in [career evidence templates](/templates). Keep this page's template as the working layer beneath whichever appraisal form your employer requires.
After the review, retain useful entries and note any corrections or follow-up questions. Look At You Go offers a private record that is not shared with your employer, helping you keep work evidence between reviews. The principle is the same in any format: capture the contribution while you can still explain it accurately.
Common questions
- Is an appraisal evidence template different from a self review template?
- An appraisal evidence template holds the underlying detail: context, actions, outcomes and proof. A self review template organises the account you submit. They work together, but your evidence record will usually contain more detail than the final review.
- What if my employer already has a performance review form?
- Use your employer's form for the submission and this template to prepare the supporting evidence. Map each relevant entry to the form's objectives or competencies, then transfer a concise summary. Keep the fuller record available for questions.
- Should I attach every piece of proof?
- Follow your employer's instructions. Otherwise, use clear references and attach material only where it helps the reviewer assess the claim and is appropriate to share. A large attachment folder is not automatically a clearer argument.
- Can I include work that did not achieve its intended result?
- Yes, when it is relevant to the assessment. Explain the intended outcome, what happened, your contribution and what you changed or learned. Distinguish a well-supported account of judgement or learning from a claim that the original objective was achieved.
You did the work. Keep the evidence.
Look At You Go turns a 90-second weekly check-in into a private, dated record you can use in reviews, promotion cases and CVs.
Start keeping the evidence