FPDSFootball Player Data Standard

Consultations / Wages

Consultation ยท OQ-2

Does a player submission include information about wages?

Wages decide many transfers before a club talks about a fee. Wages are also the most private number in football. We want to know if FPDS includes any information about them.

Status
Open
Open for
At least 14 days
Who can answer
Agents, intermediaries, club staff, players, and other people who are 18 or older
Time
About three minutes
FPDS now
A submission contains no information about wages

Why this question matters

A club with a wage limit cannot sign a player who earns more than that limit. If the club finds this out late, all parties lose time.

Some agencies say that they cannot use a standard that asks for wages. For this reason, this question has the largest effect on whether agents use FPDS.

Reasons to include wage information

  • A club knows early if a player is in its wage range.
  • Fewer talks start and then stop because of money.
  • A range tells the club enough and keeps the exact amount private.

Reasons to leave it out

  • Wages are private information about the player.
  • A forwarded document can show a wage to clubs that the sender did not choose.
  • A stated expectation can weaken the position of the player in a negotiation.

Some ideas

These ideas start the discussion. They are not the only answers. Agree with one, change one, or tell us something different.

  1. A. No wage information. Parties discuss wages outside the submission.
  2. B. A yes or no question. "Is the player open to a lower wage?"
  3. C. An expected range. A wide band, for example a range of annual wages, not an exact amount.
  4. D. The current wage. The exact amount, with its source.

Give your answer

Write your answer in your own words.

Read the privacy notice before you answer. Do not write the wage of a specific person in your answer.

What happens next

  1. The consultation stays open for at least 14 days.
  2. We publish a summary on this page. The summary shows the number of answers from each role, and the main reasons on each side. It does not show names.
  3. We record the decision and its reasons in the decision log.

Developers can also discuss this question on GitHub.