> 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/operation-blocks.md).
# Operation Blocks
Operation blocks are a unique way for you to block off a court/table to stop Customers from reserving. Operations are used as a means to perform maintenance, either on the court/table or because of something around the court/table. To block off a court/table, or multiple courts/tables:
* Create an Event like you would in an other situation
* Choose Internal, and then `Operations > Internal`
* Select the courts/tables you want to block off
* Write any internal notes on the reason why the court/table is blocked off
* Book the Operation Event
Customers will not be able to select any of the courts/tables which are blocked off.
Customers cannot be added to the Operation blocks, so if an Admin wants to hold courts for a Private Event, they should create the Private Event. Private Events are by default Unlisted and not visible for Customers to sign-up. If an Admin wants to hold courts for an Event like an Open Play or a Clinic, the Admin should leave the Event as a draft and publish when they're ready.
{% hint style="danger" %}
**Operation blocks are NOT Event placeholders.**
{% endhint %}
### Impact of Operation Blocks
Operation Events will not be reflected on your revenue in the Analytics page of the Dashboard. This ensures they do not negatively or incorrectly impact your court utilization metrics. The system will exclude Operation blocks so that it does not interfere with Analytics (e.g. the court utilization).
---
# 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/operation-blocks.md?ask=&goal=
```
`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.