Training records for audits

Training Records for Audits

Training records for audits have to show who completed which version of the training, when, and with what result. Syllabium is an enterprise learning management system (LMS) for regulated industries, made by Athantic AI LLC.

This guide sets out what an auditor asks of training records, and how Syllabium answers from its tamper-evident records and its versioned courseware.

What does an auditor ask of training records?

An auditor asks who completed which version of the training, when, and with what result. The auditor also asks whether the record has changed since it was made, and who has read or exported it.

The answers have to come from the record itself, not from a summary assembled before the audit. Security frameworks ask the same of training: NIST SP 800-53, the US federal catalog of security and privacy controls, has a control for it, AT-4, Training Records.

How Does Syllabium Answer Each Question?

Syllabium answers these questions from its tamper-evident records, and the question of version from the version each curriculum pins. Each entry carries a fingerprint, a short code computed from its contents, and a change to any entry shows.

The auditor asksHow Syllabium answers
Who completed it?Each person signs in to their own account, and every sign-in, failed attempt, lockout, sign-out and password change is recorded and kept two years. AI agents act through accounts of their own, and staff see “(AI)” beside an agent’s work.
Which version?The version the curriculum pins. Each curriculum pins every entry at a version, and its learners stay on that version until the next one is published.
When?Each entry joins its chain after the one before it, so a change to their order shows, and once a day the newest fingerprints are written to write-once storage.
With what result?Each attempt keeps the questions as they were asked and the pass mark that was applied.
Has the record changed?Every chain and seal is recomputed nightly and on demand, and a change to any entry makes every later fingerprint stop matching.
Did the learner accept the terms?Each acceptance of a versioned document is recorded. The consent record is built and not yet in operation.
Who has read the record?Each reading or export of a person’s record by someone else is recorded, whether it was shown or refused.
What did AI do?Every AI attempt is recorded with the check that decided it, and every model call with its model, its tokens (the units in which a model’s work is counted) and its cost.
Who approved the content?Every change to library content passes one publishing gate, which records its decision. Closed decisions download as CSV (a spreadsheet of plain rows), Markdown or PDF.

Where Do the Records Live?

The records live on the records and evidence page of the administrator console, beside the incident log and the consent versions. An administrator runs the export for an auditor from there, and every export is logged.

Compliance officers and auditors each have a role of their own, and an administrator exports the records for them. The incident log keeps every entry exactly as written; it is built and not yet in operation. Cohort staff can also export one learner’s lessons, attempts and surveys as a CSV file, and each such export is recorded.

What is in the export for an auditor?

The export for an auditor is one archive for a period: each record, a verification report, and a list of file fingerprints. Every export is logged.

A file fingerprint is computed from a file’s contents, so the same file always gives the same code and a changed file gives a different one. With the list in the archive, an auditor can recompute each fingerprint to check that no file has changed since the export was made.

What Makes a Record Tamper-Evident?

Each new entry carries a fingerprint of itself and of the entry before it. Change, delete or reorder one entry, and every later fingerprint stops matching.

  • Entries are added, never edited.
  • Records form chains of their own for each tenant, each organization and each kind of record, among them learning activity, consent, AI actions and publishing decisions.
  • The general audit log, the history of content and the record of each deployment are sealed row by row into a chain.
  • Every chain and seal is recomputed nightly, and on demand.

Tamper-evident means that a change shows; it does not mean that a change is impossible. The chain, from the entry to the auditor, is shown in full on Evidence.

What Is the Daily Anchor?

Once a day, the newest fingerprints are written to write-once storage outside the database, locked for seven years. Write-once storage keeps a file exactly as written: until its lock ends, no one can change or delete it.

An anchor holds fingerprints only, never personal data. Each anchor covers the chains up to the moment it is written, and the entries made after it are covered by the next day’s anchor. Comparing the database with the anchors is a procedure a person runs.

How Is Each Version Kept?

Content is authored once in a versioned library, and each curriculum pins every entry at a version, holding it fixed until a person accepts a newer one. When a newer version exists, the curriculum is told.

  • A curriculum can be frozen, and a frozen curriculum changes only by an override with a stated reason.
  • When a curriculum’s next version starts, its learners stay on their version until the next one is published.
  • A change to content flagged safety-critical stays hidden from learners until a second person approves it.
  • Each question in the question bank cites slide text word for word. When a cited slide changes, the question goes stale and is no longer drawn.

Authoring and versions are described in full on Courseware.

How Long Are Records Kept?

Retention periods are rules in the platform: most records are kept seven years, and the sign-in record and the record of who read whose record are kept two years. A nightly purge removes what has passed its period, and records what it removed.

A person’s own words can be erased while every fingerprint still verifies, and the erasure is itself recorded.

What Does the Consent Record Hold?

The consent record holds versioned terms, a privacy notice and a notice of how AI is used, and it is built and not yet in operation: it begins when the first documents are published. Before any learner page, the learner accepts each document in force. Once published, a document’s words cannot change, and each acceptance is recorded.

Are AI Actions in the Record?

Yes. Every AI attempt is recorded with the check that decided it, whether it was allowed, refused or failed, and every model call is recorded with its model, tokens and cost.

These records are tamper-evident and kept seven years, and their chained rows hold no prompt, no answer and no person’s words. A review of AI agents’ permissions is recorded, and is due every ninety days. How AI works under authority is on Governed AI and AI review before publish.

Which Standards Ask for These Records?

Syllabium is built to SOC 2 Type II, ISO/IEC 27001 and ISO/IEC 42001, and the evidence those standards ask for comes from the system itself, as records, not assembled by hand. 21 CFR Part 11 and EU Annex 11, the US and European rules for electronic records in medical technology and the life sciences, are planned targets.

Each standard is explained on Standards.

What Is Planned for Training Records?

Completion certificates, a transcript page for each learner, and continuing-education credit are planned. A page of their own for compliance officers and auditors is planned, and so is a signed-off periodic review of people’s access.

Get Started

Enroll your organization online, see the pricing, or talk to us. Syllabium is made and operated by Athantic AI LLC.

Contact us