How to Write an SOP: Format, Example and Free AI SOP Generator

To write an SOP (standard operating procedure), state its purpose and scope, list who is responsible for what, then write the procedure as numbered steps with one action each, followed by the records to keep and when the SOP will be reviewed. Write it with the people who do the work, test it once, then share it. The free AI SOP Generator drafts this format from a topic and your notes, keeping your own roles and steps.

A good SOP means a new hire can do the job correctly on day one, and an auditor or customer can see that it is done the same way every time.

The SOP format: 6 parts

Most SOPs, from a warehouse to an accounts team, use the same six sections.

Section	What it says
Purpose	Why the procedure exists, in one or two sentences
Scope	Where it applies and to whom (site, department, product range)
Responsibilities	Who does what, by role, not by name
Procedure	Numbered steps, one action each
Records to keep	The forms, notes and system entries that prove it was done
Review	How often the SOP is checked, and by whom

Add a header with the SOP title, a number, the version and the date, so people know they have the latest copy.

How to write an SOP (step by step)

1. Pick one task. "Goods receiving" is an SOP. "Warehouse operations" is a manual. Keep each SOP to one process with a clear start and end.
2. Watch it being done. Sit with the person who does it best and note every step, the software screens, and where things go wrong.
3. Write the purpose and scope. One sentence each.
4. Name the roles. Write "Store keeper" or "Accounts assistant", not people's names, so the SOP survives staff changes.
5. Write the steps. Start each step with a verb, one action per step, in the order they happen.
6. Add checks and records. Say what is checked, what is signed, and where the record is kept.
7. Test it. Ask someone new to follow the draft without help. Every question they ask is a missing step.
8. Approve, date and share it. Put it where people work: on the wall, in the shared drive, or attached to the task in your system.

With the AI SOP Generator, steps 3 to 6 are drafted for you: choose SOP, name the topic, describe how your team works today, and it returns the six sections with numbered steps, ready to edit and download as Word.

SOP example: goods receiving at a warehouse

Here is a short version of a real world SOP, to show the level of detail that works.

Purpose: make sure goods received match the purchase order before they enter stock. Scope: all inbound deliveries at the main warehouse. Responsibilities: Store keeper receives and checks; Warehouse supervisor approves differences; Accounts matches the invoice.

Procedure:

1. Ask the driver for the delivery note and check it names our company and address.
2. Find the matching purchase order in the system.
3. Count the cartons against the delivery note before unloading fully.
4. Inspect cartons for damage, and photograph any damage before signing.
5. Open a sample carton and check item code, quantity and expiry where relevant.
6. Record received quantities in the system and print the goods received note (GRN).
7. Write any shortage or damage on the delivery note, and both sign it.
8. Inform the Warehouse supervisor of any difference the same day.
9. Move goods to their storage location and update the location in the system.

Records to keep: signed delivery note, GRN, damage photos, supplier claim if raised. Review: every 12 months, or after any audit finding.

Notice how every step starts with a verb and could be checked by someone watching.

Rules for writing SOP steps people actually follow

• One action per step. "Count and inspect and record" is three steps.
• Use the words your team uses, including the names of screens and forms.
• Say what to do when it goes wrong, for example a shortage, a damaged carton or a system outage.
• Keep it short. If an SOP is more than two pages, it is probably two SOPs.
• Avoid vague words such as "properly", "as needed" or "regularly". Say what, how many and how often.
• Never invent rules. If a step depends on a law, a certificate or a limit, check the real figure. The generator writes a [placeholder] such as [review period] instead of guessing.

SOP ideas for trading and warehouse teams

Good first SOPs are the tasks where mistakes cost money: goods receiving and GRN entry, stock counts, picking and dispatch, export document checks before shipment, container loading, quality inspection, customer returns, supplier onboarding and petty cash. For export checks, the documents involved are usually a commercial invoice, packing list and bill of lading.

SOP or policy: what is the difference?

A policy says what the rule is and why: "Customers may receive credit up to their approved limit." An SOP says how to carry it out step by step: how a sales person checks the limit before confirming an order. Write the rule with the AI Policy Generator and the steps with the SOP generator.

Ready to write yours? Open the AI SOP Generator, name the task, describe how your team does it, and get a clean SOP to check with the people who do the work.

Frequently asked questions

What is the format of an SOP?

Purpose, scope, responsibilities, the procedure as numbered steps, records to keep, and review. Add a header with title, number, version and date.

How do I write a simple SOP?

Choose one task, watch it being done, write each action as a numbered step starting with a verb, say who does it and what record proves it, then test the draft with someone new.

Can AI write an SOP?

Yes, as a first draft. The TradingForms AI SOP Generator builds the standard sections from your topic and notes, keeps your own roles and steps, and leaves placeholders instead of inventing rules. Always check it with the people who do the work.

How long should an SOP be?

Usually one or two pages. If it grows longer, split it into separate SOPs for separate tasks.

How often should an SOP be reviewed?

At least once a year, and whenever the process, software or a rule changes, or after an audit finding.