> For the complete documentation index, see [llms.txt](https://docs.lsports.eu/u/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lsports.eu/u/defend/risk-controls/tiers.md).

# Tiers

Set exposure limits by competition quality tier and market

Tiers sit between Sport and Competition in DEFEND's risk hierarchy: **Sport → Tier → Competition → Market**. Instead of configuring every competition one by one, group competitions that carry similar risk into the same tier and manage their limits together.

***

## Access

Navigate to **DEFEND** → **Risk Controls** → **Tiers** in the platform sidebar.

***

## How Tiers Work

A tier is a group of competitions that share the same risk profile. Every competition is automatically classified into a tier based on its market depth and pricing confidence:

| Tier       | Description                                                                                                                         |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Tier 0** | Elite / premium leagues                                                                                                             |
| **Tier 1** | Top leagues                                                                                                                         |
| **Tier 2** | Mid-tier leagues                                                                                                                    |
| **Tier 3** | Lower-liquidity leagues                                                                                                             |
| **Tier 4** | Basic / high-risk, low-quality coverage                                                                                             |
| **Tier E** | Esports and virtuals equivalents of a conventional sport (eSoccer, eBasketball, and similar) — shown only for sports that have them |

Esports titles such as Call of Duty and League of Legends belong to the **E-Games** sport and use Tiers 0-4 like any other sport. Tier E does not apply to E-Games.

LTS maintains the tier assignments and each tier's default limit, so your competitions and markets get consistent protection as your coverage grows. You can reassign a competition's tier yourself, and set your own limits at the market level — see below.

***

## Page Layout

### Sport Selector

The left-hand panel is a searchable sport selector. Selecting a sport scopes every table on the screen to that sport.

Before you open a tier, the landing view for a sport shows:

* A card for each tier (Tier 0-4, plus Tier E where applicable)
* A Competitions table listing every competition for that sport across all tiers, with an inline **Tier** dropdown so you can reassign a competition without opening its tier first

{% hint style="info" %}
The Competitions and Market Limit tables only list what you're subscribed to on your connected TRADE account.
{% endhint %}

### Tier Detail

Opening a tier shows its detail screen with two tabs:

| Tab                        | Purpose                                                                          |
| -------------------------- | -------------------------------------------------------------------------------- |
| **Market Limit** (default) | Set the tier's default limit, and market-specific limits for InPlay and PreMatch |
| **Competitions**           | View and reassign which competitions sit in this tier                            |

Switching to a different tier keeps you on whichever tab you had open.

***

## Setting Limits

### Tier Default (Lay to Lose)

Each tier carries a default **Lay to Lose** value. This is the limit that applies to any market in the tier without its own custom limit. Changing the tier default only affects markets that don't already have a custom value — markets with a custom limit are unaffected, even if the new tier default is higher or lower.

### Market-Level Limits

On the **Market Limit** tab, set a Lay to Lose value for an individual market, separately for **PreMatch** and **InPlay**. A market-level limit is always custom and takes priority over the tier default.

Filter the Market Limit table by market name, by **PreMatch** / **InPlay**, or by **New** / **Outright** status.

**Outright markets** appear in every tier's Market Limit table with their own limit, and only in the PreMatch list, since outright markets are prematch only.

### Bulk Editing

Select multiple markets with the row checkboxes (or **select all**) to apply one Lay to Lose value across all of them at once.

***

## Limit Resolution Order

When a bet is placed, DEFEND resolves the limit to enforce in this order:

1. The **market-level limit** for the bet's phase (InPlay or PreMatch)
2. The **tier's limit** for the market's competition
3. The **sport's Tier 4 limit**, as the final fallback

The first value that resolves is the one enforced. A custom market limit is always checked before any default, so it's never overridden by a tier or platform default change.

If the resolved limit is exceeded, the bet is rejected with the reason **Exceeds limit**.

***

## New Competitions and Markets

New competitions and markets get a safe default automatically, so nothing goes live unmanaged:

* A new competition lands on **Tier E** of its sport if it's an esports equivalent of a conventional sport, **Tier 4 of E-Games** if it's an E-Games title, or **Tier 4** of its own sport otherwise
* A new market inherits its tier's Lay to Lose value

Both appear with a **New** badge and are locked until LTS publishes their default configuration. The badge clears automatically 72 hours after publishing.

***

## Related

* [Platform Limits](/u/defend/risk-controls/platform-limits.md) — Global limits across your entire sportsbook
* [Player Intelligence](/u/defend/step-4-player-management.md) — Set player-specific limits


---

# 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.lsports.eu/u/defend/risk-controls/tiers.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.