> 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-dayparts-for-plansmart.md).

# Configure dayparts for PlanSmart

Set up daypart rules so PlanSmart can plan work more precisely across the day.

Dayparts let you add extra planning rules for parts of the day.

Use them when morning, afternoon, or evening matters for route planning.

### What you can do with dayparts

You can:

* import existing dayparts
* create new daypart definitions
* set active days per daypart
* apply time-based planning preferences

{% stepper %}
{% step %}

### Open the Dayparts step

Go to **Settings → PlanSmart**.

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

{% step %}

### Review existing dayparts

Check whether dayparts already exist in your environment.
{% endstep %}

{% step %}

### Import or manage dayparts

Import existing dayparts.

Or open the management screen to add new ones.
{% endstep %}

{% step %}

### Set the daypart values

Define the code, name, active days, and enabled status.
{% endstep %}

{% step %}

### Save the setup

Save the daypart configuration.
{% endstep %}
{% endstepper %}

### Frequently asked questions

<details>

<summary>Why should I use dayparts?</summary>

They help when certain work should happen only in specific parts of the day.

</details>

<details>

<summary>Are dayparts employee-specific?</summary>

No.

They apply to the planning model, not to one employee only.

</details>

<details>

<summary>What happens if a work order has no daypart?</summary>

It is planned without a daypart restriction.

</details>

### Related topics

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


---

# 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-dayparts-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.
