> 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/moment-by-topic/integrations/file-import/tools/checklist.md).

# Checklist

To import a checklist using the import tool involves the use of a template. The template file, an Excel file, consists of two tabs. Each file contains one checklist. 

![](/files/-MedlIoDG363RK5358ac)

## Template file

### Sheets

* Checklist\
  The checklist sheet contains the data to create the checklist itself.
* Checklist Items\
  The checklist items sheet contains the various items found in the checklist. 

### Description

Columns with name in **bold** are required

#### Checklist

| Col | Name                          | Description                                                      |
| --- | ----------------------------- | ---------------------------------------------------------------- |
| A   | **Responsible User Email**    | The email for the employee that is responsible for the checklist |
| B   | Project Number                | Project number the checklist is to be related to.                |
| C   | Project Extension Name        | Name of the activity the checklist is to be related to.          |
| D   | Task Number                   | Number for the task the checklist is to be related to.           |
| E   | **Is Template**               | true/false                                                       |
| F   | **Is Public**                 | true/false                                                       |
| G   | **Title**                     | Title of the checklist                                           |
| H   | Description                   |                                                                  |
| I   | **Is Control Column Visible** | true/false                                                       |
| J   | Drawing                       |                                                                  |

#### Checklist Items

| Col | Name                         | Description                    |
| --- | ---------------------------- | ------------------------------ |
| A   | Completed by User Email      |                                |
| B   | Controlled by User Email     |                                |
| C   | **Name**                     | Name of item in the checklist  |
| D   | Documentation                |                                |
| E   | Comment                      |                                |
| F   | **Checklist Item Id**        | Unique ID number for each item |
| G   | Reference                    |                                |
| H   | **Item Completed**           | true/false                     |
| I   | Last Changed Item Completed  |                                |
| J   | **Item Controlled**          | true/false                     |
| K   | Last Changes Item Controlled |                                |
| L   | **Is Separator**             | true/false                     |


---

# 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/moment-by-topic/integrations/file-import/tools/checklist.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.