> 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/menu-areas/police-and-defence/police-tasking-products.md).

# Police Tasking Products

**Open this area:** In the CORTEX menu, select **Police operations → Police tasking**.

Retain attributable tasking decisions, versioned requirement control and locally adopted policing products.

**Who uses this:** Requirement owner, Analyst, Reviewer.\
**Open in CORTEX:** `/direction/tasking`.\
**In-app guide:** `/help?topic=police-tasking-products`.

**Expected result:** A review or strategy preserves exact source versions, while each policing draft makes consultation, gaps, refresh and independent review visible.

## Before you start

* Open an assigned workspace. Retained tasking reviews are readable with Direction read access; recording one requires Direction transition authority and current access to its source material.
* For a policing product, select an effective approved profile adopted for the relevant local jurisdiction. Retain local references outside CORTEX where restricted policy or layouts are required.

## What to do

{% stepper %}
{% step %}

## Record the review

Choose strategic or tactical tasking, record its mandate and add each agreed action. Each action pins the exact requirement or product revision considered and is attributed to the current actor.

Browse retained reviews with Previous and Next when more than one page exists; changing pages keeps an unsaved review draft in this browser.
{% endstep %}

{% step %}

## Create and control a strategy

Open Control strategies. Retained strategies are shown in access-scoped pages of 20; Previous and Next only read another authorised page and do not change retained records.

Complete Purpose, add each currently visible requirement and its separate rationale, then review the whole draft.

Back changes only the draft; Cancel retains nothing.

Retain control strategy creates one version after a fresh authority check. The owner can later add, remove or update links in a new revision; other readers see retained history without edit controls.
{% endstep %}

{% step %}

## Choose the product pattern

Choose a policing template, then explicitly replace sections only when intended.

Keep the terms of reference, time and geography, method, sources, gaps, recommendations, consultation, refresh and senior-review headings; restore missing required headings without replacing other text.
{% endstep %}

{% step %}

## Adopt local policy

Choose an approved local policing profile and record the impact review.

Visible readiness gaps remain part of the draft.

Adoption records applicability; it does not invent force, legal or jurisdiction approval.
{% endstep %}

{% step %}

## Consult and refresh

Record who was consulted and unresolved issues in the product.

Save a new reviewed content revision when subject or problem information changes; earlier text, evidence and rationale remain available.
{% endstep %}

{% step %}

## Complete independent review

Use the existing analytical assurance workflow where senior or independent review is required.

Draft export remains internal and does not authorise release or distribution.
{% endstep %}
{% endstepper %}

## Check the result

* Can every decision be traced to a named decision maker and exact material hash?
* Does each requirement link state its control rationale?
* Are local adoption limits and unresolved gaps visible?
* Does the current revision state consultation, refresh triggers and senior review accurately?

## If you get stuck

<details>

<summary>Why can I not record a review?</summary>

Read-only access lets you inspect retained reviews, but the recording form needs an assigned workspace and Direction transition authority.

Ask a workspace administrator or an authorised tasking lead to record the review.

If you have that authority, reload the workspace: every selected material must still be current and authorised, and each named participant or owner must be eligible for the combined handling scope.

</details>

<details>

<summary>Why did the review list stay on the same page?</summary>

A page could not be loaded. The current page and unsaved review remain in place so you can retry.

If current Direction access has been lost, CORTEX clears the visible reviews, source choices and unsaved review details; restore access and refresh before continuing.

</details>

<details>

<summary>What happens if paging fails?</summary>

A temporary or conflicting page read leaves the current authorised page and browser draft available to retry.

If current access is refused or a record is no longer visible, CORTEX removes the protected strategy list, requirement choices and unsaved strategy draft from the page; reload only after restoring the required access.

</details>

<details>

<summary>Why is Control strategies unavailable or why can I not revise one?</summary>

The route uses the current authenticated workspace and the same Direction and police-tasking service permissions as the rest of tasking.

A hidden navigation entry is only presentation; it does not grant or remove authority.

Only the retained strategy owner can create its next revision, and the owner must keep at least one currently authorised requirement with every link rationale complete.

</details>

<details>

<summary>Why can I not save a policing draft?</summary>

Apply the intended policing template, choose an approved local profile with an adoption reason, and restore every required policing heading.

Existing authored text is preserved when only missing headings are restored.

</details>

<details>

<summary>Why is a requirement shown as affected?</summary>

The strategy changed its link or rationale, or the current requirement moved beyond the pinned version.

Inspect both records and deliberately retain a new strategy revision if the control remains valid.

</details>

<details>

<summary>Does the selected profile approve this product?</summary>

No. It proves which reviewed profile revision was adopted locally and records known readiness gaps.

Product assurance and release remain separate decisions.

</details>

## Responsibility and limits

* A tasking record is a retained control record. It does not grant source access, release authority or a new disposition root.
* The organisation remains responsible for current local policy, restricted templates, legal review and jurisdiction-specific adoption.

**Reference and scope:** Local policy and approved UK profile adopted by the organisation; CORTEX supplies no restricted force template or jurisdiction approval.

## Related workflows

* [Define and manage an intelligence requirement](/workflow-guides/direction/requirements.md)
* [Agree an analytical commission and decision need](/workflow-guides/direction/commissioning.md)
* [Author an intelligence Product and inspect its exports](/workflow-guides/products/product-drafts.md)
* [Plan analytical assurance and obtain separate sign-off](/workflow-guides/analyse/analytical-assurance.md)
* [Read guidance for the exact retained UK profile](/workflow-guides/assurance/uk-profile-guidance.md)