> For the complete documentation index, see [llms.txt](https://docs.corpdev.ai/corpdev.ai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.corpdev.ai/corpdev.ai-docs/work-with-the-analyst.md).

# Work with the Analyst

Use the Analyst to research a question, analyze your sources and create or revise a deliverable. Available tools depend on your workspace and connected services.

## Start a task

1. Confirm the current workspace and open **Analyst**.
2. Describe the business question, audience, scope and desired output.
3. Use **Attachments** for supporting material and **@** to select existing context. Select entries from the picker so the intended source is attached to the task.
4. Choose **New Document** or an available template. A template provides a starting structure; it does not replace the need for clear instructions.
5. Choose an available model. If **Agent Team** is available, it allows the Analyst to divide suitable research among subagents.
6. Select **Create deliverable** and follow progress in the document or **Kanban** view.

## Write a useful brief

Include these five things:

* **Decision:** what the reader needs to decide.
* **Scope:** companies, geography, period and exclusions.
* **Sources:** the specific files, folders, lists or public information to use.
* **Output:** memo, comparison table, presentation or spreadsheet, with the sections you need.
* **Evidence standard:** citations, reporting periods, assumptions and how to handle missing information.

For example: “Compare these five targets against our acquisition criteria. Use the attached criteria document. Give each criterion a source-backed assessment and list the evidence we still need. Do not infer revenue where it is unavailable.”

## Continue an existing document

Open it from **Deliverables** and use its Analyst conversation. Be explicit about whether you want to change the document, create a separate version, or answer a question. For a targeted revision, name the section and the exact change.

If a job is still running, inspect its progress before starting another. A queued or partially completed job is different from a failed job. The **Document queue** in workspace settings provides visibility into queued document generation where applicable.

## Check the output

Open the underlying sources for important claims. Confirm units, currencies, reporting dates and calculations. Ask the Analyst to label uncertainty, but also review it yourself: generated text can be wrong even when it reads confidently.

Research cannot recover information absent from the connected sources. A search result is not proof that every relevant document or company has been found. If an answer misses a source, name it explicitly and ask a narrower question.

## If a run fails

Keep the document and error message. Check credits, access to referenced sources and the job status. Correct a missing permission or invalid input before retrying. If the run may have created output, inspect that output first to avoid duplicating work.

See [Troubleshooting](https://docs.corpdev.ai/corpdev.ai-docs/troubleshooting-and-support) and [Account and credits](https://docs.corpdev.ai/corpdev.ai-docs/account-subscription-and-credits).