How to quote a client with context
A testimonial earns trust when the person, permission, and surrounding facts are clear.
On this page
A client quote can show how someone experienced your work. It cannot carry a claim the speaker did not make. Readers need to know who said it, what work the quote refers to, when it was approved, and whether any business relationship affects how they should read it.
Start with the real words. The surrounding context keeps those words from becoming an advertisement that overstates the project.
Begin with a specific request
Ask after a defined piece of work, not for a broad endorsement. A useful request reminds the person what you worked on together and gives them room to decline, correct, or keep their response private.
Here is an illustrative request:
I am preparing a case study about the workshop we completed in May. Would you be comfortable sharing a short description of what was useful to you? If you agree, please tell me the wording, name, role, and organisation you are happy for us to publish. We will send the final context for approval before it goes live.
Adapt it to the relationship and the approval process your client uses.
Do not write praise for a client to approve if you can avoid it. A prompt such as “Would you say we transformed your team?” pushes the speaker toward a conclusion and tempts you to publish a claim with no useful detail. Ask an open, narrow question instead:
- What part of the work was most useful?
- What situation were you trying to address?
- What did our team provide?
- Is there any context a reader should know before seeing this quote?
- May we use your name, role, and organisation with these words?
Preserve the speaker's meaning
Light edits for spelling, punctuation, or length can be reasonable when the speaker reviews the final text. Changing the meaning is different. Do not turn “the workshop gave us a way to frame the discussion” into “the workshop fixed our strategy.” Do not add a result, client name, or job title the person has not approved.
Use a quote record that separates the original response from the public version:
| Field | Record |
|---|---|
| Original wording | [saved response or meeting note] |
| Proposed public wording | [exact text to publish] |
| Speaker | [name, role, organisation, or anonymous label] |
| Project context | [specific service or work period] |
| Approval | [written confirmation and date] |
| Restrictions | [where it may appear, expiry, edits, attribution] |
If the speaker asks to stay unnamed, do not replace their name with a vague title that makes the client identifiable through other details. You may need to remove the quote altogether if the remaining context could reveal private work.
Put the quote beside the work it describes
A quotation should answer one limited question. Place it near the description of the work so readers can understand it without guessing.
Here is a fictional example:
“The review gave our team a clear way to compare the options before the planning meeting.” Maya Ortiz, operations lead, on an approved decision-support review for a membership organisation
The quote describes a particular use of the work. It does not prove that every client will make a faster decision, that the service produces a fixed result, or that Maya speaks for the whole organisation.
Context can include:
- the service or deliverable the speaker received
- the speaker's relevant role at the time
- the month or year of the project when that affects how the quote should be read
- a brief note about a paid, client, employment, or other material relationship when required
- whether the quote is about a pilot, a completed project, or one part of a larger engagement
Leave out confidential project details that the quote does not need. A reader does not need internal revenue, a product roadmap, or a private disagreement to understand a comment about a workshop.
Do not use one quote as proof of a larger claim
Testimonials are limited evidence. They describe one person's experience, at one time, in one setting. Use them to show what that person said. Support broader factual claims with sources that directly establish them, and label results with their measurement context.
| Tempting use | Why it overreaches | Safer use |
|---|---|---|
| Quote says a session was helpful, then page promises better results | The speaker did not measure or guarantee the later result | State what the speaker found useful |
| One manager praises a team, then page says the company endorses you | The individual may not speak for the organisation | Attribute the quote to the person and role |
| Old quote appears under a current offer | The service or relationship may have changed | Add the project date and review the wording |
| Quote is paired with a private metric | The reader cannot inspect the evidence | Omit the metric or use an approved public source with scope |
In the US, the Federal Trade Commission says endorsements should reflect the endorser's honest opinions, findings, beliefs, or experience. Its disclosure guidance also addresses material connections. Apply the rules and advice that govern your own jurisdiction and publication. FTC Disclosures 101
Send the final context for approval
The final check should include the complete page section, not only the sentence in quotation marks. A speaker may approve a quote but object to the headline, result claim, image, or adjacent client list.
Ask the reviewer to confirm:
| Check | What to send |
|---|---|
| Wording | The exact quote, including edits |
| Attribution | Name, role, organisation, and date |
| Context | Headline, adjacent copy, links, images, and claims |
| Publication | The places where the quote will appear |
| Duration | Whether the approval has an end date or review trigger |
Keep the approval with the project record. Then add the approved wording, context, and review date to the case study permission checklist. Publish only the version the speaker has seen.