Case study 08

Keeping a 50-title eLearning catalogue current, including a 2026 law update

Period
Aug 2022 – present (law update Jul – Aug 2026)
Role
Production lead and Go1 technical contact
Reading time
3 min read

I updated the studio's heavy vehicle safety course for the 2026 law changes, built a short bridging module for people who'd already completed it, and look after the studio's catalogue on the Go1 marketplace.

The situation

The studio sells its courses to organisations through Go1, a global eLearning marketplace. One of them covers Chain of Responsibility, the shared duty for heavy vehicle safety under Australian law. Amendments to the Heavy Vehicle National Law took effect on a single date, 1 August 2026, with no grace period. The course had to reflect them by then.

Go1 also asked its content partners to map their catalogues to its compliance categories, with evidence for each title.

My role

I've been the studio's technical contact for Go1 since 2022: uploads, course metadata, refreshes and support cases. For the law update I owned the script correction, the bridging module and the release.

What I did

Corrected the course against the law, not memory

I checked every legal statement in the script against primary sources: the amending legislation and official guidance. Each correction went into a change log with its source, and into a tracked-changes copy so the reasoning stayed visible. A separate, independent review, run with an AI assistant, then checked the corrected script. I worked through its findings item by item, confirmed each one against current sources before changing anything, and extended the change log from 44 to 53 rows.

Built a bridging module for returning learners

Returning learners didn't need to redo the whole course, so I built a short bridging module that covers only what changed. It follows the main course's structure, style and tone, and ends with a five-question assessment with a 100% pass mark. It was published to Go1 in August 2026.

Mapped the catalogue to Go1's compliance categories

I mapped all 50 published titles to Go1's compliance categories. Each row gives the reasoning and an evidence source. Much of the studio's workplace safety, transport and privacy content had no matching Australian category. Rather than force a match, I flagged those rows clearly.

Handled Go1 support cases

When Go1 raises a case about one of the studio's courses, it comes to me. Cases range from a quiz answer a learner thinks is wrong, to missing course duration data, to an enterprise customer whose learners get stuck partway through a module. I investigate, fix and republish where needed, and reply with what I found. In 2023 I also arranged an accessible alternative for a learner who needed one.

Kept the catalogue healthy

Over the years I've split a long course into shorter modules, refreshed courses, reviewed accessibility metadata and prepared source materials for a First Nations adaptation of one course.

Results

  • The course script corrected against the amended law, with a 53-row change log tied to sources.
  • A bridging module for returning learners, published to Go1 in August 2026.
  • All 50 published titles mapped to Go1's compliance categories, with evidence for each.
  • The studio's point of contact for Go1 support since 2022, from quiz feedback to customer playback issues.

What I'd do differently

  • Source every legal statement from the first draft. The review found references that had gone out of date. If each statement had carried its source from the start, updates would be a quick check, not a search.
  • Keep a living catalogue register. The compliance mapping meant gathering details from many places. A register of every title, with its version, metadata and evidence, would make the next request a short job.

Tools and skills

  • eLearning: Articulate Storyline 360, SCORM packaging, the Go1 partner portal
  • Catalogue management: metadata, compliance mapping, partner support cases and fixes
  • AI: an AI assistant (Claude) for the script review and drafting, with every change checked against sources by me

What it looked like (recreated)

Change log layout. Recreated with invented data.
RowModule and screenOld text (summary)New text (summary)ReasonSourceReviewed
41Module 2, screen 4A duty described under the old section numberSame duty, current section numberSection renumberedAmending ActYes
42Module 2, screen 7A penalty amount from the old schedulePenalty amount from the current scheduleAmount changedOfficial guidanceYes
43Module 3, screen 2A term defined in older wordsThe term as now definedDefinition updatedAmending ActYes
44Module 4, screen 5A scenario that relied on a repealed ruleScenario rewritten around the current ruleRule repealedOfficial guidanceNo
45Assessment, question 3An answer option that is now incorrectOption corrected, feedback updatedFollows row 44Row 44No
Catalogue mapping extract. Recreated with invented data.
Course titleCompliance categoryMatchReasoningEvidence source
Course AWork health and safetyDirectLearning outcomes cover the category in fullCourse outline
Course BTransport safetyPartialCovers most of the category, not every topicScript, module list
Course CPrivacyPartialCategory is written for another jurisdictionCourse outline
Course DNo matching categoryNoneFlagged rather than forced into a near matchMapping note
Bridging module outline. Recreated with invented data.
PartWhat it coversLength
1. IntroductionWho the module is for and why it exists1 screen
2. What changed at a glanceA short summary of each change1 screen
3. Topic AThe first change, with a worked example3 screens
4. Topic BThe second change, with a worked example3 screens
5. Topic CThe third change, with a worked example2 screens
6. AssessmentFive questions, 100% pass mark5 questions
7. CloseSummary and where to find more1 screen

Client and partner names, and some details, are left out. Any visuals are recreations with invented data.

Jump to a case study

Arrow keys move through the results.