Scenario 5: a transfer started, refused, revised and approved, with the full history. Govern's Deregistration Requests with the type Transfer, as it exists, plus a receiving club on the request. Four views along the chain: the club, the district queue, the request after the return and the resubmission, and the approved request as Canada Soccer sees it.
1 Club starts›2 District queue›3 Return + resubmit›4 Approved + history
1. The club starts a transfer and names the receiving club
Request transfer is a page view, not a dialog: the player, the type, the receiving club (limited to clubs under the same PTSO), a note, documents (step 1).
The request goes to the district of the releasing club.
3. Refused with a reason, revised on the same request
The district returns the request to club review with a required reason (step 3). The club attaches the document and resubmits with a note; the request keeps its number (step 4).
Both actions are rows of the history, with actor, organization, time and the status change.
Liam Carter · U13 · born 2013 · OS7730018834 · CS4411907710
Receiving club
Riverside FC (Demo District)
Documents
lease-carter-2026.pdf · added Nov 5 by the club
Historynewest first
When
Who
Organization
Status
Note
Nov 5, 2026 11:40
Dana Whitfield
Oak Creek Soccer Club
Club review → In review
Lease agreement attached (lease-carter-2026.pdf).
Nov 4, 2026 16:15
Sam Patel
Demo District
In review → Club review
Please provide proof of the family's new address.
Nov 4, 2026 09:30
Dana Whitfield
Oak Creek Soccer Club
— → In review
Transfer to Riverside FC. The family moved to the east end in October.
Return to club reviewthe action as sent on Nov 4
Please provide proof of the family's new address.
4. Approved: the registration moves, and everyone sees the history
Approval marks the releasing registration Transferred and takes Liam off the roster (step 5). Riverside FC registers him in its Member Zone; his IDs follow him.
Anyone in the chain opens the request or the player and sees every action (step 6).