> For the complete documentation index, see [llms.txt](https://docs.cogram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogram.com/administration/report-types.md).
# Report Types
Report Types let you set up different kinds of field reports for your organization, like a Site Visit Report, a Field Observation Report, or a Punch List. Each Report Type has its own form fields, its own export layout, and its own Word templates, so your team always fills in the right details and the exported report comes out in your layout.
{% hint style="info" %}
You need to be an Org Admin or Org Owner to manage Report Types. Everyone on your team can pick from them when creating a report.
{% endhint %}
## Creating a report type
To create one:
1. Go to [Organization Settings > Field > Report Types](https://app.cogram.com/dashboard/settings/admin/field-reports#report-types).
2. Click **Create a Report Type**.
3. Enter a name (e.g., "Site Inspection" or "Safety Audit").
4. Click **Create**.
The new Report Type appears in the list, and your team can use it right away.
The Report Types list under Organization Settings > Field
## Setting a default report type
The default Report Type is pre-selected whenever someone creates a new report. To set it, hover over a type in the list and click the star that appears. The type then shows a **Default** badge, like in the screenshot above. Click the star again to clear it. Only one type can be the default at a time.
## Editing a report type
Click a Report Type in the list to open it. The page has three sections:
* **Set Up Mobile Fields**: every report already asks for a title, project, location, observations, and drawings. Add [custom fields](/administration/custom-fields.md) here for anything else your reports need, like the client's firm or the weather.
* **Linked Templates**: the Word templates for this type. All of your organization's report templates are available by default. Link specific ones here to narrow the choice, and star one to make it this type's default. Click **Link Template** to add one.
* **Format the Export**: how observations look in the exported report. See the next section.
To rename the type, click the pencil icon next to the page title.
Linked Templates on the Report Type page
## Format the Export
This section controls how each observation (the notes and photos your team captures on site) appears in the exported Word report.
The quickest way to set it up is with the **Apply preset** buttons: **Compact photo card**, **Field note**, **Photo first**, or **Legacy table (default)**. Click **Preview** to see the result on a sample observation, and **Save** when you are happy. **Reset to defaults** takes you back to the standard layout.
The Format the Export section on the Report Type page
To fine-tune the layout, edit it directly. The layout repeats once for every observation, and you can insert these placeholders from the **Add Elements** menu:
| Placeholder | What it shows |
| ------------------- | ---------------------------------------------------------------- |
| `{{ obs.index }}` | The observation's number in the report (1, 2, 3, and so on) |
| `{{ obs.type }}` | The observation type, for example "Defect" |
| `{{ obs.status }}` | The observation status, for example "Open" |
| `{{ obs.title }}` | The title captured on site |
| `{{ obs.note }}` | The written note from the field |
| `{{ obs.photos }}` | The photos, laid out per the settings below |
| `{{ obs.drawing }}` | The drawing pin image, if the observation is pinned to a drawing |
Under **Advanced layout settings** you can also adjust the photos and drawing pins:
* **Photos per row**: 1 to 6 photos side by side (default 3).
* **Aspect ratio**: **Auto (source orientation)**, **Portrait (3:4)**, **Landscape (4:3)**, or **Square (1:1)**.
* **Photo caption template**: the text under each photo. The default is `Picture {{ photo.index }}: {{ photo.note }}`, and `{{ photo.taken_at }}` is also available.
* **Drawing width (px)** and **Drawing caption template**: the size and caption of the drawing pin image.
Changes apply to the next export. You do not need to re-upload your Word templates.
## Deactivating or deleting a report type
To hide a type from the new-report picker, click the **Deactivate** icon on its row. Existing reports keep their type, and you can reactivate it at any time. Deactivating the default type also clears the default.
To remove a type completely, click the **Delete** icon. Deleting also removes the type's custom fields and template links. Existing reports keep their data, but new reports can no longer use the type.
## Related
* [Create a Field Report on Site](/guides/field-reports.md): what your team sees on mobile when they use these report types.
* [Custom Fields](/administration/custom-fields.md): the form fields you add to a Report Type.
* [Templates](/settings/templates.md): how to build the Word templates your reports export against.
* [Observation Types and Statuses](/administration/observation-types-and-statuses.md): the Type and Status options your team picks when capturing observations.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.cogram.com/administration/report-types.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.