A clear purpose
Teams should explain why information is used, which coaching workflow it supports, and what is outside the product’s role.
When a team includes younger players, families need a clear explanation of purpose, access, review, and boundaries. This page shows the principles being considered—not a live parent portal.
Synthetic examples only. No account, upload, or live data connection is active.
Trust posture
FieldSense may eventually help teams organize reviewed coaching information. That future workflow must begin with clear roles, explicit policy, and protection appropriate to the people involved.
Teams should explain why information is used, which coaching workflow it supports, and what is outside the product’s role.
Future access should match the participant’s age, the program relationship, and explicit team and guardian policies.
Coaches and authorized adults remain responsible for feedback and decisions. FieldSense must not silently decide a player’s future.
The current pages contain no account creation, media upload, roster import, sensor connection, consent form, messaging, or storage. Those capabilities require separate privacy and security gates.
Questions families should be able to ask
These answers describe the private UAT and the intended design principles. They are not promises that a production service already exists.
No. This private UAT contains only fictional fixtures. It has no form, account, upload, tracking, storage, or external connector.
No. The UAT does not rank players or make roster, selection, playing-time, recruiting, scholarship, or eligibility recommendations.
No. The displayed values are synthetic interface examples and are explicitly not health, fatigue, readiness, or injury assessments.
Magnolia would require a separately approved privacy and security design, role and consent rules, data-retention decisions, media handling, team agreements, and human review.
Shape the next review
Magnolia is using this UAT to make the purpose and boundaries concrete before any real-player workflow is considered.