3 seats free. No card. Upgrade per seat as you grow.
Free forever for teams up to 3 seats.
Your newest hires learned from YouTube, not textbooks. Here's why your training is failing them.
Free download. No credit card required.
A PDF or CSV showing which people drilled on which procedures, on which dates, with which results. This page is what's in the export, how it lands in your hands, and how the data supports the training-evidence conversation. The formatted, version-pinned audit pack is on the roadmap.
An export is generated for a date range, a group (or set of groups), and a module (or set of modules). It contains a row for every drill answer in that scope. Each row carries: the learner's identifier, the module, the source passage the drill came from, the question shape, the date and timestamp of the answer, and whether the answer was correct.
A per-learner summary and the per-drill detail table, formatted to read and to forward. The fully formatted, version-pinned audit pack (narrative cover, signature block) is on the roadmap.
The same data, machine-readable. Drop it into your GRC tool, pivot it in Excel, or merge it with HRIS data. One row per drill answer, all fields included.
A traditional LMS export shows: learner X completed course Y on date Z. The follow-up question, "and how do you know they remembered any of it the next month?", has no answer in that format. The HeyLoopy export answers the next-month question by design, because the drill is a retrieval attempt and the result is logged.
When you need to show which staff were drilled on a procedure within thirty days of an SOP change, the export filters to that date range and that module, and the answer is in the table. The chain from a procedure to a specific learner answer on a specific date is traceable. The named admin who approved that drill's wording is tracked separately inside the product (see drill quality control); version-pinning and a compliance-grade audit log are on the roadmap and not exported today.
The FFIEC examination manual sections on BSA training expect evidence that staff were trained on current typologies and that training is current. The export shows per-officer, per-typology, per-date: the kind of evidence that conversation calls for.
OSHA 29 CFR expects documentation of training content, dates, and who was trained. The export covers all three; the source-passage anchor adds the content provenance most internal-only training records skip.
Competency-assessment requirements expect evidence the clinical team can apply the procedure, not just acknowledge it. Drill answers against scenario-shaped questions provide a stronger artifact than completion certificates.
The same evidence shape works for the Indian regulatory environment. The export does not impose a US-only schema; the auditor's specific format expectations are met by selecting fields in the CSV view or annotating the PDF cover.
FCA operational-resilience expectations on staff competency, HSE training-records guidance, and CQC fundamental-standards expectations on staff training all read the same evidence shape comfortably.
EU customer onboarding requires DPA template and SCCs work in progress on our side. The audit export shape itself is compatible with GDPR Article 28 processor expectations; the contractual posture is what's pending. See trust and data residency.
From the admin dashboard, an authorized administrator selects the date range, the modules or groups in scope, and the format (PDF, CSV detail, or both). The export generates and downloads. There is no waiting on a HeyLoopy support ticket. There is no spreadsheet hand-built off raw data. The records you hand over are the records the product produces directly.
For recurring audits, the same export can be scheduled (roadmap item) and routed to a fixed location. For ad-hoc regulator requests, generation is on demand. Compliance-grade controls on the export action itself (immutable retention, separation-of-duties enforcement) are roadmap; today the product tracks who generated the export and when.
The export is evidence of training; it is not a substitute for your own SOC 2 controls. HeyLoopy aligns to SOC 2 Type II controls but is not yet independently certified. See trust and data residency.
No regulator pre-approves training-evidence formats. The shape and contents were designed to hold up under examiner review based on the framings above. We do not promise specific regulators have endorsed the export.
The export covers drill activity since your team started using HeyLoopy. Prior training records from your previous LMS are not magically migrated; those stay where they were.
Free for teams up to 3 seats. Or email the founder for a sample export PDF tailored to your situation.