The authoring flow
Author or update a training in one full-screen flow that takes you from sources to a reviewed version. This page is the map; each step has its own detailed page.
Administrators (Quality Admin, HR Admin, Corporate Admin).
Start the flow
There are two ways in, both from the Training Library:
- New training: click New. You start a net-new draft at
/training-materials/new. - New version of an existing training: open a training card. You author a new version at
/training-materials/:id/edit, seeded from the current active version. - Translate an existing training: open the training card menu and select Translate with AI. The authoring flow opens a new editable draft in your selected app language, translated from the current approved version.
The flow opens full-screen with its own stepper. It is the same surface for both creating and updating, so you only ever learn one interface.
The five steps
The stepper runs left to right:
- Sources - pick the internal effective documents that anchor the training, plus topic, scope, language, and learning objectives. Details
- Content - draft the body with AI from your sources, or write it yourself. Details
- Assessment - build an optional quiz. Details
- Settings - signature requirement, scheduling, and recertification. Details
- Review - diff against the active version, write a change reason, and submit. Details
How the stepper navigates
- New training: navigation is forward-gated. You cannot move past Sources until you have at least one attachable source and a topic. This keeps content anchored to a regulatory basis.
- New version of an existing training: all steps are reachable straight away, because the existing content is already seeded.
You can always step back to revise an earlier choice.
Drafts are local until you submit
While you work, your changes live only in your browser. A net-new draft is saved to your browser's local storage automatically, but only once it holds real work (a name, topic, source, content, objectives, or a quiz question), so empty visits do not clutter the library.
Authoring iteration never writes a training version. Selecting sources, generating content, building a quiz, and changing settings all stay in your local draft. The only step that writes to the database is the Review step's Submit for review. This protects the audit trail: there is exactly one reviewable record per real submission, not one per keystroke. See Compliance and audit-readiness.
Translating a training
When you choose Translate with AI, Better Comply:
- Reads the current approved training version, including the official controlled document body when the training is document-anchored.
- Translates the content into your currently selected app language.
- Opens the translated text as an editable manual-content draft.
- Keeps the source attachment and review workflow intact.
The translation is not published automatically. Review the draft, adjust the assessment or settings if needed, then submit it for review like any other new version. A different approver must approve and activate it before learners can complete that translated version.
Resuming and discarding a draft
The Training Library lists your in-progress net-new drafts under In progress. Each draft offers:
- Continue - reopen the draft where you left off.
- Discard - delete the local draft.
Up to five drafts are kept per user; older ones are pruned when you start more.
Leaving the flow
If you try to exit with unsaved work, you are asked to confirm:
- New training: your auto-saved draft survives, so you can keep it or discard it.
- New version: edit-mode changes live only in memory, so leaving loses them. A browser refresh or close also prompts you first.
What submit does
Submitting from the Review step:
- Saves the training-level metadata (name, description, category, recertification policy) directly on the training.
- Creates a new training version in pending review, attaches your sources, and records a change reason.
- Routes the version to the Quality Review Queue, where a different person reviews and approves it.
A submitted version is inactive until a different approver activates it. You cannot approve your own version. See Segregation of duties.