> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/mobile-app/ios-outsmart-app/core-functionalities/completing-and-submitting-a-work-order.md).

# Completing and submitting a work order

Review, complete, and send a work order from the iOS OutSmart App.

## Completing and submitting a work order

Complete the work order after you register the work done on site.

Send it to return the registered data to BackOffice.

### What completion can include

* hours and materials
* photos, files, and forms
* notes, signature, objects, and assets

### Complete the work order

{% stepper %}
{% step %}

### Open the work order

Open the planned job from **Overview**.

Review the address, description, and job details.
{% endstep %}

{% step %}

### Register the work

Start and stop the timer.

Add materials, photos, files, forms, and the other required details.
{% endstep %}

{% step %}

### Finish the visit

Collect a signature when your process requires it.

Check that the required parts are complete.
{% endstep %}

{% step %}

### Send the work order

Tap **Send** to return the completed work order to BackOffice.
{% endstep %}
{% endstepper %}

### Before you send

Your company can require photos, forms, hours, or a signature.

If something is missing, the work order cannot be sent yet.

### Saved progress

Your progress stays on the device until you send the work order.


---

# 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://knowledge.out-smart.com/mobile-app/ios-outsmart-app/core-functionalities/completing-and-submitting-a-work-order.md?ask=<question>&goal=<user_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.
