> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/field-operations/inspection-reports/create-an-inspection-report-from-the-office.md).

# Create an inspection report from the office

You don't have to be a field technician to start an inspection report - you can create one from the office on the web.

From the Inspection Reports page, click **Create Inspection Report** (top right). The modal walks you through choosing the **Asset Group Type**, then **Report Type** (only asked when that asset group type has more than one), then **Property**, and finally **Asset Group to Inspect**. Pick an existing group on that property, or create a new one and give it a name.

You can also create a report while viewing an existing asset group. Open the three-dot menu above its Assets and choose Create Inspection Report. When more than one report type is available, choose the one you want and click Create.

Create then opens a new Draft report that you fill out, save, and publish exactly like one started in the field. Creating reports needs the **Create Inspection Report** permission.

This creates a report from an existing report template. To create a new template or change fields, wording, device legends, or PDF layout, open the Essential Assistant and choose the Talk to a human tab.

> **Where to find it:** Inspection Reports page, Create Inspection Report button (top right), or an asset group page, Assets three-dot menu

Creating a report requires **Create Inspection Report**. Technicians with **Edit Inspection Report** can fill out your draft even if their role does not allow creating reports; **Submit Inspection Report** lets them publish it. See [Roles and permissions](/administration/settings/roles-and-permissions.md#let-technicians-complete-only-office-prepared-reports) to set this up.

## Related guides

* [Answer a question on many inspection assets at once](/field-operations/inspection-reports/answer-a-question-on-many-inspection-assets-at-once.md)
* [Common inspection report questions](/field-operations/inspection-reports/common-inspection-report-questions.md)
* [Can I move an inspection report to another customer or property?](/field-operations/inspection-reports/can-i-move-an-inspection-report-to-another-customer-or-property.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://learn.withessential.com/field-operations/inspection-reports/create-an-inspection-report-from-the-office.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.