How to Build a Graduate Portfolio That Shows Your Work

A portfolio helps a reviewer see how you think and what you can produce. It may be useful in design, technology, architecture, writing, media, research and many other fields where a CV alone cannot show the quality or process of your work. The format should match the opportunity rather than follow one universal template.

A strong portfolio is edited, contextualised and legally shareable. It does not need to contain every project you have completed. Before including assessed, client, workplace or group material, confirm ownership, confidentiality and permission. When uncertain, describe the learning without publishing restricted content.

Start with the role or audience

Read the application instructions and identify what evidence the reviewer needs. A software role may value a working repository and technical decisions; a design role may need visual process; a writing role may need concise samples. Build for that decision instead of showing a general archive of everything.

Choose the most suitable format

Decide whether the employer expects a website, PDF, repository, showreel, physical book or presentation. Consider file size, accessibility, device use and whether links will remain stable. Follow the requested format first, even if another format gives you more creative freedom.

Select a small set of strong projects

Choose work that is relevant, recent enough to represent your ability and varied enough to show useful range. A few well-explained examples are usually easier to evaluate than a large collection with inconsistent quality. Remove work that requires lengthy excuses or adds no new evidence.

Explain the brief and constraints

Introduce each project with the problem, audience, requirements, timescale and important limitations. This context helps a reviewer judge your decisions fairly. Keep the explanation concise and avoid inventing a commercial brief for a university exercise; label academic, voluntary, personal and paid work accurately.

Make your contribution unmistakable

For team projects, state your role, decisions and outputs separately from the group result. Credit collaborators where appropriate and do not imply ownership of work completed by others. If responsibilities changed during the project, explain the relevant part rather than using a broad title that exaggerates your involvement.

Show process when it supports judgement

Include selected research, sketches, prototypes, tests or revisions that reveal how the result developed. Do not add process pages merely to make the portfolio longer. Choose evidence that demonstrates a decision, challenge or improvement, and remove private data or feedback that was not intended for publication.

Present outcomes honestly

Describe what was delivered and what you learned. Use measured results only when they are documented and can be explained. If the project was a concept rather than a deployed product, say so. Honest limitations can demonstrate judgement more effectively than a polished claim that collapses under questions.

Tailor the order for fast review

Place the strongest and most relevant evidence early. Use clear navigation, short project labels and a consistent structure so the reviewer can understand each example quickly. Do not hide essential information behind animations, unusual menus or lengthy introductions that make the portfolio difficult to scan.

Write concise project descriptions

Use plain language to explain the objective, your contribution, the approach and result. Avoid unexplained jargon, long academic background sections or decorative claims about creativity. The text should help a reviewer interpret the work without competing with the work itself.

Check accessibility and loading

Use readable contrast, descriptive labels, captions where needed and sensible media sizes. Test keyboard navigation and mobile layouts when the format allows. Compress large files without making essential details illegible, and provide an alternative when video, animation or complex interaction carries important information.

Protect confidential and personal information

Remove names, email addresses, internal dashboards, private datasets, unreleased designs and identification details. Do not assume that obscuring one field makes a confidential page safe. When the process cannot be shown, create a permission-safe summary or a new illustrative example rather than publishing restricted evidence.

Test every link while signed out

Open the portfolio from another browser or private window and check that projects, downloads, videos and contact routes work without special access. Confirm that repositories do not expose secrets or private history. A broken or permission-locked portfolio can undermine an otherwise careful application.

Prepare to discuss every included item

Review the decisions, tools, challenges and trade-offs behind each example before an interview. Remove work you cannot explain confidently or did not substantially contribute to. Keep supporting notes privately so you can answer detailed questions without crowding the public portfolio.

Create a tailored entry point

When one portfolio serves several directions, create a relevant landing page or ordered selection for the opportunity. Do not make the reviewer search through unrelated material. Keep the permanent source intact while controlling the route and emphasis used in each application.

Ask for evidence-based feedback

Give a reviewer the role instructions and ask which project demonstrated the required capability, where your contribution was unclear and which page slowed them down. Specific observation is more useful than a general judgement about whether the portfolio looks impressive.

Maintain the portfolio after submission

Keep the submitted version stable during an active application or record any material changes. Repair broken links quickly, but avoid replacing evidence so extensively that the employer sees a different portfolio from the one referenced in your application. Archive dated versions securely.

Final checklist

• The format matches the opportunity’s explicit instructions.
• Every project is relevant, accurately labelled and legally shareable.
• Individual contributions are separated clearly from team outcomes.
• Navigation, accessibility, loading and signed-out links have been tested.
• Private, confidential and unauthorised material has been removed.

Explore subject pathways in the Univs programme catalogue, compare institutes available on Univs and see how Univs supports the student journey. The application instructions and your ownership permissions should control what the portfolio contains.