Procedures written for the person doing the work, in the conditions they do it, with the record designed alongside.
SOP development is the writing of standard operating procedures describing how a task is carried out, by whom, and what is recorded. Procedures are written for the person doing the work in the conditions they do it, which is what separates a document that gets followed from one that satisfies an auditor and sits in a folder.
A procedure nobody follows is worse than no procedure at all, because it documents a gap between what you say happens and what happens. Auditors find that gap by asking an operator to describe the task and comparing the answer against the document.
Written for the operator, mapped to the clause, with matching record blanks and a named owner. Delivered in any language, quoted on scope.
Six readers, and a procedure that serves only the last one is one of the most common kind.
| Reader | What they need | Common failure |
|---|---|---|
| The operator | Short sentences, one instruction per line, in the language the person reads. | A procedure written in technical register for a reader who will not use it. |
| The conditions | Steps that work at line speed, in gloves, in a cold store, under noise. | A procedure requiring a clipboard and five minutes at a step that allows neither. |
| The decision points | What to do when the reading is out of limit, stated at the point it is needed. | Corrective action buried in a separate document nobody opens mid shift. |
| The record | A blank designed alongside the procedure, so what is asked for can be captured. | A record demanding data the procedure never told anyone to collect. |
| The handover | Enough detail that a new starter or a cover shift can perform the task correctly. | A procedure relying on knowledge only the regular operator has. |
| The auditor | Traceable to the clause it satisfies, version controlled and approved. | A procedure that works on the floor and cannot be found in the system. |
Eight failures, and the first two produce documents that pass a desk review and fail on the floor.
A generic procedure adapted to fit, describing a process nobody recognises. Operators work around it, and the gap between the document and the practice is the finding.
Language chosen to satisfy a clause instead of to instruct. It reads well in a folder and gives the person doing the job nothing usable.
Fifteen pages covering a two minute task. Length signals thoroughness and guarantees the procedure is never opened after the first week.
The procedure says what to do when it works and goes silent when it does not. Deviations are then handled by whoever is present, differently each time.
A blank asking for information the procedure never mentions, or a procedure asking for a record that has no field for it.
A procedure belonging to nobody drifts out of date and is never revised when the process changes.
Final, final v2, final revised. Superseded copies stay in circulation on the floor while the system holds something else.
Written at a desk, approved at a desk, issued to the floor. The first person to find the procedure impossible is the operator, and they will not report it.
Delivered editable, with everything needed to maintain the set yourselves.
| Element | What it covers |
|---|---|
| Procedure set | Each procedure written for your process, in the language your team reads. |
| Matching record blanks | Designed alongside each procedure so what is asked for can be captured. |
| Clause mapping | Each procedure traced to the requirement it satisfies, so coverage is demonstrable. |
| Decision points | Corrective action stated at the step where the deviation is found. |
| Owners and review dates | A named owner and a review interval for every procedure. |
| Version control | Numbering, approval and withdrawal so superseded copies leave the floor. |
| Index | A register of every procedure, its owner, its version and what it covers. |
| Handover notes | Written so your team can maintain and extend the set afterwards. |
Food manufacturers, processors, packers and catering businesses. It suits operations with high turnover or several languages on site, where consistency has to come from the system instead of from individuals.
Your procedures came from a template and nobody follows them.
An auditor has compared a procedure against practice and found a gap.
Procedures exist and the matching records do not.
Your team speaks several languages and the procedures are in one.
A new line or process has no procedures at all.
Procedures have no named owner and are out of date.
Superseded copies are still in circulation on the floor.
New starters learn by shadowing because the procedure is unusable.
You confirm which tasks need procedures, the standard you work to, and the languages required.
The task is walked with the person who performs it, since a procedure written at a desk describes an imagined process.
Each procedure is written for the operator, with decision points and corrective action at the step.
Blanks are designed alongside the procedure so the two ask for the same things.
Drafts go back to the people who will use them, which is where impossible steps get found.
Clause mapping, owners, review dates and version control are applied, and the index is delivered.
Training your team on the procedures, which is quoted separately.
Enforcing use. A procedure that is written well still needs supervision behind it.
The wider system. A full manual with policies and supporting documents is documentation development.
Every project is quoted against its own scope. Six procedures for one line and a full set across three sites in two languages are very different pieces of work. These factors set the price.
These are the primary sources this work is built on. Where a market you sell into has its own requirement, that takes precedence and we assess against it.
It is a documented instruction describing how a task is carried out, who carries it out, and what is recorded. In a food safety system it covers the tasks that keep the controls working, from monitoring a critical limit through to changeover cleaning and goods receipt.
As long as the task needs and no longer. A two minute task described across fifteen pages will not be read, and length is not evidence of rigour. What matters is that a competent person can perform the task correctly from the document.
The person doing the work, in the conditions they do it. That means short sentences, one instruction per line, and language the reader uses. A procedure written to satisfy a clause reads well in a folder and gives the operator nothing.
Yes, at the step where the deviation would be found. A procedure that describes only the normal case sends the operator elsewhere at the moment they have least time, so deviations get handled differently by whoever is present.
Comprehension has to be achieved, and language is how that happens. A procedure in a language the operator does not read is a document, not an instruction. Procedures are written in any language you need.
The record blank should be designed alongside the procedure. Where they are written separately you get blanks asking for information the procedure never mentions, and procedures asking for records with nowhere to put them.
Enough to cover the tasks your controls depend on, and no more. Standards do not set a number. Businesses are found non compliant for having procedures nobody follows at least as often as for having too few.
A named person close enough to the task to know when it changes. Ownership by a department drifts, and a procedure belonging to nobody is never revised when the process moves.
On a defined interval, and immediately after any change to the process, the equipment, the product or the standard. The interval matters less than the change trigger, because processes move between scheduled reviews.
Frequently yes, and it is usually better if the person who knows the task drafts it. Where businesses struggle is in the volume, in clause mapping, and in writing for an operator instead of for an auditor. Support can cover the whole set or only the difficult ones.
Yes. They are delivered in editable form with an index, named owners and review dates, and the handover covers how to extend the set. Procedures you cannot maintain are procedures that go out of date.
A procedure set written for your process, matching record blanks, clause mapping showing what each procedure satisfies, corrective action at each decision point, named owners and review dates, version control, an index and handover notes.
Confi Food assigns work by subject. HACCP, labelling, certification standards, regulatory compliance, supplier assurance and monitoring are separate disciplines, and each piece goes to someone who works in that area. Every deliverable is reviewed internally by a second specialist before it reaches you.
Our technical positions are built from primary sources, meaning the legislation, the competent authority, Codex Alimentarius, the certification scheme owner or the relevant standards body. We set out how that works in our technical review and editorial policy, and what happens at each stage of an engagement in how Confi Food works.
Building the full documented system your standard requires, from policy through to record templates.
Read about Food Safety Documentation Development →A review of the records you keep against the records your standard and your regulator expect to see, including retention and legibility.
Read about Recordkeeping System Review →Certificated courses covering HACCP, auditing, hygiene and the major standards.
View courses →Expert ISO 22002 consulting worldwide. Prerequisite programmes (PRPs) supporting ISO 22000 and FSSC 22000, the 2025 restructured series with Part 100, sector-specific...
See ISO 22002 Consulting →Expert BRCGS Food Safety consulting worldwide. Gap assessments, Issue 9 certification prep, mock audits, Grade AA support and ongoing compliance for food...
See BRCGS Food Safety Consulting →Expert EU food hygiene consulting worldwide. Regulation 852/2004 and 853/2004 compliance, HACCP-based procedures, establishment approval, official controls, and 2026...
See EU Hygiene Regulations Consulting →Tell us which tasks need procedures, the standard and the languages, and receive a written quote covering the scope, the deliverable and the price.