> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/events/sign-up-for-an-event/booking-horizon-for-events.md).

# Booking Horizon for Events

Normally, [**the Booking Horizon**](https://help.podplay.app/en/articles/831745) only applies to limiting the number of days out a Customer can book a Reservation, not an Event. When an Event is published as “Listed in app,” it will be visible to all Customers, whether Members or Non-members.

Events are published at 12 pm, noon, local time to the Club’s location. Meaning, if the Booking Horizon for a Member is 14 days, they will be able to see their 14th day in the future at 12 pm, noon, today. This is different from the “last day” of a Booking Horizon for Reservations, which becomes available at 12 am, midnight.

* To publish an Event and not have the Event visible to the Customer, the [**Schedule feature**](/events/sign-up-for-an-event/how-to-schedule-events-to-auto-publish-and-copy-them.md) can be leveraged
  * This will make the Event visible to Members before Non-members (or visible to both at the same time)
  * This is not the same as creating a Members-only Event. Which to accomplish, you can learn with this article:
    * [**Can I create a Members-only Event?**](/events/sign-up-for-an-event/can-i-create-a-members-only-event.md)
* If you would like to allow Customers to see an Event and restrict them from signing up, you can use the [**FOMO feature**](broken://pages/rgHpKfdEW3Kkv2jdrTrv)


---

# 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://docs.podplay.app/events/sign-up-for-an-event/booking-horizon-for-events.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.