Before sending a long message, ask what you need the reader to understand, decide or do. Put that near the beginning.
The right length depends on the task. A technical explanation may need detail. A scheduling question may need only the proposed time, the reason and a reply deadline.
Make the message as clear as the situation allows, without cutting information the reader needs.
Lead with the point of the message
Try writing the request before the background. “Can you approve the revised service area by Thursday?” gives the reader a reason to keep reading.
Then explain the change, the options and the information needed for approval. If there is a material risk or unresolved question, keep it beside the decision it affects.
A long introduction can hide a straightforward request. It can also hide the fact that you have not decided what you are asking.
Replace vague wording with useful detail
Look for phrases that sound professional without telling the reader much. “We are proactively managing service delivery” could mean almost anything.
In a hypothetical customer update, “We will confirm your arrival window the day before the visit” tells someone what to expect. Use that wording only if the business can keep the promise.
Keep technical terms when they carry important meaning. Explain an unfamiliar term the first time rather than replacing it with a phrase that loses a safety requirement, condition or limitation.
Give the detail a clear place
When a message genuinely needs depth, organise it around the reader's questions. Use headings for different decisions, short lists for parallel items and a table when a comparison is easier to scan that way.
Keep the main request visible. Link to a supporting document when the reader may need to inspect the full evidence, and say which part matters.
For a report, distinguish observations, explanations and recommendations. A reader should be able to tell which figures were measured and which conclusion still needs checking.
Use AI to test the draft, then review the changes
If you are working with non-sensitive, approved material in an appropriate tool, this is a useful editing instruction:
Identify the main request. Suggest a clearer opening and remove repetition. Preserve facts, conditions and uncertainty. Do not add a promise, statistic or example that is not in the draft. List any meaning you changed.
Compare the proposed version with the original. Check dates, amounts, responsibilities and exceptions. A shorter sentence is not an improvement if it changes what the business has agreed to do.
Do not make a word limit the final judge. Keep the explanation that helps the recipient make a sound decision.
Read it as the recipient
Before sending, check whether someone can answer these questions:
- Why am I receiving this?
- What do I need to know or decide?
- What happens next, and who is responsible?
- Where can I find the supporting detail?
Read the message aloud if it still feels awkward. A simpler sentence often appears once you stop trying to make the draft sound more formal.
For help making website copy easier to use, tell us which services customers keep asking you to explain. We can help put those answers where people need them.
