> For the complete documentation index, see [llms.txt](https://docs.omics.ai/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omics.ai/products/workbench/variant-interpreter/generating-a-report.md).

# Generating a report

Each analysis has a single clinical **report**: the signed-off conclusion of the interpretation. Reports are built from your lab's **report templates**, printed under your organization's **report branding**, and move through a sign-off workflow before they're released.

## How reports are put together

Three pieces combine to produce a report:

| Piece                | What it controls                                                                                                                                                                                      | Set up by   | Where                                             |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ------------------------------------------------- |
| **Report branding**  | The letterhead printed on every report: organization name, address, logo, credentials, brand colour, footer. One per workspace.                                                                       | Admin       | **Settings → Report Templates → Report branding** |
| **Report templates** | Which sections a report has, their order and headings, the lab's standard wording, and the findings sections variants can be filed under. A workspace can have several templates; one is the default. | Admin       | **Settings → Report Templates**                   |
| **The report**       | The findings for this case, the clinical interpretation, and any case-specific edits to the template wording.                                                                                         | Contributor | The analysis's **Report** tab                     |

A new report is created from the workspace's **default template**. It copies the template's sections and wording at that moment, so later edits to the template don't change existing reports. A draft report can pick up structural changes with **Update from template**.

## Before your first report

A workspace can't create reports until an admin has set up reporting:

1. [Set up the report branding](/products/workbench/variant-interpreter/generating-a-report/report-branding.md). At minimum, enter the **Organization name** and choose a **Brand colour**.
2. [Create one or more report templates](/products/workbench/variant-interpreter/generating-a-report/report-templates.md), or start from the standard sections.
3. **Set a template as the default.**

Until a default template exists, the Report tab shows "This workspace has no default report template". Ask a workspace admin to finish these steps.

{% hint style="info" %}
Setting up branding and templates needs the **Sign Off Reports** capability, which only admins have. Contributors don't see the **Report Templates** settings tab. See [Workspaces & roles](/products/workbench/variant-interpreter/workspaces-and-roles.md).
{% endhint %}

## Working on a report

1. [Fill in the report](/products/workbench/variant-interpreter/generating-a-report/filling-in-a-report.md): add variants, file them under the right findings section, and write the clinical interpretation and any other sections.
2. [Submit it for review, sign off, and release it](/products/workbench/variant-interpreter/generating-a-report/sign-off-and-release.md). Released reports can be downloaded as **PDF**, **HTML**, or **JSON**.
3. If a released report needs to change, an admin reopens it to issue an [amendment](/products/workbench/variant-interpreter/generating-a-report/sign-off-and-release.md#amendments).

See [The printed report](/products/workbench/variant-interpreter/generating-a-report/the-printed-report.md) for what appears on the released document.

## In this section

* [Report branding](/products/workbench/variant-interpreter/generating-a-report/report-branding.md)
* [Report templates](/products/workbench/variant-interpreter/generating-a-report/report-templates.md)
* [Filling in a report](/products/workbench/variant-interpreter/generating-a-report/filling-in-a-report.md)
* [Sign-off, release & amendments](/products/workbench/variant-interpreter/generating-a-report/sign-off-and-release.md)
* [The printed report](/products/workbench/variant-interpreter/generating-a-report/the-printed-report.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.omics.ai/products/workbench/variant-interpreter/generating-a-report.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.