Nucleus OS Docs
    Getting started

    Launch to learners

    Enroll the right people, set due dates and reminders, communicate the launch, and track the rollout.

    Publishing a course makes it available. Launching it means the right people are enrolled, know why it matters, and finish on time. This page covers the launch checklist.

    Pilot with a small group

    Enroll five to ten people from the target audience first. Watch the common questions they ask the AI tutor and where they struggle; both usually point to gaps in the source material. Fix those before the wide rollout.

    Define who needs it

    Create an enrollment rule instead of enrolling people by hand. For example: everyone in the Support department, plus anyone who joins it later. Rules keep working as people join, move, and leave.

    Set due dates

    Use a fixed date for one-off campaigns ("complete by 31 March") or a relative date for ongoing programs ("within 14 days of start date"). Relative due dates are ideal for onboarding.

    Configure reminders

    Turn on reminders by email, Slack, or Microsoft Teams. A good default is a launch message, a reminder halfway to the due date, one two days before, and a manager notification if someone becomes overdue.

    Tell people why

    A short note from a leader explaining why the program matters lifts completion more than any reminder. Include the time commitment and the due date.

    Track the rollout

    Ask the analytics assistant questions such as "completion of the refund course by team this week" or "who is at risk of missing the deadline". See Dashboards to share a live view with stakeholders.

    Launch checklist

    ItemDone when
    Review gates passedApprover has signed off on the published version
    Pilot completeFeedback is in and source gaps are fixed
    Enrollment rule activeThe preview shows the expected number of people
    Due dates setFixed or relative, matching the policy
    Reminders onChannels chosen; manager escalation enabled
    Certification configured (if needed)Validity period and renewal set
    Dashboard sharedStakeholders can see progress without asking

    Compliance programs

    For regulated training, confirm the published version, due dates, and certification validity with your compliance owner before launch. Completion records are version-aware, so you can always prove who completed which version. See Compliance reporting.

    On this page