> For the complete documentation index, see [llms.txt](https://docs.controlbee.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.controlbee.nl/controlbee-docs/en/checken/auditplanning.md).
# Audit planning
Plan internal process audits based on the validity of processes
Internal audits are scheduled using audit schedules. The user creates a schedule of internal process audits based on the validity of the processes. If an audit is scheduled, the planned date is shown in this overview and can be edited.
## Determine periodicity
In the audit planning overview, a periodicity can be set per process, which serves as a guideline for the audit frequency.
{% hint style="info" %}
As soon as the auditor enters a date for the next audit when completing a process audit, this periodicity is used to automatically suggest a date.
{% endhint %}
## Create audit schedule
Using the plus button in the overview, or directly from the process overview, an audit schedule can be created.
When creating it, the user specifies the planned date, the auditor, the auditee, and any points of attention for the audit. The process name is prefilled and cannot be changed.
After the audit schedule has been saved, it can be edited or a process audit can be created for the specified process. See [Process audits](/controlbee-docs/en/checken/proces-audits.md).
## Export audit schedule
To get an overview of the planned audits, it can be exported to Excel.
---
# 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://docs.controlbee.nl/controlbee-docs/en/checken/auditplanning.md?ask=&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.
