> For the complete documentation index, see [llms.txt](https://docs.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/operations/service-orders/maintain-service-order.md).
# Maintain Service Orders
Changes to a service order are done from the drawer that opens after [creating](/release-8.31/voyage-management-system/step-by-step-guides/operations/service-orders/create-service-order.md) a service order.
To maintain an already existing service order, open the **Operations**
**Service Orders** module and click the order you want to change. It will now open in the drawer.
## Editing an order
### Order details
You can change order date, supplier and cost details under "Order Details".
The total cost of the order lines are calculated for estimate (advanced).
### Order reference
1. Click the more icon
at top right.
2. Select **Edit order reference**.
3. Make changes to the reference in the window.
4. Click **Save**.
### Status
You can change the status of the order at all times. There are three statuses, "Estimate", "Revised", and "Final".
Changing the status will also change the value from which the amount is derived. For "Estimated" status, the amount comes from the "Estimated" column. For "Revised" status, it comes from the "Revised" column, and so on.
1. Click the status label at the top of the drawer next to the order reference.
2. Select desired status.
## Creating order lines
Click 
in the "Order Lines" section to create a new order line.
{% hint style="info" %}
**Tip:** You cannot set the revised and final cost of an order line until after it has been created. Open an already created order line from the list to set these values.
{% endhint %}
## Handling Cost Lines
Read more about these specific service order lines here: [#handling-cost-lines](#handling-cost-lines "mention").
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/operations/service-orders/maintain-service-order.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 `build a script that syncs our docs to a CMS` 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.