How long should a receiving SOP be?

One page. Long procedures are written to satisfy an auditor and read by nobody, which produces the worst of both outcomes: the effort of documentation without the benefit of consistency. If a step genuinely needs three paragraphs, it belongs in training, not in the procedure taped by the door.

Who should write the receiving procedure?

The person who does the receiving, edited by whoever is accountable for it. A procedure written entirely by management describes what somebody imagines happens, and the first person to notice the difference is the new starter it was supposed to help.

What should a receiving SOP include?

Four blocks: checks before signing, how to count, what to record, and escalation, meaning who to tell and how fast for each kind of problem. Add a version number, an owner and a review date, because a procedure nobody owns drifts out of date invisibly.

How do I make sure people follow it?

Make the recorded outcome a by-product of the work rather than an extra step at the end. Every procedure that ends with 'then write it up' gets written up from memory at five o'clock, which is precisely the failure the procedure existed to prevent.

Does ISO 9001 require a documented receiving procedure?

The 2015 revision does not mandate a specific list of documented procedures. It requires you to keep the documented information necessary for the effectiveness of the system, and to retain evidence of conformity for released product. In practice, for goods receiving, that means a defined method and records of what you received.

A receiving procedure one person can actually follow

Q: A receiving procedure one person can actually follow

A receiving SOP should fit on one page and cover four things: what to check before signing, how to count, what to record, and who to tell when something is wrong. Anything longer gets filed rather than followed, and the two steps that get skipped first are noting damage before signing and counting independently of the packing slip.

A printable standard operating procedure for goods in, short enough to be read, plus the two places every long SOP breaks down.

By Hamza RiveraFounder, DockCountSeptember 4, 2026

In short

One page, four blocks, a version number and a name. Anything more gets laminated and ignored.
Write it with the person who does the job, or it will describe a building nobody works in.
If the last step is “then write it up”, the procedure has already failed.

Most receiving procedures fail in the same way. They are thorough, correct, four pages long, and read exactly once by the person who wrote them. The version below is shorter than it wants to be on purpose.

A flat illustration of a single sheet pinned to a plain wall beside a door frame, drawn straight on with the door edge just visible. — It has to be readable in the ten seconds somebody has while a driver waits, or it may as well be in a drawer.

Goods receiving procedure

One page. Review it once a year and put the date on it.

Document owner

Version and date

Applies to (site, dock)

Next review

1. Before you sign

Confirm the delivery is for us: address, company name, order reference
Count handling units against the carrier's paperwork
Walk once around the load and look at the outside
Photograph anything not perfect before it comes off the vehicle
Write any damage or shortage on the carrier's paperwork, on both copies, specifically

2. Counting

Count against the purchase order, not against the packing slip
Check the unit of measure before reporting any shortage
Read part numbers rather than recognising shapes
Open inner cartons wherever the outer showed damage
Record batch, lot or serial numbers where they apply

3. Recording

Enter the quantity actually received, even where it disagrees with the order
Record condition on every line, including 'good'
Attach the photographs to the delivery
Name the person who checked it

4. Telling somebody

If this happened	Tell	By when

Goods in dispute are held at

Approved by

The two places every long SOP breaks

1
It asks for a write-up after the fact. The end of a delivery is the moment with the least time and the most competing demands. Anything deferred to then is deferred to memory. The fix is not discipline, it is making the record fall out of the counting rather than follow it.
2
It has no escalation table. Everybody knows to tell somebody. Nobody agrees on who, or how fast, so the shortage goes to whoever walks past. Four rows: what happened, who to tell, by when: removes the whole problem, and it is the block most procedures leave out.

A flat illustration of four stacked horizontal bands of decreasing width, arranged like a simple flight of steps descending to the right. — Four blocks in order. The order is the procedure: most of the value is in what comes before what.

Writing the escalation rows

If this happened	Tell	By when
Visible damage, noted on the carrier paperwork	Purchasing, and the carrier	Same day
Short against the order	Purchasing	Same day
Damage found after opening	Purchasing, and the carrier	Same day, before anything is moved
Item not on any order	Purchasing. Do not put it away	Same day
Anything that stops a job running	Purchasing and the job owner	Immediately, by phone

Adjust the names, keep the shape. The value is that nobody has to decide who to tell while holding a pallet truck.

Training somebody on it

Do three deliveries alongside them before they do one alone. Watching is not training.
Give them one deliberately wrong delivery to find, if you can arrange it. People remember the one they caught.
Tell them explicitly that finding a problem is the job going well, not a complication. Most new receivers assume a clean delivery is the good outcome and quietly round toward it.

The one-page checklist that goes with this is in the receiving inspection checklist.

Questions people ask

How long should a receiving SOP be?: One page. Long procedures are written to satisfy an auditor and read by nobody, which produces the worst of both outcomes: the effort of documentation without the benefit of consistency. If a step genuinely needs three paragraphs, it belongs in training, not in the procedure taped by the door.
Who should write the receiving procedure?: The person who does the receiving, edited by whoever is accountable for it. A procedure written entirely by management describes what somebody imagines happens, and the first person to notice the difference is the new starter it was supposed to help.
What should a receiving SOP include?: Four blocks: checks before signing, how to count, what to record, and escalation, meaning who to tell and how fast for each kind of problem. Add a version number, an owner and a review date, because a procedure nobody owns drifts out of date invisibly.
How do I make sure people follow it?: Make the recorded outcome a by-product of the work rather than an extra step at the end. Every procedure that ends with 'then write it up' gets written up from memory at five o'clock, which is precisely the failure the procedure existed to prevent.
Does ISO 9001 require a documented receiving procedure?: The 2015 revision does not mandate a specific list of documented procedures. It requires you to keep the documented information necessary for the effectiveness of the system, and to retain evidence of conformity for released product. In practice, for goods receiving, that means a defined method and records of what you received.

Sources

01ISO 9001:2015, clause 7.5: documented information · International Organization for StandardizationRequires documented information to be identified, reviewed and controlled. A procedure with no version and no owner satisfies none of that.

DockCount does this job on a phone at the bay: count a delivery against the order it was placed on, photograph anything wrong, and the record writes itself. shipping and receiving software.