> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/gasketelwet-forms/form-fields-in-gasketelwet-forms.md).

# Form fields in Gasketelwet Forms

The standard Gasketelwet form groups the most important compliance details in one place.

The exact layout can differ if your team changes the form.

### Common sections in the form

#### Notification or deviation details

Use this part to record the main finding and the date.

#### Contact and location details

Use this part to identify the customer, site, and responsible contact.

#### Appliance and inspection details

Use this part to record the installation, inspection result, and observed issue.

#### Follow-up and signatures

Use this part to record actions, confirmations, and signatures.

{% hint style="info" %}
Required fields need an answer before the form result is complete.
{% endhint %}

### Good practice

* keep descriptions short and specific
* use the same naming every time
* check whether photo or signature fields are needed

### Frequently asked questions

<details>

<summary>Which fields are required?</summary>

That depends on the current form setup.

Review the required indicators in the form.

</details>

<details>

<summary>Can we add custom fields?</summary>

Yes.

Test the result after any change.

</details>

<details>

<summary>Can we change the field labels?</summary>

Yes.

Be careful with compliance-related wording.

</details>

### Related topics

* [Gasketelwet Forms](/marketplace-packages-and-power-ups/power-ups/gasketelwet-forms.md)
* [Create a form](/marketplace-packages-and-power-ups/power-ups/forms/create-a-form.md)
* [Manage form versions](/marketplace-packages-and-power-ups/power-ups/forms/manage-form-versions.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 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://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/gasketelwet-forms/form-fields-in-gasketelwet-forms.md?ask=<question>&goal=<endgoal>
```

`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.