Taking an 8-module cultural safety program from script to release

The situation

The department wanted a cultural safety program for its staff, delivered as eLearning. The cultural content and guidance came from the department's First Peoples staff. Script development was led by the studio's director, working with the department.

My job was to turn approved scripts into finished modules and get them through review, testing and release, so the department's staff and reviewers could focus on the content.

My role

I was the production and technical lead, responsible from approved script to release. I edited and formatted the scripts for the presenter and voiceover, did part of the Storyline build, made the later video edits, and owned testing, review rounds and delivery. During the release phase, every change request came to me.

I wasn't on the shoot. A freelance presenter, agreed by the studio and the department, presented on camera.

What I did

Prepared the scripts for filming

I formatted the scripts into filming documents for the presenter. After the first recordings, I listed missing voiceover lines. Later I prepared a re-record list, so the pick-up session covered everything in one go.

Ran review rounds module by module

From August 2024 I sent each module to the department for review. I collected the feedback, made or coordinated the changes, and sent the next version back. Early modules went through at least three rounds. Running modules on separate cycles spread the review load for the department.

Tested every module before it went out

I wrote testing documents for the modules and tested each version before it went to review. I made the release-phase updates in Storyline myself.

Brought user testing into the build

In January and February 2025, a testing group from the department used the first five modules. I reviewed the testing feedback with the department, module by module, and applied the agreed changes in March 2025.

Released and updated

In April 2025 a final round of script updates went across the modules. I applied them and delivered pre-release versions of all 8 modules on 28 April. Release versions and SCORM packages followed module by module between 8 and 16 May 2025.

What I'd do differently

• Pilot one module with users first. User testing came after five modules were built, so feedback meant rework across several of them. A pilot of one module would have caught the common issues earlier.
• Check voiceover against the final script on the day. Missing lines meant a second recording session. Next time I'd compare recordings to the script straight away and keep a pick-up list from the start.

Tools and skills

• eLearning: Articulate Storyline 360, SCORM packaging, staging previews
• Production: script formatting for filming, voiceover checks, pick-up lists
• Delivery: review-round management, change logs, release packaging
• Quality: module testing documents in Word and Excel