Fall 2026 Concept Season
One-Off Scheduling
Two teams propose a date, time, field, and contact path; the club representative reviews it before league submission.
Two teams propose a date, time, field, and contact path; the club representative reviews it before league submission.
Before schedule lock
The home and away contacts agree on the details.
The responsible club representative confirms completeness.
The approved details are entered into GotSport and reflected in the public view.
After schedule lock
A change becomes a tracked request with both-club acknowledgement and league-administrator approval rather than an unstructured email.
How RootSoccer handles it
RootSoccer replaces an email-or-form handoff with a stateful workflow: request, opponent review, league review, decision, application, and notification.
The original game remains visible beside every proposal, so operators can understand exactly what changed, who changed it, and why.
Why this is better than a page clone
The public explanation, structured records, permissions, status, and next action are designed as one experience. MSDSL can prove the workflow in a pilot without pretending its incumbent systems vanish overnight.
How RootSoccer improves one-off scheduling
Source parity is the baseline. This section demonstrates the operating workflow RootSoccer adds for MSDSL.
Start with the match
The original teams, kickoff, venue, competition, and season are already attached to the request.
Authenticated actors
Team and league roles determine who can request, acknowledge, revise, cancel, approve, or reject.
Validate before approval
Required reasons, timing cutoffs, duplicate open requests, and competition clashes are surfaced before a decision.
One auditable outcome
Responses, decision notes, the applied change, activity history, and notifications stay connected.