Update when your work or goals change
There is no ideal number of weeks between portfolio updates. A useful starting point is a brief check every few months, followed by a deeper review when your skills, services or goals change. The brief check can catch broken links, missing images and contact details that need attention. The deeper review asks whether the work on display still helps you reach the opportunities you want.
Add a project soon after it is finished if it fills a clear gap, such as showing your first accessible website build or your ability to coordinate a small team. You do not have to publish every completed assignment. If you are busy, keep a private list of promising projects and revisit it at your next scheduled review. This is easier than trying to rebuild your portfolio whenever an application or client enquiry arrives.
Choose work for the audience you want to reach
A portfolio is a selection, not an archive. Before changing it, write down the kind of work you hope to get next and what a visitor needs to see to trust you with it. A freelance designer seeking identity projects might show how a logo system works across several uses, rather than filling the page with unrelated graphics. A student applying for a product role might include a class project that explains a design decision and what testing changed.
Small teams can use the same approach. If the team wants projects involving handoff to developers, a case study showing organized files, clear specifications and a finished product may be more useful than a gallery of polished screens. Aim for enough variety to demonstrate your range without making visitors search for the work most relevant to them. The strongest projects should be easy to find.
Remove work that sends the wrong signal
Consider removing a project when it is no longer representative of your ability, points toward work you do not want to repeat, or duplicates a stronger example. An older project is not automatically a poor one: keep it if it still demonstrates a useful skill and you can explain its context honestly. Conversely, a recent project does not earn a place just because it is new. Ask what each item contributes that the others do not.
Take down or revise work that you cannot share appropriately. Client material, internal documents and collaborative projects may have permission or confidentiality limits. If you are unsure what can be shown, seek permission or describe your contribution without exposing sensitive details. Also remove broken demonstrations and claims you cannot support. If a project remains valuable but its presentation is weak, improving its description or images may be better than deleting it.
When you retire a project, save its files and notes privately. You may need them later to recall a method, explain your experience or build a more suitable case study. Removing something from a public portfolio does not erase the work you did.
Refresh the explanation, not just the images
An update does not always mean adding or deleting a project. Sometimes the best improvement is making an existing example easier to understand. For each featured piece, briefly identify the goal, your role, the constraints, the decisions you made and the result you can describe accurately. If the work was collaborative, distinguish what you contributed from what others did. Replace vague statements such as “improved the experience” with a concrete explanation of what changed, without inventing metrics.
Check that images are readable and have enough context to make sense. A screenshot can show the final work, while a short caption can explain a choice a visitor might otherwise miss. Students can describe what they would test next in a concept project. Freelancers can clarify how they handled feedback. Small teams can explain how they coordinated delivery. These details help a visitor understand how you work, not just what the finished piece looks like.
Make the review routine small enough to keep
Set a recurring reminder and use a short checklist: open every project, test its links, check permissions, read the copy and confirm that your contact information works. Then ask three questions about each piece: Would I like more work like this? Does it show something distinct? Can I explain my role clearly? Mark projects to keep, revise or remove, and tackle the most important change first.
For a deeper review, look at the portfolio as a first-time visitor would. Is it obvious what you do? Can someone find a relevant example quickly? Does the portfolio reflect your current direction rather than every direction you have explored? A steady routine of small edits keeps the portfolio ready to share while leaving you time to do the work that will eventually belong in it.
