> 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/outsmart-knowledge-base/outsmart-knowledge-base-nl/mobiele-app/ios-outsmart-app/moduleoverzichten/werkbon/schema.md).

# Schema

Controleer en bewerk afspraakgegevens op een werkbon in de iOS-app.

## Schema

Gebruik **Schema** om de afspraakgegevens voor de Werkbon te controleren.

U kunt het Schema bewerken wanneer uw configuratie dit toestaat.

### Gebruik **Schema**

{% stepper %}
{% step %}

### Open **Schema**

Open de Werkbon.

Ga naar **Schema**.
{% endstep %}

{% step %}

### Afspraak controleren

Controleer de geplande datum, tijd en andere bezoekgegevens.
{% endstep %}

{% step %}

### Bewerken wanneer Beschikbaar

Tik **Schema bewerken** als de knop Beschikbaar is.
{% endstep %}

{% step %}

### Verlaat het scherm om op te slaan

De app slaat niet-opgeslagen Wijzigingen op wanneer het scherm wordt gesloten.
{% endstep %}
{% endstepper %}

### Let op

Bewerken kan worden geblokkeerd door bevroren Werkbonnen, snelle weergavemodus, toegang van collega's of workflow-Instellingen.


---

# 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://knowledge.out-smart.com/outsmart-knowledge-base/outsmart-knowledge-base-nl/mobiele-app/ios-outsmart-app/moduleoverzichten/werkbon/schema.md?ask=<question>&goal=<user_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.
