> 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/custom-fields.md).
# Custom Fields
Custom fields are the extra details your team fills in when creating a field report, like the client's firm, the weather, or who was present on site. Each field appears on the report form, and its value lands in the matching spot of the exported Word report.
Custom fields belong to a [Report Type](/administration/report-types.md), so each kind of report can ask for different details.
{% hint style="info" %}
You need to be an Org Admin or Org Owner to manage custom fields.
{% endhint %}
## Adding a custom field
To add one:
1. Go to [Organization Settings > Field > Report Types](https://app.cogram.com/dashboard/settings/admin/field-reports#report-types) and click the Report Type you want to change.
2. Under **Custom Fields**, click **Add Field**.
3. Fill in the dialog:
* **Label**: the name your team sees on the form (e.g., "Client Firm").
* **Template Placeholder**: the name used in your Word template, written there as `{{ name }}`. Use lowercase letters, numbers, and underscores, like `client_firm`.
* **Helper Text** (optional): a short instruction shown under the field on mobile.
* **Field Type**: how the value is entered. See [Field types](#field-types) below.
* **Required**: check this if a report cannot be finalized without the field.
4. Click **Add Field**.
The Add Field dialog
The field appears on the report form right away. Its placeholder shows on the field's row; click it to copy it for your Word template.
The custom fields list on the Report Type page
## Field types
| Field type | What your team sees | Good for |
| ----------- | ---------------------------------------- | ----------------------------------------------------------- |
| Single line | A one-line text box | Short answers: firm name, temperature, project number |
| Multi-line | A larger text box that keeps line breaks | Longer answers: materials, comments, summaries |
| Table | A table where each entry is a row | Lists: persons present, equipment on site, inspection items |
## Setting up a table field
A **Table** field collects a list, one row per entry, like everyone present on site. When you pick **Table** as the field type, a **Columns** section appears in the dialog:
1. Click **Add Column** and enter the column's header (e.g., "Name", "Role", "Company").
2. Use the **M** toggle to allow multiple lines in a column, and the **R** toggle to make it required.
3. Reorder columns with the up and down arrows. This is the column order in the exported report.
A table field needs at least one column. In the exported report, the table grows to fit however many rows your team entered. See [Templates](/settings/templates.md#field-report-placeholders) for how to place it in your Word template.
## Matching placeholder names
The placeholder in your Word template must match the field's **Template Placeholder** exactly. If the template says `{{ Client Firm }}` but the field is named `client_firm`, the value will not fill in, and the export shows the literal text `{{ Client Firm }}`.
Names like `client_firm`, `temperature`, or `persons_present` work. Names with spaces, capitals, or punctuation (like `Client Firm` or `temp.`) are not accepted.
## Reordering, editing, and deleting fields
The **Order** column controls the field order on the mobile form and in the exported report. Use the up and down arrows on each row to reorder.
To edit a field, click the pencil icon on its row, make your changes, and click **Save**. To delete a field, click the trash icon. Existing reports keep any values they already had; the field is only removed from new reports.
{% hint style="warning" %}
If you change a field's **Template Placeholder**, update and re-upload every Word template that uses the old name.
{% endhint %}
## Related
* [Create a Field Report on Site](/guides/field-reports.md): how your team fills these fields in on mobile.
* [Report Types](/administration/report-types.md): the report setup each set of custom fields belongs to.
* [Templates](/settings/templates.md): builtin placeholders, table placement, and tips for building your Word templates.
---
# 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/custom-fields.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.