> 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/collection/quick-collection.md).

# Quick Collection

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

A short guide for a planner and the assigned collector working from a requirement.

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

**Expected result:** A plan, assigned task and actual observation are retained against the question they support.

## Before you start

* The planner needs Collection write access and a visible Draft or Active requirement that is not an RFI.
* A proposed task needs a current authorised source, an eligible collector, a real time window and capacity. The collector needs their own execute access.

## What to do

{% stepper %}
{% step %}

## Create the plan

From Direction choose Create collection plan, or select exact top-level and child questions in the Requirement tree.

One question opens the focused editor; 2–20 open the grouped editor.

Give the separate plan a title and objective, review the current question versions and handling, then Create collection plan.

This saves a Draft plan.
{% endstep %}

{% step %}

## Propose a task

Open the plan.

Under Collection tasks, use Find sources, select the authorised source and eligible collector, then complete Window and risks.

Click Continue, review the task and click Propose collection task.

This records a Proposed task, not an observation.
{% endstep %}

{% step %}

## Prepare and start

Click Plan capacity, review outcomes or retask and arrange the required approved capacity reservation.

Beside Edit collection plan choose Change status, select Active, enter a reason and Save status change.

The assigned collector selects their task, chooses Collecting under Task workflow, gives a reason and clicks Apply task transition.
{% endstep %}

{% step %}

## Record what happened

While the task is Collecting, the assigned collector enters Observed information, the actual acquisition time and the requested evaluation.

Click Continue through Observation, Evaluation and Review result, then Save observed result.

This retains what was reported; it does not accept the observation as an analytical fact.
{% endstep %}

{% step %}

## Finish the attempt

Check the saved result on the selected task.

The assigned collector can choose Completed under Task workflow and click Apply task transition with a reason.

If this is the final open task, the same save completes the Active plan; if every task was cancelled, the plan is cancelled instead. Failed tasking leaves the plan Active.

Review capacity and outcomes before any new attempt.

Finishing Collection does not satisfy the Direction requirement.
{% endstep %}
{% endstepper %}

## Check the result

* Does this task answer the stated question?
* Are source authority, collector and time window current?
* Is the result the actual observation from this attempt?

## If you get stuck

<details>

<summary>Why can I not propose the task?</summary>

Read the missing-input list. Check the source's current authority for this exact question and window, select an eligible collector and complete the required risks and reason.

</details>

<details>

<summary>Why can I not start or finish it?</summary>

Check that the plan is Active, the task is assigned to you and capacity was reserved. Completion also needs a saved result for this attempt.

</details>

<details>

<summary>Why did the source or plan disappear?</summary>

A temporary list failure keeps the last confirmed page for retry. Loss of current access clears protected results; ask the workspace Manager to check access rather than assuming the records were deleted.

</details>

## Responsibility and limits

* The planner authorises and resources the task.
* The assigned collector reports the observation and its limitations; analytical acceptance happens later.

**Reference and scope:** For source authority, capacity and evaluation rules, open Plan collection and record observed results below.

**Related workflows:** [Plan collection and record observed results](broken://pages/9f06f9da6d83f0fc97ab65193a28eb4d7165788c); [Start here: turn evidence into an assessment](file:///7397340/analyse/quick-analyse.md); [Record authority before new source use](broken://pages/3ea597edb1748357b6a7dc5c5beba4fb3e2f9c10).