> For the complete documentation index, see [llms.txt](https://atlasgxp.gitbook.io/workspace/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlasgxp.gitbook.io/workspace/typical-qms-features/checklists-beta.md).

# Checklists (Beta)

### Overview

Checklists help you implement standards and regulations.  It works like this:

1. You set up Checklists with whatever Rule Tags you want
2. You tag your documents
3. You can see

The Checklist feature is a way to create a database of tags for things like the CFRs, or a set of Standards, and then tag your SOPs and Forms with it.

Here's an example of a Checklist for 21 CFR 111:

![](https://lh5.googleusercontent.com/ZSLjffXdWTqCE1TCFjV6IcBHWF5szDU55oJF2XkNnrUH0Xnh4Whr8DaFWRiPVkUgeDYngSboN5y2KApW9v72H1sazf8g1LwBvGb2Ko1vnCJuln_m5nnm0NhszK4u-RNXFwP1FWkF)

With this checklist set up, you can tag any Document, Form or Schedule with these CFRs:

![](https://lh3.googleusercontent.com/fErGiGxoVMQnJzNCjGPSg3arsAF0zOK6Xpb2AUjkF7kOOfDV5SnlGMp5BzySzEgUwPZShoM_D2qTCQQouvPUfDwZuAwZ58b0VAEQQfvwtmPkoUPAWH66hnZIzDAKIqrsLWVEkhvq)

Then, when you click on a tag, you'll be able to see all of the Documents, Forms and Schedules that are related to it. <br>


---

# 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://atlasgxp.gitbook.io/workspace/typical-qms-features/checklists-beta.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.