A SOP format is the layout you follow when you write a standard operating procedure — the sections, in order, that turn a process living in one person's head into something a team can run without them. For a process on a fixed schedule, the monthly invoicing cycle being the classic case, the format has to do two jobs. It records the steps, and it records the decisions that stall those steps when they wait for the founder. Get both into the document and invoices go out on the dates, not on the day you happen to be free.
Key takeaways
- A workable SOP format for a scheduled process has two layers: a decision table and a step checklist tied to calendar dates.
- Write the decision layer first. List every decision that currently waits for you, then give each one a who, a limit and an escalation trigger.
- Steps written without dates drift; steps written against dates get done because someone owns each one before the deadline.
- An SOP that names who may decide is the difference between a document that frees you up and one that just adds another form to your week.
What a good SOP format looks like when the process runs on a calendar
Most SOP formats are built for a process that happens once — how to onboard a client, how to ship a release. Recurring processes break those formats, because the risk isn't getting it wrong once. The risk is that one step slips, the invoice goes out late, and the payment lands a full cycle behind.
So the format for a recurring process needs two layers:
- The decision layer. A table of the judgment calls inside the process, each with who may make it, how far they can go, and when it comes back to you.
- The step layer. A checklist of actions, each attached to a point on the calendar rather than a vague "before invoicing."
Write them in that order. Decisions first, steps second. Reversed, you get a procedural document that still routes every exception back to the founder — which is the bottleneck you were trying to remove.
The decision layer: list what currently waits for you
Keep a running note for one cycle and write down every moment the invoicing process stops because someone needs your answer. A typical list looks like this:
- Approve an invoice adjustment
- Write off a small outstanding balance
- Extend payment terms for a client who asked
- Send an invoice without a purchase order on file
- Change the billing contact or entity on an invoice
Then give each one four fields: decision | who may decide | limit | escalate when. The limit and the escalation are what make it a delegation instead of a blank cheque. The numbers below are examples — yours are yours to set.
| Decision | Who may decide | Limit | Escalate when |
|---|---|---|---|
| Approve an invoice adjustment | Billing lead | Corrections to line items on an invoice already drafted | The adjustment pushes the total past the ceiling you set, or the client disputes the original amount |
| Write off a small balance | Billing lead | Balances below the threshold you set, older than two cycles | The client is still active, or the balance sits above your threshold |
| Extend payment terms | Account manager | One extension, up to the number of days you set | A second extension is requested, or the client has already missed a date |
| Send without a purchase order | Billing lead | Only when the client has confirmed the PO in writing | No written confirmation, or the client's portal rejects the invoice |
| Change billing contact or entity | Billing lead | Contact details and billing address | The legal entity or tax details change |
The moment that table exists, five questions stop arriving in your inbox. Nobody is guessing and nobody is waiting. This is the same section that separates the free template at tools.exiuss.com/sop-template from most SOP documents — the decision table is a first-class part of the format, not an appendix.
The step layer: write the steps against dates
Now write the steps, and attach each one to a day. For a monthly invoicing cycle:
- Day 1 — Close the previous month's timesheets and expense records. Confirm every billable item has a client and a project attached.
- Day 2 — Generate draft invoices for every active client on a monthly cycle.
- Day 3 — Check each draft against the contract: rate, retainer, extras, and any agreed adjustment.
- Day 4 — Apply the decision table. Adjustments, write-offs and term extensions are cleared by whoever the table names, not by you.
- Day 5 — Send the invoices, and log the send date and the due date in one place.
- Day 10 — Confirm receipt with any client on a portal or procurement system. This is where invoices quietly die.
- Day 20 — First reminder pass on anything unpaid and past due.
- Day 28 — Second reminder, and flag any account that now needs a terms conversation.
Notice what's missing: your name. Every step has an owner, every judgment call has a delegate, and the calendar does the nagging.
The common mistake
The mistake is writing the steps first because steps are easier to remember. A steps-only SOP looks finished and behaves like a bottleneck, because every exception inside the process still ends at the founder's desk. The decision table is not polish on top of the format. It is the part that makes delegation possible.
Keeping the format alive
Review the decision table once a cycle. Two questions: which rows did nobody use, and which situations came to you that aren't in the table yet? Delete the first, add the second. The table stays accurate because it is short and it gets touched every month.
Quick checklist
- Track one full cycle and note every decision that waited for you.
- Write each one as a row: decision | who may decide | limit | escalate when.
- Set a limit and an escalation trigger for every row — no open-ended delegations.
- Write the steps as a checklist with a calendar day attached to each.
- Name an owner for every step, and remove yourself from the ones you delegated.
- Review the decision table at the end of each cycle and update it.
The fastest way to build this is to start from a format that already holds both layers. The free SOP template at https://tools.exiuss.com/sop-template walks you through the decision table and the dated checklist, and the "Fill with an example" button shows a finished invoicing SOP so you can see the shape before you write your own. Fifteen minutes, and next month's invoices don't wait for you.