A thread begins with a meeting time and ends with a request to review a draft. Days later, someone searches for the review request under a subject that still says “Tuesday room booking.” The conversation made sense while it happened, but its label stopped helping.
Decide whether the task has changed
A small update to the same decision may belong in the existing thread. A different deliverable, audience, or request can justify a new message with its own subject. Choose based on what the recipient needs to do, rather than starting over after every reply.
For an invented example, “Review the welcome leaflet by Thursday” describes a different task from “Confirm the room for Tuesday.” The clearer subject makes the action visible before the reader opens the message.
Carry over only the context needed
In the new message, explain how the request relates to the earlier discussion and include the relevant document or reference. Do not assume every recipient saw the previous thread. Equally, avoid forwarding a long history containing unrelated or private material merely to save writing two sentences.
State the action, the deadline if one exists, and the point on which you need a response. If the deadline is a proposal rather than an agreement, say so plainly.
Keep later replies useful
Once the new task has a clear home, use that thread for its related updates. If someone answers the old conversation, direct them to the current message with a short explanation, without turning the correction into a reprimand.
Our note on giving saved information a useful job reflects the same practical habit. A label should help future retrieval, not merely describe how a conversation happened to begin.