Requirements, gaps & tasks

The day-to-day loop that keeps your compliance picture current.

Requirements

A requirement is a specific, actionable obligation under a control. Every requirement has:

• Status — not started, in progress, met, gap, or not applicable.
• Priority — low, medium, high, critical.
• Owner — optional, set to a team member.
• Due date — optional.
• Evidence — zero or more pieces of proof.
• Gaps — zero or more open issues.

Evidence

Evidence is how you prove a requirement is met. It can be a link to a document, a pull request URL, a dashboard, or free-text notes. Evidence is timestamped so you know when it was captured.

Treat evidence as point-in-time proof. When the thing it refers to changes, capture fresh evidence rather than editing the old record.

Gaps

A gap is a specific, open shortfall on a requirement. Unlike status (which summarises overall state), gaps capture concrete problems — each with a severity, a recommendation, and an optional target date.

Creating the first gap on a requirement automatically moves the requirement's status to gap.

Tasks

Tasks are concrete units of work — typically created to close a gap or stand up a new control. Each task has a status, priority, optional assignee, and optional due date, and can be linked to a requirement or gap.

From any gap you can click Create task to spin up a task pre-populated with the gap's recommendation as a description, the severity as a priority, and the target date as a due date.