> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getsurfaced.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Actions

> The single queue of work that comes out of your results: what to do, who owns it, and what state it is in.

Every other screen in Surfaced tells you something. Actions is where those findings become work with an owner.

It is deliberately one queue rather than a to-do list per screen. A gap in the answers, a critical finding on your site and a page that needs rewriting are all things somebody has to do this week, and splitting them across three screens is how two of them get forgotten.

## What is in the queue

Items arrive from across the product and carry the source they came from: work on your content, a change to your website, something the answers are saying. Each one shows an expected impact, from very high down to very low, and a next step rather than a restatement of the problem.

| State | What it means |
| - | - |
| New | Nothing has happened yet. |
| In progress | Someone has picked it up. |
| Done | Finished. |
| Declined | Looked at and decided against. |

A separate **needs attention** count flags items that have gone stale or whose underlying finding has changed.

## The sidebar badge is personal

The number next to Actions in the sidebar counts the items **assigned to you**, not the total in the queue. Two people looking at the same workspace see different numbers, and someone with nothing assigned sees none at all.

This is on purpose. A badge showing the team's whole backlog is a number nobody acts on; a badge showing your own three is one you clear.

## Working the queue

Filter by state to separate triage from execution. The usual rhythm is to take the new items once a week, decline what does not fit, assign the rest, and leave in-progress work to the people holding it.

Record a decline rather than leaving the item new. The next person to open the queue then sees the decision instead of re-making it.

## How an action relates to the finding behind it

Closing an action records that you did the work. It does not verify the result. Whether the answers changed is what the next tracking run tells you, and whether your site changed is what the next [audit](https://docs.getsurfaced.ai/insights/audit-report.md) tells you.

So expect a lag. Content published this week will not move [brand visibility](https://docs.getsurfaced.ai/metrics/brand-visibility.md) until the engines have re-read your site and a run has asked the questions again. Judge the work on the next few runs.

## Where items come from

* **[Gap trends](https://docs.getsurfaced.ai/insights/gap-trends.md).** Accepting a suggestion on a gap creates work, usually a brief.
* **[Audit report](https://docs.getsurfaced.ai/insights/audit-report.md).** A content finding can become a brief directly; technical findings become site work.
* **[Content performance](https://docs.getsurfaced.ai/insights/content-performance.md).** A published page that is not being cited.

Each item keeps a link back to what produced it, so you can always get from the task to the evidence.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.