> 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/lifecycle/direction.md).
# Direction
Direction starts the intelligence cycle. Use it to state what you need to know, why you need an answer, and when you need it. A requirement gives Collection, Analyse, and Products a clear purpose.
## Before you start
{% stepper %}
{% step %}
## Select the correct workspace
Sign in and select the correct workspace. In the menu, select **Operations & workspaces → Choose workspace**, then select **Open workspace** on the correct card.
{% endstep %}
{% step %}
## Check workspace handling
Check the workspace purpose and protective marking. A similar workspace name does not mean that you can use it for the same task.
{% endstep %}
{% step %}
## Confirm Direction access
Make sure you have Direction access. The **Create requirement** action appears only when a workspace is selected and you have Direction write permission. If it is absent, ask a workspace Manager to check your access.
{% endstep %}
{% endstepper %}
## Find existing work
{% stepper %}
{% step %}
## Open Direction
In the menu, select **Intelligence cycle → Direction**.
{% endstep %}
{% step %}
## Review current requirements
Read the requirement cards and their due dates. The page puts urgent work first within the results you can see. The counts describe your current page and access.
{% endstep %}
{% step %}
## Search for a known question
To find a known question, enter words from its title, question, or decision in **Find a requirement**. You can also set **Status**.
{% endstep %}
{% step %}
## Apply the filters
Select **Find requirements**. Editing a filter alone does not change the results.
{% endstep %}
{% step %}
## Open the requirement
Select **Review requirement** on the correct card. You can also select **Browse requirement tree** to see related questions.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
Check for an existing requirement before you create a new one. An empty result means that no matching requirement is visible under your current filters and access. It does not prove that no requirement exists elsewhere.
{% endhint %}
## Create a requirement
{% stepper %}
{% step %}
## Start the requirement
On **Direction**, select **Create requirement**. The form has three steps: **Question**, **Decision and handling**, and **Review**.
{% endstep %}
{% step %}
## Choose the requirement type
In **Question**, choose **Requirement type**. Use the type that matches the work. For a normal new question, create a top-level requirement. An information need under another requirement must have an eligible parent.
{% endstep %}
{% step %}
## Enter a title
Enter **Requirement title**. Use 3–200 characters. Give the requirement a name that people can recognise in lists.
{% endstep %}
{% step %}
## Describe the question and context
Enter **Question and context**. State the question in plain words. Explain what is known and what remains unknown. This field is optional for a basic draft, but complete it before you ask others to act on the question.
{% endstep %}
{% step %}
## Set decision and handling details
Select **Continue** to reach **Decision and handling**. Set **Priority** and, when needed, **Due date (UTC)**. The due date is measured from the start of the selected UTC date.
{% endstep %}
{% step %}
## Record the decision supported
Enter **Decision supported**. Say what decision an answer will help someone make.
{% endstep %}
{% step %}
## Record information gaps
Enter **Information gaps**, one per line. Make each gap a question that someone can check. You must resolve recorded gaps before the requirement can be marked satisfied.
{% endstep %}
{% step %}
## Review handling restrictions
Review **Protective marking**, **Need-to-know compartments**, and **Caveats and handling instructions**. Use the full required marking. If this is a child requirement, keep its inherited restrictions.
{% endstep %}
{% step %}
## Review and create
Select **Continue**, read **Review before creating**, and select **Create requirement**. This final action saves one Draft requirement. It does not activate the requirement or approve collection.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
If you only have enough information to record the initial question, use **Create basic draft** in the form. This saves a Draft that you can complete later. The ordinary **Back** and **Cancel** actions do not save a partial requirement.
{% endhint %}
## Assign the owner and activate the work
{% stepper %}
{% step %}
## Check the saved requirement
Open the new requirement and check its saved version.
{% endstep %}
{% step %}
## Assign an owner
If another person must own it and you have assignment authority, open **Assign requirement owner**. Enter **Owner's exact email address** and select **Find eligible owner**.
{% endstep %}
{% step %}
## Confirm the owner
Select the correct **Eligible owner**. Enter **Assignment rationale (10–500 characters)** and select **Assign owner**. Assignment records the owner and can queue a notification. It does not grant the person access and does not approve the work.
{% endstep %}
{% step %}
## Change the status
To change the state, open **Change status**. Select a valid **New status**, enter **Reason for status change (10–500 characters)**, and select **Update status**.
{% endstep %}
{% step %}
## Resolve activation blocks
If activation is blocked, read the **Before changing status** list. A decision point can be required before activation. Complete the named item and try again.
{% endstep %}
{% step %}
## Create or view collection plans
From **Requirement tasks**, use **Create collection plan** when the question needs new collection. Use **View collection plans** to inspect work already linked to the question.
{% endstep %}
{% endstepper %}
The task menu also includes **Add information need** for eligible Draft or Active non-RFI requirements. A child need keeps the parent's handling restrictions. Use a Request for Information (RFI) when you ask an eligible person to check existing holdings; use a collection plan for new collection.
## Review the answer and close the question
Return to the requirement as Collection and Analyse progress. Read the current question, information gaps, linked work, owner, and version history. The requirement owner must assess whether the actual answer meets the need. A completed collection plan or a released product does not make this decision for them.
Use **Change status** to move through the valid next states. Before you mark the requirement satisfied, resolve every recorded information gap and review the answer. Enter a reason for each transition. If the question changes, use **Requirement tasks → Edit requirement** and save a new version with a reason. Changes made during review can return the requirement to Active, so arrange a fresh review of the changed question.
## If you cannot continue
Create requirement is absent
Confirm the selected workspace and ask its Manager to check Direction write access.
A parent or owner is missing
Search for the exact record or email. The person and parent must be eligible for this workspace and handling.
A status choice is absent
The form shows only valid next states. Read the prerequisite message beside **Change status**.
A save reports a conflict
Select **Refresh requirement**, inspect the newer version, and apply your intended change to that version.
The browser loses connection
Reopen the requirement and confirm its latest saved version before you submit again. Text that is still in a form is not proof of a saved change.
Continue with [Collection](/lifecycle/collection.md) when the requirement needs authorised new information.