Jordan Mensah
21 · LB / LWB · Halton Town
Position, age, availability and deal type all match.
Strong Shortlisted
Feature Club Requirements
Match the brief. Keep the judgement human.
Record what a club needs, compare the approved brief with your player registry and see why each player does or does not fit. Relai structures the evidence. Your agency decides what happens next.
Explainable matches. No automatic shortlist. No Deal without a human decision.
Club Requirement
Borchester Rovers · Left-back
Approved brief
Summer 2027 · owned by Andy C.
- Position
- Left-back
- Age
- Under 24
- Deal type
- Loan or transfer
- Priority
- High
Must have
- Match fit
- Available this window
- Authority checked separately
Registry scan
Every eligible player checked against the same brief.
2 strong3 possible
Malik Rowan
23 · LB · AFC Northbridge
Matches the role and age profile. Availability is recorded.
Strong
Elliot Wade
22 · LWB · Kingsport Athletic
Role is adjacent. Preferred system is not recorded.
Possible
One brief, one decision trail
Approved brief
Keep the club's actual need together.
Record the position, age profile, window, deal types and budget only after someone approves the brief.
Registry scan
Check every eligible player consistently.
Relai compares the requirement with every non-Former player and explains Strong, Possible and Not currently a match results.
Human decision
Keep fit separate from authority to act.
A match is evidence, not a recommendation. The agency chooses who to shortlist, share, pitch or discuss with the club.
Follow-through
Move from brief to accountable action.
Record the shortlist, Player Pack, pitch and outcome. Open a Deal only when the interest becomes actionable.
Workflow
01
Approve the requirement
Review the club, profile, timing and commercial boundaries before the brief becomes shared data.
02
Read every match
See the fit result and its reasons. Missing evidence stays visible instead of becoming a confident score.
03
Choose the next action
Shortlist, prepare a Player Pack, record a pitch or open a Deal when interest becomes actionable.
The difference
A requirement is useful only when the reasoning survives.
JobWithout RelaiWith Relai
Keep the club brief
A message or memory
One approved requirement
Check the roster
Ask around player by player
Every eligible player scanned
Understand fit
A hidden score
Reasons and missing evidence
Decide who to pitch
Fit implies action
A separate human shortlist
Frequently asked questions
Does Relai recommend which player I should pitch?
No. Relai explains how each registry player compares with the approved requirement. Your agency decides whether the fit and authority are strong enough to act.
Does every new message start a registry scan?
No. A captured message can produce a proposal, but no requirement or scan becomes shared workspace data until a person reviews and accepts it.
Can I keep players outside the shortlist?
Yes. The scan keeps Strong, Possible and Not currently a match results visible. The shortlist remains a separate human choice.
When should a Club Requirement become a Deal?
Open a Deal only when interest in a named player-club case becomes actionable. The requirement remains the record of the wider club brief.
Give every club brief a reasoned next step.
Keep requirements, player matches, shortlists, pitches and outcomes in one accountable workspace.