A supplier has drafted a story mentioning your organization and factual claims need checking before publication.
The useful bits
- Draft version and publication plan
- Claims needing correction
- The response should acknowledge the specific corrections and provide a new reviewable version.
Before you write
Use this example when a supplier has drafted a story mentioning your organization and factual claims need checking before publication. Gather the details below so the recipient can act without asking you to reconstruct the situation.
- Draft version and publication plan
- Claims needing correction
- Authorized communications owner
An email you can adapt
The subject “Corrections to proposed [case study]” identifies the request. Replace each bracketed field with a checked detail and remove any sentence that does not describe your situation.
Subject: Corrections to proposed [case study] Hi [name], We reviewed draft [version] and need corrections to [specific statements]. The checked facts are [approved facts], and [claim] is not approved for publication. Please send the revised version to [authorized owner] before publishing or distributing it. Our review of this draft does not approve other uses of our name, logo or data. We would appreciate confirmation that the current draft remains unpublished while the corrections are reviewed. Best, [sender]
Check the boundary
Do not approve invented performance figures, quotes or customer outcomes merely because the overall story sounds positive.
What a useful reply should settle
The response should acknowledge the specific corrections and provide a new reviewable version.
Have the authorized communications owner confirm the final wording and the intended publication scope.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction