> 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/set-up-planning-groups.md).

# Set up planning groups

Group employees for more controlled route optimization in PlanSmart.

Planning groups help you organize employees for route optimization.

Use groups when teams work by region, department, or depot.

### Why planning groups matter

Groups help PlanSmart:

* optimize within the right team
* avoid mixing unrelated resources
* keep planning more predictable

{% stepper %}
{% step %}

### Open the Groups step

Go to **Settings → PlanSmart**.

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

{% step %}

### Review existing groups

Check whether the groups match your planning structure.
{% endstep %}

{% step %}

### Add or edit a group

Create a clear group name.

Then assign the right employees.
{% endstep %}

{% step %}

### Save the group setup

Save your changes.

Then test the result in route optimization.
{% endstep %}
{% endstepper %}

### Good examples

* region-based teams
* depot-based teams
* teams with different specializations

### Frequently asked questions

<details>

<summary>Do I need planning groups?</summary>

No.

But they help when you plan with multiple teams.

</details>

<details>

<summary>Can one employee belong to more than one group?</summary>

Use the group setup that matches your planning process.

Check the available options in your environment.

</details>

<details>

<summary>When should I use groups?</summary>

Use them when employees should not be optimized together.

</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/set-up-planning-groups.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.
