> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/requests/checklists-and-sections.md). # Build your checklist Add checklist items, group them into sections, set required items and file types, attach files and reorder by drag and drop. A checklist tells your recipient exactly what to send, one checklist item per document. Each item is tracked and reviewed on its own, so you can see at a glance what's still missing. You build the checklist on the request page (or in a template) with **Checklist** selected. ## Add checklist items Each item has: * **Document Name** (required, up to 100 characters), for example "Photo of ID". * **Instructions - Optional**, for example "Driver's license or passport". Recipients see these under the item name. * **Attach Files**: files you give the recipient for this item, such as a blank form to complete or a sample. Drop files on the item or click the link. Click **Add Item** to add the next item. {% hint style="info" %} Ask for one document per item. "Last two pay stubs" is fine as one item; "Pay stubs and bank statements" is better as two, because you review each item as a whole. {% endhint %} ## Advanced item options Click **Advanced** on an item to see: | Option | What it does | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Acceptable File Types** | Limits what the recipient can pick for this item. Type an extension such as `pdf`, `docx` or `jpg` and press Enter, comma or space. Recipients see the accepted types listed under the upload box. Leave it empty to accept any file. | | **Required?** | When on, the recipient can't mark the item **Not Applicable**. They have to upload something for it. | ### Required items and "Not Applicable" By default, a recipient can mark any item **Not Applicable** if it doesn't apply to them, for example "Spouse's ID" for a single filer. A Not Applicable item counts as responded, and you see **Marked Not Applicable** on it. Turn on **Required?** for items every recipient must provide. Required only removes the Not Applicable option. ## Group items into sections Sections break a long checklist into parts, such as "Income", "Deductions" and "Identity". Recipients see the sections as headings and can jump between them. 1. Click **Create Section**. * The first time, Pipefile moves the items you already have into a section called **General**, and you can rename it. * After that, each click adds a new section with one empty item. 2. Click the section's title to rename it (up to 100 characters). A blank title becomes **Untitled Section**. 3. Click **Add Item** inside a section to add items to it. 4. Use the arrow beside a section's title to collapse or expand it while you work. Once a checklist has sections, every item belongs to one. Sections hold items only; there are no sections inside sections. ## Reorder items and sections Drag an item or section by its handle and drop it where you want it. You can drag items between sections, and drag whole sections to reorder them. The recipient sees the checklist in the same order. ## Remove items and sections Click the remove icon on an item or section. If it holds files you've already attached and saved, Pipefile asks you to confirm by typing `DELETE`, because those attachments are deleted when you save. Removing a section removes the items inside it. {% hint style="warning" %} On a request that's already been sent, removing an item the recipient has uploaded to also removes those uploads. Pipefile warns you before saving. Download anything you need first. {% endhint %} ## Turn an attachment into a fillable form On plans with forms, a PDF attached to an item can be made fillable, with fields for the recipient to complete and sign in the browser. See [Fillable forms](/forms-and-esignature/fillable-forms.md) and [E-signature](/forms-and-esignature/e-signature.md). ## Reuse a checklist Save any request as a template, from **Save as Template** in the **Send Request** dialog or **More options** > **Save as template** on a request's page. See [Create and edit templates](/templates/create-and-edit-templates.md). ## Related * [Open-ended requests](/requests/open-ended-requests.md) * [Understanding reviews](/reviewing-and-exporting/understanding-reviews.md) * [Upload documents to a request](/for-your-clients/upload-documents.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://support.pipefile.com/requests/checklists-and-sections.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.