Internal Communications Tone of Voice Guide

Internal Communications Voice Guide Write so people know what matters and what to do A practical voice guide for everyone who shares updates at Northstar Services, a fictional organization used for these examples. Keep the facts steady, make the next step easy to find, and write with warmth and respect. One update, made useful Fictional example: service desk hours change from 8:00 a.m.–6:00 p.m. to 8:30 a.m.–5:30 p.m. starting Monday, 14 September. The contact route stays the same. Message Please note the service desk has new hours. Thanks for your understanding. From Monday, 14 September, the Northstar service desk is open 8:30 a.m.–5:30 p.m. If you need help outside those hours, use the usual support request route. What improved The change and next step are unclear. The date, hours, and action are explicit; the tone stays direct and considerate. Go straight to the guidance you need Choose a page based on the message you are working on. Voice principles Make a draft warm, clear, and action-oriented. Write by channel Adapt the format without changing the facts. Adapt for your audience Give each group the context and action it needs. Sensitive messages Know when to pause and seek review. Tools and ownership See the example responsibilities and review cycle. Voice Principles A human voice, with the point up front Three practical qualities to use when drafting or editing. Warm, not overfamiliar: treat readers as capable colleagues. Use everyday language and a respectful tone. Clear, not blunt: say what is changing, when it takes effect, and where the reader can find help. Avoid unexplained shorthand. Action-oriented, not demanding: give a specific next step and explain when it matters. Do not imply blame or urgency that the facts do not support. Turn each principle into a writing move Small changes make the reader's next step easier to see. Lead with the useful fact Put the change and effective date before background detail. Write: “The service desk opens at 8:30 a.m. from Monday, 14 September.” Then explain the reason if readers need it. Replace vague reassurance with a next step Avoid asking readers to trust an undefined process. Instead of “We’re here for you,” name the established support route. Do not invent a new contact or promise a response time. Keep the ask respectful Make the action and timing visible without sounding like a reprimand. Write: “Please use the usual support request route outside service desk hours.” Add a deadline only when one is confirmed and relevant. Worked edit: service desk hours Same fictional facts: from Monday, 14 September, hours change to 8:30 a.m.–5:30 p.m.; the usual support request route remains available. Draft There will be some changes to our hours soon. Please plan accordingly. From Monday, 14 September, the Northstar service desk is open 8:30 a.m.–5:30 p.m. Next step No specific action or support route. If you need help outside those hours, use the usual support request route. Why it works “Soon” and “plan accordingly” leave readers guessing. The date, hours, and next step are specific, without adding an unverified promise. Quick editing questions How do I sound human without being too casual? Use direct sentences, “you” where it helps, and a considerate explanation. Skip slang, forced jokes, and overly familiar greetings. What if a technical term is necessary? Use the term only when readers need it. Define it on first use or pair it with a plain-language explanation. How short should a message be? Keep what readers need to understand the change and act on it. Remove repeated context, not essential dates, limits, or next steps. Write by Channel Keep the facts steady; shape the format Use the channel that fits how much context and follow-up the update needs. Across channels, keep the same change, effective date, and support route. Adjust the length and structure to suit the reader's attention and the place they will see the message. Do not rely on a short post when readers need a durable reference. One service-hours update in three channels Fictional shared facts: from Monday, 14 September, the Northstar service desk is open 8:30 a.m.–5:30 p.m. The usual support request route remains available. Email — give context Subject: Service desk hours change. From Monday, 14 September, the desk opens 8:30 a.m.–5:30 p.m. Please update any local notes that show the old hours. Outside these hours, use the usual support request route. Purpose: reach people who need a complete update. Next step: update any notes you maintain that show the old hours. Team chat — make it scannable Service desk hours change Monday, 14 September: 8:30 a.m.–5:30 p.m. Outside those hours, use the usual support request route. Purpose: give a quick, self-contained notice. Next step: use the established route outside the new hours. Intranet notice — provide a reference From Monday, 14 September, the Northstar service desk is open 8:30 a.m.–5:30 p.m. The usual support request route remains available outside those hours. Check this notice when planning work that depends on desk hours. Purpose: keep a durable update readers can return to. Next step: check the notice when planning around the hours. Choose and shape the channel A short check before you publish. Name the reader task Decide whether readers need a quick heads-up, fuller context, or a lasting reference. Choose the channel for that task Use chat for a concise update, email when readers need a complete message, and an intranet notice when the information should remain easy to find. Check the message travels intact Confirm every version has the same facts, date, and next step; verify that any link opens the intended destination. Adapt for Your Audience Make it relevant without changing the facts Adapt context, terminology, and action to the work readers do. Start with one confirmed version of the facts. Then ask what each audience already knows, what could affect its work, and what action is relevant. Tailor the explanation, not the underlying change. Avoid assumptions about people based on their role or work location. Same update, three useful angles Fictional shared facts: service desk hours change to 8:30 a.m.–5:30 p.m. from Monday, 14 September; the usual support request route remains available. Frontline operations From Monday, 14 September, the service desk is open 8:30 a.m.–5:30 p.m. Check the new hours when planning work that may need desk support; use the usual support request route outside those hours. Connect the change to shift planning and the established support route, without assuming every task depends on the desk. People managers From Monday, 14 September, the service desk is open 8:30 a.m.–5:30 p.m. Please share the confirmed hours with your team if you maintain local reference notes; the usual support request route remains available outside those hours. Give managers a specific sharing action only where it applies; do not make them responsible for facts they do not own. Office-based teams The service desk's new hours are 8:30 a.m.–5:30 p.m. from Monday, 14 September. If you need help outside that window, use the usual support request route. Keep the message concise for readers who need the hours and the next step. Check what each group needs Use these questions before producing audience versions. What do they already know? Add only the context needed to understand this update. Check whether the date or change has already been announced. Define internal terms that may not be familiar to every group. What part affects their work? Connect the confirmed change to a real task, not an assumed concern. Name the relevant action only for readers who need to take it. Keep shared facts consistent across all versions. How will they find the update? Make the message accessible in the channel readers use for that task. Use a scannable format for a quick notice. Keep a stable reference for information readers may need again. Keep versions consistent and fair How do I avoid stereotyping an audience? Base differences on work context and confirmed needs, not assumptions about preferences, ability, or behavior. When unsure, ask a representative subject-matter owner. Should every group receive a separate message? No. Use one clear message if the facts and actions are the same. Create audience-specific versions only when the context or next step genuinely differs. How can I prevent conflicting versions? Work from one approved set of facts and compare each version for matching dates, changes, and support routes before publishing. Sensitive Messages and Escalation Pause when a message could affect people or trust Use calm, factual language and involve the appropriate internal owner before sharing. Seek review when a draft could affect privacy, wellbeing, employment matters, operational continuity, or confidence in the organization. Share only the information needed for review. This example provides a routing approach, not a substitute for your organization's established incident or approval procedures. Start with the role closest to the subject Illustrative routing for a fictional organization. Confirm local owners and existing procedures before using. Message situation Suggested first review role What to bring for review People-related change or employee concern People team or designated people-policy owner The confirmed facts, affected audience, and any personal details needed to assess the draft Operational change affecting service or work arrangements Responsible operations lead What is changing, when it takes effect, and what remains uncertain Organization-wide announcement or reputational concern Internal communications lead, with the relevant subject-matter owner The proposed message, intended audience, source of facts, and requested publication timing Possible immediate risk or active incident The established incident or emergency owner Use the organization's current incident route; do not delay urgent internal escalation to polish a message Sample handoff for review A concise fictional handoff keeps confirmed facts separate from open questions. Summarize the issue “A proposed change to service desk hours may affect teams that plan work around desk availability.” Separate known from unknown “Confirmed: hours change to 8:30 a.m.–5:30 p.m. on 14 September. To confirm: whether any other support arrangements change.” Name affected readers and the decision needed “Potentially affected: teams that use the service desk. Please confirm the audience and the support-route wording before publication.” Send it to the appropriate owner Use the organization's established review route for the subject. Keep personal or sensitive details out unless the reviewer needs them. When the facts or audience are unclear What if some facts are still being confirmed? Do not present assumptions as settled facts. Ask the subject-matter owner to confirm what can be shared and label unresolved points clearly in the review handoff. What if a draft contains personal details? Pause wider sharing. Remove details that are not necessary for review and use the appropriate internal people or privacy route for anything that remains. What if the issue may be urgent? Follow the organization's established urgent or incident process and contact its responsible owner. This guide does not replace local escalation procedures. Tools, Ownership, and Maintenance Keep the guide owned, reviewed, and useful This fictional model separates editorial stewardship, subject expertise, and publishing. The internal communications owner maintains voice guidance and examples. Subject-matter owners confirm that specialized facts and processes are accurate. A site publisher checks page structure, links, and accessibility before releasing an update. One role may hold more than one responsibility in a small organization, but factual approval should still come from the relevant subject owner. Example responsibility matrix Role titles are illustrative; assign these responsibilities to real local roles before adopting the model. Work Internal communications owner Subject-matter owner Site publisher Voice principles and worked examples Drafts and maintains Checks examples in their subject area Publishes approved copy Operational or people-related facts Edits for clarity and tone Confirms accuracy and audience impact Checks the approved version is posted Links and page presentation Flags outdated destinations Confirms linked guidance remains relevant Tests links and accessible page structure Periodic guide review Coordinates proposed changes Reviews changes affecting their topic Publishes the dated revision A practical review cycle Use the cycle when a change is proposed and at the next scheduled guide review. Collect a specific change Record the page, current wording, proposed edit, and reason it would help readers. Check examples and destinations Verify that sample facts are still clearly fictional and every link opens the intended page or approved resource. Ask the relevant owner to review Have the subject-matter owner verify facts and the communications owner check tone and clarity. Publish and note the revision Update the page and record the revision date and change summary in the organization's normal publishing record. Continue with the relevant guide page These working links stay within this site; add other resources only when their destination is verified. Voice principles Apply warmth, clarity, and a visible next step. Writing guidance Open voice principles Write by channel Choose the format that fits the reader's task. Open channel guide Adapt for your audience Tailor context and action while preserving shared facts. Open audience guide Sensitive messages and escalation Identify when a draft needs subject-matter review. Review guidance Open review guidance