Publishing customer examples: document permission and scope

Separate substantiation from permission

Start with two independent questions: can we support this statement, and may we publish it in this form? Written approval cannot make an inaccurate performance claim true. Equally, an internal measurement does not automatically permit naming the organization concerned. Keep the supporting observation next to the permitted scope for every claim. Distinguish the customer's exact quotation, editorial summary and your own inference. Explore this further in the guide Publishing original B2B research: methods, samples and limits.

Ask for missing context specifically: which period was measured, what baseline applied, and what contribution can reasonably be connected to the product? If that context is unavailable, narrow the wording or omit the figure. A subject expert accepts the factual version while the relevant approver accepts the proposed use. Record these as separate decisions even when one person happens to perform both roles.

Create an identifiable material record

A material record identifies the original file or source, creation date, people and organizations involved, agreed purposes and unresolved questions. Treat a logo, portrait, screenshot and quotation as separate objects even when they came from one interview.

GOV.UK's research guidance explains the importance of participants understanding how research will be used and shared. Here it provides a methodological reference for transparent arrangements, not a legal rule automatically applicable to your business. Translate that principle into a concrete preview: this material, in this version, will appear in these places. Avoid broad internal labels whose actual scope nobody can explain to another colleague.

Which use was actually agreed?

Note visible third parties, internal project names or customer information in the background. An otherwise attractive image may be unsuitable without invalidating the whole story.

Describe channel-specific use

Write a small usage matrix covering the website case study, organic social post, paid advertisement, sales presentation and event material. Add language, planned editing and any agreed duration. Internally, permission for a case study should not silently become permission for every future promotional format. Where the scope is uncertain, request clarification or select different material before production begins.

Show a representative example of each proposed format. A short advertisement can simplify the story more aggressively than the full case study. The question is therefore not only whether individual words match, but what impression the combined presentation creates. Store restrictions on the material record so designers and sellers can see them during later exports. A qualification hidden in one person's inbox is not a dependable operating control for repeated team use.

Make approval a versioned decision

Give the proposed version an unambiguous identifier and present text, images, captions and context together. A response needs to be traceable to that exact package. Consolidate requested changes rather than allowing several contradictory email versions to circulate. After a substantively important edit, check whether the earlier response still covers what will actually be published.

Translations need their own editorial inspection. An English phrase can suggest a measurable feature or stronger promise that was absent from the German original. Review figures, comparisons and limiting conditions separately. Link the published file to the accepted permission record and the factual review. This makes the earlier decision understandable when a new employee asks why that particular statement was considered defensible at the time, rather than relying on the original editor's memory.

Fictional example: an integration story

The explicitly fictional SaaS company Nordlicht Flow wants to publish an interview about an integration. In this assumed scenario, the customer permits a factual case study naming the organization, but excludes personal portraits and paid advertising. The product team confirms the described test workflow, not a universal time saving. These invented details demonstrate the operating method; they are not actual customer results.

The editor publishes a bounded integration account with test conditions and no invented efficiency figure. A later LinkedIn advertisement is recognized as a new use in the register and held pending clarification. Instead of stretching the original approval, the team prepares a specific request with an advertisement preview. A useful story remains possible even though some material and channels are outside the agreed scope.

Inspect each derivative output

Repurposing should begin with the accepted source package, not whichever presentation slide was easiest to find. When shortening, check whether a timeframe, condition or limitation disappears.

Connect every reused graphic to its material record. If several stories are combined, preserve the provenance of every figure; combination does not create a new aggregate result. External agencies rarely need unrestricted access to all original files. Give them the materials required for the assignment together with explicit usage limits. A focused handoff reduces questions and prevents an excluded image from quietly becoming part of the default design template. Explore this further in the guide Customer advisory content: use buyer perspectives without false consensus.

Does permission cover this edition?

Removing an introductory clause must not turn a customer-specific statement into a general product promise. Output review therefore compares meaning and context, rather than checking only identical wording or the existence of an old approval email.

Handle changes after publication

Assign an owner and a backup for subsequent questions. They need to locate published pages, exported versions and active campaigns. If a customer challenges a statement or an underlying condition changes, first document the exact issue and limit further reuse. The relevant factual or legal specialist then decides what action the individual case requires; an editorial checklist cannot replace that judgment.

A correction involves more than swapping one website file. Review known presentations, social assets and partner copies where they are within your control. Record what was actually changed and what remains unresolved. Coordinate agreed retention or deletion of original material with the accountable people instead of inventing a universal retention period. The record should help the team execute a decision consistently without pretending all downstream copies can always be recalled.

Pilot a lightweight release process

Start with one story and one target channel. Editorial records the materials and claims, the product or domain team checks substantiation, the account owner coordinates the customer contact, and the relevant approver confirms the intended scope. Before release, ask an uninvolved colleague to identify the permitted version using only the register. If that person cannot do so, the process is not yet ready for a reliable handover.

Track outstanding approvals, overdue questions and avoidable rework as process observations, not proof of legal completeness. Pause when origin, authority or scope remains unresolved. Extend the process to further channels after the small workflow operates consistently. A modest register with accountable owners is more useful than an elaborate template whose fields nobody maintains during ordinary work.