How to document your processes as a freelancer
You already have processes. Every project you run follows one — the order you onboard, chase, deliver and close is a process whether it is written down or not. The problem is where it is stored: in your head — the worst database in the business. It loses records when you are tired, cannot be searched on a Friday afternoon, and takes the whole database home sick when you are. Documenting a process is simply moving it somewhere better — a page a rested stranger could run, knowing that most weeks the stranger is future you, three projects deep and running on memory. This guide covers the five to write first, the one-page format that survives real work, and the rule that keeps the pages true.
1. Why a solo needs them more, not less
A team has redundancy built in: when one person forgets a step, a colleague's memory covers it, and the way things are done survives in several heads. A solo practice has none of that. Your memory is the single copy, and it is busiest exactly when it is least reliable. The first payoff of writing processes down is therefore consistency when tired: the page does not care that it is Friday, that the week held three deadlines, or that this client is your fifth context switch of the day. The steps are the steps, in the order you chose while rested and thinking clearly. A checklist cannot do the work for you — but it can stop a tired version of you from quietly doing a slightly worse version of it.
The second payoff arrives the first time you delegate. A documented process is a brief that already exists: the steps, the decision points and the definition of done are written, so hiring your first subcontractor stops starting from a blank page. You hand over the page, stay available for the judgement calls it deliberately leaves open, and check the result against its own done definition. Work that exists only as your habit cannot be delegated at all — it can only be imitated, badly, from watching you.
The third payoff is the quietest and the largest. A business whose processes are written down is the only kind you can pause, sell or hand over, because it is the only kind that exists outside its owner. The project handover document ends a single engagement cleanly; process pages do the same for the whole practice. Illness, a long break, a buyer, a partner stepping in — every version of "someone else runs this" starts from these pages or does not start at all.
2. The five processes to write first
Do not document everything — document in this order, one page at a time, because each runs often enough to pay rent on its page, and hurts when it wobbles.
1. Onboarding a client. The highest-leverage page you own, because every engagement passes through it and its early steps — deposit, access, expectations — prevent the most expensive later problems. The freelance client onboarding checklist is its skeleton; your page adds your order, your tools and your exact messages.
2. The delivery pipeline for your core service. The work itself, stage by stage, from signed agreement to delivered files. Write the steps you actually take — including the awkward workaround in stage three — not the polished version you would describe on a sales call. A page that flatters you helps no one run the work.
3. Invoicing and the late-payment ladder. Money processes decay fastest in the head, because each late payer gets improvised treatment. Your page fixes the sequence in advance: the invoice email, the reminder dates, the firmer steps — the same ladder the invoice email guide starts and what to do when a client won't pay finishes — so an overdue invoice triggers a procedure, not a mood.
4. The weekly rhythm. The planning pass, the reply windows, the Friday close-out: the loop that keeps several clients' promises visible at once. It is documented in full in how to manage multiple clients at once; your page is the personal version — your day, your sitting, your dashboard.
5. The project close. The ending is where solo practices leak money and goodwill: final invoices unsent, files unfiled, lessons unlearned. One page chains the project wrap-up email, the project retrospective and the filing step, so a project is not finished when it is delivered — it is finished when it is closed.
3. The format that survives
One page per process. Not a manual — a page, because a document longer than its task will not be opened mid-task, and an unopened SOP is fiction with headings. Each page has the same anatomy, in the same order, so any page can be run cold.
It opens with the trigger: the event that starts the process, stated as a condition — "when a signed agreement lands…", "when an invoice is seven days overdue…". Then the steps as verbs: send, check, file, chase — each step one action, in order, with the template or tool it uses named. Where a step involves a tool, list the actual clicks or attach a screenshot taken while doing it: "update the CRM" is a wish; the three clicks are a step. Inside the steps sit the decision points, marked plainly: if the client has not replied in three working days, send template B from the template library; if the deposit has not cleared, nothing downstream starts. Decisions written in advance are decisions your tired self does not have to remake.
The page ends with the line most SOPs miss: the definition of done. What finished looks like, observably — the files in the folder, the invoice marked sent, the note in the dashboard. "Onboarding complete" is a feeling; "agreement filed, deposit cleared, kickoff booked, welcome email sent" is a state someone else can verify. One writing rule governs all of it: write the page while doing the task once, live, step by step — never from memory on a quiet Sunday. The memory version is the ideal process. The live version is the real one, workarounds included, and only the real one can be run by anyone else.
4. Keeping them alive
A process page begins dying the day it is written, because the work keeps moving. The rule that keeps the set alive is fix-on-use: when the process and the page disagree, the page loses, and you update it in the moment — two minutes, while the correction is still obvious. Not after the project, not in a monthly tidy-up that never gets scheduled. In the moment. A page corrected ten times in small ways stays true for years; a page left to drift for a quarter becomes a historical document about how you worked in the spring.
Once a quarter, sweep the five pages in the solo quarterly business review: run each against the last few projects, retire steps the tools have absorbed, and confirm the decision points still match your terms. Each page carries a one-line version note at its foot — the date and what changed, nothing more. That line is what makes the set trustworthy: a page marked as changed last month can be believed; a page of unknown age is a rumour.
5. What not to document
Restraint is half the system. One-off projects earn no page: the strange, never-repeated engagement is captured where it belongs, in its retrospective — a procedure written from it teaches the next project nothing. Taste and judgement cannot be documented either — the eye that picks the better draft, the instinct that a client is about to become difficult. What you can document are the decision rules around the judgement: the checks it runs, the evidence it asks for, the thresholds at which it says no. And anything that changes monthly has not earned a page yet: a process must hold still for roughly a quarter before writing it down is worth more than the sticky note it replaces. Document the stable skeleton and its rules; let the moving parts move.
Questions
Related: documents out, processes underneath
The freelance template library stores the documents these processes send; the handover document is the close, written for one client at a time. The process pages are the layer beneath both: the steps, in order, that make the documents happen the same way every time — whoever is running them. One more document belongs to that layer: the project brief, written from the discovery call and signed off before the quote — the process made visible to the client.