Capabilities

Direction states and outcomes

A requirement is closed because someone decided to close it.

Draft, Active, In review, Satisfied and Closed, with documented cancellation and reopening paths.

How it works

The principal progression is Draft to Active, In review, Satisfied and Closed. Activation requires a decision point, and satisfaction requires no outstanding information gaps. Content or owner changes during review return the requirement to Active.

Boundaries

Closing and reopening are explicit retained decisions. The application records the actual state rather than inferring satisfaction from activity elsewhere in the lifecycle.

Direction states and outcomes

Element

Direction

Versioning

Retained reasons

Human decision

Recorded decision

Status

Implemented

Discuss this workflow

Related capabilities

Browse all capabilities

Requirements

Direction

·

Current grants

Record the intelligence question, the decision it supports, priority, owner, due date and information gaps.

Requirements

Direction

·

Current grants

Record the intelligence question, the decision it supports, priority, owner, due date and information gaps.

Requests for information

Direction

·

Addressed responder

Ask for information already held, with a holdings review and explicit nil, refusal or referral outcomes.

Requests for information

Direction

·

Addressed responder

Ask for information already held, with a holdings review and explicit nil, refusal or referral outcomes.

Requirements

Direction

·

Current grants

Record the intelligence question, the decision it supports, priority, owner, due date and information gaps.

Requests for information

Direction

·

Addressed responder

Ask for information already held, with a holdings review and explicit nil, refusal or referral outcomes.

Browse all capabilities