Good business email writing makes 3 things easy to find: why you are writing, what the recipient should do and what happens next. Put the request near the beginning, supply only the context needed to answer it and close with a usable next step. Professional wording should clarify the work rather than disguise uncertainty behind formal phrases.
How do you write a clear business request?
Begin with the decision you need. “Please confirm which workshop outline we should prepare” is more useful than “I am writing regarding the aforementioned arrangements”. The first sentence lets the reader recognise the task before working through its history. Add background when it changes the answer, rather than copying a whole conversation into the opening paragraph.
Use a subject that identifies the work and the action. Microsoft’s email-writing guidance recommends descriptive, action-oriented subjects and changing them when the conversation changes topic. A subject such as “Workshop outline: confirm the audience” helps the reader retrieve the exchange later. A vague “Following up” provides much less context when several projects are running.
Address the right person. Microsoft distinguishes people expected to respond or act, placed on To, from people who only need information, placed on Cc. For a request that several colleagues could answer, it recommends choosing a particular respondent. This is a useful ownership rule, not a reason to exclude somebody whose approval is actually required. Check the business’s decision arrangement before deciding who receives the message.
Keep the greeting proportionate to the relationship. Purdue’s Email Etiquette guide recommends a greeting when writing to someone unfamiliar, standard spelling and clear, short paragraphs. Use the recipient’s known name and title accurately. If you do not know their preferred form of address, avoid inventing a title or relying on a copied template that still names another person.
The following fictional example turns a vague request into a usable one. Names, organisations and circumstances are invented; this message has not been sent.
Before: “Hi, following our discussions please advise on everything needed for the session so we can proceed accordingly.”
Rewritten request
Subject: Workshop outline: confirm the audience and discussion priority
Hello Leya,
Please confirm whether the workshop is intended for new supervisors or the whole operations team. We also need your preferred discussion priority: handling enquiries or maintaining customer records.
The attached outline currently assumes new supervisors and an enquiry-handling focus. Those are working assumptions, not agreed requirements.
Please reply with the audience and priority you want us to use. If another colleague owns that decision, please tell me whom to contact. We will revise the outline after receiving the confirmed brief.
Kind regards, Mutinta Workshop coordinator
The rewrite names the questions, exposes the assumptions and describes the next action without inventing an approval deadline or claiming agreement. In a real exchange, attach the actual referenced file before sending or replace the attachment sentence with an accurate description of the agreed shared document. The example’s wording does not establish that a document exists outside this fictional exercise.
Use the following original editing table as a practical review tool.
| Draft symptom | Question to ask | Useful correction |
|---|---|---|
| “Please advise” without a decision | What answer would let work move forward? | Name the choice or missing information |
| “As agreed” without a record | Was that point actually confirmed? | Label an assumption or cite the confirmed decision |
| Several recipients with no owner | Who is expected to respond? | Address the action to the responsible person |
| “Urgent” without an explanation | What dependency makes timing matter? | State the real dependency and agreed response point |
| Attachment mentioned but absent | What should the reader inspect? | Add the correct file or amend the sentence |
| “We will revert” without a next step | What will happen, and who owns it? | State the planned action and its owner |
How should replies and follow-ups move the work forward?
Answer the question before introducing a new issue. A reply to the fictional request might begin: “Please use the new-supervisor audience and enquiry-handling priority. The operations manager will confirm the participant list separately.” This gives the requested decision while keeping an unresolved dependency visible. It does not imply that the participant list or the workshop itself is approved.
If you cannot answer fully, acknowledge the message and say what you are checking. Microsoft recommends acknowledging work that needs a more extensive response and giving a realistic response point. Use a date or time only when you can support that commitment. A polished sentence is not permission to promise another person’s availability or an outcome outside your control.
Original holding reply
Hello Mutinta,
I have received the outline. I am checking the intended audience with the operations manager, so please keep the current audience description marked as provisional.
I will send the confirmed brief after that discussion. If you need the answer to meet a specific preparation commitment, please tell me what depends on it so we can agree the next step.
Kind regards, Leya
A useful follow-up should identify the unanswered decision, not merely repeat that an earlier email exists. “We still need the audience choice before revising the outline” connects the request to the work it affects. Avoid turning every follow-up into an escalation by copying more people without explaining their role. Microsoft advises using importance markings sparingly; repeated urgency can obscure the genuinely consequential message.
For a reply containing several answers, label them clearly. Purdue permits answering within quoted questions if you explain the arrangement and separate the responses. Microsoft likewise recommends identifying inline comments and distinguishing them from original text. You can use plain labels such as “Your question” and “Our answer”; the reader should not need colour perception or memory of an earlier version to identify who wrote what.
Review tone after the facts are correct. Purdue cautions that humour can be misunderstood, and Microsoft advises against sending an angry message immediately. Save a difficult draft and return to it with the intended outcome in mind. Replace accusations about motive with the observable issue: the requested document is missing, the proposed audience is unconfirmed or the supplied date differs from the agreed brief.
Finish with a simple signature and a final recipient check. Purdue recommends contact information sufficient for a reply; Microsoft favours a short, professional signature. Neither an elaborate sign-off nor a logo can compensate for a missing request. Read the message once as the recipient: can they identify the question, distinguish confirmed facts from assumptions and answer without reconstructing the entire project?
Writing is separate from mailbox setup and delivery. See business email for the service context. Get started with a fictional or redacted communication example; keep private correspondence, customer details and account credentials outside the initial enquiry.
By Spout Team. AI-assisted drafting by Codex using the linked primary writing guidance. All worked messages are original fictional examples.