# Mentor Monthly Allowance

> **Member A is eligible to receive a $150 Mentor Monthly Allowance when the following team structure requirements are met:**
>
> * Maintain **15 active members** in Layer 1, and
> * Maintain **60 active members** in total across Layer 2 and Layer 3 combined.

Once these conditions are achieved, Member A becomes eligible for the Mentor Monthly Allowance. To continue qualifying each consecutive month, Member A must demonstrate consistent team growth that meets or exceeds the required growth rate for their rank.

***

## Allowance Tiers

The monthly bonus amount is determined by the mentor's team size across all three layers. Higher team volumes unlock larger bonuses with adjusted growth requirements.

| First Layer Active Downlines | Second & Third Layers Active Downlines | Monthly Bonus | Monthly Growth Requirement |
| :--------------------------: | :------------------------------------: | :-----------: | :------------------------: |
|              15              |                   60                   |      $150     |             35%            |
|              25              |                   160                  |      $300     |             35%            |
|              30              |                   500                  |      $500     |             30%            |
|              50              |                  1,000                 |      $900     |             25%            |
|              60              |                  1,800                 |     $1,500    |             25%            |
|              80              |                  3,600                 |     $3,000    |             20%            |

{% hint style="info" %}
**Growth Calculation Example:** A mentor with 100 total team members at a 35% growth requirement must recruit at least **35 new members** that month (100 × 35% = 35), bringing the team total to **135 or more** to qualify for the full allowance.
{% endhint %}

***

## Eligibility & Performance Policy

### 1. Monthly Growth Requirement

To remain eligible for the Mentor Management Allowance, mentors must meet the **required monthly team growth rate** for their respective rank each month.

Monthly growth is calculated based on the **total number of team members across all three layers** (First Layer + Second Layer + Third Layer).

***

### 2. Performance Incentive

Mentors who exceed the **high-performance growth threshold (e.g., 55%)** in a given month qualify for an **additional performance incentive of 200 – 1,200 USDT**, based on their performance level and rank.

{% hint style="success" %}
This incentive is designed to reward exceptional leadership and accelerated team expansion.
{% endhint %}

**Performance Incentive Example**

A mentor starts the month with 100 team members, and the high-performance threshold is 55%:

$$100 \times 55% = 55 \text{ new members required}$$

| Starting Members | Members to Add | Minimum End-of-Month Total |
| :--------------: | :------------: | :------------------------: |
|        100       |       55+      |            155+            |

If the team **exceeds 155 members** by month-end, the mentor qualifies for the additional performance incentive.

***

### 3. Growth Buffer Zone

To protect mentors from short-term fluctuations, the platform applies a **Growth Buffer Zone** — a partial allowance protection mechanism.

Rather than an immediate rank downgrade for missing the target by a small margin, mentors falling within the buffer range receive a **partial allowance**.

| Monthly Growth Rate |          Outcome         |
| :-----------------: | :----------------------: |
|        ≥ 35%        |     ✅ 100% allowance     |
|      30% – 34%      | ⚠️ 50% partial allowance |
|        < 30%        |  ❌ Rank downgrade review |

***

### 4. Evaluation Period & Distribution Cycle

#### Assessment Period

* Performance is evaluated every month
* Evaluation runs from the **1st to the last calendar day** of each month
* All team data is finalized at **23:59 (system time)** on the last day of the month

#### Application Window

| Stage              | Timing                           |
| ------------------ | -------------------------------- |
| Application opens  | Last day of the assessment month |
| Application closes | 5th day of the following month   |

{% hint style="warning" %}
Applications submitted after the deadline may be deferred to the next distribution cycle.
{% endhint %}

#### Allowance Distribution

Allowances are distributed on the **20th of each month**, based on:

* ✅ Verified team growth performance
* ✅ Growth Buffer Zone evaluation (if applicable)
* ✅ Confirmed eligibility status

#### Example Timeline

| Date                    | Event                         |
| ----------------------- | ----------------------------- |
| January 1 – January 31  | Performance evaluation period |
| January 31 at 23:59     | Team growth data finalized    |
| February 1 – February 5 | Allowance application window  |
| February 20             | Allowance distributed         |

***

## Policy Objectives

This policy is built on five core principles to ensure a fair, transparent, and growth-driven environment:

| Objective                             | Description                                                            |
| ------------------------------------- | ---------------------------------------------------------------------- |
| 📈 Sustainable Growth                 | Encourage consistent and scalable team expansion                       |
| 🏆 Performance Recognition            | Reward mentors who achieve exceptional monthly results                 |
| 🛡️ Short-term Fluctuation Protection | Buffer zone prevents unfair rank drops due to minor shortfalls         |
| 🤝 Leadership Stability               | Keep experienced mentors engaged and motivated                         |
| 📋 Transparent Distribution           | Structured timelines and clear criteria for all allowance calculations |


---

# Agent Instructions: 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:

```
GET https://gloture.gitbook.io/gloture/mentor-monthly-allowance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.