> 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/introduction-to-plansmart.md).

# Introduction to PlanSmart

Understand what PlanSmart does and how it improves route planning in OutSmart.

**PlanSmart** is the AI route optimization feature in OutSmart.

It helps you plan field work more efficiently.

PlanSmart calculates the best route order for work orders.

It uses travel time, distance, and employee availability.

### What you do with PlanSmart

* optimize daily routes automatically
* reduce travel time and fuel use
* balance work more effectively across employees

### What you need first

Before you start, make sure you have:

* an active **Planning AI** Power-Up
* employees with a valid start location
* working hours and availability set up
* work orders with usable address data

### How PlanSmart works

The basic flow is simple:

1. Activate PlanSmart.
2. Complete the setup wizard.
3. Select work orders on the planboard.
4. Start route optimization.
5. Review and approve the result.

### Important to know

* PlanSmart works best with complete address data.
* Missing coordinates can block or weaken results.
* Employee schedules directly affect route feasibility.

### Related topics

* [**PlanSmart (AI Routeplanner)**](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/plansmart-ai-routeplanner.md)
* [**OutSmart packages**](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/marketplace/outsmart-packages.md)
* [**Power-Ups**](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups.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/introduction-to-plansmart.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.
