> 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/collection-plans.md).
# Collection Plans
**Open this area:** In the CORTEX menu, select **Intelligence cycle → Collection**.
Task an eligible collector against a reviewed source, preserve attempts, and evaluate observations separately from source reliability.
**Who uses this:** Requirement owner, Collector, Analyst.\
**Open in CORTEX:** `/collection`.\
**In-app guide:** `/help?topic=collection`.
**Expected result:** A versioned plan links an actual collection attempt and its observed results to the originating requirement.
## Before you start
* Use an accessible Draft or Active non-RFI requirement and current collection planning authority. The plan guide shows whether one appears in current results before entry.
* Prepare an active source with current authority for the exact requirement/version and task window. Source registration begins with name and provenance; assessed reliability and APP evaluation need their own rationale and approved profile.
* Identify an eligible collector and realistic UTC window, risks and mitigations.
## What to do
{% stepper %}
{% step %}
### Register or amend a source
In Sources, select **Apply filters** before paging a changed search or status. The pager uses the last confirmed authorised result, appears only beyond one page, and shows the returned range. A temporary read failure keeps that confirmed page for retry.
If source access is forbidden or unavailable, CORTEX clears protected source rows and paging.
Open a source and use the **Identity**, **Assessment**, **Access**, and **Review** steps.
* Name and provenance are required.
* An assessed JDP grade needs a rationale.
* APP evaluation needs an approved profile, code, and rationale.
* Access restrictions, credential reference, and publication link are optional.
* The final save retains one source revision.
* Amending a source needs a reason and triggers a fresh authority review before new tasking or ingestion.
{% endstep %}
{% step %}
### Create a linked plan
Use **Create collection plan** from the requirement or Collection.
Collection names a requirement when you open its scoped plan list and current Direction access permits it; otherwise the list uses a generic scope without linking or preselecting an unreadable requirement.
Select **Apply filters** before paging a changed search or status. The pager uses the last confirmed authorised result and appears only beyond one page.
An empty result describes the current submitted filters and access; it does not remove retained plans or prove none exist outside that view.
Use **Return to requirement** to review its current state.
**Create plan for this requirement** appears only with current Collection write access and a visible requirement, and carries that requirement into the editor, where Direction and Collection recheck access and handling.
The prerequisite panel shows if an eligible non-RFI requirement appears in the current results.
1. Select one.
2. Complete the required title and objective.
3. Review the draft.
Green steps are ready; red steps list missing input. **Back** preserves the draft; **Cancel** creates nothing.
Select **Create collection plan** only at final confirmation and inspect its retained requirement version.
{% endstep %}
{% step %}
### Plan across several questions
From Direction choose **Create collection plan**, or tick eligible questions in the requirement tree and choose **Create plan for selected requirements**.
The grouped editor shows 2–20 selected Draft or Active non-RFI questions, including child requirements, and their current versions.
* Search and page to add others.
* Remove any that no longer belong.
* Enter one outcome and handling that covers every selection.
* Review, then save the Draft.
A parent does not imply all its children.
New tasks later identify which of the plan's questions they cover and require current source-use authority for each.
{% endstep %}
{% step %}
### Change plan status
On the plan detail page choose **Change status** beside **Edit collection plan** to activate, deliberately cancel, or reopen the plan.
Pick one valid next state, enter a 10–500 character reason, and save.
While the plan is Active, its final task outcome progresses the plan in the same saved version:
* At least one Completed task with every task Completed or Cancelled completes the plan.
* All Cancelled tasks cancel it.
* Failed tasking leaves it Active.
The audit retains the initiating actor and reason.
A completed plan retains its tasks and observations but does not satisfy a Direction requirement. The requirement owner reviews the actual evidence, resolves gaps, and makes a separate satisfaction decision.
Reopening a plan is deliberate and rechecks current linked requirement versions and access.
{% endstep %}
{% step %}
### Group related questions when one effort serves several
From Collection, choose **Plan across requirements**.
Browse all visible Direction matches in pages of 25 or search by title or question. Selected questions stay while you search and change pages.
Only Draft or Active non-RFI questions can be selected, and each unavailable result explains why.
1. Select 2–20 questions.
2. Enter one title, objective, and handling that covers every question.
3. Review and create the Draft.
In its task form all questions start selected; uncheck any outside that task's actual purpose.
Current source-use authority must cover every selected exact version and the full window.
A changed or satisfied question blocks new tasking until a new plan is made.
Option comparison currently addresses one question and is not offered for grouped plans.
{% endstep %}
{% step %}
### Page grouped-plan requirements
In **Plan across requirements**, browse visible Direction matches 25 at a time or enter a title or question and select **Search**.
Edited search remains pending until Search succeeds; **Previous** and **Next** use the last confirmed search.
The pager shows the exact authorised range only when matches span pages.
A temporary failure keeps confirmed matches and selected draft questions for retry.
Lost Direction or Collection access clears protected matches and selected scope.
Searching and paging retain no plan or requirement change.
{% endstep %}
{% step %}
### Propose and allocate the task
In the plan's **Tasks and observations** tab, the prerequisite panel shows collection write authority, exact active source, eligible collector, and the later capacity reservation.
The guided task form has **Source and collector**, **Window and risks**, and **Review task** steps.
Required labels, missing-input lists, and step colours update as you enter data. **Continue** requires each step to be complete. **Back** preserves the draft, and **Clear task draft** discards it.
The final save retains one Proposed task after rechecking the plan, source revision, source-use authority, and collector.
Open **Plan capacity**, review outcomes or retask, and confirm an approved resource reservation before assignment.
{% endstep %}
{% step %}
### Start the authorised attempt
Choose **Change status** beside **Edit collection plan**, select **Active**, enter a reason, and **Save status change** when the plan is ready.
The assigned collector selects the task; focus moves from its table row to the labelled task panel, where its retained source, window, workflow, and observations can be reviewed.
Choose **Collecting** and use **Apply task transition** with a reason.
Recheck source-use authority if the operation is refused.
{% endstep %}
{% step %}
### Record actual reporting
While Collecting, the result panel shows assigned-collector and execute authority, the exact task window, and any conditional APP profile prerequisite.
Use **Observation**, **Evaluation**, and **Review result** steps.
Record:
* What was observed and optional remaining gaps.
* The actual UTC acquisition time within the task window.
* Independent JDP credibility or exact APP evaluation and any required rationale.
Required fields, step status, and missing-input messages update during entry. **Back** preserves the draft; **Clear result draft** removes it.
**Save observed result** retains a new report only after current assignment, window, and evaluation checks; it does not accept a fact or complete the task.
Keep source A–F reliability separate from observation 1–6 credibility.
{% endstep %}
{% step %}
### Finish, reassess, or retask
Complete the task only after a result exists for this attempt.
When no open task remains, the same save completes the Active plan if at least one task completed, or cancels it if every task was cancelled. Failed tasking keeps the plan Active.
Review effectiveness, delays, and gaps, then release its capacity.
A planner can reopen and propose a new attempt with an explicit collector and window, retaining earlier attempts, or reassess an exact old result.
{% endstep %}
{% endstepper %}
## Check the result
* Does the task answer a specific unresolved need?
* Are source revision, authority, and collector eligibility current?
* Is acquisition inside the approved UTC window?
* Are observation and assessment clearly distinguished?
* Does completion refer to the current attempt's actual result?
## If you get stuck
Why did Sources keep or clear the catalogue after an error?
A temporary search or paging failure keeps the last confirmed authorised source rows, submitted filters, and page so you can retry. A changed search or status remains marked until **Apply filters** succeeds.
If Collection reports that source access is forbidden or the scope is no longer available, CORTEX clears protected rows and paging. Refresh legitimate access before retrying.
Browsing, filtering, and retrying do not amend, retire, or delete a retained source.
Why did Collection keep or clear the plan list after an error?
A temporary search or paging failure keeps the last confirmed authorised page, submitted filters, named requirement context, and available creation action so you can retry without mistaking an unconfirmed request for a new result.
A changed search remains marked until **Apply filters** succeeds.
If Collection reports that the scope is forbidden or no longer available, CORTEX clears protected rows, requirement context, and creation actions. Refresh legitimate access before retrying.
Neither outcome edits or deletes retained plans.
Why did the grouped-plan requirement page stay unchanged?
A temporary Direction search or paging failure leaves the last confirmed matches, exact page, and selected draft questions visible. Retry **Search**, **Previous**, or **Next**.
Edited search text is not applied by paging.
If current requirement or Collection access is lost, CORTEX clears protected matches and selected scope; restore authority and start the selection again.
Why cannot I complete the task?
Check that the plan is Active, you are the assigned collector, the task is Collecting, and a result exists for its current attempt.
A result from an earlier attempt cannot satisfy this precondition.
Why did the plan status change with the task?
The final Completed or Cancelled task determines whether an Active plan has collection work left.
The task outcome and terminal plan status are one atomic saved version with your actor and reason. Failed tasking stays Active for review.
This does not mark any linked Direction requirement satisfied; its owner still reviews evidence and gaps separately.
Why is a selected source or collector rejected?
Refresh the displayed source revision and eligible directory result.
Review source-use scope, current requirement version, task window, and current membership; do not replace a restricted source with a weaker marking.
How do I correct credibility after completion?
With collection-management authority, select the exact retained observation and record a reasoned credibility reassessment.
Original reporting remains unchanged, and existing Analysis judgements are not automatically updated.
## Responsibility and limits
* Collectors record what they observed, limitations, and gaps; they do not certify a fact merely by completing a task.
* Planners evaluate collection relevance and source independence. F or 6 means insufficient basis to judge, not automatic lack of value; collection completion does not satisfy Direction.
**Reference and scope:** JDP 2-00 (4th ed.), 3.18–3.21 and 3.39–3.40 inform collection and separate source/information grading. CORTEX supplies the recorded task workflow.
**Related workflows:** [Define and manage an intelligence requirement](file:///7397340/direction/requirements.md); [Record authority before new source use](broken://pages/3ea597edb1748357b6a7dc5c5beba4fb3e2f9c10); [Preserve an original and review processing](broken://pages/0013ee41e1cac5e736e1d2d9f16ed6ce5675a80c).