> ## Documentation Index > Fetch the complete documentation index at: https://docs.denari.com/llms.txt > Use this file to discover all available pages before exploring further. # Request templates > Save the checklist you ask for every month or every year, then apply it to any client in a few clicks. Most of what a firm asks for repeats. The same payroll documents every month, the same package at year end, the same list from every new client. A **request template** is that checklist saved once and applied to any client entity, creating all of its [document requests](/portals/requests) at once. Templates are **firm-wide**. Anyone with portal access can apply one, and template names must be unique within your firm. ## Open the templates dialog On any portal page, click **Templates** in the **Document requests** header. The dialog lists your firm's saved checklists — *"Saved checklists your firm asks clients for — apply one to create its requests here."* From here you can **apply**, **delete**, or click **New template** to create one. ## Create a template The form is titled **New request template**. **Template name** is how you'll recognize it in the list — *Monthly payroll*, *Year-end package*, *New client onboarding*. Names must be unique across your firm. The **Requests** box takes a plain list. Each line becomes one request when the template is applied. Click **Save template**. It's available on every portal in your firm immediately. ### The `|` shorthand for notes A template item can carry the same optional note a hand-written request can. Add `|` after the title and everything following it becomes the note shown to the client: ``` Payroll checks for the period Payroll reports for the period | Include the client copy Bank statements | All accounts ``` That saves three requests: one plain, and two that carry a clarifying note into the client's portal. Put the qualifier that prevents a wrong upload in the note, not in the title. *Bank statements* is what the client is looking for; *All accounts* is the detail they'd otherwise get wrong. A template holds between **1 and 100** items. ## Apply a template Applying is always scoped to the portal you started from — the dialog is titled **Apply "template name" — client entity name** so you can confirm it. Every item starts checked. *"Uncheck anything that doesn't apply here. Each checked item becomes an open request."* The button counts what you've kept — **Send 5 requests**. Each checked item becomes an **Open** request on that client's portal. **Pruning never changes the template.** Unchecking items tailors this one application; the saved checklist is untouched and the next client still gets the full list. That's what makes one slightly-too-long template better than five nearly-identical ones. ## After applying The requests behave exactly like ones you typed by hand — same four statuses, same review actions, same **Waiting on you** list for the client. See [Document requests](/portals/requests). Applying a template twice to the same portal creates a second copy of every checked item; it does not merge with what's already there. If you re-apply after a client has partly responded, uncheck the items they've already sent. ## Delete a template Each row in the templates list has a delete action. Deleting removes the template from your firm's list — **requests already created from it are unaffected** and stay on their portals. Build templates around a cadence, not a client: *Monthly bookkeeping*, *Quarterly payroll*, *Year-end tax*. A per-client template drifts out of date the moment that engagement changes, while a per-cadence one gets pruned at apply time and stays useful for everyone. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.