TrainAR Docs
Try Free
Sessions & Procedures · Last updated 18 May 2026 · 3 min read

Sessions overview

A session is a single training run on the glasses — from "Start training session" to "Stop training session".

A session is a single training run on the glasses — from "Start training session" to "Stop training session". TrainAR records the engineer's POV video, extracts procedures from it automatically, and surfaces both in the Dashboard for you to review at your convenience.

A procedure is a structured chunk of know-how extracted from a session — typically a discrete piece of work an engineer did, surfaced as a named, replayable clip with its own thumbnail.

Session lifecycle

Engineer says "Start training session"
            ↓
Engineer works the job (POV + voice captured)
            ↓
Engineer says "Stop training session"
            ↓
Recording uploads to TrainAR
            ↓
Core App auto-extracts + auto-scores + auto-approves procedures
            ↓
Session + procedures appear in Dashboard → Sessions

No manual extraction step. No human approval step. Procedures are extracted and scored end-to-end by the Core App's pipeline on the tenant side — by the time the session appears in the Dashboard, the procedures are already named, scored, and ready.

What gets captured

  • POV video of the entire session
  • Engineer voice + AI voice replies (trainee mode)
  • Procedure clips — sub-clips of the main video, one per extracted procedure
  • Session metadata — duration, started_at / completed_at, the seat that ran it, the role (trainer or trainee)
  • Optional: a numerical score (0-100), a prose summary, trainer notes — if the Core App pipeline produced them
  • Linked Task — if the session was run against a task from an integration

Where sessions live

Dashboard → Sessions — the list view. See Viewing a session for what each session detail page shows.

Trainer vs trainee sessions

Sessions run in one of two roles, set on the engineer's seat:

Role What the engineer is doing What the AI does
Trainer Recording how an expert does the job Listens + transcribes; no real-time intervention
Trainee Following a procedure with AI guidance Talks in real time, calls skills, looks on request

Both produce session recordings and (typically) procedures.

Session status values

In the Sessions list and the detail header you'll see one of:

  • Completed — finished and processed
  • In Progress — session is currently running on the glasses
  • Failed — session ended abnormally

Minute consumption

Active session time consumes minutes from your tenant's minute pool. Pre-flight (~2 seconds) and post-session processing don't consume — only active session time. See Minutes report for current balance.

Where to next