Turn every training session into development you can show.

What it is

An operating system for the work you already do

A trainer already plans the session, delivers it, and forms a clear view of how the athlete is progressing. That judgement is the valuable part — and it is usually the part that disappears. It stays in the trainer’s head, in a text message, or in a hurried conversation at pickup.

TrainingOS is the system that keeps it. It holds the roster, the family’s permissions, the sessions, the trainer’s own account of what happened, and the approved report that goes home — in one place, in order, with a record of who decided what.

It is not a scheduling tool with reporting bolted on. The reporting is the point; everything else exists to make the reporting honest and repeatable.

Who it’s for

Built for the people running the training

The problem

Development is real. The record of it usually isn’t.

Training activity fragments almost immediately. The plan lives in one place, what actually happened lives in the trainer’s head, the notes live in a phone, and the family hears a version of it in the car park. Nothing connects, so nothing accumulates.

The costs land in predictable places. Reporting to families becomes a chore that gets done inconsistently or not at all. A trainer who leaves takes the athlete’s history with them. And a parent paying for months of training has no durable answer to a fair question: what has actually changed?

TrainingOS puts a governed workflow around that process, so the record is a by-product of doing the work rather than an administrative task stacked on top of it.

How it works

Six steps, in order, every time

1. 1 · Plan

   The trainer builds the session — individual or group — against athletes on the facility’s roster, with a focus and optional drills.

2. 2 · Deliver

   The session moves through its lifecycle as it is actually delivered. Administration stays out of the way while the training is happening.

3. 3 · Capture the trainer’s insight

   The trainer speaks their debrief while it is still fresh. Scout A.I. turns that into a structured draft — it organises what the trainer said, and never rates or scores an athlete.

4. 4 · Review and approve

   The draft is the trainer’s to correct, and it is not a report until they approve it. Nothing reaches a family that a person has not signed off.

5. 5 · Communicate

   The approved report goes to the athlete’s linked parents or guardians in their own accounts, and they are told when it is published.

6. 6 · Preserve the history

   Reports accumulate against the athlete. A report can be corrected or withdrawn, and the record keeps what it replaced rather than quietly overwriting it.

For the facility

What the facility and trainer get

• Your facility, front and centre. Your name, your mark and your colours lead the experience a family sees. HZ360 stays present underneath as the intelligence platform — it does not take your place with your own customers.
• One standard of delivery. Every trainer follows the same path from plan to approved report, so the quality a family receives does not depend on which trainer they were assigned.
• Reporting that actually gets done. The report is drafted from the debrief the trainer already gives, which removes the blank page that stops most reporting from happening.
• The work stays with the facility. An athlete’s development history belongs to the record, not to whoever happened to train them that season.
• Permissions handled properly. Consent is recorded per athlete and per scope, and an athlete cannot be selected for a session until the family’s training decision is on record.

For the family

What the athlete and family get

Measure. Develop. Improve.

Know where you are.
Know what to work on.
See your progress.

Parents and guardians get their own account — not a forwarded PDF and not a group chat. They see the reports for their own athlete, written and approved by the trainer who did the work, and they are told when a new one arrives.

The family also holds the permissions. Consent is recorded, it can be withdrawn, and withdrawing it changes what happens next rather than being filed away.

Why HZ360

Restraint is the feature

TrainingOS is built around children’s training data, and the decisions that matter most are the ones about what the system will not do. These are governed product rules, not marketing posture:

• Scout A.I. does not rate or score athletes. It organises what the trainer observed. The professional judgement stays with the professional.
• Identifiable athlete information is never sent into transcription or A.I. prompts. The mechanism is built so it cannot be, rather than relying on someone remembering.
• Nothing is delivered to a family without explicit trainer approval. There is no automatic publication path.
• A.I. supports the work; it does not replace the trainer. Every report a family reads was approved by the person who ran the session.

A facility operating this way can be designated an HZ360 Certified Evaluation Center™ — Powered by TrainingOS™ — the entry point through which athletes join the wider HZ360 ecosystem.