Most freelance case studies are written the way people pack for a trip at midnight. Start with the story you want to tell, then rummage around for anything that might support it: a half-remembered compliment, a screenshot of something going up, a vague sense that the client was pleased. The result usually reads as one of two things. Either it’s fluff (“we partnered closely to elevate their brand voice”) or it’s fiction (a suspiciously round percentage nobody can source).
There’s a better order: evidence first, story second. Gather and sort what you can actually show. Check what you’re allowed to show. Only then decide what story the evidence supports. Case studies written this way are sharper, more credible and, surprisingly, faster to write, because the hard thinking happens before the drafting.
Why does the order matter so much?
Because a story chosen first bends the evidence to fit. You start looking for support rather than looking at what’s there. Weak evidence gets promoted to strong. Impressions get rewritten as facts. Missing numbers get estimated.
When you gather evidence first, the story emerges from what’s real. Sometimes it’s a different story than you expected, and often a better one. The process you followed, the problem you untangled or the constraint you worked within may be more compelling than a metric you can’t prove anyway.
What do great investigators teach about evidence before conclusions?
The principle is old and well tested.
Sherlock Holmes. In “A Scandal in Bohemia,” published in 1891, Arthur Conan Doyle has Holmes say: “It is a capital mistake to theorize before one has data.” Fictional, yes, but it has stuck because it names a real temptation.
Charles Darwin. Darwin began developing his ideas on natural selection in the late 1830s but didn’t publish On the Origin of Species until 1859, spending the intervening years gathering and organizing evidence. Whatever spurred the timing, the book’s strength lay in its accumulated detail.
Ida Tarbell. Her History of the Standard Oil Company, published as a book in 1904 after appearing in installments in McClure’s Magazine, was built on extensive research in documents and public records. Its force came from evidence readers could check.
Your case study doesn’t need to topple a monopoly. It does need to survive a skeptical reader, and evidence-first is how you get there.
What counts as evidence for a content case study?
More than numbers. Evidence is anything you can show or document. For freelance writers and content professionals, it usually falls into six types:
- Artifacts: the deliverables themselves, published or shareable with permission.
- Before-and-after material: an old page and a new one, an earlier draft and a final version.
- Process records: briefs, outlines, interview notes, editorial calendars and decision logs.
- Client words: feedback, testimonials or quotes, usable only with permission.
- Documented outcomes: numbers the client reported or that you can source, with dates.
- Your specific contribution: what you did, as distinct from what the team or client did.
Notice that only one of the six is a metric. Many strong case studies are built mostly on the other five.
How do you separate facts from impressions?
As you gather, sort each item into one of two piles:
- Facts: things you can show or document. “Delivered 12 articles between March and June.” “Client approved the new homepage copy on April 4.” “Rewrote 30 product descriptions using a new structure.”
- Impressions: things you believe but can’t document. “The client seemed really happy.” “I think traffic went up.” “The new voice was a hit.”
Impressions aren’t worthless. They can guide what you ask the client for. But they don’t go into the case study as claims. If you think traffic went up, ask the client whether they can share anything. If they can’t, the claim doesn’t appear.
What should you record about each piece of evidence?
For each item, note:
- What it is and where it lives.
- Its date.
- Its source: you, the client, a tool, a public page.
- Your confidence: documented, partial or impression.
- Its attribution: whether the result can be credited to your work alone, partly or not clearly.
That last field keeps you honest. Content outcomes usually have many causes: the client’s sales team, a seasonal trend, a site redesign. A case study that says “traffic rose after the refresh, alongside a broader site update” is more credible than one that claims sole credit.
Where does permission come in?
Right after evidence, before drafting. For each case study, decide on a permission status:
- Named: the client has clearly agreed to be identified, on the channels where you’ll use it.
- Anonymized: the story is useful, but identity or figures are sensitive, so you use an industry and size description instead of a name.
- Do not publish: permission is missing or the risk is too high. Keep it out of public channels.
A simple readiness check helps: confirm what’s cleared to publish, and if any point is unclear, anonymize or hold the story until the client confirms. Quotes need explicit permission. Without it, paraphrase without attributing words to a specific person.
What if the evidence doesn’t include results?
Then you write a different kind of case study, and that’s perfectly professional. Many engagements end before results are measurable, or the client keeps numbers private. An honest alternative focuses on the problem, your approach, the decisions you made and the artifacts you produced. It shows how you think and work, which is often what a prospective client most wants to know.
What you never do is fill the gap with an estimate. A fabricated metric might win one pitch. It can also unravel a reputation when someone asks for the source.
How does evidence-first make writing faster?
Because the decisions are already made. When you sit down to draft, you know:
- what you can claim,
- what you can show,
- whether the client is named,
- whether you have results or will write the honest alternative.
The draft becomes assembly, not invention. Writers who struggle for days over a case study are usually trying to write and gather at the same time.
How do you build an evidence habit during projects?
The easiest case studies to write are the ones whose evidence was saved along the way. A light habit makes that automatic. Create one folder per client at kickoff and drop into it, as they happen:
- The approved brief for each major piece.
- Before snapshots of any page you’ll change, saved as dated screenshots or PDFs.
- Final deliverables, or links to them once published.
- Feedback worth keeping, copied with the date and sender.
- Any numbers the client shares, with the date and a note on what they measure.
- A running note of your decisions: what you chose, what you rejected and why.
It takes a few minutes a week. When the engagement ends, the case study practically assembles itself, and you’re not trying to remember in December what the homepage said in March.
It also makes the permission conversation easier. At the end of a project, you can show the client exactly what you’d like to feature, item by item, and they can approve or exclude specific pieces rather than deciding on a vague request. Clients say yes more often to specific asks.
What should you ask the client for at wrap-up?
A short, specific request works best. Ask whether you can name them or should anonymize, which deliverables you may show, whether they’re willing to share any outcome they’ve measured, and whether a quote from their feedback can be used with attribution. Four questions, one email, and a clear record of the answers.
What does a finished example look like?
The Content Portfolio Case-Study Kit includes a fully worked fictional example, Lumen Harbor, that deliberately contains zero performance statistics. It shows how a credible, useful case study can be built entirely from process, artifacts and documented contribution, and serves as a model for the many engagements where numbers aren’t available or aren’t yours to share.
What’s in the Case-Study Kit?
The Content Portfolio Case-Study Kit is built around the evidence-first order. Its seven-tab workbook includes Start Here, Evidence Collection (project snapshot, problem and context, your contribution, evidence inventory and attribution confidence), Permission & Anonymization, a Full Case Study template, a Short Case Study template, an Honest Alternative template and the fictional Lumen Harbor example. An 11-page guide explains each step, and Markdown templates cover every blank.
Quick answers
How many pieces of evidence does a case study need?
Enough that every claim maps to something you recorded. For a short portfolio card, that might be three items. For a full case study, perhaps eight to twelve.
Can I use a client’s private email praise?
Only with permission. Ask, and offer options: named, initials or anonymous.
Should I gather evidence during the project or after?
During. Save artifacts, dates and feedback as you go. Reconstructing them months later is slow and incomplete.
Let the evidence choose the story
Case studies written story-first end up as fluff or fiction. Written evidence-first, they end up as something better: specific, credible and true. The method is simple. Gather, sort, check permission, then write.
Get the Content Portfolio Case-Study Kit and run its Evidence Collection on your most recent project. You’ll find a story there, and it’ll be one you can stand behind.
The Content Portfolio Case-Study Kit is on Content & SEO Workflows.
Leave a Reply