> 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/general-mobile-app/complete-a-work-order.md).

# Complete a work order

Employees complete work orders from the mobile app.

They open the planned job, register the work, and send it back to the **BackOffice**.

{% hint style="info" %}
This page covers the shared mobile flow.

Use it for cross-platform guidance.

For screen-specific steps, use [iOS - OutSmart App](/mobile-app/ios-outsmart-app.md) or [Android - OutSmart NEXT](/mobile-app/android-outsmart-next.md).
{% endhint %}

### What can be registered on a work order

A work order can include:

* hours for travel time and working time
* materials and items used on site
* photos, files, notes, and comments
* forms and inspection checklists
* a customer signature
* linked objects or assets

### Complete the work order

{% stepper %}
{% step %}

### Open the work order

Open the app and choose the correct work order from the overview.

Planned work appears after synchronisation.
{% endstep %}

{% step %}

### Review the details

Check the customer address, work description, and any existing information.
{% endstep %}

{% step %}

### Start the timer

Tap **Start** when the work begins.

Choose **travel time** or **working time**.
{% endstep %}

{% step %}

### Register the work

Add materials, photos, forms, notes, files, and other job details during or after the visit.
{% endstep %}

{% step %}

### Stop the timer

Stop the timer when the work is done.
{% endstep %}

{% step %}

### Add the final confirmation

Collect a customer signature if your process requires it.
{% endstep %}

{% step %}

### Send the work order

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

{% hint style="info" %}
Your company can require specific steps before a work order can be sent.
{% endhint %}

### Why sending matters

Sending transfers the registered data back to the office.

That data can then be used for invoicing, reporting, and follow-up.

Depending on your setup, the customer can also receive the completed work order by email automatically.

### FAQ

<details>

<summary>What if I cannot send the work order?</summary>

Check whether all required steps are complete.

Your company may require photos, a form, or a signature.

</details>

<details>

<summary>Can I save my progress and continue later?</summary>

Yes. You can leave the work order and continue later.

The saved progress stays on the device until you send it.

</details>

<details>

<summary>Will the customer receive an email automatically?</summary>

That depends on your company settings.

Some setups send the completed work order automatically.

</details>

<details>

<summary>Can I add materials that are not in the catalogue?</summary>

That depends on your app settings.

Some setups allow free-text items. Others only allow catalog items.

</details>

### Related topics

* [What is the OutSmart mobile app?](/mobile-app/general-mobile-app/what-is-the-outsmart-mobile-app.md)
* [Synchronise the mobile app](/mobile-app/general-mobile-app/synchronise-the-mobile-app.md)
* [Use forms](/mobile-app/general-mobile-app/use-forms.md)
* [Add photos, files, and notes](/mobile-app/general-mobile-app/add-photos-files-and-notes.md)
* [Collect signatures](/mobile-app/general-mobile-app/collect-signatures.md)
* [Register hours](/mobile-app/general-mobile-app/register-hours.md)
* [Device policies and settings](/mobile-app/general-mobile-app/device-policies-and-settings.md)


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.out-smart.com/mobile-app/general-mobile-app/complete-a-work-order.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.