Release notes in.
Vendor release notes and roadmaps are read into a review queue, not into the course.
↻ Change spottedHow it works
Training with a“checked on” date.
Every lesson names the vendor pages it was checked against and the day it was checked. When the software changes, the lesson changes. When the check date passes, the lesson can't ship.
The short answer
How does Train Space keep training current?
Vendor release notes feed a review queue. A person checks each change on the vendor's own page, rewrites the lesson and approves it. Lessons carry an expiry date for their sources, and an expired lesson fails the build.
Learners prove each skill on a check scored on the server, and mastery fades unless refreshed.
- Copilot lessons
- Rechecked every 45 days
- Responsible AI
- Rechecked every 90 days
- Everything else
- Rechecked every 180 days
- Pass mark
- 80%, scored on the server
- Refresh
- 3 questions, 21 to 30 days later
Part one: the software moves
From release note
to reviewed lesson.
AI tools ship faster than anyone can re-record a course. So Train Space doesn't record once and hope: it treats every lesson as a claim about the software, with a source and a date.
- Claude Code: 79 releases between 5 August and 3 November 2026
- Microsoft 365 Copilot: 44 new features between 23 September and 27 October 2026
- ChatGPT and Codex: 17 updates in October 2026 alone
Checked at the source.
Each change is checked on the vendor's own page and rewritten by a person, who approves it.
✓ Reviewed, then publishedStale can't ship.
A lesson whose cited page changed is flagged for a recheck. One past its source expiry fails the build.
✦ Dated on every lessonPart two: your people learn
Watch. Read. Try.
Then prove it.
A check that rewards picking the longest answer measures nothing, so question banks are held to rules too: the correct option can't be the longest one in more than 40% of a module's questions.
A starting-point check.
Placement suggests a level and picks the department version of each lesson. It suggests; it never locks.
A film and a short read.
One idea per module. The read is 350 words at most, and the build enforces it.
One prompt on real work.
The exact prompt to paste, with its own sample input, and what a good reply looks like.
Scored on the server.
At least eight questions, 80% to pass. The answer key never reaches the browser.
Part three: the record
Not who sat a course.
Who can do the work, today.
What a manager, an auditor or a customer can see.
01 / CURRENT STATUS
Mastery that fades.
A mastered skill asks for a refresh after 21 to 30 days, so the dashboard shows who is current, not who passed once.
02 / CREDENTIALS
Proof people can share.
Each program ends in a credential with a public verification link and an Add to LinkedIn button.
03 / EXPORTS
Records you can hand over.
Progress and, for the security program, an audit export of who was current as of any date.
House rules
What we won't say.
On this site, or in a lesson.
The rules every lesson and every page here are held to.
- Every figure has a source. Statistics on this site link to the page they came from, read on that page.
- Every comparison concedes. Each comparison page says when the other option is the better pick.
- “In preparation” means in preparation. Only the Copilot course is live; Claude, ChatGPT and Gemini say so.
- No “SOC 2 compliant.” The security program is built to support CC1.4 and CC2.2. No training tool makes a company compliant on its own.
A few good questions
How does it stay current?
The details.
Still wondering about something? Ask us and we’ll answer it here.
Ask your questionHow do you keep AI training up to date when the tools change every week?
Vendor release notes and roadmaps are read into a review queue. A person checks each change on the vendor's own page, rewrites the lesson and approves it. Every lesson carries the date its sources were last checked, and a lesson past its recheck date fails the build, so it can't reach a learner stale.
How often is each lesson rechecked?
It depends on how fast the subject moves. Microsoft Copilot lessons must be rechecked every 45 days, responsible-AI lessons every 90 days, and other lessons every 180 days. Example replies captured from a live tool expire after 90 days.
What happens when a feature is renamed or retired?
The lesson and its check change with it, and the change shows up in the course's What's new list. Feature cards are marked available, preview or retired, so people can tell what is on their screen today.
Why are checks scored on the server?
So the answer key never reaches the browser. The server draws a check, stores it, scores the submission and only then shows the answers and the reasoning. A result means the person answered, not that they read the page source.
Does a skill stay mastered forever?
No. Mastery needs 80% on a check of at least eight questions, and it fades: 21 to 30 days later the module asks for a short three-question refresh. Work-based modules are completed with a record of what the person did instead.
Can I see the sources behind a lesson?
Yes. Every lesson cites the vendor pages it was checked against, with the date. The public Copilot features page lists the Microsoft sources for every feature card.
Put the learning to work
Training that's true today.
And still true next month.
See Train Space with your own team.
Priced per seat, per year.