EMPLOYEE HELP: OPTIONAL MEETING RECORDING SCRIPT Fictional role-play script. This file is not an actual transcript. Suggested title: Employee Help pilot planning - fictional demo Suggested speakers: Colin (service lead), Kadji (platform), Karin (training). Read naturally; record with consent in the demo tenant. Use the genuine recording date. The scenario dates below stay fixed. Announce that they are dates in the exercise. Colin: This is a fictional Employee Help planning meeting. The service gives employees one page for routine IT and facilities requests. The earlier brief proposed all six teams, 330 people, on 12 October 2026. We need to decide whether that is realistic. Kadji: I recommend a pilot, not all six teams. IT Support has 60 users and Workplace Services has 40. We can evaluate the routing without including HR cases, payroll or other sensitive employee information. Karin: I agree. Training a hundred pilot users is manageable. Training all six teams at once is a different commitment. Colin: Decision D01: IT Support and Workplace Services only, 100 users. People Operations, Finance Operations, Procurement and Sales Operations are later-phase candidates. They have no approved rollout date. Kadji: T02 routing still needs a tested urgent escalation path. I own that, due 24 September in the exercise. T03 pilot access is complete. Colin, the support rota cannot be signed off before routing is settled. Colin: I own T04, the support rota, due 6 October. Karin owns T06, the accessibility walkthrough, due 24 September, and T07, coordinator training, due 7 October. I own T08, the invite and help page, due 9 October. That depends on routing, rota, accessibility and training. Karin: The keyboard-focus issue means accessibility is not complete yet. Training is booked, but booked does not mean attended. Colin: Decision D02: 12 October remains a conditional target. All eight pilot tasks T01 to T08 must be complete before launch. Do not send the announcement while a gate is open. Kadji: One thing is not decided: OQ01, how long the audit log should be retained. I will ask the policy owner. Do not fill in a standard retention period just because a form asks for it. Colin: Decision D03: keep existing help channels available as the fallback. Review pilot feedback after two weeks before proposing expansion. Our targets are 90 percent of requests reaching the right queue, an owner within one working day and an accessible intake journey. These are targets, not results. Karin: I will send a separate update if the training or accessibility position changes. Colin: We have agreed scope and gates, not approval to launch. The action plan must keep those separate. End of the fictional planning meeting. After recording: stop transcription, open the saved transcript and confirm it is readable. Do not edit the transcript to manufacture a result. Correct recognition errors only through normal authorised review. Keep Latest Update.docx separate; it provides the later change during the demo.