> For the complete documentation index, see [llms.txt](https://help.memberplyhub.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.memberplyhub.net/activities-and-schedules/create-schedules.md).

# Create one-off and weekly schedules

Open **Schedules** to manage when activities run.

## Schedule a one-off session

1. Select **Schedule activity**.
2. Choose **One-off session**.
3. Select the activity, date, start time and end time.
4. Choose the site and area, or leave the area unassigned when appropriate.
5. Configure attendance, access and payment options.
6. Save the session.

## Create a weekly schedule

1. Select **Add weekly schedule**.
2. Choose the activity and one or more days of the week.
3. Enter the start and end times.
4. Choose the site and area.
5. Set the date range and keep the schedule active.
6. Save the weekly schedule.

The weekly timetable groups active schedules by day. Editing one generated session changes only that occurrence; edit the weekly schedule to change the whole series.

Memberply prevents overlapping sessions in the same area. If a conflict appears, change the area or time, or edit the existing session first.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.memberplyhub.net/activities-and-schedules/create-schedules.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.