How Vidext works
The lifecycle from raw company knowledge to measured learning.
Most organizations already have the knowledge they need. The hard part is turning it into learning: deciding what to teach, in what order, in what format, and how to verify it was understood — and keeping all of that current. Vidext moves that work into a system. Here is the lifecycle.
1. Bring your knowledge
Upload documents, import a website, or connect sources like Google Drive, Microsoft Teams, and Notion. Vidext processes each source in the background — extracting text and images, summarizing, and building a concept index — so everything downstream is grounded in your actual material, not generic content.
2. Vidext plans and builds
For an explicit creation request, Vidext plans the chapters, scenes, learning objectives, and knowledge checks internally, then starts the build without making you approve a separate outline. It infers the right teaching approach from how you describe the goal — you don't pick one from a menu (see Use cases). Where your prompt calls for it, Vidext can also research public or official sources to fill gaps.
The module opens as soon as production begins. Narrative, on-screen text, layouts, and interactions appear first; imagery and synthesized voice narration follow while the build continues. Presenter (avatar) video is deliberately absent from the draft.
Asking for a plan is different
If you explicitly ask for a plan or outline rather than a module, Vidext presents it in chat and stops. It does not create a module or start a build until you ask it to create one.
3. You review the draft
Review the actual learning experience instead of an abstract plan. Ask for structural or content changes by chat, select a scene or element to target it precisely, and use Preview to play the finished draft as a learner would. Building and editing only change the draft; neither reaches learners.
4. You publish
When the draft is right, choose Publish. That explicit action freezes the draft, renders presenter video for the scenes that need it, and validates the complete version. Learners stay on the previous published version until the new one passes verification; a first module remains unpublished until then. Published content remains editable by conversation afterwards: edits accumulate on your draft, and you publish again to push them to learners. See Draft and published.
5. Assign and deliver
Group learners into teams and assign courses to them — enrollment and notification are automatic. Or deliver inside your existing LMS via LTI, where learners launch the same experience without a new login.
6. Measure
Vidext captures first-party learning signals as people learn: time spent, scene and module completion, and quiz performance — structured data, not just "watched it." The direction of travel is measuring competence, not completion: whether people can actually do what the training was meant to teach. See Competence vs completion.
Where you stay in control
Vidext is autonomous in operational work, not careless in quality control:
- Generation is grounded in your sources, and the in-module tutor answers only from module content.
- Nothing publishes without your decision — builds produce drafts, and only an explicit Publish can move a verified version to learners.
- Published content is traceable back to the sources and the internal plan/build handoff that produced it.
- Access is governed by roles and permissions at the organization and team level.
Last updated on