Case Study Release Form: Free Template and the Six Clauses That Matter

The short answer: a case study release is a one-page agreement covering what you are publishing, where it can appear, whether the customer approves the final text, and how they can withdraw. You can copy the template below. But before you do, it is worth knowing that the form is rarely what is actually blocking you.

This article is not legal advice. It is a practical starting point written for B2B software teams. Have a lawyer in your jurisdiction review anything you plan to use repeatedly.

The form is not your bottleneck

Teams tend to believe their case study pipeline is stuck on paperwork. It usually is not.

Uplift Content surveyed 115 SaaS customer marketers in 2024 and found the top blockers were finding customers willing to participate, identifying metrics, and getting approval. Note what is absent from that list: drafting the release.

The release matters, but it matters as a tool for removing hesitation rather than as a legal formality. Used well, it makes yes easier. Used badly, sent too early and written too long, it converts a warm conversation into a procurement ticket.

So the sequencing matters more than the wording:

1. ●Ask for a conversation, not a case study
2. ●Have the conversation
3. ●Write the draft
4. ●Send the draft with the release
5. ●Let them approve both together

Sending a legal document before the customer knows what they are agreeing to is the single most common way to lose a story you had already won. If you want the whole workflow rather than just this step, we covered it in the case study approval process.

What a case study release form should include

Six clauses. Anything beyond this tends to invite a legal review you did not need.

1. What is being granted

Name the specific assets: the individual's name and job title, the company name, the company logo, and direct quotes from the interview. Be explicit, because "materials relating to the engagement" means nothing and invites questions.

2. Where it may be used

List the surfaces: your website, sales materials, social media, email, paid advertising, and press. If you intend to run their quote in an ad, that belongs here. Customers rarely object to breadth; they object to discovering a use they were not told about.

3. Approval over the final text

This is the clause customers care about most, and the one most templates omit. State plainly that they will see the final piece and can request changes before publication.

Offering this up front changes the economics of the ask. The fear that makes customers hesitate is not being quoted; it is being quoted badly, or having a claim attributed to them that they cannot defend internally. An explicit approval right kills that fear at the moment it is doing the most damage.

4. Duration and withdrawal

Say how long the permission lasts and how they can withdraw it. A reasonable default: permission continues until they ask in writing, at which point you remove the story within a stated window.

Counter-intuitively, an easy exit makes the initial yes easier. A permanent, irrevocable grant reads as a trap, and people decline traps.

5. Confidentiality carve-out

Explicitly exclude anything they cannot share: revenue figures, customer counts, contract values, internal system names. Naming the exclusion up front is what lets a cautious customer say yes to everything else.

This is also the clause that saves stories from dying at legal review, because it demonstrates you already thought about the sensitive parts.

6. Signature, date, and entity

Who is signing, on whose behalf, and when. Confirm the person has authority to grant it. For enterprise customers this is often marketing or comms rather than your day-to-day champion, and finding that out early saves weeks.

Free case study release form template

Copy this, adapt it, and have it reviewed before repeated use.

CASE STUDY AND TESTIMONIAL RELEASE

Between [YOUR COMPANY] ("we", "us") and [CUSTOMER COMPANY] ("you").

1. Permission granted. You grant us permission to publish the following in a customer story: your company name, your company logo, the name and job title of [INDIVIDUAL NAME], and quotations taken from our interview on [DATE].

2. Where it may appear. The story and extracts from it may appear on our website, in sales and marketing materials, in email, on social media, and in paid advertising.

3. Your approval. You will receive the complete draft before publication. It will not be published until you confirm in writing that you approve it. You may request changes, and we will not publish text you have not approved.

4. Duration and withdrawal. This permission continues until you withdraw it in writing. On withdrawal we will remove the story from our website within [10] working days and stop using it in new materials. Materials already printed or distributed may remain in circulation.

5. Confidential information. The story will not include: [LIST — e.g. revenue figures, customer numbers, contract value, internal system names]. Any figure that does appear will be one you have confirmed in writing.

6. Accuracy. Quotations will be your own words. We may correct obvious transcription errors and proper nouns, and may shorten a quotation provided the meaning is unchanged.

Signed: ________________ Name: ________________ Title: ________________ Date: __________

That is the whole thing. One page, six clauses, no defined-terms section.

Release form versus approval: two different problems

A release grants permission. Approval is a workflow, and it is where stories actually stall.

A signed release does not get you a customer who reads the draft. You still have to send it, wait, follow up, absorb the edit, send it back, and wait again. That loop is a meaningful part of the two-month elapsed time Uplift measured, and it happens after the paperwork is done.

This is the specific problem we built the approval loop in StoryVoice to remove. The customer gets a link, reads the story, and either approves it or requests changes in place. There is no attachment, no version confusion, and no wondering whether they saw it. Change history names the people who edited, so a customer can see exactly what was changed after their interview and by whom.

Permission is what the release covers. Approval is what the product covers. You need both.

When legal blocks it, find out what specifically

"Legal said no" is almost never a no to the whole story. It is usually a no to one element:

• ●The logo. Drop the logo, keep the company name. Often that alone clears it.
• ●A financial figure. Convert it to a ratio, a range, or a percentage. "Cut processing time by roughly two thirds" survives review when a dollar figure does not.
• ●A named individual. Replace the name with the role. "Their Head of Customer Support" carries most of the credibility of a name.

An anonymised story with a real, specific result is publishable and useful. A perfect story that never ships is worth nothing. If you are heading toward an anonymous version, we wrote about doing that honestly rather than hiding the gap behind adjectives.

What happens after they sign

The release is the easy half. The half that consumes your calendar starts the moment you send the draft over.

A signed release does not produce a customer who has read your draft. You still have to send it, wait, follow up, absorb one round of edits, send it back, and wait again. That loop runs after the paperwork is finished, and it is a meaningful share of the two months Uplift measured.

Three things make it shorter, and none of them are legal:

1. ●Send the draft as a link, not an attachment. Attachments create version confusion and give you no idea whether it was opened.
2. ●Let them edit in place. A customer who has to write "in paragraph three, change 40% to about a third" will defer it. A customer who can change it themselves will do it now.
3. ●Make the approval a single click. Every extra step is another day.

That is precisely what StoryVoice's approval loop does. Your customer gets a link, reads the story, and either approves it or requests changes in place. Change history names who edited what, so they can see exactly what happened to their words after the interview.

The release grants permission. The approval loop is what actually gets it published.

If you do not have a draft to send yet, that is a different problem, and the free AI case study generator will turn interview notes into one without asking for your email.

The honest verdict

Use a short release. Send it with the draft rather than before it. Lead with the approval clause, because that is the part that makes a nervous customer comfortable, and it is the part most teams bury.

Then fix the thing the release does not fix: the waiting.

Next: customer proof: the six types and how to capture them for the wider picture, or how to get customers to say yes for the conversation that comes before any of this.

---

Source: Uplift Content 2024 SaaS Case Study Survey (115 customer marketers). This article is not legal advice.