> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/checkpoints/template/end-user.md).

# End User

Here’s a reusable End-User (How to Use) structure that assumes the checkpoint is already configured (no setup/admin work), and stays focused on expectations + doing the task.

<br>

### End-User Documentation Structure (8–10 headings)

1. Purpose and When to Use This
   * What the user is trying to achieve, and the situations that trigger using it.
2. Who Uses This
   * Intended roles (operator/supervisor/QA, etc.) and any responsibility notes.
3. What You’ll Need Before You Start
   * Preconditions (access, device, items on hand, sensor/equipment ready, etc.).
4. What You’ll See
   * Key screen/page elements and what they mean (at a high level).
5. Standard Workflow
   * The “happy path” steps from start → submit/complete.
6. Decision Points and Exceptions
   * What to do when results are out of range, missing info, failed checks, overrides, rechecks.
7. Corrective Actions
   * How a user records/executes corrective actions and what evidence is expected.
8. Validation and Sign-off
   * Review, acknowledgement, approvals, handover, or escalation (if applicable).
9. Records, History, and Reporting (User View)
   * How to find past checks, filter/search, export/view summaries (from an end-user perspective).
10. Troubleshooting and FAQs

<br>

* Common issues and what the user should try first + when to escalate.

<br>

If you want to keep it to 8 headings, merge:

* What You’ll Need Before You Start + What You’ll See
* Validation and Sign-off + Records, History, and Reporting


---

# 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.didge.io/home/checkpoints/template/end-user.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.