Start with what you are allowed to share
A portfolio case study does not need to reveal every detail of a project to show what you can do. It does need to respect the people and organizations behind the work. Before drafting, check the agreement, project brief and any sharing rules you were given. A finished project is not automatically a public project, and material visible to a team may still be unsuitable for your website.
Make a list of items you might want to show: the client’s name, your role, screenshots, files, metrics, feedback and final deliverables. Mark each as approved, uncertain or off-limits. If permission is unclear, ask the appropriate contact what can be published and keep a record of their answer. Treat a request to share work in a private interview as a separate question; it is not the same as permission to post it publicly. If you cannot get a clear answer, use a more general description or leave the material out.
Build the story around your contribution
A useful case study explains the problem, your responsibility, the choices you made and what you delivered. Those points can often be described without naming a client or exposing internal plans. For example: “I organized a small team’s handoff process for a multi-page website” tells a reader more about your contribution than a gallery of unexplained screens. You can describe the constraints you worked within, such as a short timeline or several reviewers, without disclosing a private budget or schedule.
Be precise about your role. If you created wireframes but another person designed the final interface, say so. If you worked with a team, distinguish your decisions from group decisions. Results deserve the same care: use an approved outcome if you have one, or explain what the deliverable was intended to support. Avoid turning an unverified impression into a claim that the project increased sales, saved time or changed user behavior.
Choose visuals that do not carry hidden details
Screenshots can reveal more than their main subject. Check names, messages, account details, browser tabs, file paths, comments, metadata and background content. Cropping may remove irrelevant areas, but blurring is not always enough to protect text that can be inferred from context. For sensitive material, it may be safer to create a clean diagram that explains the workflow rather than edit a real project image.
Reconstructed examples can help readers understand your process. You might make a sample content map with fictional page names or a mock interface with invented copy and data. Label it clearly as a reconstruction or illustrative example, not a client-approved screenshot. Keep the underlying structure general enough that it does not disclose a proprietary method, unreleased feature or recognizable private content. If you cannot make a faithful but safe visual, a short written explanation is a strong alternative.
Create a public version with clear boundaries
Consider a two-layer portfolio: a public case study with the details you are comfortable sharing, and a prepared conversation about your work for interviews. The public version might include an anonymized project description, your role, a simplified process diagram and a few lessons learned. Do not assume the private conversation permits confidential disclosures. Decide in advance which points you can discuss, and request permission before showing restricted files or screens to anyone.
For a student project or freelance assignment, the same approach applies even when the work feels informal. Classmates may own parts of a group deliverable, and a small client may have good reasons not to publicize a project. When you need to show a skill that confidential work cannot safely demonstrate, consider making a separate personal exercise. Present it as independent work rather than implying it was delivered to a client.
Review before publishing—and after changes
Read the case study as someone unfamiliar with the project. Could they identify the client from a distinctive description? Does a diagram reveal a private workflow? Do the visuals match the captions, and are reconstructed elements labeled? Ask a trusted teammate to check for accidental disclosures if they are authorized to review the material. Remove anything you cannot confidently explain or share.
Keep a simple record of what was approved and which portfolio version was reviewed. Before adding a new image, result or project detail later, check it against the same boundaries rather than relying on the earlier review. A strong portfolio makes your judgment visible: it shows how you worked, credits collaborators fairly and leaves private information where it belongs.
