Many interns want portfolio pieces that show real impact, but sharing employer data or client work can be off limits. This guide walks you through a practical, ethically safe process to convert internship projects into portfolio case studies without exposing confidential information. You’ll get step-by-step instructions, an anonymization template, a worked example, a short checklist, likely challenges and mitigations, plus a small FAQ.

When to start: quick authorization and risk triage

Before drafting anything public, stop and do a short authorization check. Contact your internship supervisor or HR and ask: “Is it okay to publish a high-level case study describing the project and my role if I remove client names and numbers?” Save any written permission. If permission is denied, note whether a sanitized version would be allowed.

Also triage risk: label materials by sensitivity. Examples of material to avoid publishing unless expressly permitted: internal roadmaps, raw client data (sales, user lists, PII), proprietary algorithms, non-public market analyses, and internal screenshots that reveal account information.

Step-by-step: create an anonymized, authorization-ready case study

1. Collect your artifacts privately. Gather drafts, slides, code snippets, and your personal notes into a private folder so you can work offline.
2. Redact identifying specifics. Replace company, client and product names with generic placeholders (e.g., “regional retail client,” “internal CRM”), and remove or generalize dates if needed.
3. Aggregate metrics. Instead of exact numbers, use ranges or percentage-based outcomes (e.g., “reduced onboarding time by ~30%” or “increased engagement from low to medium levels”).
4. Rewrite sensitive methodology. Abstract proprietary processes into general approaches (e.g., “conducted structured usability tests” rather than showing a proprietary test script).
5. Ask for written approval. Send the sanitized draft to your supervisor or the compliance/PR contact and request written sign-off or specific feedback on what to remove.
6. Finalize with visual privacy checks. Review images, mockups and screenshots for metadata, visible account names, or hidden text—crop or replace graphics with neutral diagrams when needed.
7. Publish and archive permission. Keep records of approvals and a copy of the version you published, plus the original private artifacts stored securely for your reference.

Worked example: UX intern who redesigned a checkout flow

Context: You were a UX design intern who contributed to a checkout redesign for an e-commerce client. You improved form layout, added an optional guest checkout path, and ran five remote usability tests.

Original sensitive items: client name, exact conversion lifts, screenshots of production checkout, raw participant quotes containing personal info.

Sanitized case study approach:

• Title: “Checkout flow redesign for a mid-sized e-commerce retailer — UX intern case study.”
• Role: “Led wireframe updates, prototyped new flow, and coordinated 5 remote usability sessions.”
• Problem statement: “High drop-off on payment step due to long forms and unclear guest options.”
• Solution summary: “Simplified form fields, introduced guest checkout path and progressive validation.”
• Outcome phrasing: “Usability testing showed smoother task completion; post-launch metrics were in the low double-digit percentage lift range for completed purchases.” (Only share approximate ranges unless permitted to share exact metrics.)
• Visuals: Replace production screenshots with annotated low-fidelity wireframes that communicate interaction changes without exposing live UI or identifiable content.

Send this draft to the supervisor with a brief note: “I’ve anonymized the case study and replaced screenshots with wireframes. Please let me know if anything needs removal before I publish.” Log their reply.

Reusable template: case study outline (fill in and sanitize)

Use this template as your working draft and remove or generalize items flagged as sensitive.

• Project title (anonymized)
• Your role and contributions
• Context and constraints (concise, anonymized)
• Problem statement
• Approach and methods (abstracted if proprietary)
• Key deliverables (wireframes, reports, tests — sanitized)
• Outcome (use ranges or percent change language)
• Lessons learned and next steps
• Contact/availability for follow-up (your professional contact, not the company)

Quick checklist before publishing

• Get written permission or explicit no-objection from supervisor/HR
• Replace names with placeholders
• Convert exact figures to ranges or percentages unless allowed
• Remove/replace screenshots that reveal accounts or PII
• Strip metadata from images and files
• Keep a copy of the approved draft and approvals

Two common challenges and practical mitigations

Challenge 1 — Supervisor won’t respond before your deadline: If you can’t get a timely reply, prepare and keep a private, fully sanitized version and delay publishing until you have written approval. You can still use the work in interviews by bringing the sanitized materials offline (on a tablet) and explaining you obtained permission to discuss it at a high level.

Challenge 2 — The employer permits description but forbids numbers: Convert exact figures into qualitative outcomes (“moderate improvement,” “meaningful reduction”) or use ranges. Add context so the impact remains clear without precise data (e.g., “improved conversion from below industry average to within industry norms”).

FAQ

Q: Can I show code I wrote during an internship? A: Only if the company’s IP policy allows it or you obtain explicit permission. When permitted, publish snippets that demonstrate your skill but remove proprietary algorithms or credentials. Prefer pseudocode illustrating the approach.

Q: Is verbal permission enough? A: No — get written confirmation (email) when possible. Written permission protects you and provides clarity about what’s allowed.

Q: How do I handle participant quotes from user research? A: Remove any PII and attribute quotes generically (e.g., “participant, age 34”). Paraphrase sensitive comments.

Sources and scope

This article provides editorial guidance for interns turning workplace contributions into public portfolio pieces. It is not legal advice. For company-specific rules, consult your employer’s IP, confidentiality, or communications policy, or ask HR/legal for clarification. For general career resources and how to structure learning materials, see our guides: Better Lifestyle guides.

Keep records of approvals and prioritize ethical handling of client and user data. When in doubt, favor further anonymization or private-only use.