One brief, several client voices: keep tone profiles instead of duplicate templates

Separate the common message from the client's voice

The factual brief answers what happened, what changes, who is affected and what the reader should do. The tone profile answers how this client communicates: level of formality, sentence length, preferred terminology, first-person usage and phrases to avoid. Keep those inputs separate so an energetic rewrite cannot quietly introduce a stronger product claim.

Microsoft's writing guidance describes a voice that stays consistent while tone changes with context. Apply that distinction within each client's materials too. A launch announcement and a service interruption notice can share recognizable language without sounding equally cheerful. Let approved examples guide the profile rather than stereotypes about a country or industry.

Build a compact profile from approved examples

Choose a few short examples the client has actually approved and that you are permitted to use. Ask a model to propose observable rules, then review them yourself. Replace vague labels such as premium or disruptive with instructions an editor can test: lead with the practical benefit, avoid exclamation marks, or use the full product name on first mention.

In this fictional example, three clients announce a new project-status page. The page is available now, displays updates posted by the team and does not promise real-time monitoring. All versions must keep those facts. The examples describe invented clients, not measured campaign results.

Use eight tones to explore, then choose a stable profile

If you need a broad comparison, request eight deliberate lenses: concise, warm, formal, explanatory, confident, reassuring, consultative and executive. Define each one in the prompt. Eight output variants are a way to explore writing choices, not eight human approvals or proof that the versions are independent.

Use Ask separately in Colay to compare how available agents follow the same constraints. The useful question is whether each version could belong to this client. A consensus summary may help describe differences, but the client's approved profile and your editorial judgment determine the choice.

Core message and fixed claims: [facts]. Target client profile: [approved rules]. Context and reader action: [details]. Generate eight short versions using these lenses: concise, warm, formal, explanatory, confident, reassuring, consultative and executive. Keep dates, feature scope and commitments identical. For each, state what changed in tone and whether it fits the target profile. Do not introduce stronger claims, invented benefits or cultural stereotypes. Finish with one recommended draft and a list of factual or voice decisions requiring approval.

Prevent one client's language from leaking into another's work

Keep profiles in your existing approved document system and provide the relevant one when drafting. This workflow does not assume that Colay automatically maintains isolated client workspaces or remembers a brand profile across every session. Explicit context makes the process easier to inspect.

1. Label the source brief and profile with the client and version before opening a drafting session. Use fictional identifiers where appropriate.
2. Provide only the target client's permitted context. Do not carry private examples or commercial details from another client's conversation into the brief.
3. Compare terminology, pronouns, greeting, strength of claims and requested action against the profile.
4. Save the accepted draft with the profile version and the few decisions that explain why it fits. Update the profile when the client approves a lasting change.

Evaluate consistency across a small set of real tasks

Try the profile on an announcement, a routine update and a difficult message. If it produces a recognizable voice only for marketing copy, add instructions for restrained situations. Ask the client to approve the rules and examples, not dozens of unlabelled alternatives.

Measure the editing you actually need: which phrases are repeatedly rejected, which rules conflict, and which drafts need factual correction. Reuse one factual template with the appropriate profile when it works. Create a separate template only when the communication task or required information genuinely differs.

Questions, answered