Every requirement carries the decision it exists to support.

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

How it works

Direction records the need, question, decision context, priority, due date, ownership and handling, with supported display terminology for intelligence requirement, priority intelligence requirement, specific intelligence requirement, essential element of information and request for information. Content and lifecycle changes are versioned and retain reasons and audit history.

Boundaries

Amendments use expected versions, so a stale edit is reported as a conflict rather than silently overwriting another user’s work. Priority is not command approval, and downstream feedback does not close a requirement automatically.