Product and workflows
Features and institutional value
What Rafik can organise, who uses each capability, and where its limits sit.
A shared operational record
Rafik brings university membership, coaching assignments, training, scheduled events and recorded results into an institution-operated workspace. The useful organisational change is a shared record of who is responsible for what, what was prescribed and what was actually recorded. It does not automatically establish better athletic outcomes or replace the institution’s staff, policies or judgement.
The web implementation is available for evaluation. First-user sport review, privacy/security approval and operational release gates remain open. Start with synthetic records and read known limitations.
Capabilities at a glance
| Capability | How an institution can use it | Boundary |
|---|---|---|
| People and coach responsibility | Invite members with one clear role and identify the coach responsible for an athlete. | Membership does not grant access to every private record. |
| Programs and exercise library | Reuse institution programs, publish a reviewed version and assign it to selected athletes. | Publishing and assignment are separate; sport-specific exercise coverage needs coach review. |
| Groups, calendar and assessments | Schedule training, name staff, record attendance and retain defined performance results. | Measurements are not clinical findings; external reminders are not confirmed. |
| Coach tasks and follow-up | Make dated work and pending reviews visible with an explicit assignee and completion state. | An overdue task is a recorded work item, not a judgement about a coach’s quality. |
| Conversations and resources | Keep authorised discussions and exercise resources with the relevant work. | Private pairs and group membership have different access rules. |
| Nutrition and diary sharing | Separate an agreed plan from actual food entries and the athlete’s sharing choice. | A suggested meal is not recorded consumption or medical advice. |
| Feedback and reports | Review actual participation, delivered sessions and explicitly submitted feedback. | Missing feedback is unknown; these are not rankings of staff or predicted outcomes. |
| Instance ownership and branding | Operate an isolated deployment with institution identity and its own backup process. | The institution still pays infrastructure costs and supplies operational capacity. |
How the roles work together
An institution administrator establishes membership, coach responsibility and operational oversight. A trainer/coach prepares and assigns work to their current athletes, records scheduled activity and reviews submitted sessions. An athlete sees their own assigned training, records their activity and controls explicit diary sharing. Server permissions govern these boundaries; a visible roster is not permission to read unrelated records.
See roles and administration for onboarding and access changes.
Example: an institution’s training week
This is a synthetic workflow example, not a customer case study:
- An administrator invites the coaching staff and athletes, assigns coach responsibility and prepares a training group.
- A coach reviews an institution program, publishes its version and assigns it to their selected athletes.
- Staff schedule a group session and an assessor-led test using a defined measurement and unit.
- Athletes record their actual training; staff record attendance and the measured assessment results.
- A coach reviews completed work and follows up on pending items. An administrator reviews recorded workload and participation with the definitions and date range visible.
The benefit is continuity between assignment, delivery and review. The institution must still decide whether the training content and assessment are suitable for its sport and athletes.
Explore each workflow
- Programs, exercises and training: reusable plans, stable prescriptions, actual session records and review.
- Scheduling, groups and assessments: staff, participants, attendance and comparable results.
- Communication and coach tasks: authorised discussions and clear follow-up responsibility.
- Nutrition and diary sharing: planned guidance versus actual entries and consented visibility.
- Analytics and feedback: what the recorded numbers mean and which decisions they cannot support.
Sensitive participation status
A separate, limited participation-status workflow lets an athlete share the current authorised status with their assigned coach after the required consent setup. It does not expose a medical history to administrators or create a clinical service. Read roles and sensitive-record boundaries before evaluation.
Not part of the current offer
Rafik does not currently offer a confirmed managed hosting service, guaranteed external notification delivery or published native phone application. Session packages, commercial allowances and session limits are retired. Deployment, planned phone use and support explain the practical next steps.
Source and scope
Based on the maintained application API and workflow documentation reviewed on 17 October 2026. Benefits describe workflow capabilities, not measured outcomes. Institutional acceptance remains required.