The short answer
Document processes that protect revenue, customers, delivery, cash, and business continuity first. For many small businesses, these are enquiry handling, sales handover, customer onboarding, delivery, customer support, invoicing, expenses, supplier management, access changes, and weekly operational review.
A procedure does not need to be a long manual. The first useful version can fit on one page if it tells a trained person when to start, what information is needed, what to do, where to record it, and when to ask for help.
The ten processes below create a practical operating base. Adapt the order to the risks and obligations of your business.
International note: This article is written for English-speaking small businesses in the UK, US, Canada, and Europe. Check local tax, privacy, employment, consumer, and marketing requirements before acting.
1. New enquiry handling
Define where enquiries arrive, who checks them, the response time, information to record, qualification questions, and the next action.
2. Sales handover
Record what must pass from sales to delivery, including agreed scope, price, dates, contacts, promises, limitations, and payment terms.
3. Customer onboarding
Specify welcome communication, documents, access, payment, scheduling, responsibilities, and the first review point.
4. Product or service delivery
Describe the main stages, quality checks, approvals, records, completion standard, and exception route.
5. Customer support and complaints
Set channels, response times, ownership, tone, refund or remedy authority, escalation, and learning review.
6. Invoicing and payment follow-up
Define when invoices are raised, how they are checked, who monitors due dates, reminder timing, and escalation for overdue accounts.
7. Expenses and purchasing
Set approval levels, evidence requirements, preferred suppliers, payment method, record location, and reconciliation timetable.
8. Supplier and contractor management
Record selection, agreements, access, deliverables, review, renewal, and exit steps.
9. User access changes
Cover new accounts, permission approval, password handling, role changes, device return, and immediate removal when a person leaves.
10. Weekly operational review
Review overdue tasks, customer issues, cash, delivery risk, staff capacity, access changes, and the next week’s priorities. Record each action with an owner and date.
A process document must survive real work
A procedure is useful only if the person doing the work can find it, understand it, and keep the required record. A polished document hidden in a folder does not create consistency. Test each first draft by asking another trained person to complete the work.
Include exceptions and escalation. Straightforward steps are often already understood. The greatest value comes from clarifying what happens when information is missing, a customer is unhappy, approval is unavailable, or a deadline cannot be met.
Worked example
Worked example: one-page enquiry procedure
The procedure begins when a website, email, telephone, referral, or social enquiry arrives. It states where the enquiry is recorded, the response deadline, required fields, basic fit checks, acknowledgement wording, assignment rule, and escalation for urgent or sensitive messages.
The document includes one completed example and a link to the official record. A new team member follows it during a supervised week. Questions are used to improve the procedure rather than kept as informal knowledge.
One-page process template
| Section | What to record | Test |
|---|---|---|
| Purpose | Result or obligation supported | Would the team know why it matters? |
| Trigger | Event that starts the work | Can two people recognise the same start? |
| Inputs | Required information and source | What happens when information is missing? |
| Steps | Actions, decisions and owners | Can a trained person follow them? |
| Output | Completion standard and record | Can success be checked? |
| Exceptions | Authority and escalation | Are unusual cases safe? |
A practical implementation sequence
- Step 1 — Rank processes by customer, cash, delivery and compliance risk
- Step 2 — Draft the current real process on one page
- Step 3 — Test with a second trained person
- Step 4 — Correct gaps and add examples
- Step 5 — Assign an owner and review date
Mistakes to avoid
- Writing procedures without the person doing the work
- Documenting only the normal case
- Using screenshots without explaining decisions
- Keeping several uncontrolled copies
- Failing to review after systems or responsibilities change
How to keep process documentation useful
Track whether the process is actually followed. Review completion quality, missing information, questions asked, exceptions, delay, rework, and occasions when staff use a different method. A document that is repeatedly bypassed may be hard to find, out of date, too complicated, or inconsistent with the tools available.
Assign an owner and review date. Update the controlled version when systems, responsibilities, markets, or rules change. Keep a short change note so the team understands what was altered. Retire outdated copies rather than allowing several versions to circulate.
Measures to review
- Correct completion rate
- Questions and missing information
- Exceptions and escalations
- Rework and delay
- Use of the approved record
- Review and update completion
Applying this guidance across markets
The operating principles in this guide apply to English-speaking small businesses in the UK, US, Canada, and Europe. The surrounding rules do not always match. Before implementation, identify the countries in which the business, customer, worker, supplier, payment, or delivery is located. Check the requirements that apply to that specific activity rather than assuming the rules of the business’s home country cover every transaction.
Use local professional advice where tax, privacy, employment, consumer rights, regulated products, direct marketing, accessibility, or contractual obligations are material. The practical aim is not to fill the article with generic legal warnings. It is to make market ownership an explicit project task with a named person, source, decision, and review date.
Questions to take into the next working session
Turn the guide into a decision rather than another saved article. Bring the people who own the customer result, daily process, budget, and technical work into one short session. Use a real current example instead of discussing an ideal future case. Record decisions, assumptions, missing evidence, owners, and dates in one shared place.
- What business result are we trying to improve, and how is it measured now?
- Which customer, product, process, or market is included in the first version?
- What important information is still missing or unreliable?
- Who owns the decision, the daily operation, and recovery when something fails?
- What is the smallest useful version we can test without creating avoidable risk?
- When will we review real results and decide whether to stop, correct, or expand?
End the session with one next action per owner. If the team cannot name the owner, evidence, and review date, the work is not ready to move from discussion into implementation.
Practical checklist
- Each process has an owner
- The trigger is clear
- Required information is listed
- Steps reflect real work
- Records have one location
- Exceptions have an escalation route
- Instructions have a review date
Common questions
How detailed should a process be?
Detailed enough for a trained person to complete it consistently without relying on hidden knowledge.
Who should write the process?
The person doing the work should help write and test it. The owner approves responsibility and controls.
How often should processes be reviewed?
Review at a set date and whenever rules, systems, staff, products, or customer requirements change.
Related reading
How to Build a Lean Back Office for a Growing Small Business · When Should a Small Business Hire a Virtual Assistant? · Should You Automate, Delegate, or Stop the Task? · Explore operational support