Your next review is easier to prepare for when you can see what you finished, not just what you were assigned. A done list at work gives completed work a place to live after it disappears from your task board, inbox, or meeting notes. That matters when you have spent months improving a reporting process and can remember the final dashboard but not the decisions, checks, and fixes that made it reliable. The list should be quick to maintain and detailed enough to help you explain your contribution later.
What belongs on a done list at work
A done list is a running record of meaningful completed work. It can include finished projects, resolved problems, useful decisions, and smaller contributions that would otherwise vanish between reviews. Unlike a task list, it records what happened after the work was done, including anything you learned about its effect.
Use a simple threshold: would you want to remember this when explaining your work to your manager or answering an interview question? Finishing a routine status update may not qualify. Finding that two reports counted the same customers differently, resolving the discrepancy, and documenting the agreed definition probably does. You can still record work whose outcome is uncertain. Mark it as pending rather than filling the gap with a result you cannot support.
Capture the details while you can still verify them
Write an entry when a piece of work reaches a meaningful stopping point. A short note after a handoff, decision, or resolved issue is easier to write than a reconstructed account months later. Give each entry enough detail to answer these questions:
- What problem or request led to the work?
- What did you own or decide?
- What changed, or what is still being measured?
- Where could you verify the result later?
For example, “Updated the dashboard” will be hard to use in a review. A more useful entry would say: “Reworked the dashboard’s customer definition after finding inconsistent counts across two reports. Agreed on the definition with the reporting partners, updated the calculations, and noted where to check whether the discrepancy returns.” This records your contribution without claiming a business outcome that has not been measured.
A proof pointer can be a document title, a meeting date, or the name of someone who can confirm a handoff. Keep the substance of your work in a personal record without transferring confidential reports, customer-level data, or internal documents into it.
Choose a cadence you can keep
Log a clear milestone when it happens, then spend a few minutes each week looking for anything you missed. The milestone entry preserves details; the weekly check catches quiet work, such as answering a recurring question or removing a source of rework. If your work has long project cycles, you can also note a consequential decision before the final result exists.
If that rhythm does not fit your work, this guide to choosing a daily, weekly, or project-based work-logging cadence explains the tradeoffs.
Keep the list selective enough that you will read it again. A record of every meeting can bury the work you need at review time. When you miss a week, resume with the most recent finished item instead of trying to reconstruct every day. A sustainable list with a few useful entries beats an exhaustive one you abandon.
Turn finished work into usable evidence
Before a review, group related entries and look for a pattern. Several small reporting fixes may show that you improved the reliability of a process, even if none was a standalone project. For each pattern, distinguish the effort you put in from the result you can actually demonstrate. “Investigated discrepancies” describes activity; “resolved conflicting definitions used by two teams” explains a change you made.
The same record can help with interviews. Pick an entry with a decision, an obstacle, and a verifiable outcome. Expand it into an answer about how you handled ambiguity or worked across functions. If the result is still pending, say so and explain how you checked the quality of the work. Clear limits make the example more credible than a polished claim you cannot back up.
Keep the next entry small
Choose one recently completed piece of work and write four lines covering the problem, your contribution, the change, and a proof pointer. You can improve the wording when you need it for a review or interview. The important step today is preserving the details before they become difficult to recover.
ImpactLogr is built for keeping those entries together so you can return to them when you need evidence. Save your next completed-work entry in ImpactLogr.