> For the complete documentation index, see [llms.txt](https://docs.cortex.aic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortex.aic.io/workflow-guides/direction/quick-direction.md).

# Quick Direction

**Open this area:** In the CORTEX menu, select **Intelligence cycle → Direction**.

A short guide for the person responsible for stating the question and deciding when it has been answered.

**Who uses this:** Requirement owner.\
**Open in CORTEX:** `/direction`.\
**In-app guide:** `/help?topic=quick-direction`.

**Expected result:** A saved requirement names the decision, the information needed, and its owner.

## Before you start

* Select the right workspace. You need Direction write access to create a requirement.
* Have one real decision or question in mind. Know who needs the answer and when.

## What to do

{% stepper %}
{% step %}

### Check for an existing question

Open Direction. Type a few words into **Find a requirement** and click **Find requirements**. Open a matching row before creating anything new.

Changing the search box alone does not run a search.
{% endstep %}

{% step %}

### Start a requirement

If this is a new top-level question, click **Create requirement**.

If it sits under an existing question, open that requirement and click **Add information need**.

These start a draft; they do not task anyone to collect information.
{% endstep %}

{% step %}

### Write the question

Enter the question and required details shown by the guide, including the decision point, priority, due date, and handling where relevant.

Click **Continue** to move through the steps. The missing-input list tells you what must be fixed before you can continue.
{% endstep %}

{% step %}

### Save and check

On **Review**, check the full question and click **Create requirement**.

If you only have the basic top-level question ready, **Create basic draft** saves a Draft that you can complete later.

Open the saved record and check its status and owner.
{% endstep %}

{% step %}

### Make the next decision

When the decision point is recorded, choose **Active** under **Change status**, explain why, then click **Update status**.

If another eligible person will own the question, use **Find eligible owner**, select the exact account, give a reason, and **Assign owner**.

Creating or assigning a requirement does not grant that person access.
{% endstep %}
{% endstepper %}

## Check the result

* Does the question support a real decision?
* Is the owner and due date right?
* Did the requirement actually save in the intended workspace?

## If you get stuck

<details>

<summary>Why can I not see Create requirement?</summary>

Select a workspace and ask its Manager to check your Direction write access. A read-only view does not mean no requirements exist.

</details>

<details>

<summary>Why can I not choose Active?</summary>

Open the current requirement and record a decision point first. The **Change status** area shows only valid next states and names missing prerequisites.

</details>

<details>

<summary>Why did my change fail or return to Active?</summary>

Reload the current record and compare its latest version. Another edit may have caused a conflict; editing during review also sends the question back to Active for fresh review.

</details>

## Responsibility and limits

* The requirement owner decides whether the answer is sufficient. Collection results and feedback do not mark it satisfied automatically.

**Reference and scope:** For detailed rules and doctrine, open [Define and manage an intelligence requirement](/workflow-guides/direction/requirements.md).

**Related workflows:** [Define and manage an intelligence requirement](/workflow-guides/direction/requirements.md); [Start here: plan a collection task and record a result](/workflow-guides/collection/quick-collection.md).