> For the complete documentation index, see [llms.txt](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/close-management/close-checklist/intro-to-the-close-checklist.md).
# Intro to the Close Checklist
The **Close Checklist** in **Rillet** organizes your month-end close into a structured set of tasks, each with an assigned preparer, one or more ordered reviewers, due date, and supporting files, so your team can track progress and close on time with full visibility.
### Create a New Task
Follow these steps to create a new task:
1. Go to **Close Management > Checklist**.
2. Select **+ Add Task**.
3. Enter a **Title** that describes what needs to be done.
4. **(Optional):** Enter a **Description** with any additional detail about the task.
5. **(Optional):** Select a **Category** to categorize the task by the part of the close it relates to.
6. **(Optional):** Assign a **Preparer** and one or more **Reviewers**, the team members responsible for completing and signing off on the task. Reviewers sign off in the order you select them, and you can drag to reorder your selections at any time.
7. Set the task's due date:
* Select **Calendar date** to choose a specific due date, or **Business day** to set the due date relative to the close.
* Enter a number in **Business Days from Close (Optional)** if you select **Business day** (for example, 5 for 5 business days after the close). Use a negative number for days prior to the close.
* Switch a task between **Calendar date** and **Business day** at any time.
8. **(Optional):** Attach an Aura agent to help complete the task, in the **Aura can help you** section:
* Select a suggested agent (for example, **AR Invoicing Reminders**), choose a saved agent under **My Agents**, or search for one in **Create a new agent or choose an existing one**.
* Click **Preview and edit** to open the agent's prompt and make any edits.
9. Click **Add task** to add the task to your checklist.
{% hint style="info" %} **Note:**
Once a reviewer signs off, they are locked in place. You must revoke their sign-off before you can reorder or remove them from the task.
{% endhint %}
The task now appears on your close checklist, ready for your team to track and complete.
### Reorder Checklist Tasks
Take these steps to reorder tasks:
1. Hover over the task you want to move to reveal its drag handle at the end of the row.
2. Drag the task to its new position in the checklist.
The checklist reflects the new order immediately, so you can sequence tasks to match your team's actual close workflow.
### Attach and View Supporting Files
Complete these steps to attach a supporting file:
1. Click the **Paper Clip** icon from the task list.
2. Drag and drop the file you want to attach, or select it from your files.
3. Click **Save & Exit** to confirm the attachment.
Once added, the file appears in the pop-up and can be downloaded.
### Mark Tasks as Complete
Take these steps to mark a task as complete:
1. Click the checkmark icon in the **Preparer** column to mark the task as prepared.
2. Click the checkmark icon next to a reviewer's avatar in the **Reviewer** column to mark the task as reviewed. If a task has multiple reviewers, they sign off in sequence, and only the reviewer whose turn it is can mark it reviewed.
{% hint style="info" %} **Note:**
The **Preparer** column also includes an **Attach Aura Agent** icon, letting you attach or change the task's Aura agent directly from the checklist without opening the task. Hover over the **Reviewer** column to see the full list of reviewers and each one's sign-off timestamp for auditability. If you assign or change the **Preparer** after someone has already marked the task prepared, Rillet shows a notice that the change only applies going forward, and the original preparer's name and timestamp stay on record.
{% endhint %}
Once every reviewer has signed off, the task is marked as complete and the progress (for example, 1/1 Completed) updates in real time.
### Unmark a Task
Use these steps to unmark a task:
1. Click the **X** next to the reviewer’s avatar in the **Reviewer** column.
The task is no longer marked as complete, and the checklist progress updates accordingly.
### Reuse Your Checklist Next Month
Perform these steps to reuse your checklist next month:
1. Click the three dots in the upper right corner and select **Copy & Create New Month** to create the next month’s close period.
{% hint style="info" %} **Note:**
When you click the checkmark icon in the **Preparer** column, your avatar is filled in automatically. Hover over the user’s avatar in **Preparer** or **Reviewer** at any time to view the completion date and time.
{% endhint %}
These steps help your team keep the close checklist accurate and up to date each month.
### Frequently Asked Questions (FAQ)
Does the close checklist support a third level of sign-off?
A single **Prepared By** role still applies, but **Reviewed By** is not limited to one person. Assign multiple reviewers to a task, and they sign off in the sequential order you select them, each with their own recorded timestamp.
### See Also
To learn more about managing your financial close process with **Rillet**, review these articles:
* [**Close the Books**](/EjmEP4KZ9BVp9j2ho4Mh/general-accounting/close-the-books.md)
* [**Journal Entries**](/EjmEP4KZ9BVp9j2ho4Mh/general-accounting/journal-entries.md)
* [**Financial Statements**](/EjmEP4KZ9BVp9j2ho4Mh/reporting/financial-statements.md)
---
# 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.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/close-management/close-checklist/intro-to-the-close-checklist.md?ask=&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.
