AI-created editorial photo. Not the specific reviewed product.
A finished project can leave useful evidence scattered across messages, documents and screenshots. Months later, the hard part is often remembering what each item proves. A compact evidence note helps you reconstruct a decision or explain your contribution without reopening every file. Start with one project you expect to refer to again.
Name the question the evidence answers
Instead of collecting everything, decide what you may need to explain. You might want to show how you reduced a confusing instruction sheet, why a design changed or which part of a group project you completed. The question gives the collection a purpose and helps you exclude files that add no useful context.
For an illustrative workshop project, the question could be: “How did we make the exercise easier for first-time participants?” Useful evidence might include the earlier instruction sheet, the revised version and a dated note describing the change. A folder of attractive event photos would not answer that question by itself.
Save context beside the link
Write the item’s name, where the original is stored and why it matters. Add the date or version when another copy could be mistaken for the relevant one. Then describe your own role precisely. “Rewrote the opening instructions” is clearer than “improved the workshop” when several people contributed.
Separate observation from interpretation. “Three people asked where to begin during this session” records an observation if you actually recorded it. “The revised sheet eliminated confusion” is a much stronger conclusion that needs evidence. If you did not collect a before-and-after result, say what changed without inventing an outcome.
Keep permission and availability visible
A file you can access today may live in an account you will later leave. Note the storage owner and any sharing restrictions. Keep only copies you are allowed to retain. For work involving other people, a private reference may be appropriate even when a public portfolio example is not.
Avoid placing personal details in a general evidence notebook just because they appear in a source file. A short description can preserve the reason an item matters without duplicating sensitive information. If a future reader needs the full record, point them to its authorized location.
Close the project with a short handoff
At completion, write what was delivered, what remains unresolved and which version is final. Include the next person or process responsible for any follow-up. Put this note somewhere you are likely to search, using the project name and ordinary words for the problem it addressed.
Finally, try retrieving the evidence from the question alone. Can you find the relevant version and explain the contribution in a few sentences? If not, improve the note while the context is fresh. The result should be a small, trustworthy record you can reuse, not a second archive that demands constant maintenance.
Read next
Personal Note Tools Compared: Files, Structure and Capture
