> For the complete documentation index, see [llms.txt](https://help.paintscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paintscout.com/support/estimating/managing-estimates-and-work-orders/work-orders.md). # Work Orders Create, share, and translate work orders for your crew with job details, notes, and language support options. Work orders are crew-facing documents generated from your estimate content. They show your team what needs to be done without exposing customer pricing. You can control hours and notes, share the work order in several ways, and support crews who need another language. ## In This Section * [Working With Work Orders](/support/estimating/managing-estimates-and-work-orders/work-orders/working-with-work-orders.md) — Open the work order, control hours display, add crew notes, download it, and share it with your team * [Translating Work Orders to Another Language](/support/estimating/managing-estimates-and-work-orders/work-orders/translating-work-orders-to-another-language.md) — Use browser translation tools or add manual crew notes in another language for your crew --- # 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://help.paintscout.com/support/estimating/managing-estimates-and-work-orders/work-orders.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.