When and How to Update¶
The Maintenance Problem¶
Most portfolio maintenance advice says: update your portfolio regularly.
This is not wrong. It is not useful.
Regularly is vague. It produces guilt when the portfolio has not been updated — but no clear trigger for actually updating it. The portfolio sits on a mental list of things to do eventually, never urgent enough to displace whatever is more pressing today.
Effective portfolio maintenance is not driven by time intervals. It is driven by triggers — specific events in your professional life that produce portfolio-relevant material and represent the natural moment to act on it.
This document defines those triggers and the lightweight process that makes acting on them manageable.
The Trigger Model¶
A trigger is an event that produces either new portfolio material or a reason to review what is already there. Maintenance happens at triggers, not on a calendar.
Trigger Ⅰ — Project Completion¶
What it is: A significant piece of work has reached a conclusion — submitted, delivered, deployed, or published.
Why it is the right moment: The details are clearest immediately after completion. The decision reasoning is still accessible. The difficulty is still honest rather than retrospectively smoothed. The outcome is defined. The reflection is available before time softens it.
What to do:
◆ write or complete the case study for this project in the master portfolio — using the structure from Part Ⅳ
◇ assess whether this project belongs in the public portfolio — does it advance the narrative anchor, meet the quality standard, and represent where you currently are?
◆ if yes, add it to the public portfolio and consider whether an older entry should be retired or moved to archive
◇ update the bio if the project represents a meaningful shift in focus or capability
Time required: Two to four hours for the full case study, thirty minutes for the public portfolio update if the case study is already written.
Trigger Ⅱ — A Professional Shift¶
What it is: Something significant has changed in your professional situation — a new role, a work placement, a career transition, the beginning or completion of a postgraduate programme, a significant change in professional direction.
Why it is the right moment: A professional shift means the portfolio no longer fully represents you. The bio and positioning statement are likely out of date. The narrative anchor may need revision. The work foregrounded in the public portfolio may no longer be the most relevant.
What to do:
◆ revise the bio and positioning statement to reflect the new situation — not retrospectively describing the past, but accurately describing the present
◇ review the narrative anchor — has your professional direction changed? Does the portfolio's overall argument still hold, or does it need reframing?
◆ review the public portfolio entries — are the foregrounded projects still the most relevant for where you are now?
◇ update all platform profiles to reflect the change — LinkedIn, GitHub bio, Behance tagline — keeping everything consistent
Time required: One to two hours for a full professional shift review.
Trigger Ⅲ — An Upcoming Application¶
What it is: A job application, postgraduate programme application, scholarship, grant, or other professional opportunity is approaching.
Why it is the right moment: You are about to direct someone to your portfolio. It needs to be current, consistent, and calibrated to the audience.
What to do:
◆ run the identity audit from Part Ⅲ — Identity Across Platforms — check every platform for currency, consistency, and broken links
◇ build a tailored version of the portfolio for this specific application — selecting the entries most relevant to this audience and this opportunity
◆ confirm that the public portfolio and all linked artefacts are accessible — every link tested, every repository public if it should be
◇ read the case studies you will be drawing on in any interview or review — not to rehearse a script, but to have the material clearly in mind for the questions that will follow
Time required: Two to four hours for a full pre-application review, less if the portfolio has been maintained consistently.
Trigger Ⅳ — The Annual Review¶
What it is: Once per year — not tied to a specific event, but to the passage of time — a deliberate review of the entire portfolio system.
Why it is necessary: Projects get completed and not documented. Bios drift from reality. Platforms accumulate inconsistencies. Links break. The annual review is the catch-all maintenance pass that addresses everything the trigger-based model may have missed.
What to do:
◆ review the master portfolio — are all significant projects from the past year documented? Are there gaps that need filling?
◇ review the public portfolio — does it still represent where you are? Is the oldest entry still relevant, or should it be retired?
◆ run the full identity audit across all platforms
◇ update the bio and positioning statement — even if a professional shift has not occurred, a year of development leaves traces worth capturing
◆ check all linked artefacts — repositories, deployed systems, published documents — and update or remove links that have become inactive
Time required: Two to three hours. Worth scheduling as a fixed event — the same time each year, treated as a professional commitment rather than an optional task.
Trigger Ⅴ — When Something Notable Happens¶
What it is: An unexpected professional event — a project is recognised, a piece of work generates significant feedback, you publish something, you speak at an event, you contribute to an open source project that gains traction.
Why it is the right moment: These events produce portfolio material and often represent genuine milestones worth capturing before their specifics fade.
What to do:
◆ document the event in the master portfolio — even briefly, even informally — while the details are clear
◇ assess whether it belongs in the public portfolio or in the master portfolio as background material
◆ consider whether it warrants an update to the bio or narrative anchor
◇ share it appropriately on LinkedIn or other platforms where professional activity is visible
Time required: Thirty minutes to document; additional time if the public portfolio warrants updating.
The Lightweight Maintenance Process¶
For each trigger, the maintenance process follows the same lightweight sequence:
Step Ⅰ — Document first
Before deciding what is public, document what happened in the master portfolio. Raw, honest, in whatever form the material supports. The editing comes later.
Step Ⅱ — Assess for the public portfolio
Apply the curation principles from Part Ⅲ. Does this new material belong in the public portfolio? If yes, does anything currently in the public portfolio need to be retired to make room?
Step Ⅲ — Update platform profiles
Whatever changes to the public portfolio are made, propagate them to the platform profiles — LinkedIn, GitHub, Behance, personal site. Consistency across platforms is a product of updating them together, not separately.
Step Ⅳ — Test everything
After any update: click every link. Open every linked repository. Check the portfolio on a mobile device. Confirm every platform reflects the current state.
Making Maintenance Feel Manageable¶
The most common reason portfolio maintenance does not happen is not laziness — it is that the accumulated gap between current state and portfolio state has grown large enough to feel like a rebuild.
Two habits prevent this:
Document immediately after completion, not before the next application. The case study written the week after a project completes takes two hours. The case study reconstructed from memory six months later takes four hours and produces weaker material. The habit of writing while the details are clear makes every subsequent maintenance task easier.
Treat the master portfolio as the lowest-friction record.
The master portfolio does not need to be polished. Its job is to capture material while it is available. Write the case study in rough form if needed — the editing is a separate, lighter task. A rough case study in the master portfolio is infinitely more useful than a polished case study that was never written because the standard felt too high.
The five-minute maintenance habit
After every significant project session — not a complete project, just a meaningful session — spend five minutes writing a note in your master portfolio record:
- what decision was made today
- what problem was encountered
- what changed from yesterday
These notes are not case studies. They are the raw material from which case studies are built. A project documented in five-minute notes as it progresses produces case study material that retrospective writing cannot match.
This is the habit that Vestigia builds for the capstone year. Applied to every significant project — at every stage of your career — it is the foundation of a genuinely living portfolio.