Standard Operating Procedure: Format, Steps & Example

7 min read

By

TranZact Solutions Team

· Published

Hero Background
Functions of ERP System Explained

A standard operating procedure (SOP) is a written set of step-by-step instructions for doing a routine task the same way every time. A good SOP states its purpose, who does each step, the tools or materials needed, the steps in order, and the record to keep. In a factory, SOPs cover jobs like receiving material, issuing stock to production and dispatching orders. They hold best when the software your team uses follows the same steps.

What is a standard operating procedure?

An SOP turns one person's know-how into a written method anyone on the team can follow. It answers three questions: what to do, who does it, and in what order.

What does an SOP provide? The same result every time, fewer mistakes, faster training for new staff, and proof for auditors and customers.

In this guide, SOP means standard operating procedure. It is not the statement of purpose used in college applications.

The parts of an SOP

Most guides list five core parts. Factories usually add two more.

  1. Header: SOP number, title, version, effective date and who approved it.

  2. Purpose and scope: why the SOP exists and which jobs, sites or items it covers.

  3. Roles and responsibilities: who does each step, by job title, not by name.

  4. Materials, tools and safety: forms, equipment, protective gear and any hazards.

  5. Steps in order: numbered actions, one action per step.

Then add the records to keep (the form or entry that proves the job was done). Finish with references to related SOPs or standards.

SOP formats: which one to use

TechTarget's guide describes three common SOP formats. Pick one by how complex the job is.

  • Simple numbered list: short jobs with no decisions, like a daily start-up check.

  • Hierarchical steps: long jobs with sub-steps, like receiving material.

  • Flowchart: jobs with decisions, like "accept, hold or reject" at inspection.

How to write an SOP in 7 steps

1. Pick the task and the goal

Start with a job where mistakes cost money or repeat often. Write one line on what a good result looks like.

2. Watch the job and talk to the people who do it

Stand where the work happens and note every step, even the ones nobody mentions. The operator knows the real order better than anyone.

3. Choose the format

Use a numbered list, hierarchical steps or a flowchart, as above. Keep one template for every SOP.

4. Write the draft in short, plain sentences

Start each step with a verb: check, count, enter, sign. Keep one action per step and name who does it.

5. Test it on the floor and fix gaps

Ask someone new to follow the draft without help. Every question they ask is a gap to fix.

6. Approve, train and keep it where people work

Get the process owner to sign it off, then train everyone who does the job. Keep a copy at the workstation, not only in a file.

7. Review every 6–12 months and number versions

Also review it whenever a machine, material or process changes. Give each version a number and date, and withdraw old copies.

Is your SOP ready to use?
  • Number, version and date on top

  • Each step names who does it

  • One action per step

  • Tested by someone new

  • Says which record to keep

  • Signed off and kept at workstation

Why SOPs fail on the shop floor

Many factories with SOPs still see the same mistakes. The problem is rarely the document.

  • The SOP sits in an office file, far from the job.

  • Steps get skipped when a truck is waiting or an order is late.

  • Nobody checks whether each step was done.

  • Records are written later, from memory, in a register.

The fix is to put the steps where the work gets recorded. When your software follows the same order as the SOP, following it becomes the normal way to work.

How TranZact helps a factory follow its SOPs

TranZact is manufacturing AI software used by 10,000+ manufacturers. Its flows match a factory's business SOPs, step by step.

  • Purchase SOP: MRP report → indent → RFQ → PO → GRN → payment. The MRP engine runs through your orders and BOMs, then tells you what to buy and when. See purchase management.

  • Stores SOP: stock in, bin card, issue, multi-store, reorder and AI stock alerts.

  • Production SOP: multi-level BOM, work orders, process routing, sub-contracting and production costing.

  • Dispatch SOP: enquiry → quotation → order → dispatch → e-invoicing → payment. The e-way bill is generated from the GST invoice, with the e-invoice (IRN) in the same flow.

  • Checks: approvals and alerts, plus 65+ reports to check the record each step leaves.

Quality control for raw material and finished goods, and Batch Tracking & QC, are on the Dominate plan. Accounts stay in Tally, Busy or Zoho Books through a one-way sync, with no double entry. TranZact goes live in 2–3 weeks.

One honest limit: TranZact runs the business steps. Safety, machine-setting and hygiene SOPs still stay as written documents at the workstation.

Book a demo →

SOP example: receiving raw material at stores

Here is a complete SOP for one of the most common factory jobs. Change the names and steps to fit your unit.

SOP No.: ST-01 · Title: Receiving raw material at stores · Version: 1.0 · Effective date: [date] · Approved by: Plant head

Purpose: receive only ordered material, in the right quantity and condition, and record it the same day. Scope: all raw material and bought-out parts arriving at the gate.

Roles: security, stores keeper, QC inspector, purchase executive.

Step

Who

What to do

Record

1

Security

Log the vehicle and match the supplier's invoice or challan to an open PO.

Gate entry

2

Stores keeper

Count or weigh the material against the PO and invoice.

Count sheet

3

Stores keeper, purchase

Note any shortage, excess or damage. Purchase takes it up with the supplier.

Discrepancy note

4

QC inspector

Inspect items that need incoming checks. Accept, hold or reject.

Inspection note

5

Stores keeper

Make the GRN for the accepted quantity.

GRN

6

Stores keeper

Put the material away in the right store and bin.

Bin card

7

Stores keeper

Update stock the same day.

Stock entry

8

Stores keeper

Send the GRN to accounts with the supplier invoice.

GRN copy

Records kept: GRN and inspection note, filed against the PO. For the fields a GRN needs, see our GRN format guide.

TranZact at a glance
  • 10,000+ manufacturers use TranZact

  • 2–3 weeks to go live

Which SOPs a manufacturer needs first

Start with 5 to 10 SOPs where errors cost money. A good first list:

ISO 9001 expects documented processes for work that affects product quality. Pharma units under revised Schedule M also train staff on SOPs and documentation practices, such as batch manufacturing records.

Can I write my own SOP, and can ChatGPT write it?

Yes, you can write your own. The person who does the job should help write it, because they know the real steps.

ChatGPT can draft a layout and tidy the wording. But it does not know your gate, your stores or your suppliers. Test any AI draft on the floor and approve it yourself. More in what ChatGPT can't run in a factory.

Paper SOP vs SOP run in software

Point

Paper SOP

SOP run in TranZact

Where the steps live

A file in the office

In the flow your team uses daily

Order of steps

Depends on memory

A fixed order, such as indent → PO → GRN

Records

Written later in registers

Each step leaves a record

Checking

Someone audits the file

Approvals, alerts and 65+ reports

Accounts

Re-typed into Tally

One-way sync to Tally, no double entry

Safety, machine and hygiene steps

Written SOP

Still a written SOP

Write the SOP, test it, then let your software carry the business steps every day. See your purchase, stores and dispatch SOPs run in TranZact on a short call.

Don't be the bottleneck. Become the AI-Run Factory.

Book a demo →

Check out other blogs

Hero Background
Become the
AI-Run Factory

Born in India. Building for the world.

Built by IIT & IIM founders

Hero Background
Become the
AI-Run Factory

Born in India. Building for the world.

Built by IIT & IIM founders

Hero Background
Become the
AI-Run Factory

Born in India. Building for the world.

Built by IIT & IIM founders