What Belongs in a Portfolio¶

The Wrong Question¶

Most students approach portfolio selection by asking: what is my best work?

This is not the wrong instinct, but it is an incomplete question. Best by what measure? Best technically? Best received by a marker? Best in terms of what you learned? Best in terms of what it demonstrates to an employer in a specific field?

The better question — the one that produces more useful answers — is:

What work, honestly presented and specifically explained, makes the most compelling case for how I think and what I can contribute?

That question shifts the frame from impressiveness to argument. And it changes what belongs.

The Four Selection Principles¶

These principles are not a checklist to complete. They are lenses to look through when you are deciding whether a piece of work earns its place.

Not every piece of work needs to meet all four. But work that meets none of them is almost certainly archive material, not portfolio material.

Principle Ⅰ — It Demonstrates Thinking, Not Just Output¶

The most common weakness in student portfolios is the presence of finished things without explanation of how they came to be.

A screenshot of a completed application. A grade boundary achieved. A designed interface with no account of the decisions that shaped it. These tell a reader what was produced. They do not tell them anything about the quality of thought behind the production.

Work belongs in a portfolio when you can explain it — specifically and honestly.

That means: ◆ you can describe the problem it was solving and why that problem mattered
◇ you can explain at least one significant decision made during the work and what alternatives were considered
◆ you can identify something that was difficult, and what you learned from it
◇ you can point to how the outcome is better for the choices you made

If you cannot do these things for a piece of work — if it was completed but not really engaged with, or if the decisions were made by others and you executed — it is not ready for the portfolio. It may belong in the archive. It does not belong on the front page.

Principle Ⅱ — It Advances the Narrative Anchor¶

From Part Ⅱ — Identity, you have developed a narrative anchor — the central, consistent idea about who you are as a professional that holds your portfolio together.

Work belongs in a portfolio when it advances that narrative.

This does not mean every project must be in the same technical area, use the same tools, or serve the same type of client. Range can be part of the narrative. Growth from earlier to later work is part of the narrative.

What it does mean is that each piece of work, when placed alongside the others, contributes to a coherent story — rather than sitting alongside them like a piece from a different puzzle.

Ask this of every candidate piece:

If someone read this work alongside everything else in my portfolio, what conclusion would they draw? Does that conclusion serve or undermine the professional identity I am building?

Work that undermines the narrative — that contradicts the direction, introduces confusion, or pulls attention toward an area you are not developing — belongs in the archive regardless of its technical quality.

Principle Ⅲ — It Has Something Honest to Say¶

Every portfolio entry requires honesty in two directions.

Honest about what worked — the outcome, what was achieved, what the work demonstrates. This is the easier direction of honesty.

Honest about what was difficult — the problems encountered, the decisions that were wrong before they were revised, the things that would be done differently with more knowledge. This is the harder direction, and the more valuable one.

Work that is presented only in its best light — where the process is erased and only the polished result remains — is less convincing than work that shows the struggle and the learning. Not because difficulty is impressive, but because the absence of difficulty is not believable. Experienced readers know that significant work involves significant difficulty. A portfolio entry that claims otherwise raises questions about the honesty of everything else.

Work belongs in a portfolio when you can present it honestly in both directions.

If a project went poorly and produced nothing worth explaining — if the difficulty produced no learning and the outcome was genuinely weak — it may not belong. But if the difficulty produced insight, if the problem forced a rethink, if the failure was handled thoughtfully — that entry may be one of the strongest in your portfolio.

Principle Ⅳ — It Can Be Defended in Conversation¶

This is the most practical test of whether work belongs.

Imagine sitting across from a senior professional in your field. They have read your portfolio entry. They ask:

"Walk me through the most significant decision you made on this project."

"What went wrong, and how did you handle it?"

"Why did you choose this approach over the alternatives?"

"If you started this project again today, what would you do differently?"

If you can answer these questions specifically, confidently, and honestly — the work belongs. If the answers are vague, reconstructed from memory, or dependent on things you cannot actually explain — the work is not ready.

This test matters because the portfolio is preparation for exactly these conversations. Work that you cannot defend under gentle questioning is work that will undermine you in the moments the portfolio is designed to support.

What These Principles Mean in Practice¶

Academic assignments — included or excluded?¶

This depends entirely on the assignment and what you can say about it.

An assignment that required you to make genuine decisions, that you engaged with beyond the minimum requirements, and that produced something you can explain specifically — belongs.

An assignment completed to the brief with no particular engagement, where the decisions were made by the assignment specification rather than by you — does not belong.

Grade is not the deciding factor. A B-grade project that involved genuine problem-solving and learning is more valuable portfolio material than an A-grade project completed by rote.

Group work — included or excluded?¶

Group work belongs, with careful framing.

The key is specificity about individual contribution. "My team built a..." is not portfolio language. "In this group project, I was responsible for..." followed by a specific, defensible account of what you contributed — is.

Work from group projects is legitimate portfolio material when you can explain your individual contribution accurately, attribute collaborative elements fairly, and link to shared artefacts (repositories, documentation) that contextualise your contribution.

If you used Vestigia during your final-year project, your individual Guide A records and Guide B extraction work have already done much of this disambiguation. The individual contribution evidence is already documented — it now needs to be placed in portfolio context.

Work in progress — included or excluded?¶

Work in progress can belong, when it is presented as such — honestly, with a clear account of its current state, what is complete, what remains, and what the intended outcome is.

A project that is genuinely underway and shows interesting decisions and progress is often more compelling than a completed project presented without context. What it requires is that the honest, in-progress state is presented as such — not dressed up as complete.

Work in progress that has stalled — that has not been touched in months, that you have no intention of completing — does not belong. Presenting abandoned work as in-progress is a misrepresentation that surfaces quickly in conversation.

Early work — included or excluded?¶

Early work from earlier years of study belongs when it demonstrates genuine growth — when placed alongside later work, the contrast shows development rather than stagnation.

Early work placed on its own, without the context of later work that shows what you have become, often does more harm than good. An early-year project that reflects limited skills and limited engagement, presented without the frame of growth, gives a reader a snapshot that does not represent who you are now.

If early work belongs, it belongs because of the story it tells alongside what comes after — not because it was once completed and has been sitting in a folder since.

What Does Not Belong — and Why¶

Some categories of work are almost never portfolio material, regardless of how much effort they required.

Tutorial exercises and course-following projects
Work completed by following a tutorial, course, or step-by-step guide does not demonstrate your decisions — it demonstrates your ability to follow instructions. This is a worthwhile skill and a legitimate way to learn. It is not portfolio material because it cannot pass Principle Ⅰ: the decisions were made by the tutorial author, not by you.

Work you cannot speak to
Any project where the decisions were made by others and your role was execution — or where enough time has passed that you genuinely cannot explain what happened — does not belong. If you cannot defend it, including it is a liability.

Work that contradicts your narrative
A project that pulls your portfolio in a direction you are not developing — that introduces a technical area, discipline, or approach you have moved away from — creates confusion rather than depth. Even if the work is strong, its narrative cost may outweigh its individual value.

Work included out of guilt or volume anxiety
The impulse to include weak work because it took a long time, or to add projects to reach an imagined minimum number, produces portfolios that are longer than they should be and weaker for it. The time invested in work is not a selection criterion. The quality of thinking it demonstrates is.

Continue to Quality Over Quantity →