You open a message between two tasks. The question makes sense, but you need a file before answering. You intend to check later. The next time you open the inbox, the same decision starts again: what did the person need, where is the material and when will you deal with it?
Reading a message, preparing a reply and sending it are three different actions. They do not always have to happen consecutively. When you separate them, the unfinished reply needs a visible next step.
AuDHD is a community term for co-occurring autism and ADHD, not a separate diagnosis. This article offers editorial organisation suggestions and a fictional example. It does not describe everyone with AuDHD or present a personal success story. See What is AuDHD? for context.
Checking is not yet replying
Opening the inbox first tells you whether something has arrived. A reply may require additional work: reading documents, obtaining a decision or checking a date. Deal with messages leaves those differences unclear.
The NIMH overview of adult ADHD describes possible difficulties with organisation and time management. The National Autistic Society discusses written lists and planned times as possible organisational supports. These sources provide general background, not evidence that the following process or an app is effective.
This article concerns incoming messages. Turning meeting notes into tasks covers the period after a meeting. Use Check before you commit when a message asks you to take on new work.
Clarify response expectations first
Before trying fixed checking times, clarify the requirements around you. Which channels are used? What is actually urgent? Which response times have been agreed? A support shift needs a different arrangement from a project without constant availability.
Choose checking and replying times within those agreements. If there is an agreed urgent channel, it needs appropriate coverage. Do not switch notifications off indiscriminately if that interrupts a responsibility or necessary availability. Discussing channel arrangements does not require disclosing personal health information.
Possible wording: “I check this channel after the team meeting. For requests that need attention beforehand, we use the agreed urgent channel.” This is a proposal to discuss, not a unilateral change to existing obligations.
Record a decision when reading
Rather than asking only whether you can reply, identify the action the message requires:
- No reply needed: Store the information if you need it later.
- Ready to answer now: Answer the actual question if it fits the current work block.
- Preparation needed: Record the material, check or decision as the next action.
- Clarification needed: Name the unclear point before starting work on assumptions.
Marking a message unread can be a visible cue, but it does not yet describe an action. Adding check the figure in the project file explains why the reply remains open. The status should fit your existing tool; you do not need a new app or lots of folders.
A reply note to copy
For a message that needs preparation, these four lines can be enough:
Message and question: Which thread, which specific question?
Next action: What do I check or clarify first?
Material or dependency: Where is it, who needs to confirm something?
Reply deadline or review point: What is agreed, when do I check again?
Record a clear reference to the thread rather than copying the whole conversation. Keep confidential information in approved tools. A review time you choose is not a confirmed reply deadline. If you cannot answer yet, record the missing requirement explicitly.
Paper or an existing document is enough. The free interruption note already has fields for the current state, action and material. Use it as a starting point if useful, rather than creating an extra storage location you never check.
A fictional example: read, but not ready to send
Sam asks Alex whether the draft will be ready for a joint review on Thursday. Alex still needs confirmation of the scope. Reply to Sam hides that dependency. Alex records instead:
- Thread: Sam’s message about the draft; the question concerns availability on Thursday.
- First action: Clarify the outstanding scope with the responsible person.
- Material: Draft in the approved project folder; scope not yet confirmed.
- Review point: Check after today’s team meeting; discuss any effect on Thursday with Sam in good time.
If it fits the agreement, Alex could send an interim message: “The scope is still open. I will check after the team meeting and follow up about the date.” This does not confirm that the draft will be finished on Thursday. Even a short update must not contain a commitment that remains unresolved.
Plan reply time separately from the actual work
A message can trigger a project. The reply itself is not then the whole project. If answering requires checking figures, plan that check as work. The reply window afterwards is for writing, checking and sending the response.
Begin the reply window with the recorded action and relevant thread. Check recipients, the question, attachments and agreed information. Sent does not automatically mean mutually confirmed. If approval is needed, keep its status visible. Replanning unfinished tasks explores dependencies further.
If the answer will not fit the agreed time, discuss the change early. Do not merely move your own reminder date. For a direct interruption, resuming after an interruption explains how to preserve the working state.
After a pause, avoid treating every inbox item as new work
After a missed reply window, check agreed deadlines and messages with a concrete consequence first. Old information, duplicate threads and questions already resolved need not become new tasks again. Update the actual status before adding reminders.
If the open work exceeds the available time, clarify priorities and expectations. A personal process cannot replace adequate staffing or unrealistic response requirements. At the end of the workday, record the next review points without closing every open conversation.
Test a process that fits the channel
Try the reply note in one manageable channel first. At the next check, can you find the right thread? Is the action possible? Are dependencies and agreed deadlines visible? Add the missing detail rather than reorganising every inbox.
AuDHD at work provides wider planning context. The note itself needs no purchase. It is an organisation aid, not treatment or a guarantee of constant availability. The practical question is: What still needs to happen between this message and an honest, useful reply?