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, let's continue the Artifacts session. Today we create our very own first Artifact, starting with what's needed most often: documents and checklists. We'll plan the request, create a store-opening SOP for Sunset Coffee, turn it into a checklist you can tick, look at examples for offices and schools, and then put the results to use.
Step 1: Planning the request
Many small businesses run on the owner's memory. Laras knows by heart how to open the store, but when she's sick, Dimas often forgets a step or two. An SOP document turns a procedure in your head into a guide anyone can use. With Artifacts, making one takes only a few minutes. Before typing, plan the request in five parts. First, the task: create a store-opening SOP as an Artifact that can be printed. Second, the context: who uses it and where it's read. This SOP is for Dimas or new staff, posted on the kitchen wall, and the store opens at eight. Third, the data. Laras writes down the rough steps, even though they're not in order yet. Claude will tidy them up, but the content still comes from Laras's experience. Fourth, the format: a title, a one-sentence goal, numbered steps with estimated times, and important notes. Fifth, the limits: one page max, simple language, and short command sentences. These five parts don't have to be long. What matters is that Claude knows who the document is for, what it contains, and what the final form looks like.
Step 2: Creating an SOP as an Artifact
Laras sends her request. To keep things short, the screen shows only the core task and her rough list of steps. The right panel shows the SOP: a title, a goal, five numbered steps with estimated times, and an important note about milk stock. The total is about thirty minutes, so Dimas starts at seven thirty. The next step is always the same: read it carefully. Laras checks the order of the steps, the time estimates, and whether anything is missing. Something is missing after all. Laras usually plays music and turns on the sign lights, and that step isn't there yet. Laras asks for two changes in one sentence: add a step to turn on the sign lights and play music, then make the verb at the start of each step bold. Version two appears right away. The verbs are bold, so Dimas can scan the SOP in two seconds. Notice too that Claude adjusted the time for step five so the total stays at thirty minutes. From that example, there are three ways to ask for specific changes. First, name the part to change. Step three is much clearer than the middle part. Second, name the result you want. Make the verbs bold is clear, while make it nicer could mean anything. Third, name what must not change, such as don't change the order of the other steps. This keeps the parts that are already good safe. We'll go deeper into revisions and managing versions at the end of this session.
Step 3: A checklist you can tick
The document is done; now let's make it more practical. Laras asks for the SOP to become an interactive checklist: every step can be ticked, with a counter and a button to start over tomorrow. The result appears in the right panel. At the top is a counter card showing four of six done, and a ready-by time of eight o'clock. Below are six steps with checkboxes, and a start over button. This is the difference from a regular document. Dimas can open this checklist on his phone or the till computer, then tick the steps one by one as he works. No step gets missed. It's important to test it: click every box, make sure the counter goes up, then press start over. Interactive Artifacts must be tried, not just looked at. Laras wants to know who opened the store and what time they finished. She asks for a staff name field and a finish time. Version two shows the staff name field, Dimas, and a finish time card at seven fifty-six, four minutes before opening. One small request turns this checklist into a work log as well. If you want the ticks to be kept from day to day, say so in the request, then test it by closing and reopening. The ability to save data can vary, so don't assume. So when do you use a document, and when a checklist? An SOP document is usually printed and posted. An interactive checklist is opened on a phone or computer. A document suits guides and training new staff. A checklist suits work that's done hands-on every day. A document's strength is that it's complete with reasons and notes. A checklist's strength is that no step gets missed. Many businesses use both: the document for learning, the checklist for working.
Step 4: Examples for offices and schools
The same pattern works at school. Mr. Hendra asks for a math exam prep checklist for grade nine students, from seven days before the exam to exam day, in language that's friendly for teens. Claude splits the preparation by day in a table with a tick column. Students no longer cram all night, and Mr. Hendra can share this checklist before every exam. Mr. Hendra still checks the content, for example making sure each day's topics match his tutoring syllabus, before sharing it with students. Another example: Nadia writes an Instagram management service proposal for a bakery. One page, polite, with three packages and no prices. Claude writes the letter with a polite opening, a table of three packages, and a closing. The price column is left blank on purpose, because prices are Nadia's decision, not Claude's. Here are a few more ideas. Dewi at Maju Bersama Co. creates a monthly meeting prep checklist: invitations, presentation materials, the meeting room, and minutes. Nadia, the social media freelancer, creates a one-page service proposal letter with service packages and how to work together, for prospective clients. Laras creates a till-closing SOP: count the cash, match it against the sales records, then store it. And anyone can create an event prep list, for a bazaar, a seminar, or an exhibition. Try picking the one closest to your own work.
Step 5: Using and saving the results
Once the Artifact is done, how do you use it? The first step is still checking the content: the order, the times, and any steps that might be missing. Second, copy or download it. An Artifact's content can be copied into Google Docs or Word, or downloaded, depending on the buttons available. Button names may differ slightly because Claude is updated often. Third, add a version date to the document, such as version December twenty twenty-six, so everyone knows which one is newest. Fourth, print and test. Laras asks Dimas to follow the SOP tomorrow morning, then note any confusing parts to fix. Finally, a checklist before a document is used. First, the content was checked by someone who knows the procedure. Second, the interactive checklist was tried: the ticks, the counter, and the start over button. Third, the document has a version date. Fourth, a copy is saved on your computer or drive. Chat history is not an archive. And make sure there are no bank account numbers, passwords, or personal data in a document that's posted on the wall or shared with many people.
Done!
We've planned the request, created a store-opening SOP, turned it into a checklist you can tick, looked at office and school examples, and used and saved the results. In the next episode we create tables and simple calculators, such as a coffee cost-of-goods calculator and an order total, without writing any formulas ourselves. See you there!
Practice exercises
Try these on your own after watching to lock in what you learned.
Turn one of your work procedures into an SOP Artifact with a goal, steps, and important notes
Ask Claude to turn that SOP into a checklist you can tick
Print or save the result, then ask a coworker to try it and give feedback
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,290 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.
