Creator: Brendan
Date: 18 October 2026
Topic: MyFocus Health and Safety - Detailed v2
Matching deck: MyFocus_Health_and_Safety_Overview_Final_v2.pptx
Estimated duration: 797 seconds. Scene timings are provisional; adjust holds and voice timing in Synthesia.
Pronunciation: HRFocus = H R Focus. WCL = W C L. PDF = P D F.
Privacy: Fictional or cleared demonstrations; no incident, workflow or report was saved or submitted for this capture.

SCENE 01 - Welcome to MyFocus Health and Safety
Timeline: 0-30 seconds
On-screen text: Find the incident, capture the detail and keep follow-up moving
Visual direction: hero.png + hrfocus-logo-verified.png. Use focused crops; allow the audience to read each area.
NARRATION
Welcome to MyFocus Health and Safety. This walkthrough shows how the incident workspace connects the overview with the work behind each record. We will look at incident capture, recorded progress, return-to-duty information, report previews and saving, and linked tasks. We will also briefly explain where manager initiation and the configured workflow fit, so you can see how the experience supports your organisation's process.
Transition: short dissolve.

SCENE 02 - The HR incident workspace
Timeline: 30-53 seconds
On-screen text: Six incidents across the selected employee scope
Visual direction: overview.png. Use focused crops; allow the audience to read each area.
NARRATION
The workspace opens with summary measures above the incident list. Our example contains six incidents across six colleagues, with four open and two closed. Search, filters and the display controls stay close to the list, so the overview leads naturally to the record that needs attention.
Transition: short dissolve.

SCENE 03 - The measures behind the overview
Timeline: 53-78 seconds
On-screen text: Open, closed and recorded progress have different meanings
Visual direction: kpis.png. Use focused crops; allow the audience to read each area.
NARRATION
Read each measure in its own context. Pending steps counts active incidents with fewer than nine recorded steps. Here, four incidents meet that condition. Recorded progress averages the recorded steps across matching incidents, giving sixty-five percent. It is a progress measure for the process, rather than an approval or clinical outcome.
Transition: short dissolve.

SCENE 04 - Filters that keep the question focused
Timeline: 78-101 seconds
On-screen text: Company, department, incident dates and progress
Visual direction: filters.png. Use focused crops; allow the audience to read each area.
NARRATION
Choose the company, department and incident type, then narrow by status, incident dates or recorded progress. Search can find an employee, incident, claim or place. Apply the selection to update the matching records and summary. Reset restores the broad view within your existing employee access.
Transition: short dissolve.

SCENE 05 - The detail grid
Timeline: 101-126 seconds
On-screen text: Employee context beside the incident and its progress
Visual direction: grid-people.png. Use focused crops; allow the audience to read each area.
NARRATION
The grid keeps employee and organisational context beside the incident date, status and recorded progress. Leia Organa has six of nine steps recorded, while Obi-Wan Kenobi has eight. Both incidents remain open. That makes it easier to see where follow-up should begin without treating progress as a final case decision.
Transition: short dissolve.

SCENE 06 - Actions close to each incident
Timeline: 126-152 seconds
On-screen text: Documents, tasks, workflows and report entry points
Visual direction: grid-actions.png. Use focused crops; allow the audience to read each area.
NARRATION
Each incident has entry points for the work that belongs to it. Open the incident, review documents or continue with tasks and checklists. A workflow action appears where a workflow is available. Claim and resumption report actions follow the recorded process stages. The destination screen continues to enforce the relevant viewing permissions.
Transition: short dissolve.

SCENE 07 - Cards for a different reading view
Timeline: 152-176 seconds
On-screen text: The same incident context in a compact summary
Visual direction: cards.png. Use focused crops; allow the audience to read each area.
NARRATION
Cards present the same matching incidents in a format that is easier to scan by person. Each card shows the incident type, date and place, together with status, progress and document or task counts. Choose the record from its own actions while keeping the surrounding incident context visible.
Transition: short dissolve.

SCENE 08 - Incident type and status
Timeline: 176-202 seconds
On-screen text: A visual overview of the matching records
Visual direction: type-status.png. Use focused crops; allow the audience to read each area.
NARRATION
Insights uses all matching incidents, rather than only the rows on the current grid page. The type chart shows three accidents, two diseases and one informal accident. The adjacent status view shows four open and two closed. Choose a supported chart style when a different presentation makes the same values easier to read.
Transition: short dissolve.

SCENE 09 - The incident timeline
Timeline: 202-227 seconds
On-screen text: A monthly view based on incident dates
Visual direction: timeline.png. Use focused crops; allow the audience to read each area.
NARRATION
The timeline groups the matching records by incident month. This example shows one in August, two in September and three in October. Column, line and bar options provide different views of those recorded counts. The chart describes incident dates and does not forecast future incidents or an underlying risk rate.
Transition: short dissolve.

SCENE 10 - Departments and the people affected
Timeline: 227-250 seconds
On-screen text: Incident counts alongside distinct employee counts
Visual direction: departments.png. Use focused crops; allow the audience to read each area.
NARRATION
Department views help HR compare where matching incidents sit. One view counts incidents, while another counts distinct employees with those incidents. The values happen to match in this example because each colleague has one incident. They can differ when a person has more than one matching record.
Transition: short dissolve.

SCENE 11 - Recorded process progress
Timeline: 250-275 seconds
On-screen text: Nine steps give the follow-up a visible structure
Visual direction: progress.png. Use focused crops; allow the audience to read each area.
NARRATION
The progress chart groups incidents by the number of recorded process steps. Two records have all nine steps recorded. Others fall into early, middle or later ranges, and one has not started. Use these groups to find the supporting records, then review the actual incident before deciding the next action.
Transition: short dissolve.

SCENE 12 - From a chart to the supporting incidents
Timeline: 275-299 seconds
On-screen text: Selecting Accident narrows the grid to three records
Visual direction: drill.png. Use focused crops; allow the audience to read each area.
NARRATION
Select a category in an insight to apply its filter and return to the grid. Here, choosing Accident brings back three matching incidents. The summary changes with the selection, showing two open and one closed. The chart becomes a useful route to the detailed records behind the number.
Transition: short dissolve.

SCENE 13 - Capture the incident
Timeline: 299-325 seconds
On-screen text: Claim details, accident circumstances and the employee report
Visual direction: accident-fields.png. Use focused crops; allow the audience to read each area.
NARRATION
The capture screen records the claim and employer details, followed by the accident date, time and location. It also records when the employee reported the accident and the task being performed. This is a separate fictional capture example. The native fields and required indicators guide the user through the information needed before saving.
Transition: short dissolve.

SCENE 14 - Record what happened, then save
Timeline: 325-354 seconds
On-screen text: A clear description and the native Save and Proceed action
Visual direction: accident-description.png + capture-save-action.png. Use focused crops; allow the audience to read each area.
NARRATION
The next section captures the description of the accident and its injury context. Use the relevant controls and provide the supporting detail, then choose Save and Proceed when the record is ready. That action validates and saves the step before moving forward. This walkthrough shows the save control; it does not submit this fictional example or start a new workflow.
Transition: short dissolve.

SCENE 15 - Disease capture has its own detail
Timeline: 354-383 seconds
On-screen text: Diagnosis, reported dates, alleged cause and exposure
Visual direction: disease-fields.png + capture-save-action.png. Use focused crops; allow the audience to read each area.
NARRATION
Disease capture follows the same incident context with fields suited to an occupational disease. Record the nature of the disease, diagnosis date, alleged cause and when it was reported, together with the exposure and employment details that apply. Required fields and Save and Proceed remain part of the existing capture process. The values shown here are fictional layout examples.
Transition: short dissolve.

SCENE 16 - Continue through the incident stages
Timeline: 383-410 seconds
On-screen text: Particulars, supporting documents, reports and closure
Visual direction: incident-stage-navigation.png. Use focused crops; allow the audience to read each area.
NARRATION
The native incident navigation keeps all nine process stages together. It connects the capture with further particulars, documents, payments and employee information, followed by the claim report, resumption information, resumption report and closure. Recorded stages explain the progress shown on the HR dashboard. Each stage still owns its validation and deliberate save or submission action.
Transition: short dissolve.

SCENE 17 - Record the return to duty
Timeline: 410-436 seconds
On-screen text: Periods off work and periods performing light duty
Visual direction: resumption-periods-v2.png. Use focused crops; allow the audience to read each area.
NARRATION
Resumption Information captures the employee's return-to-duty detail. Record the dates and times for periods off duty and, where applicable, periods performing light duty, together with advances or salary paid during each period. Keeping these entries in the incident gives the resumption report a structured source and makes the follow-up easier to review.
Transition: short dissolve.

SCENE 18 - Complete the resumption particulars
Timeline: 436-462 seconds
On-screen text: Light duty, ongoing employment and the remaining information
Visual direction: resumption-details-v2.png. Use focused crops; allow the audience to read each area.
NARRATION
The remaining resumption fields record whether light duty was offered and performed, the relevant earnings information, ongoing employment and the other required particulars. Review the entries before using Save and Proceed. The resumption form and the report stage are separate steps, so the return-to-duty information can be checked before its report is prepared.
Transition: short dissolve.

SCENE 19 - Documents and follow-up work
Timeline: 462-489 seconds
On-screen text: Counts help you find the supporting information
Visual direction: documents.png. Use focused crops; allow the audience to read each area.
NARRATION
The document, task and checklist counts help you judge where to look next. Open the relevant area from the incident rather than searching through an unrelated list. Access continues to govern what you can view. The counts are navigation context and do not establish that evidence has been accepted or that a task is complete.
Transition: short dissolve.

SCENE 20 - Tasks linked to the incident
Timeline: 489-518 seconds
On-screen text: Open the follow-up from the incident that owns it
Visual direction: linked-task-list.png. Use focused crops; allow the audience to read each area.
NARRATION
Tasks and Checklists opens the work linked to this incident. The list shows the task title, description, status, priority and due date, with a Select action for the existing task. Add task and checklist is the entry point for new follow-up work when linking is enabled. In this demonstration we open an existing synthetic task, leaving its business state unchanged.
Transition: short dissolve.

SCENE 21 - Review the linked task
Timeline: 518-546 seconds
On-screen text: Status, priority, dates and progress remain in context
Visual direction: linked-task-detail.png. Use focused crops; allow the audience to read each area.
NARRATION
The linked task opens its native task workspace. Overview brings the description, status, priority, dates and progress together, while the other tabs provide the task's general information, dependencies, checklists, discussions and notifications. This example has no checklist items yet. The task detail remains connected to the incident, so the user can review the follow-up without losing that context.
Transition: short dissolve.

SCENE 22 - Preview the WCL report
Timeline: 546-578 seconds
On-screen text: Check the prepared report before saving it
Visual direction: wcl-first-preview-toolbar.png + wcl-form-employer.png. Use focused crops; allow the audience to read each area.
NARRATION
Open the W C L report at the relevant process stage to review its prepared P D F. The first-save preview offers Save report. That deliberate action stores the generated report with the incident and employee context. The report excerpt shown here is rendered by the native report engine using wholly fictional data. It illustrates the form and field placement without exposing a real employee's report.
Transition: short dissolve.

SCENE 23 - The accident detail in the report
Timeline: 578-604 seconds
On-screen text: The prepared WCL2 brings the captured information into the form
Visual direction: wcl-form-incident.png. Use focused crops; allow the audience to read each area.
NARRATION
The accident report brings the employer, employee and incident information into the configured form. This focused excerpt shows the accident circumstances and narrative rather than shrinking an entire multi-page report onto one slide. The report remains a document to review for completeness and accuracy before the organisation follows its own submission process.
Transition: short dissolve.

SCENE 24 - Reopen a saved report or prepare an update
Timeline: 604-633 seconds
On-screen text: The saved document and its history remain visible
Visual direction: wcl-save-history.png + wcl-preview-toolbar-cleared.png. Use focused crops; allow the audience to read each area.
NARRATION
After a report has been saved, the report stage shows its document name, who saved it and when, together with the recorded history. Open saved report returns to that document. Regenerate preview prepares a fresh version for review. Choose Update saved report only when ready to replace the saved document while keeping its name and incident and employee indexes.
Transition: short dissolve.

SCENE 25 - Preview and save the resumption report
Timeline: 633-660 seconds
On-screen text: The return-to-duty information has its own report
Visual direction: resumption-preview-toolbar.png + resumption-report-periods.png. Use focused crops; allow the audience to read each area.
NARRATION
The resumption report uses the return-to-duty information from the incident. Review the employee and claim context, the periods off duty and the periods performing light duty in the prepared report. It follows the same deliberate preview and save pattern. An existing saved report can be reopened, or a regenerated preview can be reviewed before updating it.
Transition: short dissolve.

SCENE 26 - A return path to workflow work
Timeline: 660-685 seconds
On-screen text: The workspace and approvals remain connected
Visual direction: workflow.png. Use focused crops; allow the audience to read each area.
NARRATION
The Workflows entry point returns HR to the established Health and Safety inbox. An incident with an available workflow also offers its own workflow action. That connection helps the user move between the overview and the approval work while retaining the incident context and the access rules of each destination.
Transition: short dissolve.

SCENE 27 - Where manager initiation fits
Timeline: 685-716 seconds
On-screen text: Manager capture and HR follow-up use the configured workflow
Visual direction: manager-workspace.png. Use focused crops; allow the audience to read each area.
NARRATION
The Manager Workspace keeps team context and authorised actions together. Health and Safety initiation continues through the established employee and incident capture process available to the manager. Where manager workflow is enabled, saving a new incident starts the configured workflow for its routing, including HR follow-up where configured. HR capture has a separate workflow setting. The exact route and approvals depend on the organisation's configuration.
Transition: short dissolve.

SCENE 28 - The filtered list beyond the screen
Timeline: 716-739 seconds
On-screen text: Excel follows the matching incident selection
Visual direction: export.png. Use focused crops; allow the audience to read each area.
NARRATION
The Excel action exports all incidents matching the current selection with report headings. That gives the filtered list a practical handoff beyond the on-screen page. Review the selection and the exported content before sharing it, and keep any sensitive incident information within the organisation's authorised handling process.
Transition: short dissolve.

SCENE 29 - Analytics for a broader review
Timeline: 739-763 seconds
On-screen text: Incident Overview and Follow-up complement the workspace
Visual direction: Existing dark slide. Use focused crops; allow the audience to read each area.
NARRATION
For broader analysis, the existing Health and Safety analytics covers Incident Overview and Follow-up, with supporting reports behind the configured measures. The operational workspace helps HR find and continue an incident. Analytics provides another perspective for reviewing the recorded information, subject to the portal and source access rules.
Transition: short dissolve.

SCENE 30 - From incident to follow-up
Timeline: 763-797 seconds
On-screen text: A clear process, with the supporting work close at hand
Visual direction: hrfocus-logo-verified.png. Use focused crops; allow the audience to read each area.
NARRATION
We have seen how MyFocus Health and Safety connects the incident overview with detailed capture, recorded progress, return-to-duty information, reports and linked tasks. Managers and HR continue through the access and workflow configuration that applies to their roles. The result is a clearer route from finding an incident to reviewing the work still to do. Arrange a walkthrough with your H R Focus representative to explore the process for your organisation.
Transition: short dissolve.
