← All documentation

Tasks

Tasks are the concrete work that closes your findings — the "what we're doing about it" an auditor expects to see tracked.

Creating tasks

  • From a finding, use Add a task (or let Watney draft tasks from the finding's requirement and AI evaluation). Tasks created this way link back to the finding.
  • Standalone tasks can be created from the Tasks page with New task.
  • From an open assessment, Gaps so far lists each question answered No or Partially, and Create task raises a task for it; when the assessment is completed, the finding raised for that answer takes the task.
  • From an incident, an organization admin uses Add a corrective action; the task links back to the incident, and an existing task can be linked to an incident (or unlinked) from its own page.

Each task has a title, description (steps + evidence to collect), an assignee, a due date, and a priority.

Tracking & status

  • Status: open → in progress → completed (or deferred). Overdue tasks are flagged on the list and on Home.
  • Reminders: assignees get periodic reminder emails until a task is done.
  • Approval (optional): if a task requires approval, marking it complete sends it for an approver's review before it closes. Approvers see an "awaiting approval" count, and the task shows how long it's been waiting. If a submitted task sits unapproved past the 5-day SLA, the org's approvers get an escalation notification (re-sent at most weekly until it's actioned).

Who sees which tasks

Administrators see and work every task. A contributor's list opens on My tasks, the tasks assigned to them; Everyone's shows the rest of the organization's tasks so the team can see what is in hand, read-only: a contributor updates and opens only the tasks assigned to them. An incident's corrective actions appear only to administrators and to the person each is assigned to, because a corrective action can describe the incident.

Only an administrator can delete a task, because a deleted task is gone for good and the task list is the record that each gap was followed up. A contributor who should not do a task marks it Deferred instead, which keeps it on the list with its history.

From task back to finding

A task's detail page shows the linked finding so you can jump back to the gap it closes. Closing all of a finding's tasks — with evidence — is how you resolve the finding.