Pipeline

Pipeline is for winning the mandate

Pipeline is the workspace's shared board for players the agency is pursuing to represent. It tracks the acquisition relationship from first contact through a secured mandate, rather than tracking a transfer or other football transaction.

The Board and List are two views of the same entries. Search and lead-agent filters affect both views and the summary metrics, but they do not change which records are visible to the workspace.

A pipeline entry points to one player dossier

Add an existing Prospect from the player registry, or create a new prospect when none is available. A player can appear only once on the shared mandate pipeline; existing entries are excluded from the Add prospect control so the board does not create duplicate cards.

The card shows current player facts such as position, age and club, but the pipeline entry does not own those fields. Update identity or football context on the player dossier so every connected surface sees the same truth.

See How the player registry works →

Four stages describe mandate acquisition

Use the stage that best describes the relationship now. The standard shared pipeline uses four fixed stages; custom pipelines and stage editing are not currently exposed in the app.

Initial contact

An approach has been made and the agency is building context.

Meeting organised

A conversation is booked and preparation is underway.

Awaiting response

The next movement depends on the player or advisor responding.

Secured mandate

Authority to act has been agreed and the relationship can move into delivery.

Moving a card restarts its stage clock

Drag a card between columns or change its stage through the board interaction. A stage move records the change on the player timeline and resets Stage entered at, which powers the time-in-stage display and attention metrics.

Reordering cards inside a column changes their display order only; it does not reset the stage clock. The List can sort by time in stage, making the oldest acquisition work easy to review without altering the board.

Attention indicators expose work at risk

Summary counts are calculated from the entries currently included by your search and lead-agent filter. They highlight likely follow-up rather than changing a stage or creating a task automatically.

Need follow-up

Non-secured entries in the current view that have spent at least three days in stage.

Unassigned

Entries in the current view without a lead agent.

Stale

Non-secured entries that have spent more than 14 days in the same stage.

Active prospects

Entries in the current view that have not reached Secured mandate.

Lead agent belongs to the pipeline entry

Each entry can have one current lead agent or remain Unassigned. Assignment communicates who is responsible for securing the mandate; it does not make the player private or grant additional access.

The assignment is not a global player owner. A later deal for the same player can have a different lead agent, and changing either assignment does not change the other. Existing entries remain unassigned when there is no trustworthy ownership signal rather than inventing responsibility.

Secured mandate has one deliberate player-status effect

Moving a Prospect into Secured mandate marks that player Mandated and offers an immediate Undo. Relai does not overwrite an existing Client status, and moving the card out of the secured column does not automatically downgrade the player.

Stage and player status remain separate truths after that nudge. Record the actual representation agreement on the player dossier, including its dates and any commission terms; the pipeline card alone is not the legal mandate.

Continue with the player and representation-contract workflow →

A secured mandate does not become a deal

Pipeline entries do not convert or copy forward into Deals. When a concrete transfer, loan, free move or renewal emerges, open a separate deal using the shared player dossier and add the transaction's own club, economics, stage and lead agent.

Keeping the records separate preserves the difference between relationship acquisition and transaction execution. It also allows a player to have several historical or active deals without duplicating the mandate pursuit.

See How deals work →