Transfer Agreements - Club achievements
1. Player Registration
The Player Registration Condition is a critical logic layer added to all Club Performance-based clauses to define exactly when a player must be associated with the club for a financial trigger to be valid. These conditions ensure that payouts for team achievements are only made if the specific player meets the contractually agreed-upon registration status during that success.

Even if a club is successful, they may not owe a payment if the player wasn't officially "registered" or "on the books" according to the specific wording of the contract.
1.1. Applicable Clauses
The registration conditions and loan toggles are integrated into the following club-level performance triggers:
-
Club finishes Xth in the league
-
Club finishes Xth or higher in the league
-
Club qualifies for Y international competition in a season
-
Club gains promotion from a league
-
Club avoids relegation from a league
-
Club progresses in cup competitions
1.2. Registration Condition Logic
The "Player registration condition" field is a required selectbox that dictates the timing of the player's eligibility for the clause.
| Option | Description |
| Registered with the club at time of achievement | The player must be officially registered on the exact date the achievement is secured. |
| Registered with the club during season of achievement | The player is eligible if they were registered at any point during the season the achievement occurred. |
| Registered with club at specific date in the season of achievement | The player must be registered on a set calendar date during that season. |
Specific Date Configuration
When the "Specific Date" option is selected, a new required date field appears. To ensure the clause remains non-season specific and can recur across multiple years, the user specifies only the day and month (e.g., August 31st), excluding the year.
1.3. Loan Status Tracking
To handle players who may be achieving success while away from their parent club, a new toggle has been introduced:
-
Field Name: "Include loaned or temporarily registered players" (or "Applies to players who are loaned out or temporarily registered at another club").
-
Default State: Switched OFF by default.
-
Function: This toggle enables the platform to track and trigger club-performance achievements even for players who are currently out on loan, provided the parent club meets the performance criteria.
2. League Position: Exact or Higher
In ContingencyAI, league finish position clauses are Club Achievement triggers that depend on the club’s final standing at the end of a season. These clauses are commonly used to reward the selling club if the player’s new team performs exceptionally well.

2.1. Finish on Xth Position in League
This is a "precise" clause. The bonus only triggers if the club finishes in a specific, exact spot.
-
How it works: The system monitors the official league table at the conclusion of the season.
-
Triggering: If the requirement is to win the league, and the club finishes 1st, the payment is triggered. If they finish 2nd, the bonus is not paid.
-
Typical Use: Used for specific milestones like winning the championship or finishing in a specific qualifying spot.
2.2. Finish on X Position or Higher
This is a "range" clause and is much more common in football contracts. It triggers if the club finishes at or above a certain rank.
-
How it works: You set a numerical threshold (e.g., "4th").
-
Triggering: The bonus triggers if the club finishes 1st, 2nd, 3rd, or 4th. If they finish 5th, the payout is not made.
-
Typical Use: Used for broad targets like "Qualifying for the Champions League" (Top 4) or "European Qualification" (Top 6).
2.3. Key Rules for Both Clauses
-
Official Confirmation: These clauses only trigger once the league season is officially finished and the final table is confirmed by the data provider.
-
Player Registration Check: Even if the club finishes in the required position, the Player Registration Condition (mentioned earlier) must also be met.
-
Example: If the player was sold mid-season and the clause requires them to be registered "At the Time of Achievement," the bonus won't trigger even if the club finishes 1st.
-
-
Competition Specific: You must select the specific league (e.g., "Premier League") that the clause applies to. Finishing 1st in a Cup competition will not trigger a "League Position" bonus.
3. Qualification for Continental Competition
Unlike performance clauses that rely on individual player stats, this clause monitors the club’s final status at the end of a season.
-
Logic: The system checks if the club’s final league position or cup success officially qualifies them for the selected competition (e.g., finishing in the top 4 of the Premier League to qualify for the Champions League).
-
Data Source: The system uses official league and tournament data to confirm which teams have secured a place for the following season.
3.1. Clause Configuration

The configuration form for this clause includes parameters to define the specific tournament and the player's eligibility:
| Field | Description |
| Covers season(s) starting | Dropdown to select the specific years the clause applies to (e.g., 2019, 2024). |
| Player registration condition | Required field to specify the player's status at the time of achievement (e.g., "Registered with the club at time of achievement"). |
| Loan Status Toggle | "Applicable to players who are loaned out or temporarily registered at another club" (Default: OFF). |
| Condition can be triggered | Defines the frequency of the trigger (e.g., "Once per season"). |
| Qualifying competitions | Multi-select dropdown featuring continental tournaments such as UEFA Champions League, AFC Cup, and CAF Champions League. |
3.2. Triggering and Payouts
-
The Trigger Moment: The payment is triggered the moment the qualification becomes mathematically certain or is officially confirmed at the end of the season.
-
One-Time or Recurring: Depending on the recurrence settings, a club can get paid every time they qualify (Season Isolated = ON) or just the first time it happens.
4. Progress in Cup Competition
The "Progress in Competition" clause is a Club Achievement trigger that pays out when a team reaches a specific stage or "round" in a tournament (usually a knockout cup like the FA Cup, Champions League, or World Cup).

4.1. How it Works
Unlike league-based clauses that wait for the final table, this clause triggers the moment the club's advancement to a specific round is confirmed.
-
Logic: The system monitors the tournament tree. If the clause is set for "Quarter-Finals," the system identifies when the club successfully wins their Round of 16 tie and moves into the last eight.
-
Target Stage: You define exactly which milestone triggers the payment. Common stages include:
-
Group Stage Qualification
-
Round of 16 / Round of 32
-
Quarter-Finals / Semi-Finals
-
Final
-
Overall Winner
-
4.2. Multi-Stage Payouts
Contracts often have "stepped" progression bonuses. For example:
-
Reach Quarter-Finals: £100,000
-
Reach Semi-Finals: + £150,000
-
Reach Final: + £250,000
-
Win the Tournament: + £500,000
In ContingencyAI, these can be set up as a complex expression clause with the following structure: <Reach Quarter-Finals: £100,000> OR <Reach Semi-Finals: + £150,000>. The system automatically detects each event and triggers the corresponding payment.
4.3. Key Settings and Integration
-
Player Registration: Just like other club achievements, the player must meet the Registration Condition for the bonus to trigger.
-
Integration with Matches: The system identifies the "Trigger Date" based on the specific match that secured the progression.
-
Example: If a club wins their 2nd-leg Round of 16 match on March 12th to advance to the Quarter-Finals, the trigger date for the "Progress to Quarter-Finals" bonus will be March 12th.
-
5. Promotion
The "Got Promoted" clause is a Club Achievement trigger that pays out when the player's new club successfully moves up to a higher division. This is a common bonus in transfer contracts for players joining teams in lower leagues. It tracks whether the club has secured advancement from their current league to a higher division within a specified season.

5.1. How the Clause is Set Up
When a user or support representative sets up a promotion clause:
-
Select Condition: Choose the "Got Promoted" condition type.
-
Target Competition: Select the specific league the club to be promoted to in (e.g., "The Championship").
-
Recurrence Settings:
-
Once across all seasons: The payout triggers only the first time the club gets promoted.
-
Once per season: The payout could trigger again if the club were relegated and then promoted back up in a future season (if Season Isolated is ON).
-
5.2. Triggering Logic: How the System "Knows"
The system does not just look for a "1st place" finish; it tracks multiple ways a club can be promoted:
-
Automatic Promotion: The system identifies if the club finishes in a top-table position that guarantees promotion (e.g., Top 2 in many leagues).
-
Play-off Success: If the league has a play-off system (e.g., the EFL Championship Play-off Final), the system tracks the outcome of those final matches. The bonus will trigger the moment the play-off win is confirmed.
-
Official Confirmation: The payment is triggered as soon as promotion becomes mathematically certain or is officially finalized by the league's data provider at the end of the season.
5.3. Player Registration
Even if the club celebrates promotion, the Player Registration Condition must be met for the payment to be valid:
-
Registration Check: If the clause is set to "At the Time of Achievement," and the player was sold or their contract ended before the promotion was secured, the bonus will not trigger.
-
Registration Check: If the clause is "Anytime during the season," the bonus will trigger even if the player left mid-way through the promotion-winning campaign.
5.4. Trigger Date
The system sets the Trigger Date of the payment based on the specific match or the date the promotion was officially achieved.
-
Example: If a club wins a match on May 4th that mathematically guarantees they cannot be overtaken in the promotion spots, the trigger date will be May 4th.
6. Surviving Relegation
This clause pays out when a club successfully remains in their current division at the end of a season, rather than being demoted to a lower league. This is a common safety clause for clubs buying expensive players while fighting to stay in a top division.

6.1. How the Clause is Set Up
When a user or support representative sets up an avoided relegation clause:
-
Select Condition: Choose the "Avoided Relegation" condition type.
-
Target Competition: Select the specific league the club is currently in (e.g., "Premier League").
-
Recurrence Settings:
-
Once per season (locked): The bonus can trigger every year the club stays up.
-
6.2. Triggering Logic: "When is Relegation Avoided?"
The system uses official league data to determine when a club is safe. It identifies success in two ways:
-
Mathematical Safety: The system triggers as soon as it becomes impossible for the club to finish in the relegation zone, even if there are matches left to play.
-
End of Season Confirmation: If safety is only secured on the final day, the bonus triggers once the final league table is confirmed.
-
Play-off Survival: If a league uses a "relegation play-off" (where a team from the top league plays a team from the lower league), the system tracks those results. Safety is only confirmed once the play-off win is finalized.
6.3. Player Registration
Just like other club achievement clauses, the Player Registration Condition must be met for the payment to be valid.
6.4. Trigger Date
The system sets the Trigger Date of the payment to the exact day the club's safety was officially confirmed.
-
Example: If a club wins a match on May 10th that guarantees they cannot be relegated, the trigger date for the "Avoided Relegation" bonus will be May 10th.