๐Ÿ‘€ Demo preview โ€” this Michigan FC site is a RootSoccer demonstration. Operational accounts and demo actions are test data only.Why we built this โ†’

Coaching Staff

Coaching roles, age-group assignments, experience, and contact pathways.

Coaching roles, age-group assignments, experience, and contact pathways.

The right level of visibility

Public bios build trust while private credentials and screening status remain staff-only.

How RootSoccer handles it

RootSoccer turns coaching staff from a directory into a role-aware operating workspace.

Public biographies and contacts can remain polished while sensitive qualification and assignment detail stays behind the correct access boundary.

Why this is better than a page clone

The public explanation, structured records, permissions, status, and next action are designed as one experience. MFC can prove the workflow in a pilot without pretending its incumbent systems vanish overnight.

How RootSoccer improves coaching staff

Source parity is the baseline. This section demonstrates the operating workflow RootSoccer adds for MFC.

๐Ÿ›ก๏ธ

Verified role records

Qualifications, clearances, assignments, contact visibility, and status can live on one permissioned profile.

๐Ÿ‘ฅ

Assignment in context

A coach, referee, volunteer, or staff member sees the teams, games, or tasks tied to their role.

๐Ÿ“„

Requirements stay visible

Expirations, missing credentials, acknowledgements, and training can be tracked before assignment.

๐Ÿ”—

Communication follows responsibility

Messages target the people assigned to the affected team, game, program, or administrative task.

Role-based experience

Fictional role cards show how responsibilities are separated in the demo.

CA

Club Administrator

Operations

Programs, teams, staff, registration, finance, and communications.

CC

Coach

Team experience

Team, program, and attendance tools without finance access.

WE

Website Editor

Content

Public pages, locations, and sponsors without club finance.