Start with the jobs you repeat, not the jobs you remember
Open your calendar and your sent email for the last two months and list every task that happened more than once. Invoicing, onboarding a new client, reconciling accounts, chasing a late payment, renewing a subscription and backing up files all show up quickly. Anything you did twice is a candidate. Anything you did once is not.
Rank the list by two questions: what hurts most if it is done wrong, and what would you most like someone else to do. Write procedures for the top five first. A small set that gets used beats a binder that does not.
What a useful procedure page contains
Keep each procedure to one page. It needs a name that says what it does, the trigger that starts it, the steps in order, the tools or logins involved (where to find them, never the passwords themselves), and a line saying how you know it is finished.
The last line matters most. 'The invoice is sent and logged in the tracker' is checkable. 'Handle the invoice' is not. If you cannot say how you know the job is done, the job is not yet defined.
Write the steps as you do them
The fastest way to get accurate steps is to do the job once with a blank page open and write each action as you take it. Memory skips the awkward parts, such as the setting you always forget or the report that only works in one browser. Notes taken during the work keep them.
Use short, plain sentences that start with a verb. 'Export the bank report for the month.' 'Compare the ending balance to the statement.' A stranger should be able to follow it without asking you what you meant.
Name an owner and a review date
Even when you are the only person, put a date on every page and a note of when you will look at it again, usually once or twice a year. Tools change, clients change, and a procedure that still describes last year's software is worse than none because it sounds trustworthy.
If a helper or contractor joins, add the name of who does the job. When you change how something is done, change the page the same day and add a line to a change log at the bottom, so nobody works from an old copy.
Test a procedure by handing it to someone
The proof that a page works is that another person can follow it. Ask a friend, a family member or a contractor to do a small job from the page alone while you watch without helping. Every question they ask is a gap in the page.
Fix the gaps, then file the page where you will find it in a hurry: one folder or one workspace, with the same names you use in your calendar.
Common mistakes
The first is writing too much. Pages that run to five screens do not get read. The second is storing passwords in the document; keep them in a password manager and write where to find them. The third is writing procedures once and never touching them again.
A ready-made set can save time if its pages are close to how you work, but always edit them to match your own tools and clients. The SOP Library on this site is built that way: editable pages you adjust, not rules to follow.
Common questions
How many procedures does a one-person business need?
Start with five for the jobs that hurt most when done wrong or that you most want to hand off. Add more only when you catch yourself explaining the same thing twice.
Should procedures be in a document or a database?
Either works. Use whichever you will actually open. The important parts are one page per job, a date, and a place you can find them quickly.
Do I need procedures if I never plan to hire?
They still help when you are away or ill, and they make it easier for an accountant or a family member to step in if they ever must.
This guide is general information, not tax, legal or accounting advice. Rules, fees and due dates change; check with the IRS, the NJ Division of Taxation or a licensed professional for your situation.