Day 19: Create a Personal SOP

The concept

A Standard Operating Procedure, often shortened to SOP, is a written version of how to do a recurring task well.

The phrase can sound corporate, formal, or heavy. But the idea is simple: if you do something repeatedly, and doing it inconsistently costs time or quality, write down the best current version of the process. Then follow it, improve it, and stop reconstructing the same steps from memory every time.

SOPs are useful at work, but they are not only for large companies. You can use them for personal admin, client onboarding, monthly reporting, content publishing, family routines, volunteer projects, financial reviews, travel preparation, or any task that repeats often enough to deserve a reliable process.

AI makes SOP creation much easier because you do not need to start from a perfect process. You can describe what you currently do, even roughly, and ask AI to turn it into a clear document. You then edit it with your real knowledge.

Plain English

An SOP is a checklist with context. It tells you what to do, when to do it, what you need, and how to know it was done properly.

Why SOPs are worth the effort

Most people carry too many processes in their heads. They know how to prepare a monthly update, respond to a certain type of client request, organise tax documents, send invoices, plan a workshop, or publish a newsletter. But because the process is not written down, they have to rebuild it each time.

That creates hidden cost.

You lose time remembering the steps. You miss small details when you are tired. You explain the same process repeatedly when someone else needs to help. You struggle to improve the process because it exists only as a feeling, not as a visible object.

An SOP removes that friction. It gives you:

• Consistency The task is done the same reliable way each time.

• Lower mental load You follow the process instead of holding every step in memory.

• Easier delegation Someone else can run the process without a long explanation.

• Better improvement A written process can be reviewed, simplified, and upgraded.

What belongs in an SOP

A good SOP does not need to be long. It needs to be usable.

Use these five sections:

1. Purpose

Explain what the process achieves and when to use it. This prevents the SOP from becoming a disconnected list of steps.

Example:

Use this process every Friday to prepare the weekly client update so the client understands progress, blockers, and next actions before Monday.

2. Required inputs

List what you need before starting. This might include files, links, approvals, data, meeting notes, templates, account access, or previous reports.

Missing inputs are a common reason processes stall. Naming them upfront prevents false starts.

3. Step-by-step instructions

Write the steps in order. Make them specific enough that someone new could follow them. Avoid vague instructions such as "clean up the document" unless you define what clean means.

Good steps often start with action verbs:

• open
• check
• copy
• compare
• update
• send
• save
• review

4. Quality check

This section answers, "How do I know I did it right?"

For a report, the quality check might include accurate dates, updated numbers, clear summary, no unresolved comments, and correct recipient list. For a household process, it might include visible completion, supplies restocked, or confirmation sent.

5. Common mistakes

This is where an SOP becomes truly useful. Include the mistakes that happen in real life: forgetting an attachment, using last month's data, sending before approval, skipping a review step, or saving the file in the wrong place.

Start with one process

Do not try to document everything at once. That turns SOP work into a project you will avoid.

Start with one task that meets at least two of these conditions:

• you do it every week or month
• it has more than five steps
• mistakes are annoying or costly
• someone else may need to do it someday
• you often forget one part
• the output matters to another person
• the process changes slightly each time

Good candidates include:

• preparing a weekly review
• sending a client update
• creating a monthly invoice
• publishing a blog post
• onboarding a new customer
• planning a recurring meeting
• backing up important files
• preparing documents for an accountant
• handling a common support question

The point is not to choose the most important process in your life. Choose one where documentation will immediately reduce friction.

Make it real, not ideal

An SOP should describe the process you can actually follow, not the process you wish you followed.

If the current process is messy, say so. If you usually check information from three different places, include all three. If one step depends on a person who often replies late, include that dependency. If the process has a shortcut you use when time is tight, document the shortcut honestly and explain when it is acceptable.

AI can help turn reality into order. But it can only work with what you provide. If you describe an ideal process, you will get an ideal SOP. It may look impressive and still be useless.

A useful rule

A trustworthy SOP sounds like something a real person could follow on a busy day.

Use AI to improve the process, not only document it

Once AI creates the first SOP, ask a few improvement questions:

• Which steps are unclear or too vague?
• Where could this process fail?
• What can be simplified without reducing quality?
• What should be checked before the final step?
• What information is missing from my description?

These follow-ups turn the SOP from a transcript of your current process into a better version of that process. Sometimes AI will spot gaps you have normalised because you are used to working around them.

Store it at the point of use

An SOP is only useful if you can find it at the moment you need it.

Do not bury it in a general folder called "Documents." Put it where the task begins. If it is for a monthly report, keep it in the reporting folder. If it is for a recurring meeting, link it in the meeting notes. If it is for personal admin, pin it in your notes app. If it is for a team, place it in the shared workspace where the team already looks.

The easier it is to open, the more likely you are to use it.

Today's practice

Choose one recurring task. Paste your rough current process into today's prompt. If you do not know every step, describe what you remember. AI can help fill gaps, but you should review the output carefully.

When the SOP comes back, check it using this review list:

• Would I know when to use this SOP?
• Are the required inputs clear?
• Are the steps specific and in order?
• Is there a quality check at the end?
• Does it include common mistakes from real experience?
• Is it saved somewhere I would actually look?

Then run the process once using the SOP. As soon as you notice what is missing, update it. That is the moment the document becomes useful.

By the end of today, you should have one process out of your head and into a form you can reuse, improve, or share.