Athlete Experience
A clear view of every contract, payout, and required action.
The athlete-facing experience connects agreements, revenue-share and travel-per-diem status, payment history, tax documents, and required actions to the same institutional record.
Inside the Athlete Experience
Built for athlete clarity. Governed by the institution.
Agreements and required actions, revenue-share and travel-per-diem visibility, and tax-document access — organized around how athletes actually use it, inside the institutional platform.
Product views are grounded in the Stevera OS product design and shown with fictional data.
Action Center
Agreements and Actions
See which agreements need a signature and which required actions need attention, in one place.
Payment Status Visibility
Track revenue-share distributions and travel per diem as they move through the institutional workflow.
Notifications
Get notified when a document needs a signature, a payment updates, or a new tax document is ready.
Travel Per Diem Visibility
See travel per diem as its own payment category — event, amount, date, status, and deposit confirmation — once Stevera Integrated Payments is active.
Tax Documents
Tax-Document Access
Institution-approved tax documents, including 1099-NEC records, become available directly in the athlete application alongside agreements and payment history.
Sample document — not filed or accepted by any tax authority.
Payment Delivery & Status
Payment status and delivery, connected to the institutional record.
Approved payments move through the institutional workflow to the athlete's designated receiving account — the athlete's existing bank account. Where Stevera Integrated Payments is active, integrated third-party regulated payment infrastructure executes the funds movement, and status returns to the same record athletes and staff both see.
Stevera does not hold funds or provide a bank account. Athletes continue using their existing receiving account.
Privacy and Role Boundaries
What the athlete sees. What the institution sees. What it never sees.
Athlete Sees
- Agreements and required actions
- Revenue-share and travel-per-diem payment status
- Recorded payment activity
- Tax documents
Institution Sees
- Agreement status and signature completion
- Institutional approvals
- Payment-setup status
- Required reporting records
- Audit history
Institution Does Not See
- Athlete-only account and security settings
- Information outside the staff member's assigned role
The current permission model is designed to keep private athlete information outside institutional views that don't need it.
What This Is — and Is Not
- Stevera does not hold funds or provide a bank account. Athletes continue using their existing receiving account.
- University access to athlete information remains governed by institutional permissions and policy.
Connected to the Institutional Record
Purpose-built for participation in the university workflow.
The athlete application provides a dedicated experience for agreements, payment status, tax documents, and required actions — connected to the institutional workflow without exposing private athlete financial information to university staff.
See how the athlete experience supports your institution's operation.