> 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/translating-work-orders-to-another-language.md).
# Translating Work Orders to Another Language
Translate work orders using browser translation tools or add manual crew notes in another language for your team.
## Option 1: Use the Google Translate Chrome Extension
[Google Translate for Chrome](https://chromewebstore.google.com/detail/google-translate/aapbdbdomjkkjkaonfhkkikfgjllcleb)
Once you have downloaded the extension, here's how to translate your page!
Here are some notes about it:
* Downloading or Sending links to Work Orders would *not* have the translations... It's only on the browser that you have the translator running. You should be able to print with the translations on though.
* We aren’t liable for any of the translations. They would be provided by Google Translate, which we have no control over. It's just doing the same thing as copying/pasting text into
## Option 2: Add a Crew Note in another language
You can add a crew note to any production rate or line item.
These notes will only show on the work order for your team to see.
Here are some notes about it:
* You are manually adding the translations to the crew notes. It won't automatically translate the area label or product etc.
* You won't really be able to avoid *some* English on the page.\
---
# 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/translating-work-orders-to-another-language.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.
