Running
Comments
Every task on a checklist has a comment box. Open the checklist, find the task, and select Add a comment. Tasks on My work have the same box: expand one and it is under the buttons.
Anyone who can see the checklist can comment on any task on it. The task does not have to be yours, and it does not have to be open — a task that is blocked, ready, complete or skipped all take comments.
What to write
A comment is for what the workflow never thought to ask about: what you had to work around, why something took as long as it did, who you had to call.
Fields collect the answers the process expects every time. A comment is for the once. If the same remark comes up on every checklist, that is a sign the workflow needs a new field or a better instruction, and not a comment.
What a comment does not do
A comment changes nothing. The task keeps the status it had, nothing waiting on it is unblocked, and no automation fires. To close a task, see Running a checklist.
Comments stay
You cannot edit or delete a comment. If you got something wrong, write a second comment that corrects it. This is the rule the rest of the record follows: a record that people can quietly rewrite is a record nobody can rely on.
Your name and the time go on a comment when you post it. The name is frozen at that moment, so an old comment still reads correctly after somebody changes their name or leaves the team.
Comments are on the checklist page and on My work. When the last task closes, the checklist page becomes the read-only summary, which does not list them yet.
Comments and Claude
Claude reads the comments when it reads a checklist, and it can leave one. Ask it to note something on a task and the comment goes on under your name, exactly as if you had typed it. See Claude and other AI.