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

# Choose and complete your next useful action

> Review current evidence, complete one useful action, and decide what to check next.

Use this playbook for a regular review or when taking over an existing Project. You will leave with one completed action or a clear blocker, plus a follow-up check. You do not need to watch every video first.

## Before you start

Select the intended Project and Market. If you are taking over, read its Brand Profile and Prompt Library before changing them. Keep the core Prompts stable while comparing results; record any scope changes in your team's notes.

## 1. Check that the evidence is ready

Open **Analytics → Reports & history** and check whether the latest Analysis completed. For visits, open **Traffic → Setup** and check the source status and Google's **Last synced** time. If a source has no data, use [Diagnose missing traffic](https://docs.videntic.com/troubleshooting/traffic-data.md) before treating an empty chart as zero visits.

Do not start another Analysis just because one is still running. If it failed, follow [Common issues](https://docs.videntic.com/troubleshooting/common-issues.md).

## 2. Pick one finding worth acting on

Open Project Overview or Prompt Performance and read the AI answer behind one result. Compare the same Market, Prompts, AI Platforms and time window. Check whether a relevant page already exists before deciding to create another.

Open **Actions → Board** to see work from Technical Audit, Content Studio and Opportunities. Start with **Needs review** if work is already prepared; otherwise inspect a **Suggested** item. If the board is empty or reports unavailable data, open the relevant product surface directly. An empty board does not establish that there is nothing to improve.

## 3. Complete one piece of work

If the evidence does not justify a change, record that decision and what you will check after the next completed Analysis. Keeping a useful page unchanged can be the right outcome; do not create work just to finish the routine.

Choose the route that matches the evidence:

* **Content needs an answer or an update:** [review an opportunity](https://docs.videntic.com/playbooks/content-studio/opportunities.md), then [create or revise an Article](https://docs.videntic.com/playbooks/content-studio/draft.md). Review sources and claims before publishing.
* **A technical issue affects a page:** [investigate the finding](https://docs.videntic.com/playbooks/technical-audit/investigation.md), make the approved change and verify the live site.
* **A relevant discussion needs a useful reply:** [read the discussion](https://docs.videntic.com/playbooks/offpage-opportunities/discover.md), then [review the reply before posting](https://docs.videntic.com/playbooks/offpage-opportunities/reply.md).

If you cannot complete it, record the blocker, the person who can resolve it and your next step in your team's notes. Preparing a draft is useful progress; it is not a published result.

## 4. Verify the action and plan the next check

Return to the source item and inspect what changed. Open the live page after publication, the posted reply after posting, or the live-site check after a technical fix. **Actions** separates **In progress**, **Needs review** and **Done**. Done includes work marked as applied; run Technical Audit to verify those fixes.

In your team's notes, record the item URL, what changed, the date and the evidence you will revisit. After a later completed Analysis, compare the same Prompts and inspect their responses. Check Traffic separately for visits when the source has collected data. Publication does not guarantee citations, and a later metric change does not prove your edit caused it.

## Expected result

You can point to a checked action, an assigned blocker or a reason to make no change, and you know which evidence to review next. Continue with the same routine on your next review rather than changing several things without recording them.


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