Turning a Private Client Case Study Into a Public Quote

During a private client review, an executive hears a vivid story about a hospital team reducing handoff delays. Weeks later, a writer places the story in an attributed conference quote, removes the hospital’s name and calls it anonymous. The combination of region, specialty and rollout date still points directly to the client, and nobody asked whether the discussion could be used publicly. A private story can become a public quote only after four separate decisions: the facts are checked, the client permits the use, the identity risk is tested and the speaker approves the wording.

Private case material can help a communications team understand a subject. That usefulness does not grant publication permission. The PRSA Code of Ethics↗ frames this as client trust, which requires appropriate protection of confidential and private information¹. Turning it into a public quote requires a chain of decisions about the facts, the intended use, the client’s identity, the speaker’s memory and the organization’s disclosure rules.

Where it came from, who provided it, when, on what terms and who may see it, then the separate factual assertions inside it and the details that could identify the client. Most PR teams already draw this line with AI tools: in Muck Rack's State of AI in PR 2026↗, 69% said they avoid entering personal data or proprietary material².

Record where the story came from, who provided it, when, under which stated terms and who may access it. Preserve the original notes or recording according to the organization’s authorized process. Label your summary as a summary. If the account team cannot establish the terms, treat public use as pending rather than interpreting attendance at the meeting as consent.

Split the story into factual assertions: the client type, setting, initial problem, intervention, timing and observed outcome. Check each against an appropriate source and owner. A speaker remembering the conversation can confirm what they recall, but that memory alone may not establish the client’s measured outcome.

Map identifying details together. Removing a name may still leave a distinctive job title, city, project date or result. The risk is well documented for personal data: a NIST review of de-identification research↗ notes that researchers have shown some de-identified data can sometimes be re-identified³. Treat a client described by region, specialty and rollout date with the same caution. Ask the client or rights owner to decide whether attribution, anonymized use, a composite, a more general lesson or no use is permitted. A composite should never be presented as one actual client’s experience.

Four: use it named with approval, anonymize it after a real identification check, state the general lesson without the case, or hold it.

QuoteIt keeps these strands apart. A spokesperson's voice comes from material they approved and is kept separate from the organization's facts, and from other clients' material. Wording that gives the speaker an experience, a view or a feeling is marked as proposed until they approve it, and the facts inside that wording are still checked against their sources.

Remove the invented observation and the unsupported effect, keep only what the organization has approved, and send the result to the speaker and the client as a proposal.

Consider a fictional private case note: a regional clinic tested a scheduling process for six weeks and reported fewer missed handoffs in its internal review. The executive did not observe the work directly. The clinic has not approved external use. This scenario is invented to demonstrate the decision path.

A risky proposed quote says, “I saw how our approach transformed patient care at a leading regional clinic.” It invents personal observation, introduces a broad effect on care and leaves the clinic potentially identifiable; the observations hidden inside an executive’s view need checking like any other claim. Removing “regional” does not repair the other claims.

If the organization has separately approved the operating principle, a possible proposal is: “Scheduling changes matter when they make responsibility for the next handoff clear.” The sentence avoids claiming a client result and still needs the speaker’s approval plus a check against the organization’s current position, keeping the company’s voice and the spokesperson’s own distinct. If a concrete case is essential, the team should seek specific client permission and verified wording, with an approval that names the exact copy and use.

The private source, the proposed wording, what was kept and removed, the remaining identification risk and the intended channels, with the client's decision recorded apart from the speaker's.

Show the private source, proposed public wording, facts retained, details removed, remaining identification risk and intended channels to authorized reviewers. Record the client or rights decision separately from the speaker’s acceptance of the quote. If either changes the wording materially, repeat the affected check.

The process can take longer than writing a fresh generic quote. It can also preserve the concrete human insight that made the story useful, the kind of detail that lets an executive quote add something to the story. The transformation record makes that tradeoff explicit: retain the case only when its evidential and permission decisions justify the detail it contributes.