The Portfolio That Explains Your Part

A finished piece can look impressive while leaving the important question unanswered: what did you do?

Perhaps you prepared the information but did not design the page. Perhaps you checked the figures but did not run the project. Perhaps the sample is an independent exercise, not something a client commissioned. Each can be useful evidence when its description is accurate.

This book is about making that description clear. It does not ask you to shrink a real contribution. It asks you to make a claim that the accompanying work can support.

CareerOneStop describes a portfolio as work samples showing skills and qualifications. [1] That gives us a starting point, not a guarantee that a portfolio earns a job. The examples and exercises in this guide are original editorial constructions. Its main learner and workplace are invented; their results are not employment research.

Start with a sentence beside one item: In this piece, my responsibility was ___ .

If the answer is everything, check whether that is actually true. Who set the brief? Who supplied the material? Who approved the result? Who built something that your work depended on? Naming those roles can make your own part more understandable rather than less valuable.

If the answer feels too small, replace the size judgment with an action. I checked twelve labels against an approved list says more than I just helped. You can then show a suitable, permitted piece of evidence for that action.

The public sources used for limited context are CareerOneStop's Portfolios, the National Careers Service's How to write a CV, and W3C WAI's Images Tutorial. Full references and the research date appear in Unit 10. They do not endorse this book or its original exercises.

A useful portfolio starts where a reader can connect your words to the work.

Before selecting samples, name the kind of opportunity you want to discuss. A portfolio for office support may need different evidence from one for illustration. One collection does not have to prove every possible ability.

Read the actual request where there is one. Note the tasks, required format and submission instructions. Do not infer permission to send a large attachment or an extra website link when the application process says otherwise.

The National Careers Service advises tailoring a CV to the opportunity. [2] In this guide, the corresponding editorial exercise is to choose samples for a relevant question, rather than assembling everything you have ever made. It is an adaptation for this notebook, not a claim that every employer requests a portfolio.

Write two questions a reader might reasonably ask about the work. Can this person organise information so someone else can use it? Can they check a small set of details carefully? Then look for legitimate evidence, not the most decorative file.

Keep a short selection list. Beside each candidate, write what it demonstrates and what it cannot establish. A polished presentation may show layout choices without proving that the training changed behaviour. A practice exercise may show how you approach a task without proving client experience.

You may discover that one useful item is enough for a particular conversation. You may need more. The number is determined by the purpose and actual instructions, not by a universal rule in this book.

Leave an item out if it needs a false explanation to fit. Selection should reduce the reader's work without enlarging your history.

Possessing a file is different from being entitled to publish it. Access during work, a friendly comment or an old download does not answer every question about sharing.

Before using workplace or collaborative material, check the relevant agreement, policy and authorised permission. Ask about the particular item, the particular audience and the proposed form. Permission for a private interview document is not automatically permission for a public website.

This book offers a planning record, not legal advice or a substitute for qualified advice about rights, confidentiality or contractual duties. If permission is uncertain, keep the item out while you establish what applies.

For each sample, record the material, who can authorise its use, what has actually been agreed, and any limit. Do not turn no response into consent. Keep the permission record private where appropriate; it is not an exhibit that needs to reveal another person's contact details.

Redacting a name may not remove all identifying or confidential information. A screenshot can contain a customer address, an internal note, a file name or a distinctive combination of details. Follow the applicable rules rather than assuming that a visual edit makes every use acceptable.

When real material cannot be shown, consider a separate demonstration you create from invented information. Label it as an independent demonstration. Do not describe it as the hidden client project, reproduce protected material from memory, or suggest that invented results were observed at work.

A missing sample is preferable to an unauthorised disclosure. You can explain a permitted responsibility in words without pretending that the unavailable evidence is publicly inspectable.

A portfolio can steal credit without copying a file. It can do so with a sentence that lets a reader assume you led a whole project when you contributed one part.

Write the first description using the verbs you can defend. Prepared. Checked. Interviewed with permission. Drafted. Implemented. Tested under stated conditions. Choose the action that actually happened, not the grandest available title.

Then name the boundary. Prepared the text using an approved list; graphic layout by a colleague. Checked the figures in a supplied report; source data and final approval by the project lead. These descriptions make responsibility visible.

For this exercise, split one paragraph into three lines: the shared purpose, my action, and other contributions that matter to understanding the sample. This is an original writing aid, not an official hiring format.

Avoid the opposite error of giving away all your work. If you wrote the first draft and resolved a difficult inconsistency, say so accurately. Collaborative credit need not turn your description into a page of apologies.

If you cannot establish an exact division, acknowledge that uncertainty rather than inventing a percentage. A contribution does not become more truthful because it is expressed as a number.

Where tools or generated material were used, describe their role when it is relevant to understanding your contribution. Do not imply that an untouched output demonstrates skills you did not exercise. You remain responsible for the accuracy of the claim you make about the sample.

The sentence should still be defensible when another contributor reads it.

A deliverable is something produced. A result is what happened with or because of it. You may have evidence for one without evidence for the other.

Twelve draft labels prepared is different from a stockroom error rate reduced. The drafts can be inspected. The error-rate claim needs an appropriate record of errors, a meaningful comparison and a defensible explanation. Do not add a percentage because a case-study page seems empty without one.

Make three boxes in your working notes: what I made; what was observed; and what remains unknown. You do not have to fill every box with a success.

If a piece was approved, say what approval covered. Approval of wording is not proof that the finished system was deployed, used correctly or responsible for a later business change.

If a result comes from another person's report, identify that source appropriately and check whether you may share it. Do not silently turn someone else's estimate into your own measured finding.

An honest unknown can be brief: I do not have post-launch usage data. That sentence allows the reader to assess the work without being asked to believe an invisible success story.

You can still describe a decision. I separated the item name from the location code because the two had been hard to distinguish in the supplied draft explains a choice, if that is what happened. It does not automatically prove fewer mistakes in use.

The aim is a portfolio that can survive a follow-up question, not one that runs out of evidence as soon as the interview begins.