Document Customer Case-Study Permission Before Publishing

Overview

A positive customer story still needs permission

A customer may praise a business in a private message, give a testimonial during a call, or agree to be interviewed. Those actions do not automatically settle whether the company may publish the customer’s name, logo, photograph, quotation, or performance data in every channel. A case study can be useful evidence, but the process should respect the customer’s control over how their story appears.

Before drafting, identify what the business wants to use and where it plans to publish it. A named case study on a website is different from an anonymous summary in a sales deck, and both differ from a paid advertisement. Record the proposed use rather than relying on a vague statement that the customer is “happy to help.”

Create a permission record with specific scope

Use a short approval record that captures the customer organization or individual, the authorized contact, the asset types involved, the channels, the intended duration if relevant, and any restrictions. List whether permission covers the person’s name, job title, company name, logo, quote, photo, video, and numerical results. If the story may be translated, edited into short clips, or used in paid promotion, say so explicitly.

Keep the scope understandable. Do not bury broad rights in an informal email thread where the customer cannot tell what they are approving. If a customer approves the written quote but not the portrait, mark those decisions separately. For complex or regulated contexts, obtain appropriate legal review rather than treating a generic checkbox as sufficient for every use.

Substantiate every outcome claim

Case studies often include impressive results: reduced processing time, more enquiries, lower costs, or increased revenue. Before publishing, identify the source for each number, the measurement period, the baseline, and any calculation. A claim such as “sales doubled” is incomplete without knowing the period and comparison. A metric drawn from a customer’s internal report should be approved for public disclosure by someone authorized to share it.

Separate measured results from the customer’s opinion. “The team found the workflow easier to manage” is a reported experience; “the workflow increased revenue by 40%” is a quantitative claim requiring evidence. Do not imply that one customer’s outcome is typical unless the business has evidence supporting that broader statement. If the evidence is limited, narrow the claim or remove the number.

Protect the customer from accidental disclosure

Interview notes may contain customer names, operational details, internal systems, or commercially sensitive facts that were never intended for public release. Store raw notes in a restricted location and create a separate approved-content draft. Remove unrelated personal information and avoid sharing internal notes with a broad team merely because they are interesting.

For anonymous case studies, assess whether details could still identify the customer. A unique industry, city, company size, and unusual project can reveal identity even without a name. Anonymization is not just deleting a label; it may require generalizing or removing combinations of details. If confidentiality is part of the relationship, confirm that the proposed story does not violate the agreement.

Use a structured approval sequence

A practical sequence is: outline the story, verify claims internally, draft the case study, send the relevant excerpts to the customer, collect explicit approval, complete brand and legal checks where needed, then publish. Make it clear whether the customer is approving factual accuracy, exact quotations, identifying details, and final presentation. Give a reasonable response deadline and do not interpret silence as approval.

Consolidate feedback through one contact on each side. Record which version was approved and preserve the final text or file alongside the permission record. If the customer approves a quote but asks to remove a logo, ensure the production team receives that restriction before design begins. Approval should be attached to the specific content, not merely to the general idea of a case study.

Plan updates, corrections, and withdrawal requests

Published material can become outdated when a customer changes role, a product is discontinued, or a metric is later corrected. Decide who monitors the case study and how customers can report an issue. If the business receives a reasonable correction request, investigate it promptly and document the resolution. The response may be an edit, an updated note, or removal, depending on the agreement and applicable obligations.

Set a review date for content with time-sensitive claims. Do not keep old figures on a landing page indefinitely just because the original approval exists. If the company wants to reuse the story in a new context, check whether the original permission covers that use.

Build a reusable case-study folder

Store the brief, interview notes with restricted access, evidence for claims, approval messages, final approved copy, design files, publication URLs, and any usage limits. Label the approved version clearly so staff do not accidentally publish a draft containing unapproved details. Include an expiry or review date when the permission or facts may change.

A clear permission trail speeds future reuse and protects the customer relationship. It also improves content quality: claims become easier to verify, edits become more deliberate, and the business can explain exactly what the customer authorized.

Practical checklist

• Specify the exact assets and channels being approved.
• Verify numerical claims and distinguish measured outcomes from opinions.
• Save approval against the exact version and honor reuse restrictions.

Conclusion and next steps

Before the next customer story goes live, verify each result, match approval to the final version, and record exactly where the content may be reused. Set a review date for claims that can become stale. These small controls make case studies more credible and reduce the risk of treating a friendly conversation as unlimited permission to publish.