AZVYRADocumentation
EN AR
Getting started·02

The trainee journey

From first visit to renewal, with account and subscription states at each step.

3 min read Updated 3 Nov 2026 ForAdmin · Head coachTraineeAssistant coach

The admin's decision may be approval, a request for more information, or a rejection with a reason that reaches the trainee. A request can return for editing before it is approved.

The full path, step by step#

#StepRoleWhat the system doesOutcome
1Visits the site and reads about the coachVisitorTracks the visit, shows plans, exposes “Start now”Starts sign-up
2Creates an accountVisitorCreates the user, sends an OTP, records consentpending_questionnaire
3Completes the questionnaireTraineeAutosaves, validates required answers, medical flagpending_review
4Admin receives a notificationSystemNotification plus queue entryRequest ready for review
5Admin reviews and decidesAdminApprove / request info / reject with reasonapproved_unpaid or needs_info
6Trainee paysTraineeInvoice, gateway, payment verificationactive after success
7Subscription activatesSystemOpens permissions and sends a welcome noticePlan and dashboard available
8Trainee uses the platform dailyTraineeLogs workouts, meals and measurementsData and progress accumulate
9Coach reviews and adjustsCoachNotes plus a new plan versionUpdated plan
10Expiry approaches, then renewalSystem + trainee7/3/1-day reminders and a renewal invoiceSubscription continues

Expected timing per stage#

StageTargetOwner
Account creationInstantSystem
Questionnaire10–15 minutesTrainee
Admin reviewWithin one business dayAdmin
Invoice and paymentInstant, or one business day for a bank transferTrainee + system
Subscription activationInstant after payment confirmationSystem
First planWithin 48 hoursCoach + nutritionist
Weekly check-inEvery 7 daysTrainee + coach
Renewal7 days before expirySystem + trainee

What happens behind the scenes#

  • A request is not a subscription: the request lives in the review queue; the subscription starts only after approval and payment.
  • Every state transition is recorded: previous state, new state, actor and timestamp go into the activity log.
  • Notifications follow events: request created, approval, invoice, payment success, expiry warning and renewal.
  • Permissions follow state: an expired account can read history and reports only; the live plan and chat stay closed.
  • Plans are versioned: every coach edit creates a new version, and the previous one remains reviewable.

    Trainee account states

    StateMeaning
    pending_questionnaireRegistered but has not completed the questionnaire
    pending_reviewQuestionnaire complete, waiting for the admin
    needs_infoAdmin requested more information
    rejectedRequest rejected (with a reason)
    approved_unpaidApproved, waiting for payment
    activeSubscription is live
    expiringSeven days or fewer remain
    expiredSubscription ended (plan access restricted, history retained)
    pausedSubscription frozen
    suspendedAccount suspended by the admin

    Three separate lifecycles

    Do not model the account, the registration request and the subscription as one status field. Each has its own lifecycle; see Binding operating rules.