> 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/configure-employees-for-plansmart.md).

# Configure employees for PlanSmart

Prepare employees with the right start location and availability for route optimization.

Each employee needs the right setup before PlanSmart can include them.

### Required employee data

For each employee, check these values:

* start address
* start type
* working hours
* valid location coordinates

Without this data, PlanSmart cannot build accurate routes.

{% stepper %}
{% step %}

### Open the Employees step

Go to **Settings → PlanSmart**.

Open **Employees** in the setup wizard.
{% endstep %}

{% step %}

### Review employee readiness

Check which employees are marked as ready.

Look for missing start location data.
{% endstep %}

{% step %}

### Open an employee

Click the employee you want to edit.
{% endstep %}

{% step %}

### Set the start type

Choose whether the employee starts from **Home** or **Depot**.
{% endstep %}

{% step %}

### Enter the start address

Fill in the full address.

Then save the employee.
{% endstep %}

{% step %}

### Confirm the coordinates

Check that the location data is retrieved correctly.
{% endstep %}
{% endstepper %}

### Frequently asked questions

<details>

<summary>Why is an employee not marked as ready?</summary>

The start address is missing or the coordinates are not valid.

</details>

<details>

<summary>Can I exclude employees from PlanSmart?</summary>

Yes.

Employees without a complete setup are not included.

</details>

<details>

<summary>What is the difference between Home and Depot?</summary>

**Home** starts from the employee address.

**Depot** starts from a shared location.

</details>

### Related topics

* [**PlanSmart (AI Routeplanner)**](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/plansmart-ai-routeplanner.md)
* [**Set working hours and availability**](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/plansmart-ai-routeplanner/set-working-hours-and-availability.md)
* [**Set up PlanSmart with the setup wizard**](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/plansmart-ai-routeplanner/set-up-plansmart-with-the-setup-wizard.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/configure-employees-for-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.
