These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Fitness Trainer Platform
- Features
- Training sessions
Training sessions
Record attended training and carry it through independent review.
OverviewTraining Sessions List×
Fitness Trainer Platform · Training sessions
New
Training Sessions List
Approval waits for the booking supervisor
| Name | Status | Revision | Parent | Organization | Client | |
|---|---|---|---|---|---|---|
| Session 918 | Submitted | 100 | BKN-86099 | ORG-3125 | CLN-327 | |
| Session 535 | Submitted | 880 | BKN-39757 | ORG-6959 | CLN-834 | |
| Session 871 | Submitted | 520 | BKN-81746 | ORG-7106 | CLN-228 | |
| Session 583 | Submitted | 210 | BKN-65813 | ORG-3869 | CLN-837 | |
| Session 924 | Submitted | 240 | BKN-32166 | ORG-7723 | CLN-867 |
6 of 6 records
Session 918Training sessions · TS-93324
SubmittedRevision100
ParentBKN-86099
OrganizationORG-3125
ClientCLN-327
What you can do
Keep the attended work with its booking
A training session is the record of work performed for a booking. It holds the client name, start time, duration and workout revision used for that attendance. The trainer can save a Draft, submit the record for review and see whether it has been Approved, Rejected or Completed. Every session remains linked to its parent booking and organization, so a later decision can be read in the context of the accepted training time.
The session calendar is useful for locating an attended date. The status board is useful for finding work still in Draft or Submitted. The list carries the detail needed for a supervisor to open a specific record. These screens are different views of the same session records, allowing the team to move from a schedule question to an evidence question without losing the booking link.
How the work is organized
- Trainer records attendance. The person who delivered training records what occurred and which workout revision was used.
- Submission invites review. A Submitted session enters the supervisor’s decision queue.
- Decision stays separate. A reviewer records an outcome and reason in a decision record before completion is treated as settled.
What to agree during setup
Define the minimum session evidence your supervisors require. Decide when a trainer must submit it after attendance, which files should accompany it and who may correct a rejected record. Agree how the organization handles a booking with more than one attended session. Clarify whether the workout revision identifies an external plan or a version your trainers maintain elsewhere; the recorded revision should be understandable when revisited months later.
Train reviewers with one complete session and one returned for correction. Include a booking where the client did not attend, so staff do not create attended evidence for a missed appointment. Keep the trainer and reviewer as distinct people when testing the decision.
Check the handoff on an actual case
A trainer delivers a confirmed Tuesday appointment. Afterward, the trainer opens the linked session, records the client, start, duration and workout revision, and attaches supporting evidence to the booking. The Draft remains editable while the trainer checks the facts. Once Submitted, the supervisor reads the booking and the attachment, records an Approve decision with a reason, and the session can show Approved.
If the duration does not match the supporting note, the supervisor chooses Return or Reject with a reason. The trainer corrects the session rather than changing the supervisor’s decision. The booking is completed only after the attended work and its review are consistent.
What your team sees
- Training Sessions List — Attended records with their booking and review status.
- Training Sessions Calendar — Session start dates alongside scheduled work.
- Training Session Status Board — Draft, submitted and decided records grouped by status.
Follow the work through
Session review shows the evidence and decision path. Booking to attendance explains the parent booking.
What it keeps track of
Data model- Training sessions
- Attended training-session evidence submitted for independent review.
- Bookings
- Scheduled training bookings with guarded lifecycle and execution evidence.
- Review decisions
- Independent approval, rejection, and return decisions on submitted work.
- Record attachments
- Evidence files linked to booking operations and review context.
Who uses it
PermissionsSet up Fitness Trainer Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.