> For the complete documentation index, see [llms.txt](https://finspectors.gitbook.io/finspectors-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://finspectors.gitbook.io/finspectors-documentation/audit-modules-auditor-view/requests/creating-a-checklist.md). # Creating a checklist ### **Step 1. Open the engagement** Navigate to **Home → Clients → Engagement** and select the engagement for which you want to create a checklist. ### **Step 2. Click Create New Request** Inside the engagement, open the **Requests** tab from the left panel and click **Create New Request**. ### **Step 3. Choose how to create the checklist** You can either: * Start from a blank checklist * Use a predefined template ### **Step 4. Select the request type** If you start from a blank checklist, each request can be one of three types: **Document** Use this when you want the client to provide supporting documents. You can: * Ask for a specific document * Attach a sample document for reference * Link the request to an existing workpaper * Select samples from the linked workpaper * Ask the client to upload supporting documents against those specific samples This is useful when evidence needs to be collected against transactions already selected for testing. **Short Answer** Add a question that requires the client to provide a brief written response. **MCQ** Add a question and provide multiple-choice options for the client to select from. ### **Step 5. Build your checklist** Add as many requests as required and combine different request types within the same checklist. For document requests linked to workpapers, review the selected samples and ensure the correct items are included before creating the checklist. ### **Step 6. Create the checklist** Once all requests are added, click **Create Checklist**. The checklist is now saved and ready to be assigned and shared with the external collaborator. ### **What happens next** Once the checklist is created, auditors can: * Assign it to an external collaborator * Track submission status * Review uploaded responses and documents * Validate documents submitted against sample items * Approve the response or request additional information {% embed url="" %}