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.
| Details | Needs editing | Ready to understand |
|---|---|---|
| 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.