> 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/sources-and-evidence/intelligence-reports.md).

# Intelligence Reports

**Open this area:** In the CORTEX menu, select **Sources & evidence → Intelligence reports**.

Receive unsolicited information, protect source-risk details separately, and obtain an exact, independently approved recipient projection.

**Who uses this:** Collector, Analyst, Reviewer, Author, Administrator.\
**Open in CORTEX:** `/intelligence-reports`.\
**In-app guide:** `/help?topic=intelligence-reports`.

**Expected result:** An accountable report has a unique reference, retained history, and a deliberate path into a product with current source-risk checks.

## Before you start

* Choose the intended workspace. The node operator must enable reports with a stable issuer; an administrator must explicitly grant ordinary or protected capabilities within your current handling scope.
* Receipt does not require an intelligence requirement. Record a lawful policing purpose, necessity, attribution, and uncertainty; receipt grants no covert collection or investigative authority.
* Keep source identity, proximity, and risk out of ordinary wording. These belong in Protected source and risk and require separate permission.

## What to do

{% stepper %}
{% step %}

## Find the current report

The report list shows only records visible to your current account.

Edit the title or reference search, then select Search reports to apply it from page 1; a changed-filter message distinguishes typed text from the last confirmed results. Previous and Next continue with the last successful search.

If a temporary load fails, the confirmed reports and page remain available for retry. A current access loss clears them. The pager range and total come from the authorised service response and may change as reports or access change.
{% endstep %}

{% step %}

## Receive the information

Choose Receive a report.

The four steps cover purpose and receipt, observations, optional necessary subjects, and review. Required inputs and a missing-input list update as you enter data; red or green step status shows readiness, and Back preserves values.

Complete receiving unit, purpose, retention necessity, observations, and time/location qualifications. Add an operation reference or up to ten necessary subjects only when needed; a subject name and necessity become required if added. DOB and PNC identifier are optional.

On review, set jurisdiction and handling and explain the receipt reason in 10–2,000 characters. Unsolicited receipt needs no Direction requirement.

Save retains your identity, UTC receipt time, and unique report reference.
{% endstep %}

{% step %}

## Clarify and connect

Open the report.

An evaluator can request clarification or link an accepted active requirement found by name. The reporter or evaluator can amend ordinary content with a reason. Each action appends history.

A report amendment requires a fresh protected proposal, evaluation, and review before a new projection.
{% endstep %}

{% step %}

## Protect source details

With protected-source read and write authority, open Protected source and risk.

Retain identity/contact, proximity, risk assessment, and mitigations. Optionally link a named source revision and exact evidence quotations.

Custody handling must cover every input and is fixed after first save.
{% endstep %}

{% step %}

## Evaluate under an adopted policy

An authorised evaluator selects one approved England/Wales profile and adoption rationale.

Record separate source, information, and sharing assessments, plus permitted action and sanitisation conditions. Rationales stay protected.

Retain evaluation for independent review.
{% endstep %}

{% step %}

## Complete independent review

A different authorised reviewer inspects the ordinary wording and exact protected proposal.

Request changes, reject, or approve recipient projection with an explicit expiry within 90 days. S2 approval requires evidence and actual UTC time of completed consultation.

Neither the reporter nor proposal author may review their own work.
{% endstep %}

{% step %}

## Prepare a sanitised report when needed

From protected custody, choose Prepare sanitised report.

The page confirms the exact original and protected source-risk custody prerequisite; changed access or custody is checked again on save. Use the same four steps to review every ordinary field and record a protected rationale.

A new reference and protected origin link are retained; handling is preserved. The derivative needs its own fresh evaluation and independent review.
{% endstep %}

{% step %}

## Use the approved projection

In the product editor, find the report by title or reference and inspect its current approved projection.

Add this exact approved projection, review inherited handling, and save. Up to four reports can be retained.

Product preview and PDF, Word, and JSON use only approved recipient fields. Fresh release stages recheck current report, review, policy, and expiry.
{% endstep %}
{% endstepper %}

## Check the result

* Is the purpose and retention necessity explicit?
* Are observations attributed and time/location uncertainties preserved?
* Are optional subject identifiers necessary?
* Does the recipient wording exclude protected source details?
* Is the evaluation tied to the applicable approved policy?
* Is review independent, current, and supported by completed S2 consultation where required?

## If you get stuck

<details>

<summary>Why did my save fail?</summary>

Check the message and linked guide. Required narratives have bounded lengths; future DOB, incomplete consultation, inadequate handling, and stale versions are rejected.

Failed validation or concurrency preserves the entered draft. Compare the current record before deliberately refreshing or leaving the page.

</details>

<details>

<summary>Why is there no approved projection?</summary>

Resolve clarification, retain a source-risk proposal against the current ordinary version, evaluate with a current adopted policy, and ask an independent reviewer to make a valid decision.

Approval is not inferred from receipt or a grading code.

</details>

<details>

<summary>Can an ordinary recipient inspect source risk or sanitised origins?</summary>

No. Ordinary report and approved projection contracts exclude protected source identity, proximity, risk, consultation, and origin payloads.

Authors and reviewers must still ensure that manually entered ordinary prose is suitable for recipients.

</details>

<details>

<summary>Does this prove compliance with a national report template?</summary>

No. NI, Scotland, and restricted national or force-template compliance remains unverified without applicable source access, usage rights, owner confirmation, and reviewed acceptance evidence.

Do not label exports as nationally compliant templates.

</details>

## Responsibility and limits

* Ordinary report read does not grant protected-source access. Workspace roles narrow explicit global grants; independent source-risk review requires Manager workspace authority as well as its explicit capability.
* Earlier report, custody, and Product revisions remain retained. Amending or sanitising does not delete or declassify an original.
* Receipt retries use the same operation reference. If the response is uncertain, remain on the form and retry the same values. Sanitisation retries can recover a partially completed protected-origin write; do not use an incomplete derivative.
* Approval is bounded to the exact report and source proposal. Later edits, expired review, or unavailable policy block fresh use and release. Historical approved snapshots and already released package bytes remain unchanged under current access.

## Reference and scope

Supports F11 report handling and Appendix A metadata. APP 3×5×2 evaluation requires an adopted England/Wales profile. NI, Scotland, and restricted national or force templates remain unverified until applicable sources, rights, and owner evidence are available.

## Related workflows

* [Plan collection and record observed results](/workflow-guides/collection/collection-plans.md)
* [Record authority before new source use](/sources-and-evidence/source-authority.md)
* [Record JDP or policing evaluation and sharing conditions](/menu-areas/police-and-defence/policing-evaluation.md)
* [Author an intelligence Product and inspect its exports](/workflow-guides/products/product-drafts.md)
* [Review, approve and publish an exact internal release](/workflow-guides/products/release.md)
* [Manage accounts, grants and workspace membership](/workflow-guides/assurance/access.md)