CourseLantern side
CourseLantern content workflow
Source mapping, script and scene design, stakeholder review, AI-avatar video, language versions, captions and transcripts, agreed course-package preparation, and content version records.
Delivery and system fit
Build for the LMS environment you already operate.
CourseLantern focuses on creating and maintaining the training content. Your LMS continues to manage learners, assignments, access, and reporting. We define the handoff with your administrator before production assumptions become delivery problems.
- Asset set
- Video / captions / transcript
- Test owner
- LMS administrator
- Handoff gate
- LMS test required
Source CL-014approved input
Scriptlesson sequence
Reviewedexpert approval
EN / ES / FRlanguage set
Videocontrolled output
LMS handofftested destination
System boundary
Two systems, different responsibilities.
Customer side
Your learning management system
Authentication, audience assignment, enrollment, learner access, due dates, completion records, scores, reporting, and retention of learner data.
Discovery checklist
Confirm the delivery behavior before choosing the format.
LMS product, version, and administrator contact
Accepted media, embed, or course-package formats
Hosting requirements and allowed external content
Completion and scoring rules
Caption, transcript, and accessibility requirements
Mobile and bandwidth constraints
Language selection and catalog structure
Test environment and acceptance owner
Replacement behavior when a module is updated
Reporting fields the business expects to see
Handoff path
From approved video to tested learning object.
01 / Define
Define
Document the LMS constraints, learner context, required outputs, and test owner.
02 / Prepare
Prepare
Produce the agreed media, captions, transcript, metadata, and package materials within the confirmed scope.
03 / Test
Test
Validate playback, language presentation, completion behavior, and other agreed criteria in the customer's target environment.
04 / Release
Release
The customer's administrator publishes and assigns the approved content through the LMS.
05 / Replace
Replace with control
When the source changes, use the version manifest and LMS replacement rules to plan the update.
Compatibility statement
Compatibility is confirmed, not assumed.
LMS configurations differ by product, version, enabled features, hosting policy, and reporting setup. CourseLantern confirms the required delivery route with the customer's LMS administrator and includes target-environment testing in the agreed handoff plan.
Technical answers
LMS integration questions
Use these answers to prepare the first conversation with your LMS administrator. Final delivery details are confirmed against the target environment.
Does CourseLantern replace our LMS?
No. CourseLantern produces and maintains training content for delivery through the LMS or distribution environment you already operate.
Do you support SCORM?
SCORM packaging can be discussed during discovery when it matches the target LMS and required tracking behavior. A confirmed scope names the supported version, package behavior, testing process, and responsibility for publication.
Can you provide a video file instead of a course package?
Video, captions, transcripts, hosted media, embeds, and course packages are possible delivery categories. The exact set depends on the customer's LMS, accessibility requirements, hosting policy, and agreed scope.
Who tests the content in our LMS?
CourseLantern can prepare the test asset and support a defined acceptance check. The customer's LMS administrator controls the environment and owns final publication, assignment, and reporting configuration.
What happens when a policy changes?
The version manifest connects the module and its language variants to the approved source. We use that record to identify affected content, scope the update, repeat the required review, and prepare replacement assets around the LMS's update behavior.
Technical discovery
Put your LMS administrator in the first conversation.
A short technical discovery at the beginning can clarify package, hosting, tracking, language, and update requirements before the content workflow is scoped.
Plan an LMS handoff