Tasks

Tasks in the app is /tasks.

Tasks are how you keep the program operational. If a control has no owner and no recurring task, it tends to degrade.

The page does not maintain a separate task database. It assembles the current user's work from source records they own, are assigned, or must approve. Current task groups are policies, risks, evidence, control implementations, vendors, and risk treatments. Each row links back to the source record.

Use this when…

• a control needs a recurring check (access reviews, restore tests, vendor reviews)
• a finding needs remediation and tracking
• you want to avoid “audit-mode crunch”

Recommended workflow

• Create tasks for:
  • recurring controls (monthly/quarterly)
  • evidence refresh (e.g. “upload policy approval record for Q2”)
  • remediation and follow-ups from internal audits
• Assign a single owner and a due date.
• Link tasks to the control/evidence/risk they relate to (so context stays attached).

How to use /tasks

Search by title/description and filter by type or status. The table shows task, source type, source status, priority where available, assignment, due date, and a link to the record. Complete or update the work on the linked page; Tasks reflects that state when it reloads.

Because Tasks is an aggregation, a missing row can mean no record is assigned to you—not that the organization has no outstanding work. Managers should review the underlying registers and unowned-record filters in addition to their personal task view.

Use due dates and assignment fields on the source entity consistently. Avoid creating parallel reminders that have no link to the control, evidence, risk, vendor, or treatment whose state needs to change.

Compliance value

The page helps demonstrate accountability and follow-through, especially for recurring reviews, remediation, approvals, and risk treatment. It does not prove completion by itself; the source status, change history, and linked evidence carry that proof.