> For the complete documentation index, see [llms.txt](https://docs.cottfile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cottfile.com/clerk-guide/printing.md). # Printing Court clerks frequently need printed copies of filed documents for physical case files, judge chambers, or in-court proceedings. The **Print Queue** page (from the **Printing** link in the sidebar) is where you batch and print them: "Select documents and print them in batch." ## The Two Tabs * **Queue (N)** -- Documents waiting to be printed. * **Printed (N)** -- Documents you have already printed. Each card in the queue shows the file name, filing number, case number, document type, page count, filer name, and when it was queued. The sidebar badge on the **Printing** link shows how many items are waiting. ## Adding Documents to the Print Queue * **From the review screen** -- In the Actions step, use **Send to Printer** and click **Add N document(s) to Print Queue**. Documents already in the queue are not duplicated. * **From the case view** -- Click **Send to Printer** in the case-view header to queue all non-rejected documents on the case. * **At standalone parishes**, accepted and judge-signed documents are added to your print queue automatically -- see [Standalone Parishes](/clerk-guide/standalone-parishes.md). ## Printing 1. Select the documents you want (or none, to print everything). 2. Click **Print All (N)** or **Print Selected (N)**. The selected documents are combined into **one PDF** and your browser's print dialog opens. As soon as the dialog opens, the documents are **marked as printed automatically** and move to the Printed tab -- there is no separate "Mark as Printed" step. If the dialog fails to open, you'll see: "Couldn't open the print dialog. Nothing was marked as printed -- try again." {% hint style="info" %} **📹 GIF:** The Print Queue page -- selecting several documents, clicking Print Selected, the combined PDF opening in the browser print dialog, and the documents moving to the Printed tab automatically. {% endhint %} ## Managing the Queue * **Drag cards to set print order.** The combined PDF prints in the order shown. * **Remove (N)** -- Takes selected items out of the queue, after a confirmation ("...will be removed. This cannot be undone."). * **Clear selection** -- Deselects everything. * **Preview** -- Click any card to open a preview panel, with **Previous**/**Next** to step through the queue. ## The Printed Tab * **Reprint All** / **Reprint Selected** -- Print again; the documents stay in the Printed tab. * **Remove (N)** -- Remove selected printed items. * **Clear All (N)** -- Empty the Printed tab. ## What the Printed Copy Looks Like * A document queued **before** acceptance prints with the stamp you placed on it in the review screen; if you placed none, it prints with the default FILED stamp. * Originals that were split and documents that were replaced are left out -- only the current version prints. * Print order matches the order of the cards in your queue. ## Printing Tips * **Scale to fit** -- Court stamps are positioned relative to the page. If you scale the print, the stamp scales with it. * **Color vs. grayscale** -- Court stamps include the court name, date, and recording number. Print in color if your court requires color stamps on official copies. * **Duplex printing** -- For multi-page documents, enable double-sided printing to reduce paper use. * **Multiple copies** -- Set the copy count in your browser's print dialog rather than printing the same batch twice. --- # 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.cottfile.com/clerk-guide/printing.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.