The club requirement is the working record
Each requirement represents a real need from a named club. Its page keeps the approved brief, timing, responsible person, source provenance, latest registry scan and player decisions together. There is no separate opportunity record to find or maintain.
Record notes remain attached to the player, club, contact or deal they concern. They do not appear as a second kind of item in the Club Requirements workspace.
A completed scan waits for a human decision
Open Needs review
Opening a requirement does not silently mark it reviewed. Choose Mark reviewed, record that no suitable player exists today, shortlist or dismiss a player, or create an actual Player Pack Share.
Check the approved criteria and provenance
Approved means your agency confirmed that Relai may use the detail. It does not mean the club verified it. Correct the requirement when the source was interpreted too strongly; a material edit automatically queues a fresh scan.
Fit and authority answer different questions
Strong and Possible describe how recorded player facts compare with approved criteria. Not currently a match means a supported required fact conflicts with the brief. Why this match expands the evidence criterion by criterion.
Authority is shown separately. A football fit does not prove the agency may pitch the player. Relai never changes the calculated fit when an agent shortlists someone for human reasons.
Scan activity is temporary; results are durable
A match-ready Active requirement scans every non-Former player in the workspace registry. The animated activity stripe appears only while work is queued or running. When it disappears, the result remains on the requirement and Needs review remains in navigation.
Use lifecycle states that reflect the real request
Active requirements continue scanning. Filled, Expired and Withdrawn requirements move to History, stop scanning and retain their final evaluation and decisions. Reactivating one queues a fresh scan without erasing its history.
A completed linked deal prompts the responsible person to review whether the requirement is satisfied. Relai never marks it Filled automatically.
Shared conclusions do not expose private Inbox evidence
Workspace members can see the accepted requirement, approved criteria and any evidence excerpt explicitly made shareable. The original Inbox message and private captured source stay visible only to the people entitled to them.
The creator or accepting member becomes Responsible by default. The responsible person or an admin can change the requirement and assignment; the workspace can still inspect the shared record and its current results.