Choose a reader before choosing a sample
A prospective client usually needs an answer to a practical question: can this person help with the problem I have? Start with a particular type of work, such as editing support articles, building a small business website or organizing a reporting workflow. A focused selection makes your relevance easier to assess than a large archive of unrelated pieces.
Read several genuine project briefs and note the deliverables, constraints and collaboration skills they ask for. Choose samples that answer those needs. An operations assistant might show a sanitized procedure and a handover checklist. A writer might show a source-based article alongside a short explanation of audience and editorial choices. A developer might show a working feature, installation notes and a clear description of trade-offs.
You can use self-directed work when paid examples are unavailable. Label it clearly as a practice project, describe your own brief and avoid implying that a real company commissioned or approved it. If you redesign a public interface as an exercise, explain that it is an independent concept and not client work. A precise label builds more trust than a borrowed brand logo.
Use a case study that can be scanned
Give each case study a plain-language title describing the task. Lead with a short summary, then let the reader inspect the supporting evidence. The following outline is a structure to adapt, not a requirement to make every project sound like a major transformation.
A practical case-study outline
- Context: Who was the intended audience, and what needed to happen?
- Your role: Which parts did you own, and who else contributed?
- Constraints: What limited the time, budget, information or tools?
- Approach: Which decisions did you make, and why?
- Artifact: Show a relevant excerpt, accessible document, screenshot or working example.
- Outcome: Report observed results and distinguish them from assumptions.
- Reflection: Explain what you would test, improve or do differently.
For example, a self-directed support-documentation project could begin with a confusing set of fictional help requests. You could categorize the questions, draft a short article and test whether a volunteer can follow it. Report the test as a small usability exercise, not evidence of business-wide savings. If you did not measure a result, explain the intended effect and how you would evaluate it.
Be exact about collaboration. “I produced the content structure and first draft; another contributor created the illustrations” is more informative than “I built the entire experience” when that is not true. Keep original drafts or version history privately where appropriate so you can discuss your process without publishing confidential material.
A modest result you can explain is stronger than a dramatic claim you cannot support.
Connect evidence to a workable service
A portfolio shows capability, but a project also needs boundaries. Explain the kind of deliverable you offer, what information the client must provide, how feedback is collected and what counts as a revision. Separate a defined deliverable from ongoing availability. A sample landing page does not automatically establish that you can provide indefinite maintenance or specialist legal copy.
Before agreeing to work, discuss ownership, permitted use, milestones, acceptance criteria and the process for changes. Payment terms and cancellation arrangements should be documented. Freelancers may also need local advice about business registration, tax and insurance. A platform’s standard contract does not replace understanding the obligations you are accepting.
Keep the portfolio itself usable. Give links descriptive labels, add alternative text to meaningful images and provide a readable text explanation alongside visual work. The W3C Web Content Accessibility Guidelines offer a recognized accessibility reference. Avoid forcing a reader to create an account merely to understand a sample.
Depending on your field, GitHub, Behance or a straightforward personal website may suit your evidence. Check sharing permissions and licensing rather than assuming that everything uploaded can be reused freely. A small, well-organized PDF may also be appropriate if it is accessible and easy to open.
Should I complete a large unpaid test to win a client?
Ask how the work will be evaluated, how long it should take and whether it will be used commercially. Propose an existing sample or a limited, paid exercise when appropriate. Do not provide a production-ready project simply because a request is framed as a test.
Review the portfolio when your target work changes. Remove broken links, outdated claims and samples you can no longer explain. Then connect the most relevant example to a concise CV or interview story, rather than sending every reader the same unfiltered archive.