Employee Learning and Growth Internal Trainer and Consultant Guide

1. Teach one practical outcome

Coming Soon | Release 2026.10.1.0 | Edition 1 | 20 October 2026. Availability follows your organisation rollout, configuration and access. This guide is a preview reference, with no committed release date.

Internal use. The participant should be able to locate the next activity, interpret transcript source/result/progress, then identify the correct credential or growth follow up.

Use a practical 30-minute session: 3 minutes for context, 12 for one coherent demonstration, 5 for role-appropriate configuration, 5 for a read-only exercise and 5 for questions. Dates, presenter and invitations remain undecided.

Keep the shared demonstration and participant manual suitable for its audience. Configuration diagnostics, reset instructions and private evidence belong in the internal handoff. Upcoming client material stays Coming Soon; At Launch drafts remain held.

2. Rehearse and demonstrate

1. Confirm environment, approved fictional personas, effective role and module readiness. Do not circulate credentials or internal identifiers.
2. Confirm the starting activity, hierarchy, period or selected team. Check local data is appropriate and any outbound workflow/notification effects are contained.
3. Use the sequence below. Stop before any unapproved save, approval, publication or submission.
4. Retain a read-only fallback using the current deck and cleared captures. A screenshot does not prove a transaction completed.

• Open My Learning in the approved employee context and explain Overview, Transcript, Credentials, Growth and Achievements.
• Find the fictional Jedi activity and read its source/date/result separately from progress.
• Show the offered player action as an entry point; actual resume/completion needs its own verified journey.
• Explain credential health and the separate award/evidence record, then show the goal editor and its deliberate save.

Learning / General controls enhanced dashboard/player/credentials/growth/gamification and native source/action visibility. Check employee mapping, source status and published assignment separately.

Practice exercise: participants locate one fictional Jedi record, explain the relevant count/status and name the next authorised source action. Ask them to distinguish viewing from changing the record. Do not require live writes to complete the exercise.

3. Consultant handoff and reusable assets

The current deck has 24 slides and matching scene narration estimated at 570 seconds. Final voice timing is a production check; this companion creates no audio/video. Use the existing PowerPoint and notes without creating a competing deck.

Master sales/QA deck alignment remains outstanding because the actual master was not reviewed for this companion. Select module scenes for the audience and retain their lifecycle and scope wording.

After the demo, close unsaved windows and clear only temporary filters/context through normal controls. Use an approved reviewed reset if authorised. Do not delete shared catalogue, real outcomes, requests or awards to reset a session.

4. Questions limits and escalation

• Does a Pass always mean progress should be 100 percent? Historical and self-paced sources can represent different evidence.
• Does completion issue a credential? Completion, award and printable evidence are separate.
• Why is Growth absent? Check the enabled feature, employee context and supporting access/schema.
• Are chart totals current-page rows? Read each view scope; Cards can show the current page while insights cover matching records.

Verification boundary: the retained captures show selected native views. Current local evidence includes Course and Module persistence and native editor launches; a filtered employee transcript XLSX was checked locally and in Dev. This does not verify every School, Programme, Schedule or result save, content publication, learner completion, credential award or certificate issuance. Dev workflow persistence remains outstanding.

Record unanswered questions with environment, role, action, expected and actual result and next owner. Keep private evidence and raw diagnostics outside attendee exports. Candidate FAQs can be reviewed for Knowledge content later; this guide does not publish them.

Handoff checklist: correct edition; matching deck/notes/narration; cleared assets; approved demo starting state; expected source action; read-only fallback; remaining UAT boundaries; reset owner. No session scheduling, outreach or Hub publication is included.