When the Company Voice and the Spokesperson’s Voice Differ

An employee announcement needs a quote from a chief executive who usually speaks in short, concrete sentences. The corporate style guide asks for calm, formal language and a defined name for the initiative. The first draft follows the guide so closely that it could have been signed by anyone. The second follows the executive so closely that it skips the terminology employees need. Neither draft has solved the assignment. The fix is to give each voice its job: the company sets the facts, terms, promises and limits; the spokesperson sets the order, the examples and the plain wording. Where they genuinely conflict, the company boundary wins and the owner decides.

Company voice and spokesperson voice answer different questions. The organization says what it can responsibly promise, how it names products and groups, and which positions must remain consistent. The person supplies a recognizable way of explaining priorities. A good quote assigns each source its proper job, and the result is usually a quote that tells readers something they did not already know.

The company decides terms, promises, policy and cleared facts; the spokesperson decides how the point is made, in which order and with which example. The spokesperson's side is easier to keep when it is written down in an executive voice guide built from approved examples.

QuoteIt drafts a person's quote this way. The organization and the spokesperson are separate personas: the spokesperson's voice comes from material they approved, the organization supplies its voice, policy and facts, and where the two pull apart the organization's boundaries come first. Nothing from one person's material is carried into another persona's drafts.

It takes its sequence and limits from the company and its plain acknowledgment from the speaker, so it reads like a person and still says only what has been decided.

Imagine a company preparing a staff update after acquiring a smaller business. The approved company position says that employment arrangements will be discussed with affected teams and that no further timetable is confirmed. The chief executive tends to speak directly about operational work, not broad claims about culture. These are invented workshop details, not a model for a real transaction.

A corporate-only version might read: “The organization remains committed to an orderly integration that reflects our people-first values.” It supplies a sentiment but no useful next step. An executive-only version might say: “We have a lot to sort out, and we will see what happens.” It may sound natural but creates uncertainty without a clear boundary.

A combined proposed quote could be: “We have work to do together before we can confirm the next steps. Teams affected by the integration will hear from their managers first, and we will share the timetable when it is agreed.” The organization supplies the sequence and restriction. The executive supplies the plain acknowledgment. Each sentence still needs the relevant owner’s approval.

Do not soften it quietly or keep it because it sounds authentic; write a short decision note for the accountable owner with two paths, support it or narrow it.

A personal preference can conflict with an organizational boundary. Perhaps a leader wants to describe a product as “the safest option,” while the current approved evidence only supports a more limited performance statement. The writer should not quietly preserve the stronger claim because it sounds authentic; a word like “safest” sets up a comparison that needs the same review as any other superlative. The PRSA Code of Ethics↗ asks members to investigate the truthfulness and accuracy of information released on behalf of those they represent¹, and that duty covers a leader’s favorite phrase as much as a statistic. Nor should they quietly delete the executive’s intended concern if it is central to the message.

Put the conflict in a compact decision note. Name the exact sentence, the relevant organization boundary, the speaker’s intended meaning, the accountable fact or policy owner, and two possible paths: support and approve narrower wording, or remove the claim. This turns a taste dispute into a decision with a traceable basis, in the same way that sorting conflicting reviewer comments into decisions does for a crowded draft. It also protects the writer from treating an executive’s preference as permission to make a factual assertion.

Read it three times: as the organization for names, facts and promises, as the spokesperson for order and examples, and as the audience for what they need to do next. Most teams do this check by hand. In Muck Rack's State of AI in PR 2026↗, 98% of PR professionals said they always or often edit what AI produces². Generic copy costs you with reporters too: in Cision's 2026 State of the Media survey↗, 53% of journalists opposed AI-generated pitches, citing accuracy and personalization³.

Read the draft first as the organization. Are names, promises, facts and policies current? Are any qualifications missing? Then read it as the spokesperson. Does the sentence order fit their normal way of making a point? Did a useful example become a slogan? Small changes can do this, and the habits in editing a quote while keeping how the person talks help here. Finally, read as the audience. Does the combined result answer a real concern in language they can understand?

Keep the organization example and approved spokesperson examples beside the brief. When a sentence feels wrong, the worksheet lets a reviewer locate the cause: an unsupported promise, conflicting terminology, an unsuitable voice pattern or a mismatch with what the audience needs.