> 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/compliance-requirements-for-gasketelwet-forms.md).

# Compliance requirements for Gasketelwet Forms

Gasketelwet Forms is designed for a Dutch compliance process.

It helps you register inspection findings and keep a consistent record.

### How the form supports compliance work

The form helps you:

* capture the required inspection context
* record findings and deviations clearly
* keep the result linked to the work order
* export the result for records and review

### What to keep in mind

The form supports your process.

Your team is still responsible for using the right procedure, wording, and follow-up.

{% hint style="warning" %}
Review the current legal and sector requirements that apply to your organization.

Use the form as part of that wider compliance process.
{% endhint %}

### Frequently asked questions

<details>

<summary>Does the form itself make us compliant?</summary>

No.

The form supports compliance work, but your process and execution still matter.

</details>

<details>

<summary>Should we keep completed form results?</summary>

Yes.

Keep records according to your internal and legal requirements.

</details>

<details>

<summary>Can we use the PDF export for records?</summary>

Yes.

That is one of the main reasons to export the result.

</details>

### Related topics

* [Gasketelwet Forms](/marketplace-packages-and-power-ups/power-ups/gasketelwet-forms.md)
* [Export Gasketelwet form data and PDF](/marketplace-packages-and-power-ups/power-ups/gasketelwet-forms/export-gasketelwet-form-data-and-pdf.md)
* [Forms](/marketplace-packages-and-power-ups/power-ups/forms.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/compliance-requirements-for-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.