Editorial review: 9 October 2026
Choose the message that matches the workplace action
A workplace message should make its purpose clear. A status update describes the present position; an information request asks someone to supply a missing fact; a correction replaces an earlier inaccurate statement. Mixing these purposes can leave a colleague unsure whether they need to act, approve something or simply read a note.
This guide works through three complete messages drawn from one original fictional task record. It focuses on routine work coordination rather than interview delivery or salary negotiation. The separate communication skills guide covers spoken explanation and clarification.
Purdue's general business-writing guidance supports writing for the reader, presenting relevant information clearly and revising your wording. The records and messages here are editorial originals, not Purdue examples or a claim that a particular workplace uses these procedures.
Establish the source before writing
Imagine a small team preparing an internal practice pack containing three invented exercises. The following facts are expressly supplied:
| Item | Supplied state |
|---|---|
| Exercise A | Draft wording complete; answer checked |
| Exercise B | Draft wording complete; answer not checked |
| Exercise C | Draft wording incomplete; answer not checked |
| Pack owner | Leela |
| Answer-check owner | Sameer |
| Review meeting | Friday at 14:00; no calendar date supplied |
| Permission | The team may share these fictional draft states internally |
| Release decision | Leela must expressly authorise release; no such decision supplied |
Do not manufacture a completion percentage from this table without defining what counts as complete. One of three exercises has a checked answer, but this does not make the whole pack one-third ready for release. Wording, answer checks and owner approval are separate conditions.
The meeting time lacks a calendar date. You can report the supplied wording, but you should ask for the date before adding a calendar invitation or treating it as an unambiguous deadline. The examples do not involve sharing real candidate data or confidential workplace records.
Message one: a brief status update
The intended reader, Leela, needs to know which work is complete and which remains. A useful message leads with the current state rather than a long introduction about how busy the team has been.
Internal practice pack — draft status
Exercise A has complete wording and a checked answer. Exercise B has complete wording, but its answer check is pending. Exercise C still needs its wording completed and its answer checked. Sameer owns the answer checks. No release approval is recorded, so I am reporting draft status rather than saying the pack is ready. The review is listed for Friday at 14:00; its calendar date still needs confirmation.
Every completion claim maps to a supplied fact. The message does not say that Sameer has promised a finishing time, that Leela has approved release or that the missing exercise is almost finished. Those additions would require evidence absent from the record.
A status update can be short and still complete for its purpose. It need not include every sentence of the practice exercises because the reader needs the state of the pack, not the exercise content. Relevant detail depends on the reader's actual task.
Message two: an information request
The same facts support a different message to Sameer. Here the purpose is to ask for the next information needed, not to instruct him to meet a deadline he has never accepted.
Answer-check plan needed for exercises B and C
Sameer, the current record shows that B's wording is complete but its answer check is pending. C's wording is incomplete and its answer check is also pending. Please confirm when you can check B and what completed wording you need before checking C. I do not have your agreed completion time. The review is listed for Friday at 14:00, but I am asking Leela to confirm the calendar date before using it as a deadline.
This request names the two affected items and the information needed. It acknowledges the dependency for C. Asking for a check does not prove that the check was performed, and a requested time is not an accepted commitment.
If Sameer replies only, “I can check B,” that response resolves willingness for B, not when it will be checked or what happens to C. A focused follow-up can ask for the remaining time and dependency information. Avoid labelling the entire request complete merely because a reply exists.
Message three: correct an earlier inaccurate update
Suppose the fictional sender previously wrote, “All three answers are checked.” That statement conflicts with the source. A correction should identify the earlier claim and replace it with the actual state; a vague “small update” can hide what changed.
Correction to my earlier answer-check update
My earlier statement that all three answers were checked was incorrect. The current record confirms only A's answer check. B and C remain unchecked; C's wording is also incomplete. Please use this corrected state when planning the review. I have not recorded a release approval or an agreed completion time for the pending checks.
This correction does not claim that the mistake had no effect. The source gives no evidence about whether anyone relied on the earlier message. If another person supplies an actual consequence, record it separately and respond to that situation rather than inventing reassurance.
The correction is an original practice artifact. It is not advice to disclose real internal material publicly, and it does not override your organisation's communication or access rules.
Check acknowledgment and completion separately
Leela replies: “I have seen the correction: only A is checked.” That explicitly confirms receipt and the stated answer-check position. It does not authorise release, finish B or C, or confirm the Friday date.
A revised status entry can say, “Leela acknowledged the corrected answer-check state; release approval and the review date remain unconfirmed.” The entry preserves the limited meaning of the reply.
This distinction matters whenever a message contains several requests. A response might address one of them. Match the response to each requested item before marking the whole conversation complete. Acknowledgment is useful evidence of receipt, but it should not silently become approval or execution.
Keep a correction visible in the working record
If the team uses a status document, update the affected answer-check entry and note that it replaces the earlier inaccurate statement. Use the process available in the actual workplace rather than assuming every team has the same version-history or chat tools.
When copying a status into another channel, check that its meaning remains intact. “B wording complete” cannot be shortened to “B complete” without losing the pending answer check. Likewise, “Friday at 14:00, date unconfirmed” must not become an invented calendar date.
Purdue's email guidance offers narrow guidance on meaningful subjects, clear paragraphs and checking recipients. If email is the actual channel, apply those ideas to your own message rather than copying institutional examples. No channel choice by itself certifies confidentiality or guarantees that a colleague will respond.
Practise a new fact without overwriting old limits
For a separate changed-input exercise, Sameer supplies this fictional update: “B's answer is now checked. I have not checked C.” The status changes for B only. A remains checked; C remains incomplete in wording and unchecked.
A complete revised message is:
A and B now have complete wording and checked answers. C's wording and answer check remain pending. Sameer's new update confirms B's check only. Release approval and the calendar date for the Friday 14:00 review are still unconfirmed.
This is a separate exercise with a new explicitly supplied fact, not an assertion that Sameer actually completed work after the earlier conversation. It tests whether you can update one field without converting unrelated unknowns into completed work.
Use a review task before sending
Ask a practice reader to identify three things from your draft: the current state, the action requested and any commitment actually authorised. Compare their answers with the source table. If they believe the pack is approved for release, revise the sentence that created that impression.
Also check the intended recipient, names, item labels and time wording. These checks serve this particular message; they are not a guaranteed method for reducing errors throughout an organisation. Record actual feedback rather than claiming better productivity or career advancement without evidence.
For messages involving competing requirements and a decision owner, see the stakeholder management guide. Do not insert a negotiation into a routine factual correction unless the actual situation requires a decision.
Frequently asked questions
What is the difference between an update and a request? An update reports the state. A request names information or action needed from the reader. A message can contain both if their roles stay clear.
Does a reply mean the task is complete? Check what the reply actually confirms. Receipt, willingness, completion and approval are different claims.
Can I fill in a likely deadline to make a message concrete? Use the supplied deadline or ask for the missing detail. An invented date makes the message more specific but less accurate.
How should I correct a mistake? Identify the inaccurate statement, provide the supported replacement and keep any unresolved effects or approvals visible.