Turn a screen recording into checked instructions

A screen recording can become clear instructions, but a transcript is only the starting point. Extract the steps, tie them to timestamps and have someone else perform the job using the draft. Missing clicks, private information and spoken guesses need a review before the instructions are shared.

This is a fictional example. The transcript and timestamps below are invented to demonstrate the method. There is no underlying recording presented as real evidence.

Source excerpt

00:00: Open the weekly order export. Make sure it is the current week.

00:18: Filter to orders marked ready. I usually hide these duplicate rows here.

00:42: Copy the order IDs into the dispatch checklist.

01:05: If an order has no address, leave it out and ask Daniel.

01:24: Save the checklist. I think we send it to the warehouse, but Daniel does that bit.

The excerpt is not enough to publish a final procedure. “Current week” needs a date rule. “Duplicate” needs an identifier rule. The final send belongs to Daniel and was not demonstrated.

The checked draft

Purpose: prepare a dispatch checklist for the approved weekly period.

Input: the weekly order export and the period agreed by the operations owner.

Output: a saved draft checklist containing unique ready-order IDs, plus a separate held-order list.

1. Confirm the export covers the agreed dates. Record its filename and source date. If the dates are unclear, stop.
2. Filter the status to ready. Keep the original export unchanged. Source: 00:18.
3. Group rows by order ID. Flag repeated IDs for review. Do not delete rows until the owner confirms which row is authoritative.
4. Copy each approved unique order ID into the draft checklist. Source: 00:42.
5. Put an order with no address on the held-order list and assign it to Daniel. Do not include it for dispatch. Source: 01:05.
6. Save the checklist as a draft with the period in its name. Source: 01:24.
7. Ask Daniel to check the checklist. Sending to the warehouse is outside this recorded procedure until Daniel supplies and verifies that step.

The draft is more precise than the transcript because it makes the gaps visible. It does not quietly fill them with plausible clicks.

Instructions you can reuse

Convert this approved transcript into a procedure. State its purpose, inputs, output, prerequisites and numbered steps. Cite a timestamp for every observed action. Separate observed steps from questions or proposed checks. Do not invent screen controls or the final action. List sensitive details that need removal before sharing. Finish with a test someone else can perform.

If using images from a real recording, crop or redact private information before sharing. A transcript may omit information still visible on screen. Permission to record does not automatically settle permission to publish.

Test it with someone who did not record it

Give a reviewer the draft and a safe copy of the input. Ask them to produce the checklist without help from the person who recorded it. Record where they pause, what they assume and whether the output matches the expected list.

Include a wrong-week export, duplicate order IDs, a missing address and an unexpected status. Check that each reaches the stated hold. If the reviewer needs an unrecorded explanation, add it to the procedure and test again.

A passing read-through is not enough. The check is whether another person can complete the job and identify the exceptions. Save their result beside the instruction version and source version.

Publish the tested version

Name the person who owns updates and the event that triggers a review, such as a changed export or screen. Keep a revision history. If a control changes, hold the affected step until it is checked again.

The finished artifact is the tested procedure, the held questions and the review record. It is not an unsupported claim that any recording becomes a complete manual.

The standup-to-actions kit covers another way to turn spoken work into a checked output. The client onboarding example shows how to name owners before creating tasks.

Keep a record of the finish

Record the source version, draft version, reviewer, decision and time. A correction changes the draft version and cancels the earlier approval. Save the final destination and its reference separately from the review decision.

If the last action fails, check the destination before trying again. A missing reply does not prove nothing happened. Keep the job on hold until its owner has checked. Never repeat a send or create a second record just to clear an error.

Use the sample build plan to name access, stop rules and recovery. Start with the Job Picker if you are still choosing the job. Session bookings aren't open yet. We'll email when dates are available. There's no opening date to announce yet. Join the AI With Hands Session waitlist for help choosing your first job.