> For the complete documentation index, see [llms.txt](https://docs.scribeware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scribeware.com/into-the-weeds/report-automations.md).

# Report Automations (Beta)

Describe a job in one sentence and ScribeWare does it on every report: look up facts before the inspection and fill them in, or review what you wrote before it goes out.

Report Automations take the chores you repeat on every job and do them for you. You describe each one in a single plain-English sentence, such as *"The day before each inspection, add the FEMA flood zone to the inspector notes."* ScribeWare turns that sentence into a rule, lets you test it on a real report, and runs it on every report from then on.

Find it under **Settings → AI**, in the **Report Automations (BETA)** card at the top of the page.

<figure><img src="https://3342988038-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmvEyXa42lNFnWTj9YA8%2Fuploads%2Fgit-blob-c822a6c328bdbd167a7757dc071263a6e918d232%2Fcapture-desktop-report-automations-01-settings-card.png?alt=media" alt="Settings → AI with the Report Automations (BETA) card: (1) the sentence box, (2) the Compile button, (3) the Examples list"><figcaption><p>Write a sentence (1), press <strong>Compile</strong> (2), or start from one of the <strong>Examples</strong> (3).</p></figcaption></figure>

{% hint style="warning" %}
Report Automations are in **beta**. Only companies on the beta or alpha channel see them. They use AI, and AI can be wrong, so every automation starts in **shadow** mode, where only you can see what it would have done. Nothing reaches your inspectors until you choose to make it live.
{% endhint %}

## Two Kinds of Automation

|                             | **Auto-fill**                                                                                                                                      | **Check**                                                                  |
| --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| **What it does**            | Gathers facts *before* the inspection and fills them into the report                                                                               | Reviews what the inspector *wrote* and flags problems                      |
| **When it runs**            | Before each confirmed inspection, at a time you pick                                                                                               | When a chapter is marked finished, and again before publishing             |
| **Example**                 | *"As soon as an RV inspection is confirmed, decode the VIN from the booking and add the coach type, year, make and model to the inspector notes."* | *"Every observation marked Safety must have at least one photo attached."* |
| **What the inspector sees** | An **Auto-filled** note on the field, with **Confirm** and **Undo**                                                                                | An item to review, with **Apply fix** or **Dismiss**                       |

You don't choose the kind. ScribeWare works it out from your sentence and shows a blue **Auto-fill** or green **Check** tag on the card.

## Shadow First, Then Live

Every new automation is saved in **Shadow**, a trial mode:

* **Shadow:** the automation runs on real reports, but inspectors never see it. What it *would* have filled or flagged is saved as samples in Settings. You mark each sample **Looks right** or **Wrong**, and adjust the automation until it behaves.
* **Live:** auto-fills fill empty fields, and checks show their findings to inspectors. You can move an automation **Back to shadow** at any time.

<figure><img src="https://3342988038-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmvEyXa42lNFnWTj9YA8%2Fuploads%2Fgit-blob-6718702a0bb13f764f6613d3b30b763e9d18f94a%2Fcapture-desktop-report-automations-03-saved-automations.png?alt=media" alt="The Saved automations list: a live check and a live auto-fill, each with an Enabled checkbox, Edit, and a Back to shadow button"><figcaption><p>Each saved automation shows its mode, its kind, when it runs and how often it has fired.</p></figcaption></figure>

## Where to Next

{% content-ref url="/pages/VHvO9c7kkAisiGRD7v3S" %}
[Creating an Automation](https://docs.scribeware.com/into-the-weeds/report-automations/creating-an-automation.md)
{% endcontent-ref %}

{% content-ref url="/pages/u0xi0MqdNCmPo6SSt0bL" %}
[Auto-fills](https://docs.scribeware.com/into-the-weeds/report-automations/auto-fills.md)
{% endcontent-ref %}

{% content-ref url="/pages/qCVLhV5y6ZPYYHvstLp7" %}
[Checks](https://docs.scribeware.com/into-the-weeds/report-automations/checks.md)
{% endcontent-ref %}

{% content-ref url="/pages/RozX8hzvjTzdDPKSH5tV" %}
[What Inspectors See](https://docs.scribeware.com/into-the-weeds/report-automations/what-inspectors-see.md)
{% endcontent-ref %}

{% content-ref url="/pages/NkhGEQzDEQH9Ez9pERyL" %}
[Limits and Your Data](https://docs.scribeware.com/into-the-weeds/report-automations/limits-and-your-data.md)
{% endcontent-ref %}


---

# 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.scribeware.com/into-the-weeds/report-automations.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.
