OPERATIONS & SYSTEMS / RUNBOOK BUREAU
Freelancer SOP Examples for Repeatable Client Work
Document tasks that recur and are easy to miss or repeat inconsistently. A standard operating procedure, or SOP, explains when a task starts, how to carry it out and what counts as finished. For a freelancer, it can be a short working instruction rather than a formal manual.
Use Trigger → Steps → Owner → Check → Complete
- Trigger: name the event that starts the procedure, such as an accepted proposal or a completed review round.
- Steps: list the actions in the order needed, with links to the current template or working record.
- Owner: say who performs the work and who makes any required decision. In a solo business, this may be you and a named client approver.
- Check: define the quality or readiness check before the work moves on.
- Complete: record the output and completion point, including the next handoff.
Document the stable parts of a task so you do not have to reconstruct them each time. Keep judgment visible: “assess the request against the brief” is different from an instruction to accept every request automatically.
Example 1: prepare a proposal or quote
Trigger: discovery has produced enough information to define an offer. Steps: confirm the outcome, estimate delivery and coordination, state assumptions and exclusions, and prepare the proposal. Owner: you. Check: the scope, fee and dates agree across the document. Complete: save the version sent and record the next decision or follow-up date.
Keep a short checklist for missing inputs. If the scope is still unclear, return to discovery instead of forcing an estimate through the procedure.
Example 2: onboard the client and start the project
Trigger: the client has accepted the offer. Steps: confirm start conditions, collect missing client information, prepare the brief, obtain required assets and agree communication and review responsibilities. Owner: you coordinate; the client supplies the named inputs. Check: the agreed scope and starting dependencies are ready. Complete: send the kickoff summary and record the first delivery actions.
Separate “client welcomed” from “project ready to start.” A friendly welcome email does not resolve a missing brief or unavailable access.
Example 3: deliver work and handle revisions or approval
Trigger: a deliverable is ready for internal review. Steps: check it against the brief, check files and links, send the identified version to the approver, collect consolidated feedback and assess revisions against the agreed allowance. Owner: you handle delivery; the named client contact approves. Check: required corrections are complete and any additional work has a recorded decision. Complete: save the approval with the final version.
Use a delivery checklist for repeatable checks such as file naming and opening exported files. Keep the client’s creative or commercial judgment outside an automatic tick-box decision.
Example 4: issue an invoice and follow up
Trigger: an agreed billing milestone is reached. Steps: confirm the amount and billing details, prepare and send the invoice using your billing process, record its due date and check receipts before a reminder. Owner: you or the person responsible for accounts. Check: payments and credits match the outstanding balance. Complete: reconcile payment, or record the next follow-up and any promised date.
A sent reminder is not the same as a resolved invoice. Keep the next action open when payment is still outstanding.
Example 5: close out a completed project
Trigger: final delivery has been approved. Steps: hand over agreed files and instructions, confirm remaining actions, review billing, arrange access handback where needed and archive the working records. Owner: you coordinate the handover with the client. Check: the client can locate and use the agreed deliverables. Complete: record the closeout status and any unresolved billing or support action separately.
Do not leave an entire project marked as active just because one invoice is outstanding; keep that remaining action visible in the appropriate record.
Leave out work that does not benefit from a procedure
A one-off experiment or an evolving creative decision may need notes rather than an SOP. Do not document every click in an interface if the useful instruction is simply to produce and check an output. Avoid copying a full paid toolkit into an internal manual when a link to the current working template is enough.
An SOP has become too complicated when you cannot tell what starts it, which path applies or where it ends. Split genuinely different triggers into separate procedures, remove obsolete steps and test the remaining instructions on a real task.
Keep it usable after the first draft
- Write down the process you actually use, then test it rather than documenting an ideal routine nobody follows.
- Give each procedure an owner and a review note so outdated instructions are not mistaken for current practice.
- Link to one current template instead of attaching conflicting copies.
- Avoid checks such as “ensure quality” without saying what must be checked.
- Update the procedure when the work changes, not only when a scheduled review arrives.
Document one recurring task this week
Choose the task you most often reconstruct from memory. The Freelancer Operations System includes a Process Library, SOP Builder, Checklist Builder, recurring-task records and review/version records in Excel. Find its card in Operations & Control to inspect the included files and continue to Etsy.
For editable documents to support intake, briefs and kickoff, explore the focused onboarding kit. View the Client Onboarding Kit →
Paid products are purchased on Etsy.