Review an AI action before it changes work
Check the target, fields and consequences of a proposed action before proceeding.
Review an AI action before it changes work
A useful draft can suggest a next action, but the suggestion still needs checking. A correct task title does not compensate for the wrong Board, person or due date.
This guide is a review checklist, not a promise that every CoBrain action is available in your workroom. Use it whenever an assistant presents a concrete proposal, and use the ordinary module form if you choose to perform the work manually.
Read the proposed change
1. Identify the operation: create a task, edit a record, send a message or arrange a recurring action. Separate these if the proposal combines them.
2. Check the destination. For a task, confirm the workroom and Board. For a message, confirm the actual recipients—not just a vague “team.”
3. Compare the proposed fields with your request: title, description, source version, date, initial status and responsibility. Read default values too.
4. Look for extra effects. Assignment, notification, external sending and recurrence should not be added merely because they seem convenient.
5. Decide whether the proposal is ready. Correct known wrong details; ask for missing information rather than letting the assistant guess.
If you use the manual task route
The Board route is Create New → New Task. Select the Board, enter the task details and use Create Task for a new record. Editing an existing task uses Update Task instead.
Before saving, search for an existing matching task. After saving, find that exact task again and check its fields.
Your result is a deliberate, understandable action—not just approval of a confident-looking paragraph. If an earlier automatic attempt might already have created the task, check the Board before making a manual replacement. Otherwise you can create a duplicate even when the manual form is correct.
Continue learning
In this series: Work with CoBrain — guide 5 of 7.
Turn what you learned into the way the team works.
Mark this lesson complete once the workflow exists in your workspace—not simply when you reach the bottom.