Source: [Northstar — make every handover clear — Skills for Business]() NORTHSTAR · FICTIONAL TRAINING # Make every handover clear. A process and its owners, arranged for colleagues who need to know what happens next. ## The task New service-desk colleagues: follow the process, identify each owner and escalate at the stated threshold. Complete fictional notes. No company records. [Try this workflow ↗](https://skillsforbusiness.ai/skills/present/?example=service-handover#start) ``` # Service handover — fictional training brief Audience: new service-desk colleagues, in a 10-minute team induction. Task: practise the sequence and identify the owner of each handover, then handle an escalation. Use a process-led layout with responsibilities beside each step. No decorative imagery is needed. ## Fictional source notes — preserve these facts and qualifications - The sequence is Receive → Triage → Resolve → Close. - Owners: Receive — Service desk; Triage — Duty lead; Resolve — Resolver; Close — Service desk. - Acknowledge the request within 30 minutes. - Record the current status and the next action. - If unresolved after 2 hours, contact the duty lead. - The service desk confirms closure with the requester. - Practice scenario: a request is still unresolved after 2 hours. Contact the duty lead. Share the current status and next action. - Keep the requester informed. - Fictional training process; confirm local procedures before use. ## Identity and content lock Use the fictional Northstar service-desk name, a clear system sans serif, navy ink, near-white background and teal emphasis. Differentiate sequence, responsibility and escalation through composition, not color alone. Preserve all approved wording, thresholds, roles and the visible qualification during the visual review. No customer or company records were used. ``` [Transcript & evidence](https://skillsforbusiness.ai/examples/service-handover/#transcript) · [Download HTML](https://skillsforbusiness.ai/examples/service-handover/draft.html) Unique design · Slide 1 · process ### Separate equal boxes show the steps, but the visual route between handovers is weak. A new colleague can follow the work from Receive through Close without inferring the next step. Unique design · Slides 2–3 · escalation and practice ### Equal cards give the situation and the action similar weight. The training audience can locate who acts and when, while preserving the two-hour threshold. **Retained:** All visible slide wording, owner roles, 30-minute acknowledgement, 2-hour escalation, visible fictional-process qualification, Northstar identity, navy/teal palette and Present controller. [Download first draft ↓](https://skillsforbusiness.ai/examples/service-handover/draft.html) [Transcript & evidence](https://skillsforbusiness.ai/examples/service-handover/#transcript) · [Download HTML](https://skillsforbusiness.ai/examples/service-handover/presentation.html) Unique design · Slide 1 · process ### A connected process rail, directional arrows and aligned owner rows make sequence and responsibility visible together. A new colleague can follow the work from Receive through Close without inferring the next step. Unique design · Slides 2–3 · escalation and practice ### An asymmetric handover layout pairs context with the next action; the action keeps the emphasis. The training audience can locate who acts and when, while preserving the two-hour threshold. **Retained:** All visible slide wording, owner roles, 30-minute acknowledgement, 2-hour escalation, visible fictional-process qualification, Northstar identity, navy/teal palette and Present controller. [Download after review ↓](https://skillsforbusiness.ai/examples/service-handover/presentation.html) **Run & verification** Codex · Present 1.0.0 + Unique design 1.0.0 · 2026-10-29. File-capable repository workspace; published instructions read from retained releases. Local file creation and Chrome rendering; no native provider skill installation. Model and account plan are not exposed to this workspace. Human corrections: None. Brief and fictional source material authored during this website implementation. Fictional training process. This is a Codex workspace run, not evidence of an approved operating procedure, provider installation or user trial. - **contentLock:** Build checks identical visible slide text between draft and after review, plus protected renderer sections. - **rendered:** Pass locally: draft and after-review files, 3 slides each, captured at 1920×1080 and 1366×768. Contact sheet and all slides inspected at readable size; no clipping of essential slide content observed. - **offline:** Pass locally: all four artifacts opened from local files with HTTP(S) blocked; zero HTTP(S) requests and zero page errors. Production-delivered bytes still need deployment verification. - **pdf:** unverified; no PDF is offered - **userTrials:** 0 of 5; pending - **date:** 2026-10-29 - **reviewer:** Codex workspace agent - **browser:** Google Chrome 156.0.8078.73 - **interaction:** Pass locally on all four artifacts: one active slide, arrow navigation, slide menu, notes and blank screen, with reduced motion. - **fonts:** Actual Linux rendering inspected through Chrome: Liberation Serif/Italic for Horizon headings and Liberation Sans for chart labels; Liberation Sans/Bold for Northstar. These are system fallbacks, not bundled brand fonts. [Run record](https://skillsforbusiness.ai/examples/service-handover/run.md) · [Hashes, findings & transcripts](https://skillsforbusiness.ai/examples/service-handover/generated.json) · [Source brief](https://skillsforbusiness.ai/examples/service-handover/brief.md) **Slide transcripts** ### First draft #### 1\. Four steps. One owner at each handover. SERVICE HANDOVER Four steps. One owner at each handover. 1. Receive Service desk 2. Triage Duty lead 3. Resolve Resolver 4. Close Service desk Acknowledge the request within 30 minutes. Fictional training process; confirm local procedures before use. #### 2\. Keep the handover visible. SERVICE HANDOVER Keep the handover visible. Resolver Record the current status and the next action. Duty lead If unresolved after 2 hours, contact the duty lead. The service desk confirms closure with the requester. Fictional training process; confirm local procedures before use. #### 3\. Practise the handover. SERVICE HANDOVER Practise the handover. Scenario A request is still unresolved after 2 hours. Your next action Contact the duty lead. Share the current status and next action. Keep the requester informed. Fictional training process; confirm local procedures before use. ### After review #### 1\. Four steps. One owner at each handover. SERVICE HANDOVER Four steps. One owner at each handover. 1. Receive Service desk 2. Triage Duty lead 3. Resolve Resolver 4. Close Service desk Acknowledge the request within 30 minutes. Fictional training process; confirm local procedures before use. #### 2\. Keep the handover visible. SERVICE HANDOVER Keep the handover visible. Resolver Record the current status and the next action. Duty lead If unresolved after 2 hours, contact the duty lead. The service desk confirms closure with the requester. Fictional training process; confirm local procedures before use. #### 3\. Practise the handover. SERVICE HANDOVER Practise the handover. Scenario A request is still unresolved after 2 hours. Your next action Contact the duty lead. Share the current status and next action. Keep the requester informed. Fictional training process; confirm local procedures before use. Compare a decision-led presentation. [See the Horizon case ↗](https://skillsforbusiness.ai/examples/quarterly-update/)