A customer agrees to give you a testimonial. They send a written quote, you record a Zoom video with them, you take a photo at an industry event. Three months later, you put the quote on your homepage, the video on your YouTube channel, and the photo on a LinkedIn ad. Two months after that, the customer sees the LinkedIn ad and asks "wait, did I say you could use this for advertising?"

That conversation, on average, ends one of three ways: a polite request to take it down, an awkward back-and-forth that costs the relationship, or — rarely but expensively — a lawyer's letter. All three are avoidable with a one-page document signed at the time of recording.

This post is about what that document should contain, why each clause is there, and how to keep the process light enough that your customers do not bail out at the friction.

Why a verbal yes does not actually cover you

When a customer says "sure, you can use this," they are usually thinking about the obvious case — your website, your social media, the next sales deck. They are usually not thinking about: paid advertising, third-party media buys, billboards in cities they have never been to, future products you have not built yet, derivative works (clips, transcripts, translations), or use after they leave the company.

Most of the time, none of this matters. They never see most of those uses, or they do see them and do not care. But "most of the time" is not a legal standard. The standard is: do you have an enforceable agreement covering the specific use? A verbal yes plus a friendly tone is not enforceable, and it is also not specific.

Three things commonly go wrong:

The customer leaves the company. The new comms person at the customer's firm sees their old colleague's face on your homepage and asks for it to come down. You cannot reach the original person.
The customer's employer asserts ownership. In B2B, the employer often owns statements made about commercial products by employees. If you only got the individual's permission, the employer can demand removal.
The use case expands. You used the quote on the website, which was fine. Then you ran it as a Facebook ad targeting a competitor's customers. The original yes did not cover paid advertising, and the customer is reasonably annoyed.

A written release closes all three of these by being specific, durable, and signed.

The minimum a text-only release should contain

If all you have is a written quote — no photo, no audio, no video — the release can be very short. You need:

Identification of the parties. Full legal name of the customer (and company, if B2B), full legal name of your company.
The specific testimonial content. Either inline ("the quote 'ProofShow saved us 12 hours a week' attributed to Sarah Chen, VP Marketing at Acme Corp") or by reference to an attached document.
Permitted uses. "Marketing materials, website, social media, sales materials, paid advertising, partner co-marketing, press releases, and any successor or derivative use."
Term. Either perpetual ("in perpetuity") or time-bounded ("for five years from the date of signing, renewable").
Modifications. "Light editing for length, clarity, and grammar is permitted. The substance of the testimonial will not be altered."
Right to withdraw. Whether the customer can pull the testimonial later, and on what terms. Common: "The customer may withdraw consent in writing with 30 days notice; existing physical materials may continue to be used through their natural lifecycle."
Governing law and signature. Jurisdiction, date, signature.

That is enough for a text-only release. You can fit it on one page in 11pt body text.

What changes for photo and video releases

Photo and video introduce two new rights: likeness and recording. Both need to be addressed explicitly because they are governed by different bodies of law than written content.

Add to the text-only release:

Likeness rights. "I grant ProofShow the right to use my image, voice, name, and likeness in connection with the testimonial."
Recording rights. "I consent to being recorded on [date] for the purpose of producing this testimonial."
Edits and clips. "ProofShow may edit, excerpt, caption, subtitle, translate, and combine the recording with other materials." This is the part most release forms forget. Without it, you cannot make a 15-second TikTok clip out of a 5-minute interview without going back for new permission.
No compensation clause (if applicable). "I am not receiving payment for this testimonial." If you are paying or providing incentive, omit this and add the disclosure language we covered in the FTC piece.
Background music and overlays. Especially for video, you may add music, on-screen text, or B-roll. The release should cover this so the customer does not later object to a music choice.

For video specifically, double-check whether the recording was on a platform (Zoom, Riverside, Loom). Some platforms have their own terms about ownership of recordings. The release should explicitly confirm that the customer agrees to ProofShow having full rights regardless of platform terms.

What about photos taken at events?

Event photos are the highest-friction case. The person did not necessarily consent to being photographed, much less to having the photo used in marketing. Two paths:

Get consent before publishing. Send the photo to the person, ask "is it OK if we use this in our customer roundup?" If they say yes, save the email or message as the record.
Use a generic event-photography release. Some companies put a notice at event registration: "Photos taken at this event may be used by ProofShow in marketing materials." This is weaker than individual consent but better than nothing. It does not cover featured use (where the person is the focal point of the photo) — that still needs individual consent.

Recognizable individuals featured prominently always need individual consent. Crowd shots where individuals are not the focus generally do not. The line is fuzzy in the middle and you should err on the side of asking.

B2B: who actually has authority to sign

The customer says "yes, you can use this on your website." But who is "the customer"? In a B2B context, the answer is usually a layered question:

The individual has rights to their likeness, voice, name, and quoted statements made about themselves.
The employer typically has rights to statements made about the employer's use of the product, statements made in the course of employment, and any logo or brand used alongside the testimonial.
The legal/comms team at the employer often has internal policy authority over external statements.

A clean release covers both: signed by the individual, and either signed or formally acknowledged by the employer's appropriate authority (usually marketing, comms, or legal).

In practice, for small or mid-size customers, the individual signing alone is fine and the employer never raises an issue. For enterprise customers, you almost always need formal sign-off, and you almost always wait 4-12 weeks. This is the single biggest reason enterprise testimonials are slow. Build that timeline into your forecast.

The "withdraw consent" clause is more important than you think

Customers sometimes change their minds. The company gets acquired and the new owners want to control all messaging. The individual leaves the company under bad terms. A scandal at the customer's firm makes their endorsement awkward. A new privacy regulation gives the individual right to be forgotten.

If your release says nothing about withdrawal, you are in a gray zone. The customer can plausibly demand removal; you can plausibly refuse. Either side might escalate to lawyers.

A clear withdrawal clause defines the rules upfront. Common language:

"Customer may withdraw consent at any time in writing. Upon receipt, ProofShow will remove the testimonial from active marketing channels within 30 days. Existing printed materials and historical campaigns may continue through their natural lifecycle."

This is fair to both parties. The customer keeps long-term control. ProofShow does not have to pulp $50K of trade-show banners because someone changed their mind.

Storage, retrieval, and audit

Releases are only useful if you can find them. Common pattern:

One folder per customer in a shared drive: releases/<customer-slug>/
Each file named with date and type: 2026-05-01-acme-text-release.pdf, 2026-05-01-acme-video-release.pdf
A simple spreadsheet or database row linking each testimonial asset to its release file
Quarterly audit: pull a random sample of live testimonials and verify the release exists and is still in force

If your testimonial program is small, a Google Drive folder and a Notion table are enough. If it is large or you operate in regulated industries, a dedicated system (or a lawyer-managed contract repository) is worth the cost.

A reasonable workflow that does not scare customers off

The friction of a legal-looking document can scare customers off, especially individual creators or small businesses. To minimize that:

Do not lead with the form. Lead with the conversation. Get them excited about being featured. Then send the release as the last step.
Keep the form to one page. Nobody reads three-page contracts. A one-pager in plain language signals reasonableness.
Use e-signature. DocuSign, HelloSign, even an emailed PDF with typed name. Friction kills completion rates.
Explain why. A two-line preamble — "we ask everyone to sign this so we can use the testimonial across our marketing without having to come back to you for each new use" — makes the form feel routine instead of legalistic.
Offer a copy. Send them the signed copy after. They will not read it, but it makes the relationship feel symmetric.

A reasonable completion rate is 80%+ of customers who agreed verbally. If you are seeing significantly lower, the form is too long or the language is too aggressive.

The shorter version

Get a written release before publishing. Cover identification, content, permitted uses, term, modifications, withdrawal rights, and (for media) likeness and editing rights. Keep it to one page. Use e-signature. Store releases in a findable system. Audit annually. Build the form once, use it forever.

For more on the legal context around incentives and disclosures, see Testimonial incentives and FTC disclosure. For the workflow leading up to the release, see How to collect testimonials from customers and Testimonial request email templates.

Testimonial Permission and Release Forms — What to Include and Why It Matters