> For the complete documentation index, see [llms.txt](https://ontime.gitbook.io/v2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ontime.gitbook.io/v2/views/countdown.md).
# Countdown
{% hint style="info" %}
> [Countdown](/v2/views/countdown.md)
{% endhint %}
Imagine a case where a particular department in the building needs to keep track of a specific event. eg: the actor dressing room number 3 needs to know when it is his time to enter, he does not concern himself of any other times.
Enter Countdown view!
With this view you can choose any scheduled event, from here, ontime will keep track of its running status and either show the Running timer of the event (if running) or a countdown to the event start
{% hint style="info" %}
When calling the route `:4001/countdown` you are able to choose any of the events in the list. From here ontime will follow the event by its ID.
You can also use the direct routes `:4001/countdown?event=1` to follow an event by its order in the list (subject to change) or `:4001/countdown?eventid=test` to follow a specific event regardless of its position
This is a great workflow to pair with [URL aliases](/v2/features/url-aliases.md)
{% endhint %}
Good stuff!
---
# 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://ontime.gitbook.io/v2/views/countdown.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.