A B2B case study is approved when the customer, not your team, says yes to the exact final version, in writing, for specific uses. Everything else in the process (internal review, legal checks, quote sign-off, record keeping) exists to get you to that yes quickly and keep it defensible later. This guide walks through the full path, from the first ask to the archived approval, so your best customer stories stop stalling in someone’s inbox.
TL;DR
- Ask for permission before you write, then send the customer a clean, editable draft only after your own internal and legal review is done.
- Name one contact on the customer side who consolidates comments, and one accountable approver on your side who resolves disagreements.
- Get written approval of the exact final version, covering names, logos, quotes, metrics, channels, duration and withdrawal.
- Quotes and numbers need their own check: under FTC rules, endorsements must reflect the speaker’s honest experience and cannot be edited to distort it.
- Record the whole chain (consent, edits, approvers, scope) so you can prove what was approved when someone asks a year later.
Table of Contents
- What case study approval actually means
- The approval workflow, step by step
- What written approval should cover
- Customer quote approval: what the speaker should see
- Legal and FTC guardrails for customer stories
- Documenting approvals and handling changes or withdrawals
- How we think about approvals at Clareefai
- Put approvals on rails with Clareefai
- Common approval problems and how to fix them
- FAQ
- Sources
What case study approval actually means
In B2B, “approval” is not one signature. It is a short chain: your marketing owner, your legal or compliance reviewer, the customer’s day-to-day contact, and often the customer’s communications or legal team. Each one checks something different.
A useful way to think about it is to separate review from approval. Many people can review a draft against defined criteria (accuracy, tone, brand, legal). One accountable person approves, resolves disagreements and authorizes publication. Ampere’s workflow framework draws exactly this line, and it keeps stories from dying in committee.
The customer’s role is special. A B2B case study is about someone else’s company, their people and their results, so the external decision-maker has the final word. QueryChart’s process template makes the same point: structure the workflow so the customer’s answer is treated as decisive. If a customer says no to a quote, a metric or the whole story, the draft changes or it does not run.
Cisco’s published partner-story process is a good large-company reference. It calls for formal approval from the partner, Cisco and the customer before publication, and it advises you to identify customer stakeholders early and ask for one contact to consolidate changes. That single point of contact is the cheapest speed-up in the whole process.
The approval workflow, step by step
Here is a workflow you can adopt as is. It follows the sequence in Cisco’s playbook and adds the legal and record-keeping steps most teams skip.
1. Get permission before you write
Do not invest in an interview, a designer and a video shoot before you know the customer is open to being featured. Ask for a light, in-principle yes first: “Would you be open to a short customer story? We’d interview your team, you’d review everything before it goes live.” That framing matters. Customers say yes more readily when they know they control the final version.
Check the contract at the same time. Your legal team should confirm that the customer agreement permits reference use and that any NDAs allow it. Moxo’s approval process lists this legal check as a standard part of internal approval, and it is far easier to do before the story exists than after.
2. Map every stakeholder on the customer side
The champion who loved working with you is rarely the only person who can sign off. Ask directly:
- Who needs to approve a public mention of the company name and logo?
- Does their communications or brand team review external content?
- Does legal need to see quotes and metrics?
- Are any executives quoted who will want to see their own words?
Cisco’s guidance is to involve the customer’s marketing lead early, since the customer may need other stakeholders for final sign-off. Then ask for one person who will collect everyone’s edits and return a single consolidated set of comments. Without that person, you get contradictory feedback in four email threads.
3. Run internal review first
Before the customer sees anything, your own house should be in order:
- Accuracy review. Sales, customer success and the product team check every claim and metric against your records.
- Legal review. Confirm usage rights, claim substantiation and any regulated language.
- Brand and editorial review. Tone, formatting, length.
Then send a clean draft. Cisco’s process recommends completing internal and partner review before the customer gets an editable version, which spares them your internal back-and-forth. Send a Word or Google document with tracked changes, not a PDF, so edits are easy.
4. Send the draft with a clear ask and a deadline
A draft without instructions sits. Tell the customer:
- What you need from them (accuracy check, quote sign-off, logo approval).
- The date you would like feedback by, and the day you will follow up.
- What happens next, including where the story will appear.
Pick a deadline that is realistic for a busy executive, then follow up on the date you named. Do not describe the deadline as a pressure tactic; frame it as the point at which you will schedule design and publishing.
5. Handle edits and circulate material changes
Incorporate the customer’s edits. If a change is material (a new number, a removed claim, a reworded outcome), circulate the revised version to the other approvers too, since your legal reviewer approved the earlier text, not the new one. Minor wording tweaks rarely need another full round, but a changed figure always does.
If the customer asks for revisions, address them and resubmit for approval. Never publish “mostly approved” copy.
6. Get written approval of the exact final version
Email confirmation is usually enough for the story itself, provided it names the version. “Looks good!” on a thread with three attachments is not an approval. Ask for a reply that says something like: “I approve the attached final version of the case study, dated and titled as follows, for the uses listed in our release.” Save the file and the reply together.
7. Authorize and record
Once the customer and legal approvals are in, your marketing leadership gives the final publication authorization. In Moxo’s description of the workflow, the system records the full chain, including consent and usage scope. Whether you use software or a shared folder, keep the same things: who approved what, when, which version, and for which channels.
Teams that handle content at volume often build these governance habits into their wider editorial process. If you want to see how other brands structure it, content marketing examples can show how coordination between stakeholders looks in practice.
What written approval should cover
The approval of the story and the permission to use it are related but separate. A signed-off draft does not automatically mean the customer agreed to a billboard, a paid ad campaign or a five-year run on your homepage. The release or consent should state the scope.
According to Inherit.site’s testimonial rights guidance, a robust rights package explicitly covers name, likeness, logo, quotes and video, and defines geographic scope, duration and permitted media channels. A thorough case study release also identifies the parties and the project and lists compensation, intellectual property terms and any revocation process.
Use this checklist for your own form:
| Item | What to specify |
|---|---|
| Parties and project | Legal names of both companies, the story title or project |
| Company name and logo | Yes or no, with any brand guidelines to follow |
| Individual names and titles | Each named person, with their own consent where they are quoted |
| Quotes | The exact text approved, not a general permission |
| Metrics | Each figure and its time frame, so nobody “updates” a number later |
| Images, video, screenshots | Which assets, and whether product screenshots may show customer data |
| Channels | Website, sales decks, ads, press, events, social, partner materials |
| Duration and geography | How long and where the story may run |
| Compensation | None, or what was provided |
| Future reuse | Whether excerpts may be repurposed, and who approves new formats |
| Withdrawal | How the customer can ask you to stop using it going forward |
On that last point, Inherit.site recommends release language that permits future use across marketing, sales and PR channels while giving the customer a clause to request withdrawal of future use. It is fair to the customer and it keeps your rights clear. If you need a form that holds up to a review, our checklist on making a testimonial release form audit ready goes through it point by point.
Customer quote approval: what the speaker should see
Quotes cause more approval delays than any other element, mostly because they are the part customers care about most. They are their words, under their name, at their employer.
A practical rule: show every quote in its context, exactly as it will appear. Do not send a bare list of lines pulled out of an interview, because a sentence that reads fine in conversation can look bold or off-message on a landing page. Send the paragraph, headline and image the quote will sit with.
When you ask a customer to review a quote, they should be able to see:
- The exact wording you plan to publish, including any trimming or light grammar edits.
- Their name, title and company as they will be displayed.
- The channels where the quote will appear.
- Any numbers attached to it, and what they refer to.
- A simple way to suggest changes or decline.
The U.S. rules back this up. Under the FTC’s Endorsement Guides, an endorsement may not be presented out of context or reworded to distort the endorser’s opinion or experience. In plain terms, editing for length is fine only if the meaning the customer intended stays intact, and your quote approval should confirm that.
There is also a time dimension. The same guides say an advertiser may use an expert or celebrity endorsement only while it has good reason to believe the endorser still holds the views presented. The FTC took that position in its 1996 consent order, which barred the respondents from using a testimonial unless they had good reason to believe the named person still subscribed to its facts and opinions. For a B2B team, the practical takeaway is to re-check older quotes, especially when the speaker has changed jobs or the product has changed since the quote was given.
Legal and FTC guardrails for customer stories
This section is general information, not legal advice. Have your counsel review your templates and any claim you are unsure about.
The FTC’s rules were written with consumer advertising in mind, but they apply to endorsements and testimonials used to promote products, and many B2B marketing teams follow them as a baseline. Four points matter most for case study approvals:
- Honest opinions. Under 16 CFR Part 255, endorsements must reflect the endorser’s honest opinions, findings, beliefs or experience, and claims made through them must be substantiated.
- Typical results. Under 16 CFR 255.2, an endorsement about a central product attribute will likely suggest that the endorser’s experience is generally representative. You should substantiate that, or clearly disclose what results are generally expected. If a customer cut onboarding time by 60 percent and most do not, say so.
- Material connections. Advertisers can be liable for not disclosing unexpected material connections. If a customer received a discount, credit, gift or payment for the story, the approval file should say so and the story should disclose it where it would surprise a reader.
- Fake and misleading reviews. The FTC’s rule on consumer reviews and testimonials, in effect since October 21, 2024, prohibits buying or selling fake reviews, using misleading company-controlled websites and certain review suppression practices.
The FTC has also acted against companies that relied on affiliates. In one case, it said endorsements that looked like they came from ordinary consumers needed clear and prominent disclosure of the affiliate’s financial relationship, and it faulted the company for not reasonably monitoring them. The lesson for case study programs is that you own what your partners, agencies and sales reps publish about your customers, so your approval records should cover reuse by others too.
For a deeper walkthrough, see our six step verification workflow for FTC testimonial guidelines and our checks on testimonial data governance.
Documenting approvals and handling changes or withdrawals
A good approval record answers four questions in under a minute: who approved, what exactly, when, and for which uses. Store these together for every story:
- The signed release or consent email.
- The final approved text, with a version date.
- Written confirmation from each approver, including legal.
- The list of approved channels and expiry or review date.
- Any later change requests and your response.
If the customer’s consent is missing, or the person is unreachable, don’t guess. MangoApps’ customer story SOP tells the content advocacy manager to verify written consent and, if it is absent, escalate or choose an alternate candidate. That is the right default: no consent, no publication.
When a customer asks you to take it down
Withdrawal requests happen: a merger, a new brand policy, a change of heart, a new CMO. Treat them as routine rather than as a conflict.
- Acknowledge the request in writing and confirm the date you will act by.
- Remove it from owned channels (website, sales decks, email templates, CRM-linked assets).
- Pause paid or scheduled uses and ask partners or agencies to do the same.
- Log what was removed and when.
- Check what your release said about content already distributed, and be honest with the customer about what you can and cannot recall.
The faster you can find every place a story lives, the easier this is. That is why cross-channel tracking matters; our cross-channel testimonial publishing playbook covers how to keep that map current.
How we think about approvals at Clareefai
We work with B2B sales and marketing teams every day, and the same pattern shows up: approvals rarely fail because customers say no. They fail because nobody owns the follow-up, the scope of consent is vague, or the proof lives in someone’s inbox.
Our view is that an approved story is a verified sales asset, not a loose piece of praise. That means the person is real, the context is clear, the permission is on file, and the team can find the record when a prospect, a lawyer or a new colleague asks. When you treat approval as part of how testimonials are collected, rather than as a final hurdle, customers respond faster because they were told from the start what they were agreeing to.
We also recommend asking for approval at the moment of peak enthusiasm, such as after a successful launch or renewal, and keeping the ask small: one quote, one logo, one metric. Larger stories can follow once trust is established. Our step-by-step testimonial workflow shows how to sequence it.
— ClareefAi
Put approvals on rails with Clareefai
If your approvals live across email threads, spreadsheets and shared drives, a central system saves hours. Clareefai verifies customer identities, organizes testimonials, reviews, video and case studies in one place, and connects them to your CRM so your team publishes only what is approved. Plans are published on our pricing page: Basic is $250 per month, Professional is $624 per month and Enterprise is $1250 per month, with a free trial available and no long-term contracts.
Want to see how it fits your process? Start a trial and we’ll show you how to set up your first approval flow.
Common approval problems and how to fix them
| Problem | Likely cause | Fix |
|---|---|---|
| The draft sits for weeks | No deadline, no named reviewer | Set a date, name one consolidating contact, follow up as promised |
| The customer rewrites everything | Draft was rough or arrived before internal review | Send a clean, reviewed draft and explain what feedback you need |
| Legal blocks it late | Contract and NDA were not checked up front | Check reference rights before the interview |
| A metric is disputed | Numbers were not sourced or dated | Attach the data source and time frame to each figure |
| The story is reused in new formats | Release covered only one use | List channels and require re-approval for new ones |
| Executive left the company | Quote was never re-checked | Review older stories on a regular schedule |
For privacy-related questions, such as how to store consent data and who may access it, see our testimonial privacy policy checks.
FAQ
Who should approve a B2B case study?
The customer has the final say on their name, quotes, metrics and logo, often through a marketing lead plus legal or an executive. On your side, several people can review, but one accountable approver should authorize publication. Your legal team should confirm that usage rights and claims hold up.
Do I need written approval for a customer quote?
Yes, get it in writing, and tie it to the exact wording and the channels where it will run. Email is usually fine if it names the version. Under FTC guidance, an endorsement should not be reworded in a way that distorts the speaker’s opinion or experience.
How long should I wait for a customer to approve a case study?
Give a clear deadline that fits the customer’s workload, then follow up on the date you stated. If there is no answer after your follow-ups, escalate to the customer’s marketing lead or choose another customer. Do not publish without confirmation.
Can a customer withdraw approval after publication?
It depends on your release. A good one gives the customer a way to request withdrawal of future use, and you should confirm what happens to content already distributed. Act on the request promptly, remove the story from owned channels and log what you changed.
Do FTC rules apply to B2B case studies?
The FTC’s Endorsement Guides and its rule on reviews and testimonials govern endorsements used in advertising, and they set a sensible standard for B2B stories too. Ask your counsel how they apply to your claims and your channels.
Sources
- The co-creation process, Partner Stories Playbook (Cisco)
- Case study approval (Moxo)
- Case study approval process flowchart (QueryChart)
- Content approval workflow: steps, roles, and templates (Ampere)
- Customer Story Production SOP Template (MangoApps)
- Testimonial Rights, Consent Forms & Greenwashing Risk (Inherit.site)
- How to Fill Out and Sign a Case Study Release Consent Form (LegalClarity)
- 16 CFR Part 255, Guides Concerning Use of Endorsements (eCFR)
- 16 CFR 255.2, Consumer endorsements (eCFR)
- Trade Regulation Rule on the Use of Consumer Reviews and Testimonials (Federal Register)
- FTC consent order, 1996
- FTC business guidance on deceptive endorsements, 2011