Name the specific work and the requested action in the subject. Add a due date only when it is confirmed, and make the first sentence ask for the same thing. For an ordinary internal review, “Review the workshop room layout” tells a colleague more than “Quick question” without manufacturing urgency.
The subject is a small work instruction, not a promise that someone will respond. Its job is to make the request visible in a colleague’s inbox. This is different from configuring an email filter, maintaining a support macro or preparing a customer reply: it concerns neither mailbox automation nor a service response nor audience redaction.
Start with the request, not the tone
Microsoft explicitly recommends descriptive, action-oriented subjects, stating the requested action in the subject when action is required, and changing the subject when the conversation topic changes. It also recommends putting action items or questions on separate lines so they stand out. [1] These are useful checks for a message to one colleague: identify the work, name the action and make the request easy to find again in the body.
“Quick” does not explain what needs reviewing. “Important” does not identify the document. Before choosing either word, write down the actual task. Is the colleague checking positions in a layout, approving the whole workshop plan or merely receiving an update? Those are different requests. A subject should not quietly promote a narrow check into approval of an entire document.
GOV.UK’s service-content guidance advises tailoring subjects to the actual subject matter rather than using generic wording. It says to get important information into the first sentence, remembers that email subjects are often shortened, and calls for clear instructions and deadlines. [2] Adapted here to an ordinary internal email, that supports putting the useful action and document near the front and repeating the precise request in the opening. This adaptation does not turn GOV.UK’s government-domain, permission or legal rules into universal business policy.
Use the proposed MAJLS review card
Prepare the card before polishing the message. It records what the wording is allowed to say, not permission to send anything.
Purpose: What work needs attention, and what answer would be useful?
One action owner: Who is being asked to respond? Keep this separate from the person approving the draft.
Source of timing: Where does any proposed due date come from? If the brief supplies none, record “not supplied” rather than guessing from a meeting date or the sender’s preference.
Proposed subject: Name the action and specific work. Remove introductory filler that could displace useful words when the subject is shortened.
Matching opening: Address the colleague, identify the exact check and say how to respond. Keep background after this instruction.
Unresolved question: Record anything the sender must settle, such as the timing or which document version the recipient should use.
The card can expose a missing fact without forcing every field into the subject. A missing deadline is a question for the coordinator; it is not an invitation to add “today.”
Filled example
This is a synthetic illustration, not an actual MAJLS exchange. Omar is the human workshop coordinator. Lina is the colleague asked to review a room-layout draft. The source brief asks her to check whether the entrance and materials table are correctly located. It supplies no due date.
Purpose: Obtain corrections to the entrance and materials-table positions, not approval of the complete workshop.
One action owner: Lina.
Source of timing: The source brief gives no due date. Timing disposition: not supplied. Do not add “urgent,” “today” or an invented deadline.
Original subject: “Quick question”.
Proposed subject: “Review the workshop room layout”.
Proposed opening: “Lina, please check the entrance and materials-table positions in the room-layout draft and reply with any corrections. Omar will confirm when the review is needed.”
Unresolved question: When does Omar need the review? Omar must confirm that before a deadline can be added.
The opening narrows the broad word “review” to the requested positions and identifies the expected response. It does not ask Lina to redesign the room, approve catering or accept ownership of the workshop. These drafts have not been sent, opened, accepted or tested with users.
Separate information from changed scope
Use “Workshop room layout: updated draft for information” only when no response is actually requested. That FYI-only subject cannot honestly introduce a body that asks Lina to check positions and reply. If a response is needed, keep the action subject.
A new catering question also needs its own descriptive subject, such as “Confirm the workshop catering requirements,” when that accurately describes the new request. Do not leave a room-layout review subject unchanged while switching the body to catering. This applies Microsoft’s topic-change advice without implying that a new topic authorizes a new recipient or additional work. [1]
Checklist
- Compare the subject with the brief: does it name the actual document and requested action, rather than merely saying “question” or “update”?
- Read the opening beside the subject: do both request the same work from the same colleague?
- Trace any due date or urgency label to confirmed timing; leave unsupported timing out and flag it for Omar.
- Check an FYI subject against every question in the body; remove the FYI framing if a response is required.
- Give a changed topic a descriptive subject instead of concealing it inside an old request.
Keep sending authority separate
Omar approves the final message wording before anyone sends it. An assistant may prepare the draft and flag a missing due date, but may not invent urgency, change recipients or send on the strength of the review card.
For your next internal review request, place the proposed subject and opening beside the source brief. Circle any timing claim the brief does not support, then take that question to the coordinator before final wording approval.
