Session Coaching

Session mode activates when you open Coach on a Race, Qualifying, or Practice session page.

Coach reads that session's stored data — standings, laps, incidents, and full XML when available.

What you can ask

Race summary

• Final position, gaps, and key moments
• Lap time progression and consistency
• Sector deltas vs rivals

Incidents and penalties

• Collision and off-track events from session data
• Penalties and position impacts
• Lap 1 incidents and first-lap dynamics

Stints and strategy

• Pit stop timing and stint lengths
• Tyre wear and compound changes
• Fuel and virtual energy usage (when in XML)

Rivals and gaps

• Gap to the car ahead or behind
• Who you gained or lost positions to
• Head-to-head vs specific drivers in the session

Community comparison

When community data exists for the same track, car, and conditions:

• How your pace compares to other MyLMU drivers
• Percentile-style context for lap times
• Same analysis foundation as Deeper Analytics

Linked telemetry

If telemetry files are linked to this session, Coach can reference them — though deep trace analysis works best in Telemetry mode.

Example prompts

• "Summarize this race — what went well and what cost me time?"
• "Why did I lose positions in the final stint?"
• "Compare my pace to the community for this session"
• "What incidents affected my result?"
• "How was my Lap 1 compared to the field?"

Data limitations

Tips

• Session analysis typically costs 28–88 CC — narrower questions save credits
• Open the session page before opening Coach so context attaches correctly
• For corner-level driving feedback, open the linked telemetry file instead

Related

• Session details
• Deeper Analytics
• Lap Times Explorer — career-wide pace trends and reference benchmarks
• Telemetry coaching