All classes Claude from Zero to Expert Syllabus · Episode 61 of 100

Claude from Zero to Expert Class #61: Writing SOPs That Are Easy to Follow

0 views

Learn to write SOPs (standard operating procedures) with Claude: uncover how the work is done through an interview, draft the SOP in an Artifact, test it with staff, then store it in a Project so it stays current. Example: the SOP for taking WhatsApp orders at Sunset Coffee. Episode 61 of 100, Session 13: Claude for Business.

Software: Claude
Level: Intermediate
Duration: ± 8 min
Series total: 15 h 1 min · 100 videos
Published: October 28, 2026

Episode 61 of 100 · view syllabus

Download PDF (5 PDF pages)

0 downloads

Unlock All Premium Classes ▶ Watch the video lesson0 plays

▶ Video Lesson

Watch every step above performed live, with English narration.

0 plays

Class book

Page 1 / 5

Claude from Zero to Expert Class #61: Writing SOPs That Are Easy to Follow: Cover: Claude from Zero to Expert Class #61: Writing SOPs That Are Easy to Follow

Claude from Zero to Expert Class #61: Writing SOPs That Are Easy to Follow: Before you start, step list, and Step 1: Why small businesses need SOPs

Claude from Zero to Expert Class #61: Writing SOPs That Are Easy to Follow: Steps 2–3: Let Claude interview you

Claude from Zero to Expert Class #61: Writing SOPs That Are Easy to Follow: Steps 4–5: Testing the SOP with staff

Claude from Zero to Expert Class #61: Writing SOPs That Are Easy to Follow: Done: summary and further practice

The end

Cover: Claude from Zero to Expert Class #61: Writing SOPs That Are Easy to Follow

Click a page or use ◀ ▶ to turn · swipe on mobile · to enlarge

Want to go deeper?

Join one of our courses or ask us directly on WhatsApp.

Download PDF· 0 downloads View the full 100-episode syllabus View Claude AI Courses Ask on WhatsApp

Recommended classes for you

Picked from the software, topic, and level of “Claude from Zero to Expert Class #61: Writing SOPs That Are Easy to Follow”.

6 episodesFree preview

Python · Intermediate–Advanced

Brain Tumor Segmentation with U-Net

6 video lessons with PDF guides, 1 h 10 min in total. Starts with: Brain MRI Dataset & Tumor Mask: Loading, Visualization & Patient-wise Splitting.

1 h 10 min 28 0

View class

50 episodesFree preview

Agentic AI · Beginner–Intermediate

Agentic AI Without Coding

50 video lessons with PDF guides, 14 h 29 min in total. Starts with: Chatbots, Automation, and AI Agents: What's the Difference?.

14 h 29 min 66 0

View class

Deep Learning CNN-LSTM Pneumonia Detection

6 episodesFree preview

Python · Intermediate–Advanced

Deep Learning CNN-LSTM Pneumonia Detection

6 video lessons with PDF guides, 57 min in total. Starts with: Chest X-ray Dataset: Loading, Exploration & Data Splitting.

57 min 22 0

View class

ANFIS Metaheuristics Time Series Forecasting

6 episodesFree preview

Python · Intermediate–Advanced

ANFIS Metaheuristics Time Series Forecasting

6 video lessons with PDF guides, 59 min in total. Starts with: Non-Linear Time Series: Dataset, Stationarity, and Patterns.

59 min 13 0

View class

Need more than a video?

Other ways we can help with Claude.

Learn with a mentor

Scheduled AI & Machine Learning courses with live guidance and a certificate.

Course

Midjourney Course: Create Stunning AI Images from Text

★ 4.9

Course

DALL-E Course: Creating Professional AI Images from Text

★ 4.9

Course

Stable Diffusion Course: AI Art from Beginner to Professional

★ 4.9

See all in AI & Machine Learning →

Have it built for you

No time to learn Claude? Our team can do the project for you.

Service

AI Image Creation with Stable Diffusion — Unlimited Custom Visual Production

★ 4.9

Service

AI Image & Video Creation with Leonardo AI — All-in-One Visuals for Business

★ 4.9

Service

AI Image Creation with Midjourney — Cinematic AI Art for Business

★ 4.9

See all in AI & Machine Learning →

Get notified about new Claude classes

At most one email a week. Unfollow anytime with one click.

Transcript

The full narration of this video. The current sentence is highlighted while the video plays; click any sentence to jump there.

Show transcript

Introduction

Hi, and welcome back to Claude from Zero to Expert. We're starting a new session, Claude for Business, where we create the core documents of a business. The first document we create is an SOP, a written work procedure. We'll uncover how the work is done, write a draft, test it, and then store it so it always stays current.

Step 1: Why small businesses need SOPs

SOP stands for standard operating procedure. It's a written sequence of steps for a task that repeats every day. Picture Sunset Coffee. Until now, Laras has been the one who knows best how to take WhatsApp orders. When Laras has a day off, Dimas often hesitates, and customers wait too long. A good SOP has four signs. First, the steps are numbered and short. Each step holds just one action, not several piled together. Second, every step starts with a verb, such as check, reply, record, or send. The reader knows right away what to do. Third, there are clear measures. Write reply within ten minutes, not reply as soon as possible. Everyone reads as soon as possible differently. Fourth, there's a way out when something goes wrong. For example, if the cold brew is sold out, what should Dimas offer the customer instead? These four signs are exactly what we'll ask Claude for, so the result isn't a long document that just sits in a drawer.

Step 2: Let Claude interview you

The hardest part of writing an SOP is remembering steps that have become habit. So we flip the approach: Claude asks, and we answer. Start with the role of an operations consultant. Then the context: your business name and the task you want to standardize. Just replace the parts in curly braces with your own business. The task is the key part. We ask Claude to interview us first, one question at a time, before writing anything. Finally, the constraints. We ask Claude to cover common mistakes, because that's the part most often forgotten in an SOP. After the prompt is sent, Claude doesn't write the SOP right away. It opens with the first question: what does Laras check before replying to an order? Laras answers casually, as if telling a story. Check the stock, especially cold brew, which often sells out in the afternoon, then ask for the address to work out shipping. Claude moves on to the second question, about the most common mistake. It's a question we rarely think of when we write on our own. Laras's answer is very valuable: forgetting to confirm the total and forgetting to record the order. These two will become required steps in the SOP. A few tips for answering. First, answer as if you're explaining things to a new employee. No need for formal language. Second, give real numbers, such as opening hours, reply time limits, or shipping costs. Numbers make an SOP measurable. Third, share the bad incidents that have happened before. Those incidents are where prevention steps come from. And one rule: don't paste customers' phone numbers or real conversations. Just describe the pattern.

Step 3: Drafting the SOP in an Artifact

After eight questions, Laras asks Claude to write the SOP as a document, with a purpose, a person in charge, numbered steps, and a section for problems. The document appears in the right panel as an Artifact. Notice the purpose and person in charge at the top, then the table of steps with time limits, and the out-of-stock section below. Laras reads carefully and finds one gap. The free shipping rule above two hundred thousand rupiah isn't written yet. She asks for it right away. This is why reading every step matters. Claude only knows what we tell it. Details missed in the interview are still ours to fill in. The structure Claude used here works for any SOP. Start with the purpose, which is the result you expect. Then the person in charge: who does the work, and during which hours the SOP applies. The core is the numbered steps with time limits. Try to keep it under ten steps. If there are more, split it into two SOPs. Finally, the section for problems, including who to contact. This section is what gives employees the confidence to make decisions.

Step 4: Testing the SOP with staff

An SOP isn't finished until it's tested. Laras asks Dimas to follow the SOP for three days without asking her anything. Every time he's confused, Dimas makes a note: which step, which term wasn't clear, or which order felt odd. Those notes go to Claude for improvements. Claude can split steps that are too long or replace confusing terms. Once improved, the SOP gets a version number and an effective date. That way, everyone knows which version is the latest. Here's an example. Laras sends two notes from Dimas, then asks for a one-page checklist version to post at the cashier's desk. Claude replaces the confusing term and adds an afternoon stock check. In the right panel, a short checklist appears with checkboxes, a version number, and an effective date. So one business can have two forms: a full SOP for training new staff, and a short checklist for daily use. These screens are simulations, and menu names may differ slightly because Claude is updated often.

Step 5: Storing and maintaining the SOP

A finished SOP shouldn't just sit in a folder. Laras adds it to a Project called Sunset Coffee Operations. Look at the instructions on the right: the SOP writing rules we just learned. The next file is the product price list. Since SOPs often mention prices and shipping, this one file is the single source. Then the opening and closing SOP, which is still a draft. Because the instructions are saved, new SOPs automatically follow the same format. Look at the chats on the left too. Dimas can ask, out of stock, what should I offer? Claude answers based on the official SOP, not something it made up. An SOP is a living document. Review it whenever prices, shipping, or opening hours change. Also when there's a new app or work tool, for example when Sunset Coffee starts using an online order form. If the same mistake happens twice, that's a sign one of the steps isn't clear enough. If new staff keep asking the same question, the SOP needs an extra example or picture. And even if nothing goes wrong, schedule a review at least every three months. Just send the old SOP to Claude and explain what has changed. Once your first SOP is done, write the next one with the same pattern. At Sunset Coffee, the next candidate is how to pack gift hampers, so the contents and presentation are always the same. In the office, Dewi at Maju Bersama Co. could write an SOP for receiving goods from suppliers: checking quantity, condition, and whether the invoice matches. Mr. Hendra at Cerdas Tutoring, could standardize how student attendance is recorded, including when to notify parents. For your own business, start with the task employees ask about most, or the one that causes the most mistakes. One SOP a week is enough. In two months, your business will have a complete work handbook, and you'll no longer be the only person who knows everything.

Done!

We've built an SOP from an interview, written it in an Artifact, tested it with staff, made a checklist version, and stored it in a Project so it always stays current. In the next episode we write proposals and offer letters that win over prospective customers. See you there!

Practice exercises

Try these on your own after watching to lock in what you learned.

Write one SOP for a routine task using the interview pattern from this episode
Ask a coworker to follow the SOP without asking questions, then note the confusing parts
Create a one-page checklist version to post at your workplace

Ask the class material

Type a question or keyword; we find the part of this episode that explains it and jump the video there.

My notes

Notes are saved with the current video time and are only visible to you.

Questions & answers

Stuck on a step? Ask here; the instructor and other learners can answer.

No questions yet.

Your instructor

Cerdas Inovasi Digital Team

Software developers, BIM & 3D engineers, and AI practitioners

53 video classes1,296 episodes

We build software, BIM models, games and AI automations for clients every day, and turn that hands-on work into step-by-step classes: every step is shown on screen and comes with a PDF guide you can keep.

See our clients →

Memuat

Claude from Zero to Expert Class #61: Writing SOPs That Are Easy to Follow

0 views

Software

Claude

Level

Intermediate

Duration

± 8 min

Series total

15 h 1 min · 100 videos

Published

October 28, 2026

Episode 61 of 100 · view syllabus

Unlock All Premium Classes

▶ Watch the video lesson0 plays

Transcript

The full narration of this video. The current sentence is highlighted while the video plays; click any sentence to jump there.

Show transcript

Introduction

Step 1: Why small businesses need SOPs

Step 2: Let Claude interview you

Step 3: Drafting the SOP in an Artifact

Step 4: Testing the SOP with staff

Step 5: Storing and maintaining the SOP

Done!

Your instructor

Cerdas Inovasi Digital Team

Software developers, BIM & 3D engineers, and AI practitioners

53 video classes1,296 episodes

See our clients →

▶ Video Lesson

Recommended classes for you

Need more than a video?

Transcript

0:03Introduction

0:24Step 1: Why small businesses need SOPs

1:29Step 2: Let Claude interview you

3:14Step 3: Drafting the SOP in an Artifact

4:25Step 4: Testing the SOP with staff

5:32Step 5: Storing and maintaining the SOP

7:38Done!

Practice exercises

Ask the class material

My notes

Questions & answers

Your instructor

▶ Video Lesson

Recommended classes for you

Need more than a video?

Transcript

0:03Introduction

0:24Step 1: Why small businesses need SOPs

1:29Step 2: Let Claude interview you

3:14Step 3: Drafting the SOP in an Artifact

4:25Step 4: Testing the SOP with staff

5:32Step 5: Storing and maintaining the SOP

7:38Done!

Practice exercises

Ask the class material

My notes

Questions & answers

Your instructor

Introduction

Step 1: Why small businesses need SOPs

Step 2: Let Claude interview you

Step 3: Drafting the SOP in an Artifact

Step 4: Testing the SOP with staff

Step 5: Storing and maintaining the SOP

Done!

Introduction

Step 1: Why small businesses need SOPs

Step 2: Let Claude interview you

Step 3: Drafting the SOP in an Artifact

Step 4: Testing the SOP with staff

Step 5: Storing and maintaining the SOP

Done!