How to write a portfolio case study from real work

A CV says what you did. A case study shows how you think. It takes one piece of real work and lets a reader see the problem, your part in it, the decisions you made, the evidence for the result and what you learned. Designers, analysts, project managers, engineers, teachers and consultants all use them, in portfolios, in applications and in interviews. A good one is short, honest and easy to check. A weak one is a list of impressive words around a screenshot. This guide explains how to write the good kind, and how to deal with confidentiality, which stops many people from writing one at all.

What a case study is, and what it is not

A case study is not a summary of a project, and it is not a marketing success story. A summary says what the project was. A success story says it went well. A case study answers a reader's practical questions: what was wrong, who was affected, what did you do yourself, why did you choose that option, how do you know it worked, and what would you change?

The reader is usually a hiring manager or a client with five minutes. They want to judge your reasoning, not admire the finished product. That is why a case study can be strong even when the project was small, or partly failed, as long as the account is clear and truthful.

Choose a project you can discuss properly

Before you write, test each candidate project with five questions.

Is it relevant? Does it show the kind of work you want to be hired for next?
Is your contribution clear? If you cannot say what you personally did, the reader cannot judge you.
Do you have evidence? Documents, measurements, before-and-after material, feedback, or at least a clear memory of the decisions.
Do you have permission? More on this below.
Can you answer follow-up questions? If the project was five years ago and you remember little, choose another.

Two or three strong cases are better than ten thin ones. If you are early in your career, a study, volunteer or personal project can serve, as long as you label it as such. The UK National Careers Service makes the same point about CVs: if you are applying for a first job, focus on skills learned through projects, work experience or volunteering.

Set out the problem and the starting point

Start with the situation, in a few sentences. Who was the work for? What was not working? What constraints were there: time, budget, tools, a team that was already stretched? The aim is to let the reader see how hard, or how simple, the starting point was. Without it, any result looks bigger or smaller than it is.

The National Careers Service recommends the STAR method for describing experience: situation, task, action, result. A case study is a longer form of the same thing. The situation and task are your opening. The action is the largest part, because it is where your thinking shows. The result closes the account.

Say what you did, and what others did

Almost all real work is shared. That is not a weakness, but it makes a case study easy to overclaim. Be exact:

Your role. Your job title, the dates and what you were responsible for.
Your actions. "I interviewed twelve users" and "we interviewed twelve users" mean different things.
Your decisions. Show at least one choice where you weighed two options. Name the option you rejected, and why.
Others' contribution. A short line crediting the team is honest and costs nothing.

An interviewer will probe exactly this part. If the case study says "I led" and you cannot explain how, the case study works against you.

Present evidence and results accurately

A result is a number or an observation with a comparison. "Faster" is not a result. "Average time to complete a routine request fell from 18 to 13 minutes over the two months we measured" is a result. Whenever you can, give three things: the measure, the baseline and the period.

Also say how sure you are. The honest limits of a result are part of the evidence:

The sample. Twenty requests are not two thousand.
The period. A change that held for one month may not hold for a year.
Other causes. Staffing, season or a change in the mix of work can move numbers too.
What you could not measure. Say so.

If you have no numbers, describe the observable change instead and be clear that it is an observation. Do not invent a figure to fill the gap.

Confidential and personal information

This is where many case studies stop. A project was done for an employer or a client, and you worry you may not show it. Treat the question seriously, because the consequences of getting it wrong land on you.

Start with permission. Check your contract and your employer's policies, and if you are unsure, ask in writing. A short, clear email from a manager or client saying which parts you may show is worth far more than a guess. Rules differ by country and by contract, and this guide is not legal advice.

If permission is limited, change what makes the work identifiable. The UK Information Commissioner's Office (ICO) guidance on anonymisation says that whether you can effectively anonymise personal data depends on the techniques you use, and that you should reduce the risk of identifying people to a sufficiently remote level. For a portfolio, that has practical consequences. Taking a person's name off a screenshot may not be enough if their role, team, location or a distinctive detail still points to them. Numbers can identify a client too. Consider:

replacing the client with a general description, such as "a regional retailer";
rounding or indexing figures, and saying you did so;
redrawing a screen or a chart with invented data in the same layout;
leaving out anything about a named individual.

If none of that is acceptable, write the study about a fictional or personal project that uses the same method. Label it clearly as an example. A fictional client presented as a real one would damage your credibility far more than not having the case at all.

Worked example: a process improvement

The numbers here are invented. A fictional team measured how long a routine request took to complete, before and after a change to how requests were sorted.

Measure	Before	After
Average time per request	18 minutes	13 minutes
Period measured	4 weeks	4 weeks

The change is 18 - 13 = 5 minutes. As a share of the starting value: 5 / 18 x 100 = 27.8 per cent. A case study can say that the measured average fell by about 27.8 per cent between the two periods.

What it should not do is say that the person who wrote it caused the whole reduction. In this example, the mix of requests may have changed, staffing may have differed, and only four weeks were measured on each side. An honest paragraph would say: "The average fell from 18 to 13 minutes. I redesigned the sorting rules, and a colleague updated the template. We cannot rule out that a quieter period also helped." That sentence separates what was observed from what you did, and from what you cannot claim. Readers who see this care trust the rest of the case.

Build a portfolio around the cases

A portfolio is an index plus the cases. Keep a simple record for each project: the title, your role, the dates, the permission you have, the evidence you hold and where it is stored. This record saves time when you adapt a case for a particular application, and it keeps you honest about what you can say.

For each case, write a three-sentence summary you can say aloud. Interviews rarely ask you to recite a document. They ask you to talk through a project, and the people who do well are those who know the story and its limits. Practise the account out loud, including the part where it went wrong.

Finally, consider access. Use real headings, short paragraphs, readable colour contrast and text descriptions for images, so that people who use screen readers or print the page can follow the case. A case study nobody can read has not helped anyone.

Tool that fits

The Career Casebook (EUR 19, paid once) has 12 case-study layouts as editable Word templates with guidance and highlighted placeholders: project overview, problem statement, research, process, design decision, implementation, collaboration, challenge, measurable outcome, lessons learned, before and after, and project summary. It also has 12 worked examples as HTML and PDF in both A4 and US Letter, using fictional organisations only, a 10-page guide and a blank portfolio index. It is guidance and templates. It does not promise interviews or offers, and it is not legal advice.

What to do next

The Career Casebook has 12 case-study layouts as editable Word templates, 12 worked examples in HTML and PDF (A4 and US Letter, fictional organisations only), a 10-page guide on evidence, confidentiality and interviews, and a blank portfolio index. €19 once; it promises no interviews or offers.

See the Career Casebook

Questions people ask

What if my project has no impressive numbers?

Use what you do have: the starting situation, what you decided and why, what changed in plain terms, and what you would do differently. A modest, honest result with clear evidence reads better than a large number nobody can check. If you have no measurement at all, say so and describe the observable change, such as fewer questions from colleagues or a process that now has written steps.

Can I include confidential client or employer work?

Only with permission, or after you have removed what makes the work identifiable. Removing a name is not always enough: the ICO guidance on anonymisation says effectiveness depends on the techniques used and on reducing the risk of identification to a sufficiently remote level. When in doubt, ask in writing, or write the case study about a fictional or personal project that uses the same method.

How many case studies does a portfolio need?

There is no fixed number. Two or three well-evidenced cases that match the kind of job you want are usually more useful than a long list. Choose projects where your own contribution is clear, and where you can answer follow-up questions in an interview.

Sources

We checked each source on 17 October 2026. If a fact here is out of date, tell us at hello@hiddenway.info.