Daniel sent us this one — he's been thinking about standard operating procedures again, and he's making an interesting pivot. We've talked about SOPs as safety tools, the industrial context, the checklist-for-crisis angle. But he's pointing at something different. What about the boring stuff? The monthly expense filing, the client onboarding paperwork, the routine admin that nobody wants to do and everyone puts off. He's asking, if a small business owner wanted to build an SOP folder specifically to handle the tedious recurring tasks, what should actually go in there? It's a practical question, and it's one I think a lot of people get wrong.
They do, and I think the instinct is to start by listing all the tasks. Here's my expense filing SOP, here's my client intake SOP, here's my quarterly tax prep SOP. And that's not wrong, exactly, but it's skipping a step. The first thing any small business owner should do is build an SOP for deciding what gets an SOP.
The meta-SOP.
And I'm completely serious about this. If you just start writing procedures for everything, you end up with a binder that's fifty pages long and you never open it. It becomes the documentation equivalent of a gym membership in January.
Optimistic, expensive, and abandoned by February.
So the -SOP is about triage. You ask three questions. One, does this task happen at least four times a year? If it's a once-a-year thing, you might still document it, but it's lower priority than the weekly stuff. Two, is the cost of getting it wrong high? Not just financially — reputationally, legally, emotionally. And three, does it require information you won't remember in the moment?
That third one is doing a lot of work. It's where the ADHD angle really clicks. The whole problem with boring admin tasks isn't that you don't know how to do them, it's that when you sit down to actually do them, your brain has ejected every relevant detail.
Decision fatigue plus working memory limitations plus task initiation friction. There's actually solid cognitive science here. When you're tired or distracted, your prefrontal cortex is essentially running on a low battery. It's the part of your brain that handles sequencing, prioritization, and holding multiple pieces of information in mind simultaneously. An SOP externalizes all of that. It's not a training document for someone who's never done the task — it's a cognitive prosthetic for someone who has done it a hundred times but is doing it at four thirty on a Thursday.
I'm writing that down.
It's not my term, but it's exactly right. The SOP becomes an extension of your working memory. You don't have to remember the seven steps, the login credentials, which folder things go in, what the naming convention is. You just follow the document.
Let's get concrete. Someone's building this folder. They've done their -SOP triage. What's actually in it?
I'd organize it into probably five or six categories, and I'd start with the financial rhythm section. This is the stuff that has hard deadlines and real consequences. Monthly expense reconciliation, invoicing, quarterly estimated tax payments, annual filing requirements. For each one, you want a trigger, a checklist, and a done condition.
Break those down.
The trigger is the most overlooked part of any SOP. It's not enough to know how to do the thing — you need to know when to start doing it. So for monthly expenses, the trigger might be the first weekday after the month ends. For quarterly taxes, it's two weeks before the deadline. The checklist is the actual procedure. And the done condition is how you know you're finished — receipts uploaded, spreadsheet updated, confirmation email received, whatever the closure signal is.
The done condition seems obvious until you don't have one, and then you spend twenty minutes poking at things wondering if you forgot something.
Without a done condition, you're in what psychologists call an open loop. Your brain keeps spinning on it, burning cognitive resources even after you've walked away. Closing the loop is the whole point.
Financial rhythm is category one. What's next?
This is where I see small business owners bleed the most time. Every client relationship has an administrative life cycle — onboarding, active engagement, offboarding — and most people reinvent the process for each client. The SOP folder should have a client intake checklist that covers everything: contract sent, scope of work documented, payment terms confirmed, contact information logged, welcome email template ready to go.
The welcome email template is a good catch. The kind of thing that takes five minutes to write from scratch every time, and five minutes doesn't sound like much until you multiply it by forty clients and realize you've spent an entire workday writing variations of "great to meet you, looking forward to working together.
It's not just the time. It's the mental switching cost. Every time you stop to compose that email, you're interrupting whatever else you were doing. Templates are the cheapest productivity win available.
We've got financial rhythm, client documentation. What's the third category?
Digital hygiene and access management. This is the unglamorous infrastructure stuff that nobody thinks about until something breaks. Password management procedures, backup protocols, software license tracking, domain renewal calendars. If you're a solo business owner and you get hit by a bus — or just lose your phone — can anyone else figure out how to access your accounts?
The bus factor.
It's a real thing in risk management. Sole proprietorships are especially vulnerable because all the institutional knowledge lives in one brain. An SOP folder is partly an insurance policy against your own absence, whether that's a vacation or something more serious.
I'd add a fourth category.
Every small business has recurring communications that aren't exactly client work but still need to happen. Newsletter if you do one, social media posting schedule, check-ins with contractors or collaborators, even just the weekly review of what's coming up. These things feel optional in the moment, so they get skipped, and then three weeks later you realize you haven't posted anything and your pipeline is dry.
The SOP for that isn't just a to-do list. It's a template with the actual content structure. If you do a monthly client newsletter, the SOP should include the standard sections, the voice guidelines, the call-to-action formats, maybe even the subject line patterns that have worked before. You're not starting from a blank page every month.
That's the thing people miss about SOPs for creative or communicative work. They think it's going to make everything feel robotic and samey. But the opposite happens — by automating the structural decisions, you free up your brain to be creative about the content.
There's a great analogy here from, of all places, restaurant kitchens. The mise en place — everything in its place. Chefs don't chop vegetables to order. They prep all the ingredients beforehand so that when service starts, they're not making decisions about where the diced onions are, they're just cooking. An SOP is mise en place for your administrative brain.
The sloth approves of this metaphor. Preparation is underrated.
I knew you'd like that one. So let me add a fifth category, and this one is especially relevant for the ADHD context Daniel mentioned.
What's a reset procedure?
It's an SOP for what to do when you've fallen off the wagon. You missed a week of expense tracking, or you haven't updated your client records in a month, or your inbox is at four figures and climbing. The normal SOP assumes you're current. A reset procedure tells you how to dig out.
That's brilliant. Because the worst part of falling behind isn't the backlog itself, it's the paralysis about where to even start.
The reset SOP breaks the paralysis. It says, step one, don't try to fix everything. Step two, identify the most time-sensitive items only. Step three, process those. Step four, schedule a block of time for the rest. It's basically triage for administrative debt.
I like that term. It accrues interest too — the longer you leave it, the more painful it becomes.
Unlike financial debt, there's no bankruptcy option. You can't discharge your unprocessed receipts in court.
Although I'd watch that courtroom drama.
Those are the five categories I'd build an SOP folder around. Financial rhythm, client documentation, digital hygiene, communication cadences, and reset procedures. But there's a design principle that cuts across all of them, and I want to land on this because it's where most SOP advice goes wrong.
SOPs for small business owners need to be written for the tired version of yourself. Not the aspirational, well-rested, Sunday-afternoon version who's feeling organized and motivated. Write them for the version of you who's doing this at nine PM after a long day, or first thing in the morning before coffee, or while distracted by something else entirely.
That's a design philosophy, not just a writing tip. Design for the worst-case user, and the worst-case user is you on a bad day.
It changes how you write the steps. You don't write "log into the accounting software and reconcile transactions." You write "go to this specific URL, your username is this, if you've forgotten your password the reset link is here, once you're in click on the Transactions tab in the left sidebar — it's the third item down with the little credit card icon.
The difference between assuming competence and assuming cognitive depletion.
It's not insulting. It's realistic. When I was practicing medicine, our clinical protocols were written this way. Not because doctors are incompetent, but because in a high-stress, high-fatigue situation, even the smartest person can miss a step. The checklist catches you.
This connects to something I've noticed about small business owners who actually use their SOPs versus the ones who let them gather dust. The ones who use them treat the document as a living thing. They update it when something changes. They add notes when they discover a better way. The SOP isn't a monument, it's a garden.
That's the sixth thing I'd include in the folder, which isn't a category of SOP so much as a maintenance SOP. A procedure for reviewing and updating your procedures. Go through the folder, check if anything's outdated, add anything new you've learned, remove anything that's no longer relevant.
The -SOP has a sibling. The maintenance SOP.
They're bookends. The -SOP decides what goes in, the maintenance SOP keeps it alive.
Let me push on something, though. There's a type of small business owner who hears all this and thinks, I don't have time to build an SOP system, I'm too busy doing the actual work. What do you say to that person?
I say the math is straightforward. Let's say you spend two hours building an SOP for monthly expense filing. And let's say that without the SOP, the task takes you forty-five minutes of fumbling around, and with the SOP it takes twenty. You're saving twenty-five minutes per month. The SOP pays for itself in about five months, and after that it's pure time savings, every month, for as long as you're in business.
That's just the direct time savings. It doesn't account for the cognitive relief of not having to dread the task.
The dread reduction is probably the bigger benefit, honestly. There's a concept in behavioral economics called the "pain of paying" — the psychological discomfort of parting with money. I think there's an equivalent "pain of administering." It's the low-grade anxiety that comes from knowing there's administrative work lurking. An SOP doesn't eliminate the work, but it dramatically reduces the activation energy required to start it.
That's the physics term, right? The energy needed to start a chemical reaction.
Yeah, and it maps perfectly to task initiation. For a lot of people, especially with ADHD, the hardest part of any boring task isn't doing it, it's starting it. The SOP lowers the barrier. You don't have to figure anything out, you just follow step one.
We've got a framework. Six categories plus the design principle of writing for your tired self. Let's get even more tactical. What does the actual document look like? Are we talking about a three-ring binder, a Notion page, a folder of text files?
The format matters less than the accessibility. The best SOP system is the one you'll actually use, which means it needs to be frictionless to access in the moment you need it. For most people, that's going to be digital. Something searchable, something you can pull up on your phone if needed.
I'd argue for plain text or markdown files in a folder that syncs across devices. No proprietary formats, no dependency on a specific app that might disappear or change its pricing model.
That's the resilient approach. I've seen people build elaborate Notion dashboards that are genuinely beautiful and then abandon them because loading the page takes eight seconds and they can't find anything. Simple scales, fancy fails.
Simple scales, fancy fails. That should be on a poster somewhere.
Whatever the format, each SOP document should have a consistent structure. I'd recommend a header with the procedure name, the date it was last updated, and the trigger condition. Then the steps, written as imperative commands — do this, then this, then this. Then the done condition. And then a notes section at the bottom for anything unusual that came up.
The imperative commands thing matters more than people realize. "Log into the accounting software" is vague. "Open Firefox, click the bookmarks bar, select Accounting Dashboard" is a command you can execute without thinking.
If there's a decision point — if this, then that — make it explicit. Don't assume you'll remember the branching logic. Write it out. "If the client is international, use form W-8BEN instead of W-9." Whatever the thing is.
What about screenshots? I've seen some SOPs that are basically annotated screenshots with arrows and circles.
Screenshots are fantastic for software procedures where the interface matters. They're also a trap if the software updates frequently and your screenshots go stale. I'd use them sparingly and only for the parts of a process where the visual layout is non-obvious.
The folder is built, the documents are written, the tired version of you has clear instructions. What's the failure mode here? Where does this system break?
The biggest failure mode is that people stop using the SOP because they think they've internalized it. They've done the procedure five times, it feels familiar, so they skip the checklist. And for a while that works fine. And then one day they're tired or distracted and they miss a step, and that's when the error happens.
Familiarity breeds contempt, and contempt breeds errors.
The antidote is to make using the SOP easier than not using it. If your expense filing SOP is a document you have to dig through folders to find, you'll stop using it. If it's pinned to your bookmarks bar or linked from your home screen, you're more likely to actually open it.
There's also a social dimension here that I think is worth touching on. If you're a solo business owner, you're the only person who'll ever see these SOPs. There's no accountability. No one's checking whether you followed the procedure.
Which is why the SOP needs to sell itself on benefits, not obligations. You're not following it because someone told you to. You're following it because it makes your life easier and reduces your stress. If it doesn't do those things, you'll abandon it, and you should — a bad SOP is worse than no SOP because it wastes your time and erodes your trust in the whole concept.
The quality bar is real. A vague, incomplete, or outdated SOP is actively harmful.
And I think that's why a lot of small business owners have tried SOPs and bounced off them. They encountered a bad example — maybe at a previous job, some corporate procedure manual that was ninety pages of unreadable jargon — and they concluded the whole approach isn't for them.
The corporate SOP trauma. "I see you've attempted to complete form TPS-417 without the requisite cover sheet.
And that's the opposite of what we're talking about. A good SOP for a small business should feel almost embarrassingly simple. Like, "is this really worth writing down?" If you have that reaction, you're on the right track.
Because the things you think are too obvious to document are exactly the things you'll forget when you're tired.
There's a name for this in cognitive psychology. It's called the "curse of knowledge" — once you know something, it's very hard to imagine not knowing it. So you underestimate how much detail you actually need to include. The cure is to test your SOP on a bad day. If you can follow it while exhausted and distracted, it's detailed enough.
I want to circle back to something you mentioned earlier about the ADHD context. Daniel mentioned this explicitly, and I think there's a deeper layer here that's worth pulling on.
For someone with ADHD, the problem with routine admin tasks isn't just that they're boring. It's that the executive function required to sequence the steps, maintain focus, and resist the pull of more interesting activities is disproportionately high. An SOP offloads the executive function demands. You're not relying on your brain's task-management system, you're relying on the document.
And it connects to something called "scaffolding" in ADHD management. The idea is that you build external structures to compensate for the internal systems that are unreliable. Calendars, reminders, checklists, SOPs — they're all forms of scaffolding. And the key insight is that scaffolding isn't a crutch, it's an accommodation that lets you function at your actual capability level rather than being dragged down by the administrative overhead.
The distinction between a crutch and scaffolding is important. A crutch implies something's broken. Scaffolding implies you're building something.
The building never stops, which is why the maintenance SOP matters. Your business changes, your tools change, your clients change. The scaffolding needs to adapt.
Let's talk about a specific example. Monthly expense filing. Walk me through what a good SOP for that would look like.
So first, the trigger. "First weekday of each month, nine AM. Calendar reminder set to repeat monthly with a link to this document." That's step zero, and it's the most important step because if you don't start, nothing else matters.
The trigger as step zero. I like that framing.
Step one: open the accounting software. And I'd include the exact URL, the login method — "use the Google sign-in, not the email and password" — and what to do if you're locked out. Step two: navigate to the transactions page for the previous month. Step three: open your business bank account in a separate tab. Step four: for each transaction in the bank account, find or create the matching entry in the accounting software. Step five: for any transaction you can't identify, flag it and move on — don't get stuck.
That "don't get stuck" instruction is doing a lot of emotional labor.
It's critical. Perfectionism is the enemy of completion. If you spend twenty minutes trying to identify a seven-dollar charge, you'll run out of momentum and abandon the whole process. The SOP should explicitly give you permission to flag and move on.
Permission to be imperfect, codified in a document.
Step six: upload receipts. If you use a receipt-scanning app, the SOP should name the app and the folder where scans go. Step seven: run the reconciliation report and verify that the balance matches the bank. Step eight: mark the month as complete in whatever system you use. Done condition: confirmation email from the accounting software or a checkmark in your tracking spreadsheet.
How long should that take, following the SOP?
For a typical solo business with maybe thirty to fifty transactions a month, twenty minutes. Without the SOP, the same person might spend an hour, mostly on task-switching and trying to remember where things are.
The SOP is essentially pre-making all the decisions so you don't have to make them in real time.
That's the whole game. Decision-making is metabolically expensive. Your brain consumes a disproportionate amount of energy relative to its size, and every decision, even trivial ones, draws from the same limited pool of cognitive resources. By pre-making the decisions — which software to use, which tab to click, what order to do things — you're conserving that resource for the parts of your work that actually require judgment and creativity.
The ROI on a good SOP isn't just time saved. It's better decisions on the things that matter, because you're not decision-depleted from the things that don't.
There's a famous study on this with judges. Parole judges in Israel, actually, which is an interesting connection. Researchers found that the likelihood of a favorable ruling started at about sixty-five percent at the beginning of the day and dropped to near zero by the end of a session, then jumped back up after a meal break. The judges weren't being cruel, they were just depleted. Decision fatigue is real, and it affects everyone.
If you're a small business owner making important decisions in the afternoon, you want your morning administrative work to be as decision-light as possible.
The SOP is protecting your decision-making capacity for the things that actually need it.
I think we should address the objection that this all sounds like a lot of upfront work. Someone listening might be thinking, I'm already overwhelmed, and now you're telling me to build an entire documentation system before I can even start fixing my admin problems.
That's a fair objection. And my answer is, don't build the whole system at once. Pick one category. Pick the one that's causing you the most pain right now. If monthly expenses are the thing you dread, start there. Write that one SOP. Use it for two months. See if it helps. If it does, pick the next one.
The iterative approach. Minimum viable SOP.
One good SOP that you actually use is worth more than a comprehensive system that sits in a folder untouched. And the process of writing the first one teaches you what level of detail you need, what format works for you, what triggers are effective. You get better at writing SOPs by writing SOPs.
The first one is the hardest because you're building the template at the same time as the content.
Use someone else's template. There are plenty of good ones online. The structure isn't the hard part, it's the content — the specific steps for your specific business with your specific tools.
What about involving other people? If you have a virtual assistant or a part-time bookkeeper, does the SOP change?
It becomes even more important, and the writing standard changes. When you're writing an SOP for yourself, you can get away with shorthand and assumptions because you know your own context. When you're writing for someone else, you need to be much more explicit. But the payoff is also bigger — if you can hand off an entire administrative process to someone else with a clear SOP, you've just bought back hours of your life.
The SOP as delegation tool.
As a quality control tool. If the assistant follows the SOP and something goes wrong, you can look at the procedure and figure out whether the SOP was flawed or the execution was flawed. Without the SOP, you're just guessing.
We've covered the categories, the design principles, the cognitive science, the implementation approach. Is there anything we're missing? Any category of routine admin that small business owners consistently overlook?
I'd add one more, and it's a bit. An SOP for capturing ideas that should become SOPs.
The idea inbox.
Every time you do a task and think, I should really document this, or every time something goes wrong and you realize a procedure would have prevented it, you need somewhere to capture that thought. Otherwise it evaporates and you make the same mistake again six months later.
The full system is: -SOP for deciding what to document, the actual SOPs organized by category, the maintenance SOP for keeping them current, and an idea inbox for capturing new candidates.
That's the ecosystem. And I want to emphasize that this isn't just for people who are "process-oriented" or whatever personality type people associate with checklists. This is for anyone whose brain has finite capacity, which is everyone.
The universality point matters. There's a weird cultural thing where people treat organizational systems as a personality trait rather than a tool. Like, "oh, I'm just not a checklist person." As if checklists care about your self-concept.
Checklists are profoundly indifferent to your identity. They work whether you believe in them or not. It's like saying you're not a hammer person. The hammer doesn't care, it just drives nails.
Although I will say, as someone who moves at a deliberate pace, there's a particular satisfaction in having a system that matches your rhythm. When your SOP is well-designed, the pace of the work feels natural rather than rushed.
That's the difference between an SOP that's imposed from outside and one you've designed for yourself. The corporate SOPs people resent are usually written by someone else, for someone else's convenience, with someone else's assumptions about how the work should flow. When you write your own, you can build in your own rhythms and preferences.
The self-authored SOP is a completely different psychological experience from the assigned one.
It's the difference between a map someone handed you and a map you drew yourself. Same function, totally different relationship to it.
All right, so if someone's listening and they want to start this weekend, what's the thirty-minute version? The smallest possible start?
Take one recurring administrative task. The one that annoys you most. Open a blank document. Write the trigger at the top — when and how you'll know it's time to do this thing. Then write the steps, in order, as commands, with enough detail that you could follow them while half-asleep. Include the done condition. Save it somewhere you'll actually find it. Set a calendar reminder with a link to the document. That's it. If it helps, do another one next weekend.
If it doesn't help, the problem is probably that the steps aren't detailed enough or the trigger isn't specific enough. Iterate, don't abandon.
The most common failure mode for a first SOP is that the trigger is too vague. "When I have time" is not a trigger. "When I notice it needs doing" is not a trigger. The trigger needs to be external and specific — a calendar event, a recurring task notification, something that exists outside your brain.
Because your brain, when faced with a boring task, will reliably decide that now is not the time.
Every single time. The brain is a master of justification. It will convince you that you'll definitely do it tomorrow, that it's not that urgent, that you work better under pressure anyway. The trigger bypasses the negotiation entirely. The calendar says do it, so you do it.
The calendar as benevolent dictator.
And the weird thing is, it's a relief. Having the decision made for you — even by your past self via a calendar event — removes the mental burden of constantly re-deciding whether to do the thing.
Decision removal as a service. That's essentially what a good SOP system provides.
That's the pitch I'd make to anyone who's skeptical. You're not building a bureaucracy. You're building a system that removes decisions from your day so you can spend your mental energy on the parts of your business that actually need you.
The parts that can't be reduced to a checklist.
Which, ideally, is the majority of what you do. The admin is the overhead. The SOP handles the overhead so you can focus on the work itself.
I think that's a good place to land. Categories, design principles, cognitive rationale, and a thirty-minute starter kit. Daniel, if you're listening, we'd love to hear what ends up in your folder.
Now: Hilbert's daily fun fact.
Hilbert: The largest documented extinct sign language dialect was the Hausa trade sign system of northern Niger, which had an estimated two thousand distinct gestural lexemes before it disappeared in the nineteen twenties, making it larger than most modern national sign languages at the time.
Two thousand hand signals for trading in the desert. a lot of haggling vocabulary.
I want to know what the gesture for "your price is unreasonable" looked like.
This has been My Weird Prompts. Thanks to our producer Hilbert Flumingtop for keeping us running. If you enjoyed this episode, leave us a review wherever you listen — it helps. We'll be back soon.
