A standard operating procedure earns its place when it answers questions at the moment someone has them, usually while holding a box that arrived warm. Most procedures fail that test because they describe what should generally happen rather than what to do when it does not.
Scope, stated narrowly
Start by saying what the document covers and what it does not. A receipt and storage SOP covers material from arrival to the point it enters use, and explicitly not what happens after that. A document that tries to cover everything is a document nobody reads.
Name the material types in scope, since lyophilised vials, solutions and films have different handling, and a procedure written only for powder leaves a gap the first time a spray arrives.
Responsibilities by role, not by name
Assign each step to a role rather than a person. People leave; roles persist. Where a step requires a decision — accepting material with a recorded excursion, for instance — name which role has the authority to make it and which role is informed.
A step with no owner will not happen reliably, and the step most often left unowned is the one that decides whether to quarantine.
The receipt sequence
Write this as an ordered list with a decision rule at each point where there is a choice.
- Record arrival: date, time, courier, who received it.
- Inspect the outer package before opening, and record damage before it can be attributed to unpacking.
- Read the temperature indicator or logger if present, and record the reading whether or not it is within range.
- Check contents against the order and the documentation, including that certificate lot numbers match vial lot numbers.
- Inspect vials for physical defects.
- Move to storage, recording the time, or quarantine with the reason recorded.
The thing to get right is the decision rules. Not "check the temperature indicator" but "if the indicator shows an excursion, quarantine and notify the named role; do not place in general stock." A procedure full of verbs without thresholds leaves every judgement to whoever is holding the box.
Storage
- The condition for each material type, matching what the supplier specifies.
- Where each condition is physically located.
- How the location and date are recorded against the lot.
- The monitoring arrangement and who reviews the records, with a stated frequency.
Exceptions, which is the part that gets used
The exception section is what people actually turn to, and it should cover the situations that genuinely occur: a shipment arriving warm, a missing or mismatched certificate, physical damage, a monitoring alarm, a power failure, and material approaching its supported date.
For each, state the immediate action, who decides, and what gets recorded. If the honest answer to a case is that it requires judgement, say who exercises it rather than leaving the question open.
Keeping it true
Date it, version it, and set a review interval. An SOP describing equipment that was replaced or a role that no longer exists is worse than none, because it trains people to ignore the document.
The honesty test is simple: does the procedure describe what the practice actually does? Where it does not, either the practice changes or the document does. A procedure maintained as a description of reality gets followed; one maintained as an aspiration gets filed.
Two clauses are worth writing explicitly because they are otherwise decided by default: what happens when a shipment arrives outside its temperature range, covered in temperature excursions on arrival, and whether a date on a vial is treated as a retest or an expiry, covered in retest dates and expiry dates.
For how this fits with everything else that happens to a vial between delivery and use, peptide storage and handling for clinics covers the full picture.

