Skip to main content

    New feature

    Prove they read it. Not just that they finished the course.

    Compliance Sign-off records that a named person agreed to a specific statement, in a specific language, on a specific version of your policy - with a timestamp set by our server. Permanent, impossible to edit, and exportable to CSV the moment an auditor asks.

    What is a compliance sign-off?

    A compliance sign-off is a page in a course where a learner reads a short statement - for example "I have read and understood the code of conduct" - and confirms it. CourseAgent saves who confirmed it, the exact words they agreed to, which version of the course they saw, the language they read it in and the time our server recorded. Nobody can change or delete that record, and you can download the whole list as a spreadsheet whenever someone asks for proof.

    The problem

    "Course completed" is not evidence.

    • An auditor asks who accepted the code of conduct this year - and the answer lives in a spreadsheet, a mailbox or a drawer.
    • Your LMS records "course completed". It cannot show the wording the learner agreed to.
    • The policy was updated in March. Nobody can say who signed the old version.
    • Half your workforce reads the policy in another language. There is no record of which one they read.

    A sign-off closes that gap. It captures the statement itself, not a note that somebody once ticked a box.

    Eight things in every record.

    Add a sign-off to any page of any course, write the confirmation statement yourself - with links out to the full policy - and optionally require the learner to type their first and last name as well as ticking the box. Every confirmation then writes one permanent record.

    What a CourseAgent compliance sign-off record contains
    RecordedWhy it matters
    Who signedName and email, or the LMS learner id - the individual is identified.
    The exact wording they agreed toThe evidence itself, stored in full - not a pointer to a document that may since have changed.
    The sign-off labelThe policy name as it appears in your reports and audits, for example "Code of conduct 2026".
    The timestampSet by our server, never by the learner's device, so it cannot be shifted.
    The course versionProves which edition of the policy they actually saw.
    The languageProves they read it in a language they understand.
    How they reached the courseAcademy, shared link or their own LMS.
    Their typed name, if requiredAn extra deliberate act of confirmation on top of the tick.

    The clock is ours, not theirs

    The timestamp is generated by our database and never sent by the browser, so a learner cannot change when they signed.

    Evidence you cannot lose

    Records are insert-only - nobody can edit or delete them through the product - and they survive deletion of the section, the page and the entire course.

    Not optional

    No sign-off, no certificate.

    A sign-off is always mandatory - there is no switch to make it optional, because an optional attestation is worthless. It behaves as a forward barrier rather than a simple page tick.

    • Continue is blocked on the page until the sign-off is confirmed.
    • Every page beyond it is locked in the navigation menu, with the reason shown.
    • The course cannot be completed and no certificate is issued.
    • Moving backwards is always allowed - learners can re-read anything.
    • This holds even in free-navigation courses, and even when page-interaction rules are switched off.
    The report

    One screen answers "show me the evidence".

    Insights includes a Sign-offs tab covering the whole account, and the same report appears inside each Academy for administrators there.

    See it, filter it, export it

    • Five figures at the top: Expected, Signed, Outstanding, Compliance percentage and average time to sign.
    • Filter by course, sign-off, status, date range, delivery method and academy group; search by name or email.
    • Choose your own columns - including typed first and last name, course version, language and last reminder.
    • Export everything to CSV. That file is what you hand the auditor.
    • Academy administrators see the same report, scoped to their own academy only.

    Chase the stragglers in one click

    • Chase anyone outstanding individually or in bulk, up to 200 at a time.
    • One email per person listing everything they still owe - nobody gets five emails.
    • One reminder per person per day; repeats the same day are skipped and reported.
    • A confirmation dialog names exactly who will be emailed before anything is sent.

    Where it runs - and where it does not.

    A sign-off needs an identified learner. Where there isn't one, we record nothing and say so rather than pretending.

    Delivery surfaces where compliance sign-off is active
    DeliverySign-offLearner identity
    Academy portalYesTheir academy account
    Assigned / sign-up linkYesThe learner account on the link
    Launched from your own applicationYesThe signed link identity you pass
    Dynamic SCORM in your LMSYesThe LMS learner id
    Open public linkNoNo identified learner - nothing recorded, nothing gated
    Static SCORM packageNoOffline file, no live connection

    What we do not claim.

    Compliance software that oversells itself is a liability. Here are the boundaries, in plain language, before you buy.

    It is not a digital signature

    There is no certificate authority and no cryptographic or qualified e-signature. It is an authenticated acknowledgement backed by a server-side audit record - which is what internal policy attestation actually needs. It is not a replacement for a contract e-signature product.

    Open links and static SCORM record nothing

    Both are anonymous, so there is no learner to attribute a record to. The panel shows an explanatory line instead and nothing is gated. If your whole distribution model is anonymous open links, this feature will not help you as it stands.

    We cannot email reminders to LMS learners

    When someone opens a dynamic SCORM package in your own LMS, the LMS holds their email address, not us. Those rows are still counted and reported - they simply say "Sent by the LMS".

    Built for every learner on the list.

    24 languages, full RTL

    The learner card, the report, every filter and column heading, the status pills and the reminder email are all translated - including Arabic, Hebrew, Persian and Urdu with a mirrored layout.

    Screen-reader ready

    Table captions and header associations, named icon-only controls, the row expander announcing its state, reminder results announced and visible keyboard focus.

    Works on a phone

    The report becomes a stacked card list - one card per sign-off, tap to expand - with figures two across and filters full width.

    Insert-only by design

    Records cannot be edited or deleted through the product by anyone, including the account owner, and they survive deletion of the section, the page and the whole course.

    The questions every compliance lead asks.

    Start your 14-day free trial today.

    Full Professional access. No credit card. No technical skills required.
    Just describe what you want to teach.

    See what's included in the 14-day trial →