PlaysbyMoat8
Back to the library
The workflow guideHR

Turn a workshop recording into a navigable learning guide

Package an authorized workshop recording as a chaptered training resource. Pair verified timestamps with concise companion notes so colleagues can revisit specific tasks.

6 implementation stepsIntermediate

How this works

A recording is difficult to reuse when colleagues must scrub through it to find a single procedure. This workflow builds a navigable learning artifact around the existing material, with concise instructions and explicit references to the corresponding moments.

The guide should help a learner find and repeat what was actually demonstrated. It must not quietly fill gaps with invented steps or expose internal information through a public video embed. A local HTML preview and companion document are useful outputs before publication is authorized.

Before you start

Release scope

Confirm who may access the recording, transcript and any demonstrated systems or examples.

Trainer review

Identify the subject-matter owner who can verify the instructions and note outdated demonstrations.

Playback source

Use a stable authorized recording or local video file with a known duration and timebase.

Prepare the inputs

recording
Required

video file or permitted player reference

Check duration, audio and whether edits have shifted timestamps.

transcript
Required

timestamped text with speaker labels if available

Identify gaps and uncertain words; do not assume transcript time exactly matches the player.

learning_goals
Required

audience and target tasks

Prioritize reusable procedures over every topic mentioned.

publication_scope
Required

local, internal or approved public

List redactions and access requirements before constructing embeds or downloads.

Implementation, step by step

  1. Inspect coverage and sharing limits

    • Inventory the recording, transcript and referenced materials. Check for sensitive screens, participant names and unsupported permissions.
    • Keep private sections out of derivative notes and record whether a redacted recording is required before sharing.

    Checkpoint: The source set and permitted audience are explicit.

  2. Build a topic map

    • Group the transcript into meaningful tasks, each with a clear learner outcome.
    • Separate demonstrated procedures from discussion, questions and speculative suggestions. Draft short chapter labels that describe the action.

    Checkpoint: The proposed chapters reflect actual teaching rather than arbitrary time slices.

  3. Verify chapter boundaries

    • Watch each proposed start and end in the recording. Adjust timestamps so the learner begins with enough context.
    • Check whether a demonstration spans multiple sections and link prerequisites instead of splitting a required sequence misleadingly.

    Checkpoint: Every chapter jump has been verified against the current video.

  4. Write companion instructions

    • Summarize prerequisites, demonstrated steps and the expected result in plain language.
    • Mark unclear or missing steps as trainer questions. Keep updates beyond the recording visibly separate and approved by the trainer.

    Checkpoint: The notes distinguish observed teaching from later editorial additions.

  5. Assemble the learning artifact

    • Use a simple accessible template with chapter links, readable notes and a fallback when embedded playback is unavailable.
    • For synchronized navigation, use the player’s supported events and retain a chapter index that works without synchronization.

    Checkpoint: The guide remains usable through keyboard navigation and direct chapter references.

  6. Test and hand off

    • Check every chapter jump, download, video permission and layout on a narrow screen. Ask the trainer to verify a representative procedure.
    • Deliver the local preview, companion notes and unresolved issues. Publish only when the destination and audience are authorized.

    Checkpoint: The handoff states which learning and playback checks passed.

Decisions along the way

A demonstrated interface has changed

Label the recording version and request an approved update; do not silently rewrite history.

A procedure cannot be reproduced from the source

Add a trainer question and withhold claims that the guide fully teaches it.

Embedded playback is blocked

Provide an authorized direct playback reference and chapter times instead.

What you will produce

workshop-guide.html

HTML

A local or approved-hosted navigable training guide.

Include: title · audience · chapters · video_reference · notes · version

chapter-index.csv

CSV

A portable chapter map with verified playback coordinates.

Include: chapter_id · title · start_time · end_time · learning_outcome · verification_status

companion-notes.md

Markdown

Concise instructions and unresolved teaching gaps.

Include: prerequisites · procedures · source_chapters · open_questions

Check the result

  • Verify all chapter starts after any edit to the recording.
  • Ensure notes contain no steps unsupported by the source or trainer approval.
  • Check that downloads preserve the same access and redaction boundaries as the guide.

When something goes wrong

Transcript timing drifts

Re-align against the recording and recheck every affected chapter.

Sensitive material appears in a demonstration

Hold publication and obtain a redacted version or omit the section.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Synthetic: turn an internal spreadsheet workshop into a reusable guide.

Inputs

A 24-minute recording demonstrates importing a CSV at 03:10 and validating totals at 11:40. The transcript omits a warning shown at 12:05.

Expected result

Create two verified chapters and include the visible warning only after trainer review. Link validation as a required next step after import; retain a local preview until internal hosting is authorized.

Run a small pilot

Start small

One workshop with two or three concrete procedures.

Record the baseline

Record how long colleagues take to find and follow those procedures in the unstructured recording.

Agree success criteria

Agree chapter accuracy and learner task-completion criteria with the trainer.

Stop or revise

Pause release when source permissions, redaction or instructional accuracy remain unresolved.

Keep the scope clear

  • A polished guide does not prove that learners have acquired a skill.
  • Do not publish participant information, internal systems or source media beyond the approved audience.

Check before using

The trainer verifies timestamps, instructional accuracy and what may be shared.

Business activities

  • Maintain shared company knowledge
  • Deliver courses and training

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Workshop recording · Timestamped transcript · Learning goals and release scope

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗