Procedure extraction

Procedures are extracted from session recordings automatically by the Core App on the tenant side. By the time a session appears in the Dashboard the procedures are already named, clipped, scored, and approved. There's nothing for you to do.

What "automatic" means

The Core App's post-session pipeline runs end-to-end without human input:

1. Recording uploaded — the raw POV video lands in TrainAR storage
2. Procedure segmentation — the pipeline identifies discrete chunks of work within the session (a service step, a part replacement, a fault-find sequence) and splits them
3. Naming + description — each procedure gets an auto-generated procedure_name and (where possible) a description
4. Per-procedure video clip — each procedure gets its own sub-clip from the main recording, with its own auto-generated thumbnail
5. Scoring — the pipeline produces a 0-100 quality score (visible in the Session Summary card if generated)
6. Approval — procedures are auto-approved at the end of the pipeline. No human signoff required.

By the time you see the session in Dashboard → Sessions, all of this has happened.

Why there's no approval step

Earlier versions of TrainAR had a manual approve/reject flow on the Dashboard. We removed it because in practice every tenant approved everything — the human step was friction without quality signal. The Core App pipeline now does the quality assessment itself, surfaces the score on the Summary card, and lets the procedure go straight to viewable.

If a session goes badly (audio dropout, camera occluded, no procedures detectable), the pipeline will flag the session status as Failed in the Dashboard list and the Procedures card will show "No procedures extracted for this session". No procedures appear if no quality content was captured.

What each procedure contains

In the database (and what surfaces on the Session detail page):

• procedure_name — auto-generated short title
• description — auto-generated longer description (may be empty)
• video_url + thumbnail_url — the per-procedure clip and its thumbnail
• duration_seconds — clip length
• status — set by the pipeline (procedures with insufficient quality may be excluded)
• created_at — when the pipeline produced it

Other fields exist in the procedures table for cross-tenant Marketplace publishing — those aren't relevant to the tenant view.

Typical processing time

5-15 minutes for a 20-minute session. Larger sessions or sessions on poor connectivity (the recording uploads after the engineer stops) can take longer.

What you do with extracted procedures

Just watch them. The Dashboard surfaces each procedure as a numbered list item with its name, description, and clip. The clips are useful for:

• Reviewing what the engineer actually did
• Coaching (sharing a specific clip with another engineer)
• Audit (proving a step was performed correctly)

The procedures themselves also live inside the AI's knowledge for trainee-mode sessions on the glasses — the AI can reference past procedure clips when relevant to what a current trainee is asking.

Where to next

• Viewing a session — the Dashboard surface
• Sessions overview — the lifecycle in context
• Privacy & GDPR — what's stored, how long