In this guide
A lightweight method for remembering outcomes, changed priorities and the support you needed.
Record the things memory loses
A performance conversation is easier when both employee and supervisor can discuss concrete work. Tufts’ Performance Management Cycle guidance emphasizes regular check-ins about priorities, goals and development. This article offers an independent note-taking method to support those conversations; it does not replace official forms, determine a rating or promise a compensation outcome. Keep a small running record rather than attempting to reconstruct an entire period immediately before a review. The aim is accuracy and reflection, not a diary of every email and meeting.
For each meaningful piece of work, note the intended outcome, your contribution, what happened and the evidence available. Include changes in scope or priority. A task that was deliberately paused may reflect a sound decision rather than a missed commitment, but that context is easily forgotten. Record who made the decision and what replaced the work, using appropriate internal practices. Avoid turning your personal notes into a repository of confidential material that belongs only in an authorized system.
Distinguish effort from result
Effort matters, especially during difficult periods, but it is not the same as an outcome. Explain what the effort enabled. Did a process become clearer, a request reach the right owner, a deadline become achievable or a recurring error get identified? Use numbers when they are meaningful and verifiable. If a result cannot be measured precisely, describe an observable change. Do not invent a percentage to make careful administrative or service work sound more impressive than the evidence supports.
A hypothetical record might say that an employee revised instructions after noticing repeated incomplete requests. The useful evidence could be the revised document, feedback from users and a comparison of the issues being raised, if tracking is authorized and practical. The employee should also note who reviewed the change and what remained unresolved. This is more informative than “improved efficiency,” because it lets a reviewer understand the intervention and its limits rather than accept an unsupported conclusion.
Include obstacles and learning
A balanced record includes work that did not proceed as planned. Describe the obstacle, what you tried, when you raised it and what support would have helped. Avoid writing solely to assign blame. A dependency outside your control is relevant, but so is how you communicated it. Discuss significant barriers while they are active instead of saving them for the review. A contemporaneous conversation gives the team a chance to change priorities or provide help before the problem becomes a retrospective explanation.
Keep one or two development observations alongside delivery examples. Perhaps you learned to prepare a clearer handover or recognized that a technical task requires more training. Connect the learning to work you can actually show. Course completion can be part of the record, but it should not crowd out what changed afterward. The method in Turn a training course into a useful development plan can help you convert a broad development intention into a small practice task and a specific feedback question.
Prepare a conversation, not a defense brief
Before a formal review, group your notes around the agreed goals and responsibilities. Select the examples that explain the period fairly rather than presenting everything you collected. Identify successes, material changes, unresolved concerns and a few priorities for the next period. Check the applicable university and departmental process for timing and required documentation. A general web page or a colleague’s schedule may not fully describe the process that applies to your own situation.
Bring questions as well as conclusions. Ask which contributions had the most value, where expectations differed and what should receive less attention next. A useful review leaves both people with clearer priorities. Your record supports that outcome by making the conversation less dependent on recent events or confident recollection, while preserving room for feedback you did not anticipate.
Continue reading: Turn a training course into a useful development plan, Prepare for a campus disruption before the announcement arrives, Four campus settings, many different working days.