SOP from a recorded walkthrough (three-step)

Use this to turn a screen recording or call where someone explains how they do a task into a clear standard operating procedure. The model drafts the SOP, asks about the gaps, then produces a final version and a quick-reference checklist.

What you'll fill in

• [process name] The process being documented e.g. “Processing a wholesale order”
• [walkthrough transcript] Transcript of the recording or call where someone explains the process e.g. “(transcript of a 20-minute screen recording)”
• [sop audience] Who will follow this SOP and how experienced they are e.g. “New part-time warehouse staff with no prior system access”

The prompt

Steps: Step 1 — Draft the SOP → Step 2 — Resolve the gaps → Step 3 — Final SOP and checklist

How to use it

1. Open a new chat in Claude (the others work too).
2. Paste step 1 and replace every [bracket] with your details.
3. When it replies, paste the next step in the same chat.
4. Review the output, check any facts, and edit to taste.

Why Claude: Claude follows long, rambling walkthrough transcripts closely and writes clear step-by-step documentation.

Tips

3 tips for this prompt come with the pack.

Example output

Preview of the example output. The full example comes with the pack.

Try a free prompt from the same pack

Transcript to action items with owners and dates

Use this right after any meeting. Paste the transcript or your rough notes and get a clean action-item list with owners, due dates and source quotes, plus a list of anything left unassigned.

You are a meticulous chief of staff. Extract every action item from this meeting. Accuracy matters more than completeness of fields. Never invent an owner or a due date.

Meeting: [meeting name and date]
Attendees: [attendees]

Transcript or notes:
"""
[transcript or notes]
"""

Output:
1. Action items table with columns: # | Action (starts with a verb, specific enough to act on without the meeting context) | Owner | Due date | Source (a short quote from the transcript showing where this came from).
   - Owner: use the name only if someone clearly took it on or was clearly assigned it. Otherwise write "UNASSIGNED".
   - Due date: only if stated. Convert relative dates ("by Friday") into actual dates based on the meeting date, and show the original phrase in brackets. Otherwise write "No date".
2. Unassigned or vague items: anything that sounded like a commitment but has no clear owner or outcome ("we should look into..."), with a suggested owner based on roles, clearly marked as a suggestion.
3. Open questions raised but not answered.
4. Possible misses: anything an attendee said they would do that is easy to overlook (said in passing, mid-discussion).

Keep actions concrete: "Email the carrier to request a revised pickup window" not "Follow up on shipping".

FAQ

More prompts in Meeting notes to action items