> For the complete documentation index, see [llms.txt](https://docs.milientsoftware.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.milientsoftware.com/help/quality-system/checklists/work-with-checklists.md).

# Working with checklists

### Create and edit a checklist

1. In your project, go to Quality assurance > Checklists
2. Create a new checklist. Two options:
   1. Create new checklist from scratch. Give it a title and a short description. 
   2. Create new checklist based on a [template](/help/quality-system/checklists/templates.md). As soon as you have chosen "Use this", it will be added to your list of project checklists. Click into the list to edit the name and description.
3. Choose whether you want to include the [control column](/help/quality-system/checklists/activating-control-column-in-a-checklist.md) or not.
4. Go into your newly created checklist and start adding checklist items. You can add as many as you need.
5. You can also create "separators" in your checklist. This will make it possible for you to divide the content into areas, to improve readability and structure.
6. To sort the checklist items, simply click the dots on left side, and drag & drop the rows.

### Converting a checklist to a template

If you want to convert a project checklist into a template, find your checklist in the list of checklists and click "convert". This action is only possible for access role "Quality manager".

### Locking a checklist

Sometimes it can be convenient to lock a checklist. Simply click the locker symbol. As soon as the checklist is locked, no one can edit it. This action is only possible for access role "Quality manager".


---

# 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://docs.milientsoftware.com/help/quality-system/checklists/work-with-checklists.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.