Draft a short reply before deciding whether to send it
Published · Updated · Sources checked 2026-11-06
Draft a short reply in your own document, check the question asked and separate writing from the decision to send. Includes a worked example.
The example below treats a reply as a drafting task: get the words into a usable shape first, then make a separate decision about what to do next. It does not imply that Lumahari sends email.
Frame the task as one concrete reply
Suppose a colleague asks:
Could you send me the revised outline by Friday? If not, let me know today so I can reorganize the schedule.
Instead of beginning with a broad task such as “Handle the project,” enter one specific task in the task field:
Draft a two-sentence reply to the outline request, including whether I can send the revised outline by Friday.
The smallest-action field can hold the next physical step rather than the entire desired outcome. For this example, choose:
Write one opening sentence that answers “Can you send it by Friday?”
There are several reasonable choices, depending on what is actually true:
- If the outline will be ready: “Yes, I can send you the revised outline by Friday.”
- If it will not be ready: “I can’t send the revised outline by Friday, but I can send it by Monday.”
- If the deadline is uncertain: “I’m checking whether I can finish the revised outline by Friday, and I’ll let you know today.”
The smallest action should match the current reality. Do not choose “Confirm I can send it by Friday” if that has not been established. A smaller and safer step might be:
Check the current outline deadline, then write the first sentence.
Once the first sentence exists, the second sentence can address the consequence. If the colleague needs to reorganize the schedule today, the second sentence could be:
If Friday does not work, I’ll send you a revised date by the end of the day.
Build the two-sentence draft
After completing the smallest action, assemble a rough two-sentence reply. For example:
I can send you the revised outline by Friday. If anything changes before then, I’ll let you know by the end of the day so you can adjust the schedule.
A second possible draft, when Friday is not possible, could be:
I can’t send the revised outline by Friday, but I can send it by Monday. I’ll confirm that timing today so you can adjust the schedule if needed.
If the colleague’s question has several parts, list them in the task field before writing. For example:
Draft a two-sentence reply that says whether the outline can be sent by Friday and when I will confirm.
Check that the draft answers the question asked
Review the reply against the original request rather than against what you wish the request had said. Use a short check:
- Does the first sentence answer whether the revised outline can be sent by Friday?
- If the answer is no, does it give a workable alternative?
- Does the second sentence explain when there will be confirmation?
- Is every statement something you can stand behind?
- Can the reply be shortened without removing a required answer?
Separate the draft from the sending decision
When the draft is ready, stop drafting. Reading it again to hunt for the perfect phrase can turn a bounded task into an open-ended one.
Make a separate decision:
The draft is complete. Review it once, then decide separately whether to send it using my usual method.
This wording keeps two activities distinct. Write the full reply in your own document; Lumahari holds the short planning instruction. Sending, if appropriate, is a later choice outside the drafting task. Lumahari does not send email, make calls, or read files, so the guide does not treat any reply as already delivered.
Before deciding, check three practical points:
- Accuracy: Does the stated date match the current plan?
- Completeness: Does the reply answer the request in two sentences?
- Intent: Do you currently want to send this reply, revise it, or leave it as a draft?
Set a stopping point and restart cleanly
A short stopping point prevents one reply from consuming the whole day. For this task, use:
Stop after the draft is checked. If I reopen this later, start with reviewing the two sentences and the requested deadline.
If you use the optional 2-, 5-, or 10-minute timer, set it only for the drafting interval. The timer supports start, pause, and reset, and it makes no sound. When it ends, do not immediately launch a larger communication task. Instead, assess the draft:
- If it answers the request, stop.
- If it is missing the date, fill in that gap.
- If the facts are unresolved, write the one check needed to resolve them.
- If it has become irrelevant, stop without polishing it.
For a restart note copied to your own document, use:
Resume: read the original request, confirm the Friday answer, review the two-sentence draft, then choose separately whether to send it.
This note names the request, the key fact, the draft and the next decision. Copy it outside the temporary page before leaving.
Using the task fields
Enter one activity and one smallest action, up to 200 characters each, then select Focus on this step. Both inputs are required. Park a thought holds up to 3,000 characters. Clear thoughts removes that whole area after confirmation. Choose a different step lets you edit the current instruction; there is no task history.
The task starter keeps entries only in the current page’s memory. Refreshing or leaving clears them. Copy lasting notes elsewhere before leaving.
For a related next step, see how to start a first paragraph and leave an editing note and how to write a clear task handoff note. Find more examples in the task initiation guide hub.
Sources
General information, not a diagnosis or personalized treatment advice.