Describe the voice in observable terms
Instructions such as “sound innovative” or “be human” are too vague to guide writers or AI tools. Write a short voice guide with three to five traits and show each one in action. For example, “direct” can mean opening with the reader's problem and avoiding abstract slogans. Include before-and-after rewrites, approved product terms, words to avoid, and a few examples of how to explain uncertainty.
Separate voice from message. Voice describes how the brand speaks; the message describes what the product claims and offers. A draft can sound perfectly on-brand and still promise an unavailable feature. Both require review. Keep the facts in an approved brief and the voice guidance in a separate, reusable layer so each can be updated by its owner.
| Review dimension | Question | Example correction |
|---|---|---|
| Clarity | Can the reader understand the point quickly? | Replace a slogan with a concrete benefit |
| Tone | Does the wording fit the audience? | Reduce hype in an executive report |
| Accuracy | Is each product claim approved? | Narrow a feature statement |
| Channel fit | Does the format suit the platform? | Turn a dense paragraph into a short series |
Allow the channel to shape the expression
A board report may be concise and measured; a social reply may be conversational; documentation should favor precision and direct instructions. They can still share vocabulary, honesty, and a recognizable point of view. Provide channel examples instead of forcing one template everywhere. If an AI workflow creates first drafts, include audience, job, approved facts, and two or three representative examples in its task context.
Review a sample of actual published or near-published work. Have two editors independently note deviations, then compare judgments. This exposes ambiguous rules. Store recurring corrections as examples in the guide and update prompts or templates from them. Do not claim a numerical consistency rate unless the team has a defined rubric and reliable scoring process.
Keep the system maintainable
Assign a brand owner, a product-claim owner, and a review cadence. When positioning changes, update the source guidance and identify assets that need revision. A useful system helps people write faster while still letting them exercise judgment. The goal is recognizable, accurate communication, not a rigid sameness that makes every channel feel automated.
Write examples that show judgment
A useful voice guide contains more than adjectives. Take real pieces of copy and show an approved rewrite with a short reason. Explain why a sentence feels inflated, too casual, inaccessible, or vague for the intended audience. Include examples of acknowledging uncertainty without sounding evasive. Give writers a small vocabulary of preferred terms for the product, but allow natural variation where meaning remains clear.
Build channel guidance from the reader's task. In documentation, clarity means a direct instruction and expected result. In a board report, it means a conclusion with evidence and caveats. In a social conversation, it means answering the point without turning every reply into a pitch. These are different expressions of the same underlying commitments.
Measure revision patterns
Sample a set of drafts from several channels and ask two editors to annotate deviations independently. Separate tone changes from factual corrections; otherwise a serious product-claim issue can be hidden inside a general “voice” score. Compare the most frequent edits and update the guide with before-and-after examples. If reviewers disagree often, the rule may be too subjective to apply reliably.
Review published work periodically as well. A prompt can perform well on test drafts and drift when campaign context changes. Assign an owner to update the voice guide when positioning shifts and notify channel owners of the revision. Consistency should help the audience recognize the brand and understand the offer, while leaving enough room for the context and writer's judgment.
Questions to settle when copy sounds inconsistent
Is the problem voice or message?
Ask whether the sentence is factually true before debating tone. “Our platform supports every integration” is a claim problem if the product has limits, even when the sentence matches the brand's confident style. Once the facts are correct, review whether the phrasing fits the audience and channel. Keep separate annotations for accuracy, clarity, tone, and format so the owner of each issue can act.
How much variation is acceptable?
Variation is useful when a channel serves a different reader task. A concise social post and a detailed implementation guide should not use identical paragraphs. They should share accurate terms, a recognizable degree of directness, and the same boundaries on claims. Use approved examples to show that family resemblance rather than enforcing a fixed sentence template.
Copy this editorial review card
List audience and channel, intended reader action, approved source facts, voice traits, example of a good opening, prohibited claims, accessibility checks, and reviewer. For a sample of drafts, record the exact edit and its reason. At the next guide revision, turn common edits into a before-and-after example. If two editors disagree often, clarify the rule with real copy rather than inventing a more precise-sounding score.