Separate a commitment from a possible next step
An email saying you will send a document is different from an idea that might be worth discussing. A useful task list should make that distinction. I work through examples with you so suggestions do not quietly become obligations.
A due date also needs a basis. If a message does not include one, the assistant can ask for a date or leave it unset. Inventing a deadline makes the list harder to trust.
Put the list where you already look
The destination might be Google Tasks, a printed daily plan or an existing task system. The first choice is the habit you will maintain. Adding a second system that needs manual checking can create another place for work to disappear.
- Record the person, commitment and source together.
- Distinguish your next action from waiting on someone else.
- Agree how completed and postponed tasks leave the active list.
Make exceptions easy to correct
Two emails can refer to the same follow-up. A later reply can change the date or cancel the request. We test those cases before expanding the setup, and agree what happens when the assistant is unsure.
A useful review is whether the list reflects your actual commitments. Where you want to estimate its value, we can use your own record of missed follow-ups or time spent rebuilding the list.
Illustrative example
Example first project: documents you promised to send
An illustrative first version tracks one clear category instead of trying to recognise every possible commitment.
- Choose messages containing an agreed document handover.
- Prepare a task with the recipient, document and link to the message.
- Check the tasks together and define how completed handovers are recorded.
What we would agree first: A reminder does not confirm that a document is correct or authorised for sharing. You review the document and decide when to send it.
Questions you may have
Will the assistant contact clients for me?
The first version can simply prepare your list. Drafting or sending client messages is a separate capability with its own permissions and review rules.
Can it work with the task list I already use?
That is the starting preference. I check whether the existing system supports a suitable connection before proposing a change.
How do we avoid duplicate tasks?
We agree how tasks are matched to their source messages and test replies, changed commitments and completed items. You need a clear way to correct the list.