Tasks, review, and sign-off
Understand how tasks move through Mission Control and when review, revision, and human sign-off happen.
Mission Control keeps work visible by moving tasks through clear stages rather than hiding status inside agent conversations.
Task stages at a glance
| Stage | What it means |
|---|---|
| Inbox | the task exists but is not owned yet |
| Assigned | the task has been routed to a specific agent |
| In Progress | the agent is actively working on it |
| Review | the work is waiting for approval or sign-off |
| Revision | changes were requested before the task can be completed |
| Done | the task is complete |
| Blocked | work cannot continue until something changes |
What happens in review
Review is the checkpoint between execution and completion.
In plain language, this is where ClawControl asks: Is the work ready to move forward?
Depending on the task, review can include:
- LEAD approval
- human sign-off
- a revision request that sends the work back for changes
Human sign-off explained simply
Human sign-off is for work that should not be treated as complete until a person approves it.
That is useful for things like:
- customer-facing output
- high-risk operational changes
- work that needs business approval
- any result where a final human decision still matters
If sign-off is required, the task can move into review and wait for a human to approve it or request revision.
Approval and sign-off are different
ClawControl separates internal workflow approval from final human sign-off.
- Approval is usually the system's coordination step, often handled through a LEAD workflow.
- Sign-off is the final human acceptance step when the task explicitly requires it.
That means a task can be approved by the workflow and still wait for a person before it becomes done.
What revision does
If review finds problems, the task moves to Revision instead of pretending the work is finished.
This helps teams keep the feedback loop visible. The assigned agent can then rework the task with clearer direction.
What blocked means
Blocked should be used when work cannot continue because something external is missing.
Common reasons include:
- missing access
- unanswered questions
- dependency delays
- environment problems
Blocked work is not failed work. It simply needs input before it can resume.
Good task workflow habits
- write tasks with a clear outcome, not just a topic
- use required expertise so the right specialists see the work
- turn on sign-off only when a real human approval step is needed
- use revision instead of informal side comments when work should be redone
- treat blocked status as a signal to unblock, not as a dead end