Case study 08 · Aug 2022 – present (law update Jul – Aug 2026) · Production lead and Go1 technical contact # Keeping a 50-title eLearning catalogue current, including a 2026 law update 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. ## At a glance - **My role:** production lead for the update; the studio's technical contact for Go1 - **Period:** Aug 2022 – present (law update Jul – Aug 2026) - **Scale:** 50 published titles on Go1 (as at Aug 2026); a full course script corrected; one new bridging module - **Worked with:** the studio's director and Go1's partner and support teams - **Tools:** Articulate Storyline 360, SCORM, the Go1 partner portal, Word, Excel - **Headline outcome:** the course and a new bridging module reflected the amended law, and the catalogue was mapped to Go1's compliance categories ## 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 --- *Client and partner names, and some details, are left out. Any visuals are recreations with invented data.*