top of page

What’s New at LUMA1 - June 2026

Blue LUMA update graphic with megaphone icon and text, We’ve got an update.

The first in a monthly note on the people, customers, product, and ideas moving LUMA1 forward.


We’re starting something this month that we intend to keep up: a monthly post about what’s changing at LUMA1. A plain account of who’s joined, what we’ve shipped, who we’re working with, and what we’ve been thinking about.


Some editions will lean heavier on product, some on people, some on the bigger questions about where workforce readiness is going. This is the first one, so it’s a little of each.

 

The idea this month: being App-less

LUMA1 has always been App-less. It’s not a new feature or a pivot,  it’s how the platform has worked from the start, and it’s worth saying plainly, because it’s the thing that makes everything else possible.


The frontline doesn’t live in one place. A foreman runs his day on WhatsApp. A site standardizes on an App like innDex, Hammertech, Quentic or their own. The office and the PM live in Teams. On a remote job, SMS might be the only channel that reliably reaches anyone. Workers move between these tools all day, and no single one of them is “the” place training should live.


So we don’t ask anyone to come to us. Because LUMA1 is a web app, there's nothing to install, no app store, no account a worker has to create before they can do anything useful, we can show up inside whatever they already use. The same content can be shared into an App, sent over WhatsApp, their LMS, dropped into Teams, accessed by QR code, email or texted as a link. A completion lands in the worker’s existing profile instead of in some parallel record nobody checks.


That’s what App-less means: not that we have no interface, but that we never require anyone to adopt a new one. Less friction, fewer logins, no new icon to keep track of and training that meets people wherever they already are.


The job of a readiness platform isn’t to win attention. It’s to remove the excuse. “No worker starts without clearance” only works if clearance is genuinely easy to deliver and impossible to dodge  and you get there by meeting people on their turf, not by asking them to come to yours.


You’ll see this idea running straight through this month’s product work.


What we shipped

A busy month from Eric and the team. Grouped by what it actually does for you, rather than the order it landed.


Meeting workers where they are

  • Share to WhatsApp. A redesigned share dialog now lets you push content and full playlists straight to WhatsApp. This is the App-less idea made literal training that arrives in the app the crew already checks.

  • More integrations. LUMA1 runs in over 70 different apps and learning management systems and counting.  We also use these integrations to become your single source of truth for readiness giving you full visibility of your employees, sub-contractors, contingent workers and temps all in one place.

  • New mobile web app experience. A new navigation experience that makes the on-phone experience faster to move through for the people who use it most workers, in the field.  New additions include new video capture and processing ideal for capturing and sharing knowledge and new reporting.


A better training experience

  • Resume and retake. Admins decide where resuming is appropriate and where a fresh start is required.

  • Choice-question hover effect. Optional per-option hover styling that makes questions clearer and easier to answer correctly in busy frontline environments.

  • Tutorials hub refresh. Cleaner in-product tutorials and help, so people find the answer without leaving the screen they’re on.


Managing content and people at scale

  • Group Assignments. Assign content and certifications to whole groups at once, with a dedicated report to see where each group stands.

  • Content archiving. Archive and unarchive catalogue content to retire outdated material or old versions hidden from learners and kept out of reports, without being deleted. This makes records management simple.

  • Playlist Topics manager. Bulk-edit topic titles and descriptions across an entire playlist from a single screen.


Reporting and admin

  • Summary report. A new summary view with monthly and annual periods and selectable items, for the roll-up numbers leadership actually asks for.

  • Date format preference. Choose US or international (DD/MM/YYYY) per site. A small thing that matters a lot when you operate across the UK, Canada, and the U.S.

 

A note on LLMs, and what they’re for

There’s a lot of noise right now about AI doing everything. We have used AI from the very beginning, and we’re clear-eyed about where it belongs.  It’s worth saying plainly what we think.


Importantly, how text-heavy a subject is matters. For example, highly specialized subjects in the world of work won't have reliable coverage. What a large language model is extraordinary at one thing: language. That's why we can voice and translate content across 80-plus languages at a quality and speed that simply wasn’t available a few years ago. That’s real, and our customers feel it every day in how fast multilingual content reaches a multilingual crew.


But a model is a tool for delivery, not a source of truth. It can render a toolbox talk in Punjabi beautifully. It cannot tell you whether the worker who watched it is actually ready to work at height. It predicts the next likely word; it does not witness the work.


That distinction between delivering training and proving readiness is the whole game in safety, and it’s where we think a lot of the industry is about to make a category error. The temptation is to let a model “assess competence” because it sounds efficient. We won’t. We use AI to move language; we use measurement, not models, to decide what a worker has actually demonstrated. Outcomes decide what can be claimed. A confident sentence from a model isn’t an outcome.


Used inside those lines, AI is a genuine advantage. Asked to carry weight it can’t bear, it becomes a liability dressed up as progress. We’d rather know the difference.


What’s next for LUMA1

We’ll keep building toward the same thing we always have: making sure no worker starts unready, with as little friction as the job allows. More App-less channels, deeper integrations into the systems sites already trust, and next month an introduction to some of the people making it happen.


See you next month.


John

 
 
 

Comments


bottom of page