> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/how-the-apps-work/screens/checklists/edit-checklist.md).

# Edit checklist

{% hint style="info" %}
Draft, written by an agent and not yet checked by a person ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). Platforms: web, iOS and Android. [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/checklists/edit-checklist.md).
{% endhint %}

Build or change a checklist: its name, whether it needs a signature, its sections, and its items with their answer types and settings.

![Edit checklist](https://3653879137-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsVVGa79QbcEkJ7n8srxe%2Fuploads%2Fgit-blob-4cae089a15554f8e7aeff5df69d37ee1f51b8caa%2Fedit-checklist.png?alt=media)

* **Where:** web: "Edit" in the checklist menu on a task, asset or planned task ([Checklist menu](https://docs.snapfix.com/how-the-apps-work/screens/checklists/checklist.md#checklist-menu)); the card's "+", "Create New Checklist", for people who get a checklist made for one task; and the Site Console "Checklists" tab, which opens the same dialog for a template ([Console: checklists](https://docs.snapfix.com/how-the-apps-work/screens/console/checklists.md)). iOS: `EditCheckListVC`, from "Edit Checklist" at the bottom of the checklist or in the checklist menu, or from a template. Android: `EditChecklistActivity`, from the same places.
* **Who:** people who can manage checklists: the site's "manage checklist" permission (iOS `canManageChecklist()`, Android `fManageChecklist`). On the web, a task's checklist that was made from a template can be edited only by site admins, which edits the template itself while the checklist hasn't been started; planned tasks can always be edited. The web's save route checks the same permission, except when a checklist is first opened ([`POST /v1/app/todos/multi`](https://docs.snapfix.com/engineering-reference/api/checklists.md#post-v1apptodosmulti)); the apps' save actions check no access at all.
* **Feature:** [Checklists](https://docs.snapfix.com/product/features/checklists/checklists.md); [Checklist templates](https://docs.snapfix.com/product/features/checklists/checklist-templates.md).

Filling the checklist in is on [Checklist](https://docs.snapfix.com/how-the-apps-work/screens/checklists/checklist.md). Template folders and the template list are on [Console: checklists](https://docs.snapfix.com/how-the-apps-work/screens/console/checklists.md).

## Getting here

* **From the checklist.** Web: the menu's "Edit". iOS and Android: "Edit Checklist" at the bottom of the checklist, or in the checklist menu. On iOS and Android the editor also opens by itself the first time a person who can manage checklists opens an empty checklist.
* **From a new checklist.** Web: the card's "+" opens [Add a checklist](https://docs.snapfix.com/how-the-apps-work/screens/checklists/checklist.md#add-a-checklist). A site admin with at least one folder who chooses "Create New Checklist" gets the "New Checklist" dialog ([Create a template](#create-a-template)); anyone else gets this editor for a checklist made for this task only.
* **From a planned task.** Web: "Edit" on a [planned task](https://docs.snapfix.com/how-the-apps-work/screens/planner/planned-task.md)'s checklist. The changes go back to the planned task and are saved with it; the editor sends nothing. iOS does the same for a planned task.
* **From the Site Console.** Web: the "Checklists" tab opens this dialog for a site template. The template is saved on its own, and no task changes ([Console: checklists](https://docs.snapfix.com/how-the-apps-work/screens/console/checklists.md)).
* **From a template (apps).** iOS and Android open the same editor for a site template.

## Layout

### Web

1. **Title.** "Edit your Checklist" when the checklist has items, or "Create your Checklist" when it is new; on assets "Edit your Template Checklist" and "Create your Template Checklist". An info button explains the controls: "Create, edit, and manage checklists efficiently. You can add, remove, duplicate and reorder sections and items. Use the buttons below to:", with "Remove the Section", "Remove the checklist Item", "Drag and move a Section", "Duplicate entire Section/Item" and "Expand/Collapse a Section".
2. **Base controls.** "Checklist Name": the name, which a click turns into a field, and a three-dot menu with "Edit Name" and "Delete Checklist" ("Delete Checklist" only while there are sections). Then the "Require Signature" switch, off and disabled while there are no sections.
3. **Sections.** One card per section, in order. The header has a drag handle, the NA switch when the section allows NA, the name ("ADD A SECTION NAME" when it has none), a pencil, a three-dot menu and an arrow that opens it. The menu has "Add A New Checklist Section", "Duplicate", "Allow Users To Set This Entire Section As Na" (a switch) and "Delete".
4. **Items.** Each item has a drag handle, a disabled checkbox (a preview, not an answer), its name ("ADD AN ITEM" when it has none), a "\*" when it is mandatory, the NFC icon when it has a Smart Tag check, a settings button ("Item settings", [Item settings](#item-settings)) and a three-dot menu with "Edit", "Add More", "Duplicate" and "Delete". Under it are a preview of its answer buttons (pass, flag, fail and "NA"; "YES" and "NO"; or 1 to 5), its description, and "Add Description" or "Remove Description".
5. **Empty states.** With no sections, "Add a new checklist Section" is the only control. An empty section shows "Add a new checklist Item".
6. **Footer.** "Cancel" and "Save". The dialog is at least 840 pixels wide, and clicking outside it doesn't close it.

### iOS

`EditCheckListVC` is a full screen with:

1. A title: "Edit: " for a task, "Edit:


---

# 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.snapfix.com/how-the-apps-work/screens/checklists/edit-checklist.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.
