How to Build an SOP Library for a Small Supplement Business
A small brand does not need a quality manual. It needs about ten one-page procedures. Written procedures matter when the person who knows how something works is unavailable. Here are the ones worth writing first.
Why a Small Brand Needs Any
This guide is for small supplement, Ayurvedic and herbal brands in India.
In a small business, procedures live in one or two people’s heads. That works until someone is unavailable, a new person joins, or a question arrives about something done months ago that nobody can now reconstruct.
The purpose of written procedures at this scale is continuity, not formality. They answer how something is done consistently when the person who normally does it is not there. That is a much smaller ambition than a quality management system, and it is achievable in a few hours of work.
Keep each one to a page. A procedure nobody reads provides nothing.
The Ones Worth Writing First
In rough priority order for a small brand.
- Goods receipt: what to check when stock arrives, including batch number, quantity, condition, expiry and recording.
- Certificate of analysis review: how to check a COA against the specification and what to do if something is missing or out of range.
- Complaint handling: triage separating health effects from quality and service issues, what to record, and who escalates.
- Health effect escalation: a short, clear path for anything involving a reported health effect.
- Dispatch: how orders are picked, checked and recorded, including batch numbers at dispatch.
- Returns: how returned stock is handled, inspected and segregated, and what cannot re-enter stock.
- Stock rotation: first expiry first out, and how ageing stock is reviewed.
- Artwork approval: the steps from brief to print, including the compliance review gate.
- Change control: what to do when a manufacturer proposes an ingredient, source or process change.
- Product file maintenance: what gets filed, where, and when.
What Each Should Contain
Keep the structure identical across all of them.
| Section | Contents |
|---|---|
| Purpose | One line on what this procedure is for |
| Who does it | The role, and a named backup |
| When | The trigger: on receipt, on complaint, monthly |
| Steps | Numbered, in order, specific enough to follow |
| What gets recorded | Which log or file, and which fields |
| What to do if something is wrong | The exception path, including who to escalate to |
| Version and date | So changes are traceable |
The exception path is the part most often missing and most often needed. A procedure that only describes the normal case leaves the person stuck precisely when the procedure matters.
How to Build Them Without Stopping Work
Write them as you do the task, not as a separate project.
Write While Doing
The next time you receive stock, write down what you check as you check it. That is the procedure, nearly finished.
Start With the Riskiest
Health effect escalation and complaint triage first, because those are where improvisation causes the most harm.
Have Someone Else Test It
Give the draft to someone who has not done the task. Where they get stuck is what is missing.
Revise After Real Use
A procedure survives contact with reality or it does not. Update it the first time it proves awkward.
Do not write procedures for things you do not actually do. An aspirational procedure is worse than none, because it creates a record of a process that is not followed.
Keeping Them Alive
Four maintenance habits.
- Store them where more than one person can access them, not on one laptop.
- Version and date each one, so you know which was current when.
- Review them when something goes wrong, since an incident usually reveals a gap.
- Review the whole set once a year, and delete any that no longer reflect how you work.
Checklist
Build the first set.
- Write goods receipt, as you next receive stock.
- Write certificate of analysis review, next time one arrives.
- Write complaint triage and health effect escalation first if time is limited.
- Write dispatch, including recording batch numbers.
- Write returns handling and stock rotation.
- Write artwork approval with the compliance gate included.
- Write change control.
- Write product file maintenance.
- Use the same structure for every one, including an exception path.
- Keep each to one page.
- Have someone untrained test each draft.
- Store them where more than one person can access them.
- Version, date and review annually.
Need Documentation Your Procedures Can Rely On?
Share your product and our team will set out the batch documentation, testing and certificates your processes will handle.
Frequently Asked Questions
Does a small brand really need written procedures?
For continuity rather than formality. Procedures that live in one person’s head work until that person is unavailable, someone new joins, or a question arises about something done months ago that nobody can reconstruct.
How long should each procedure be?
One page. A procedure nobody reads provides nothing, so the test is whether someone who has not done the task could carry it out correctly from the document. Past two pages it probably needs less, not more.
Which should I write first?
Complaint triage and health effect escalation, because those are where improvisation causes the most harm. Then goods receipt, certificate of analysis review, dispatch with batch recording, returns and stock rotation.
What is most often missing from procedures?
The exception path: what to do when something is wrong and who to escalate to. A procedure describing only the normal case leaves the person stuck exactly when the procedure matters most.
How do I write them without stopping work?
Write each one while actually doing the task. The next time you receive stock, note what you check as you check it. Then have someone untrained test the draft, and revise it the first time it proves awkward in real use.