> For the complete documentation index, see [llms.txt](https://help.urbanpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.urbanpiper.com/business-manager/setting-up-schedules-for-locations.md).

# Setting up Schedules for Locations

{% embed url="<https://urbanpiper.portal.trainn.co/share/3ykCkZHVj88v5NtJCLz2QA>" %}

## How to Create Associate Schedules for Operating Hours at a Location

In this guide, we will learn how to create schedules to set the operating hours for a given location. Follow these steps to create and associate schedules effectively.

1. **Navigate to Schedules:**
   * On the navigation section, click on **Groups**.
   * Then, click on **Schedules**.
2. **Create a New Schedule:**
   * Click on **Regular Schedules** and then **Create New**.
   * Enter the name of the schedule.
   * Click on **Next** to proceed.
3. **Add Timings:**
   * Select the type of schedule: **Daily**, **Weekdays**, **Weekend**, or **Custom**.
   * Select the open and close time.
   * You can choose to add further timings if applicable.
   * Once the timings are created, click on **Save**.
4. **Associate Locations:**
   * Click on **Associate Your First Location**.
   * Select the list of locations you want to associate with the schedule.
   * Click on **Update** to finalize the association.

Now, the schedule has been successfully created and associated with the selected location. Thank you for following this guide!


---

# 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://help.urbanpiper.com/business-manager/setting-up-schedules-for-locations.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.