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

# Quick Feedback

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

A short guide for the named recipient and the person responsible for responding to their observations.

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

**Expected result:** The recipient's actual receipt and feedback are recorded, with any follow-on decision made in its own workflow.

## Before you start

* The recipient must be named on a Released package and have current receive access. The analyst response needs separate feedback review authority.
* Only acknowledge a package you actually received and checked.

## What to do

{% stepper %}
{% step %}

### Get the exact package

Open the release intended for you. Enter a download reason and click **Prepare and download controlled ZIP**. Check the file and its SHA-256 against the release record.

Downloading alone does not record receipt.
{% endstep %}

{% step %}

### Confirm receipt

Click **Refresh release**. Enter the SHA-256 of the package you received and a **Recipient acknowledgement** statement, tick the confirmation box, then click **Record my explicit acknowledgement**.

This records your own receipt of that exact package.
{% endstep %}

{% step %}

### Give useful feedback

Click **Give feedback on this received product**. Record usefulness, timeliness and whether the requirement seems met, with a reason. Add corrections or follow-on needs if any, then click **Save recipient feedback**.

This records your view; it does not change the requirement.
{% endstep %}

{% step %}

### Decide what to change

The responsible owner or analyst reviews the feedback and opens the linked Direction requirement. If needed, use its **Change status** or gap actions, or create new Collection work under the normal permissions.

Make and verify that separate decision before describing it as done.
{% endstep %}

{% step %}

### Record the response

Return to the feedback record and click **Refresh feedback**. On **Response and actions**, an authorised reviewer checks the observed requirement version, explains the action taken or why nothing changed, and clicks **Record analyst response**.

Check it refers to the intended feedback revision.
{% endstep %}
{% endstepper %}

## Check the result

* Was this exact package received and verified?
* Does the feedback describe usefulness, timing and concrete corrections?
* Was any claimed follow-on action actually saved?

## If you get stuck

<details>

<summary>Why can I not see Give feedback?</summary>

Check that you are a named recipient, the release is Released, you explicitly acknowledged its current package and you have feedback write access.

</details>

<details>

<summary>Why was acknowledgement rejected?</summary>

Refresh the release and compare the SHA-256 with the actual file you received. A download or copied link alone is not verified receipt.

</details>

<details>

<summary>Why did the analyst response conflict?</summary>

The feedback or requirement changed after you opened it. Refresh both current revisions and reassess what action actually happened before recording the response.

</details>

## Responsibility and limits

* Recipients report honestly. The requirement owner decides satisfaction and further work; a feedback rating never changes Direction automatically.

## Reference and scope

For complete receipt, dialogue and response rules, open [Acknowledge the exact package and close the feedback loop](/workflow-guides/feedback/feedback.md) below.

## Related workflows

* [Acknowledge the exact package and close the feedback loop](/workflow-guides/feedback/feedback.md)
* [Start here: use Direction to ask for intelligence](/workflow-guides/direction/quick-direction.md)