> 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/marketplace-packages-and-power-ups/power-ups/plansmart-ai-routeplanner/start-route-optimization-from-the-planboard.md).

# Start route optimization from the planboard

Select work orders and start a PlanSmart optimization run from the planboard.

You start route optimization from the **planboard**.

Select the work orders and let PlanSmart calculate the best route order.

### What you review before starting

PlanSmart shows an overview with:

* selected work orders
* fixed work orders
* plannable work orders
* selected resources
* work orders without coordinates
* the selected date range

{% stepper %}
{% step %}

### Open the planboard

Go to **Planning → Planboard**.
{% endstep %}

{% step %}

### Select the day or period

Choose the planning range you want to optimize.
{% endstep %}

{% step %}

### Select the work orders

Use multi-select to choose the work orders you want to include.
{% endstep %}

{% step %}

### Open PlanSmart

Click the **PlanSmart** button in the toolbar.
{% endstep %}

{% step %}

### Review the overview

Check the selected data.

Then start the optimization.
{% endstep %}

{% step %}

### Wait for the result

The progress bar shows the run status.
{% endstep %}
{% endstepper %}

### Frequently asked questions

<details>

<summary>Can I optimize existing planning?</summary>

Yes.

Existing work can be included unless it is fixed.

</details>

<details>

<summary>What happens to work orders without coordinates?</summary>

They appear in the overview and can block a clean result.

</details>

<details>

<summary>How long does an optimization take?</summary>

That depends on the number of work orders and resources.

</details>

### Related topics

* [**PlanSmart (AI Routeplanner)**](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/plansmart-ai-routeplanner.md)
* [**Review and approve route results**](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/plansmart-ai-routeplanner/review-and-approve-route-results.md)
* [**Visualize routes on the planboard**](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/plansmart-ai-routeplanner/visualize-routes-on-the-planboard.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 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/marketplace-packages-and-power-ups/power-ups/plansmart-ai-routeplanner/start-route-optimization-from-the-planboard.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.
