A project can look busy while an important promise disappears into a chat. “Prepare a proposal” is work; “send the proposal to the client by Friday” is also a commitment to a person. Recording that distinction helps you follow up without inventing a promise later.
Write the agreement, not a guess
Record the person, what was agreed, who owes it and the due date if one was actually set. If the date or responsible person is unclear, check the conversation before recording it. A reminder is a prompt to review, not evidence that the other person accepted a deadline.
The APX task guide describes tasks and commitments on the shared board. Commitments can represent what you owe someone or what they owe you. Read the task discussion and the actual artifact before declaring it complete.
Review the outcome
At the agreed time, inspect the email, delivery or other evidence and record the outcome according to what happened. If the other person agrees to a new date, record the renegotiation rather than silently moving the old deadline. If nothing was agreed, avoid marking the commitment as kept or released.
A clear board reduces forgotten follow-ups, but it does not send a message or deliver a file merely because a task exists. Confirm the external result separately.
Sources
More articles
How to let an AI agent work on a site without sharing your password
A practical guide to browser handoffs, sessions and safer sign-in for AI agents.
Can an AI agent work from WhatsApp or Telegram? What to check first
Plan a chat-based agent workflow around identity, approval, delivery and privacy before connecting a messaging app.
Why an AI agent cannot use a connected tool: an MCP checklist
Troubleshoot an MCP connection in stages: scope, approval, sign-in, tool discovery and a safe test.