What's New at LUMA1 — August 2026

A monthly note on the people, customers, product, and ideas moving LUMA1 forward. 

Last month's post drew a hard line: a training record and a ready worker are not the same thing. Most of what we shipped in August chips away at that gap from the record's own side. Closing off the ways “completed” could mean something less than it says, and handing more of that record back to the person it's about. And underneath it is the start of something bigger: a first real look at proving who someone is and what they're cleared for, right at the point they need to be let onto a site. 

What we shipped 

Completion has to mean completion 

• Locking the test until the training is done. A playlist can now be set so a learner can't open an assessment until every piece of content ahead of it is finished. There's a matching setting at the individual video level that hides the progress bar on a first watch, so there's no scrubbing past the parts that matter either. Any administrator can switch them on themselves. 

Handing the record back to the worker 

• A real profile page. Every learner can manage their own details, documents and credentials. They now have a profile of their own, reachable from their own menu, where they can update their name, mobile number, and the language their training is delivered in. They can also see every credential document they've uploaded and, for the first time, manage them. Every change, by them or by an admin, is logged along with what the value used to be. 

HammerTech Integration: One less profile to keep in sync 

• Live with HammerTech. LUMA1's course catalog and Ally Safety library now feeds straight into a worker's HammerTech profile. Training assignments, completions, and renewal dates sync automatically, because every LUMA1 course maps to a HammerTech license type, so nobody's re-entering the same completion twice. HammerTech stays the system of record for onboarding, orientation, and site records; LUMA1 handles the training and keeps it current, including early warning before something's about to expire. 

Smaller, but real 

• Expired reset links now say so. A reset link that's expired or unrecognized now says so plainly, with a way back to sign in and request a new one. 

• Reminders that know when to stop. Overdue certification reminders used to send every day, with no limit. They now taper off with a real cap and read like something that's already overdue rather than still coming up. 

• One pass finds every problem in an import. Uploading a user list now checks the whole file at once and reports every problem it finds, along with the filename and the row count it read. 

Where your data lives 

• Regional data residency for the UK and Canada. Customers hosted in the United Kingdom and in Canada now read data that is kept in their own region, instead of reaching across to the United States for it. This is worth knowing if you're the one who ends up answering data-residency questions. 

For the record 

Two things worth noting:

• SCORM. We export and import both SCORM 1.2 and SCORM 2004 4th Edition. Not just 1.2.  

• Languages. Full localized captions and neural voice cover in 80+ languages. Haitian Creole is also supported, but captions only, no neural voice yet. 

Proof, Not Just Paperwork 

We keep coming back to that Three Principles stat: 77 percent of construction workers killed in falls had completed working-at-heights training; only 16 percent were properly protected when it happened. A completion record didn't fail those workers because it was faked. It failed because “completed” can mean “sat through it,” “skipped the parts that felt slow,” or “genuinely learned it” and a checkbox can't tell you which. 

What we shipped this month closes one version of that gap: you can't call something finished until it actually is. The profile work closes a different one: the record is about the worker, so the worker should be able to see it, correct it, and manage the documents behind it, with a trail of what changed and when. 

Meet Sam: Customer Success Specialist 

Continuing what we started last month, this month’s conversation is with Sam, LUMA1's Customer Success Specialist. The person closest to what customers actually run into day to day.

What's your role at LUMA1, and what did you work on this month? 

I'm on the Customer Success team at LUMA1, where I handle onboarding, training, and helping clients build out their success plans. I'm also the go-to for troubleshooting, if something's not working or a client has questions on how to use the platform, that comes to me. This month has been heavily focused on onboarding and training new clients.

What's a readiness or safety problem you think the industry still gets wrong? 

One of the biggest gaps is treating "certified" as the same thing as "competent". Passing a quiz doesn't mean the material actually stuck. Add in content that's dry or checkbox-driven, and workers end up technically trained but not truly prepared.

Something outside work worth knowing about you? 

I live on the West Coast of Canada, so I'm an outdoors person through and through. Hiking or skiing in the mountains, a walk on the beach, or fishing on a river all make me happy.

What's next for Luma1

• Moving site access and card verification beyond the pilot tenant

• More of the same on the record-integrity side. This month's gating and profile work is a start, not the whole job. 

• More conversations with the people behind LUMA1

See you next month. 

John