> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/mts/features/timeframe-tournament-ratings.md).

# Timeframe Tournament Ratings

Timeframe tournament ratings (TFTR) is an MTS and ITS feature that gives the traders more control over tournament ratings during the pre-kickoff period. Using the TFTR options, they can set 10 different tournament ratings to be applied on events in different timeframes before the match start.

Configuring different ratings for different timeframes allows for more careful approach on volatile tournaments where events are published far in advance and markets can be exposed to heavy movements. &#x20;

<table><thead><tr><th width="340.58148193359375">Currently supported timeframes</th></tr></thead><tbody><tr><td>Publication time</td></tr><tr><td>14 days before the kickoff</td></tr><tr><td>7 days before the kickoff</td></tr><tr><td>3 days before the kickoff</td></tr><tr><td>2 days before the kickoff</td></tr><tr><td>1 day before the kickoff</td></tr><tr><td>12 hours before the kickoff</td></tr><tr><td>6 hours before the kickoff</td></tr><tr><td>3 hours before the kickoff</td></tr><tr><td>1 hour before the kickoff</td></tr></tbody></table>


---

# 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://docs.sportradar.com/mts/features/timeframe-tournament-ratings.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.
