By Onkar Jadhav · 8 min read
What a cricket player profile should actually hold.
For amateur cricket, a player profile is the thread that connects a registration form to an auction lot to a scorecard line. Here is the field list that makes that work, and the ones that only look useful.
What should a cricket player profile hold?
A cricket player profile for local cricket holds four groups of fields: identity (name, photo, mobile number), playing attributes (role, batting hand, bowling style), tournament history (which squads they have played for and the matches they appeared in), and auction history (base price, who signed them and for how much, in each season). The mobile number is the key that keeps the same player joined across all four.
Four groups of fields
| Group | Fields | Where it comes from |
|---|---|---|
| Identity | Name, photo, mobile number | Registration |
| Playing attributes | Role, batting hand, bowling style | Registration, refined by the organizer |
| Tournament history | Squads played for, matches appeared in | Scoring, per match |
| Auction history | Base price, sold or unsold, buying team, price paid | The auction, per season |
The mobile number is the key that holds all four together across seasons. Everything else can change spelling, role or team; the number is what makes a returning player the same player.
Auction history is the part nobody keeps
For amateur cricket this is the most interesting thing on a profile and almost no system stores it. Across two or three seasons, a player’s auction record is the most honest available measure of how their own local pool values them: what tier they were placed in, whether they sold, who bought them and for how much.
It is also directly useful to the organizer. Last season’s prices are the best starting point for this season’s base-price tiers, far better than an organizer’s impression of who is good. How to categorise a pool.
What to publish and what to keep private
Publish the playing record. Keep the contact details private.
- Public: name, photo, role, teams played for, batting and bowling aggregates, auction history.
- Private: mobile number, email, address, date of birth.
Fields that look useful and are not
Three that get added to profiles and never used:
- A skill rating out of ten. Someone has to maintain it, nobody does, and a stale rating attached to a named person is worse than none. Base-price tiers do the same job with a stated basis.
- Availability as a profile field. Availability is specific to a date, so it belongs on a match rather than a person. A profile flag set once stays set all season by accident.
- Current team as a field on the player. The single most damaging modelling choice available, because changing it erases the player’s connection to everything they did for the previous side.
Programmatic player pages on this site
This site is the information layer and holds no first-party player records, so there is no directory of named players here. The generators that build player, team, tournament, auction and match pages are implemented and wired to a provider interface, and they render nothing until a real dataset is connected.
That is a deliberate choice rather than an unfinished one. Seeding a programmatic layer with invented players would mean publishing fabricated statistics attributed to named people, which is not something worth doing for traffic. Real player records live in the platform.
Player profile FAQ
What should a local cricket player profile show?
Name and photo, playing role with batting hand and bowling style, the teams they have played for, their batting and bowling aggregates per tournament, and their auction history. For amateur cricket the auction history is the part players care about most and almost no system keeps.
How do you keep the same player joined across seasons?
Key on mobile number rather than name. A player registering for a third season will spell their own name differently from last time at least once, and name-matching silently creates a second profile with none of their history.
Should player profiles be public?
Publish the playing record and keep the contact details private. The playing history is why a player wants a profile and is reasonable to show; a mobile number on a public page collects spam and is the field a player will ask you to remove.
What is auction history on a player profile?
The record of every auction the player has been in: the base price they were listed at, whether they sold, which team signed them and the final price. Across two or three seasons it becomes the most honest available measure of how a local pool values a player.