Writing the OSP for a Handler Facility

A handler facility's Organic System Plan is a fundamentally different document from a producer's. The land-and-soil questions disappear. In their place: every ingredient sourced, every cleaning protocol between conventional and organic runs, every label claim reconciled against the National List, every lot traced from receiving dock to outbound truck. The certifier is not asking how you grew it — they're asking how you kept it organic after it left the field.

This guide is for operations that process, package, store, repackage, or distribute organic agricultural products: a flour mill, a produce packing house, a dairy processor running organic Mondays and conventional Tuesdays, a co-packer making three private-label granolas, a cold-storage warehouse holding organic almonds for export. The governing regulation is NOP §205.270, and the modules below are the practical translation of that rule into an OSP a certifier will accept.

The handler-OSP question that decides everything

Before any module makes sense, an operation has to answer one question: does this facility take possession of organic products?

The answer determines which modules apply.

Yes — the facility takes possession. This is the standard handler scenario: receiving, processing, repacking, labeling, distributing. Modules H2 through H5 (and beyond) apply in full.
No — storage of others' product only. The facility holds organic product belonging to other certified operations but never takes possession or alters it. Only the receiving-and-storage module (H2) is required, and the rest of the H series is gated off.
Not applicable — the facility is conventional production only. No organic activity occurs here. None of the H modules apply. The facility is still on the OSP as a property record but doesn't trigger handler scope.

Inside Quick Organics this is the handlerPossession field on every facility record, with a downstream cascade that controls which questions surface. It maps to the regulatory test in NOP §205.270: an operation that handles organic products — defined as selling, processing, or packaging — needs a handler OSP. A facility that only stores someone else's certified product is held to a narrower bar; a facility with no organic activity isn't a handler at all.

The second question is what kinds of handling actually happen there. The handler activities checklist has nine entries:

PROCESSING_MANUFACTURING — turning raw inputs into a different product
STORAGE_DISTRIBUTION — holding finished goods and shipping them
LABELING_RETAIL — applying organic labels for retail sale
WAREHOUSING_STORAGE_ONLY — storage with no transformation
REPACKING — moving product into different containers
TRANSLOADING — transferring between transport modes
IMPORTING_EXPORTING — bringing product across borders
TRADER_BROKER — buying and selling without taking physical possession
OTHER — with a freeform description

The first six imply physical possession. When handlerPossession=NO, those six lock out automatically — only the storage-only and broker categories remain selectable. A facility that doesn't take possession can't be doing processing, repacking, or transloading, definitionally.

Once those two answers are locked in, the OSP modules below are scoped accordingly.

H1: Facility Information

The lightest module to write but the one that frames everything else. Required entries: legal name of the operation and facility (an operation can have multiple facilities, each with its own H1 record), physical and mailing addresses, facility category and storage sub-type, square footage and capacity, production type, whether the facility is shared-use, and a site map showing receiving, storage, production, packaging, and shipping zones with the path organic product takes through the building.

The site map is the single most important attachment. Inspectors trace organic product through the facility on the day of inspection; the map is what they walk with. A drawing made in PowerPoint with labelled arrows beats a CAD blueprint with no path overlay.

For a co-packer this section has to disclose every brand the facility runs, not just the organic ones — the question on the back end is always: what does the facility do when it isn't doing organic, and how do you keep those runs from contaminating each other?

H2: Receiving and Identity Preservation

The first module where things get specific. Every organic input arriving at the facility has to be:

Received with documentation — a current organic certificate from the supplier covering the specific product, plus a bill of lading and an invoice that references the lot
Verified on arrival — the receiving clerk visually confirms the product matches the documents, the seal is intact, the labels say what they should
Lot-coded and identified — every incoming lot gets an internal identifier that ties back to the supplier's lot and forward to every outbound shipment containing that material
Stored separately from non-organic — physically segregated, labelled, and recorded by location

The OSP describes this as a procedure. "We check the certificate" is not a procedure — "the receiving clerk pulls the supplier's organic certificate from our supplier file (or downloads the current copy from the Organic Integrity Database), confirms the product on the BOL is listed on the certificate, confirms the certificate is current as of the receipt date, and stamps the BOL 'ORG VERIFIED' before signing it" is.

The receiving log is a recordkeeping artifact, not part of the OSP, but the OSP describes its structure: date, supplier, product, lot, quantity, certificate verified (Y/N), receiving clerk initials. Inspectors sample receiving logs against actual incoming product on inspection day.

H3: Commingling Prevention

The most heavily reviewed handler module, governed by NOP §205.272. Commingling is the unintended mixing of organic and non-organic product, and a single commingling event can cause an entire lot to lose its organic status. The OSP has to describe how the facility prevents it across four vectors:

Spatial separation. Organic product is stored in a designated area, labelled, with a physical barrier (rack, room, fence) between it and conventional. Where space prevents physical separation, the OSP describes the visual labelling system and audit frequency.

Temporal separation. When organic and conventional run on the same line, the OSP specifies the sequence (organic first, or organic only on designated days) and the cleaning protocol between runs. A typical organic-then-conventional protocol: "Organic run completes. All product is removed from the line. Sanitation crew runs the documented dry-clean (compressed air through every reachable surface, brush-down of the conveyor, vacuum of catch pans), followed by an allergen-and-organic-grade wet wash with an approved sanitizer from NOP §205.605. Verification swabs are pulled at six points and tested. Line release is documented before the conventional run begins."

Equipment separation. Where equipment can be dedicated to organic, it is, and the OSP says so. Where it can't, the cleaning protocol takes over. Belts, bearings, hoppers, augers, and pocketed surfaces get specific attention — that's where residue lingers between cleanings.

Procedural separation. Organic runs Monday through Wednesday. Conventional runs Thursday and Friday on a different line in a different room. Forklift drivers use color-coded tags. The OSP describes who does what, when, and how they know they're doing it right.

For a co-packer running multiple brands the commingling section frequently runs longer than the rest of the OSP combined. Certifiers reading this module look for failure modes — what happens when a line worker pulls the wrong scoop, what happens when a conventional pallet ends up in the organic aisle, what the corrective-action protocol is.

H4: Pest Management

Under NOP §205.271. The handler pest-management hierarchy is the same shape as the producer one: prevention first, then mechanical/cultural, then allowed materials.

For handlers, prevention dominates: door sweeps, bird netting, dock-leveler seals, sanitation schedules that deny pests food and harbourage, monitoring with traps and pheromone lures. The OSP describes the prevention program as a written schedule (e.g. monthly pest-control technician visit with documented trap counts) and the approved materials list.

Allowed materials must be on the National List for the use case. Insecticidal applications inside a food-handling area face additional restrictions: organic-compatible isn't enough — it has to be approved for food-contact context. Boric acid in a wall void is fine; boric acid on a flour mill line is not.

If a prohibited substance has to be used (a regulatory mandate, an emergency pest event), organic product must be removed from the area and not exposed. The OSP describes the protocol: when the conventional pesticide is applied, what gets covered or removed, how long the area is closed to organic product, and what verification looks like before the area is released.

H5: Sanitation and Cleaning

Treated as its own module because of the volume of detail. The OSP lists every cleaning agent and sanitizer the facility uses and confirms each is approved for organic-handling contact under NOP §205.605. A few rules that catch operations off guard:

Chlorine sanitizers are allowed but residual chlorine in the final wash water must meet the Safe Drinking Water Act maximum (4 ppm). A produce packing house running a chlorine wash has to monitor and document this every batch.
Quaternary ammonium ("quat") compounds are not on the National List. Quats for non-organic-contact surfaces (locker rooms, restrooms) are fine; quats on the line are not.
Peracetic acid is allowed and widely used as a no-rinse sanitizer at controlled concentrations.
Caustic-based clean-in-place (CIP) cycles are allowed for dairy and beverage equipment with a documented potable-water rinse.

The OSP describes cleaning frequency for each zone and the verification method (visual, ATP swab, environmental monitoring). It attaches the master sanitation schedule and the approved-chemical list with SDS sheets.

H6: Ingredient and Label Verification

Where the OSP meets the marketing claim. Every product the facility makes needs a recipe, and every ingredient gets classified into one of three categories: organic agricultural (certified organic with a current supplier certificate), nonorganic agricultural (listed on NOP §205.606 as commercially unavailable in organic form), or nonagricultural (listed on NOP §205.605 with the specific use case approved — yeast, baking soda, certain enzymes, certain natural flavours).

These categories drive the label tier:

"100% Organic" — every ingredient is certified organic agricultural; only water and salt may be added without counting against the percentage
"Organic" — at least 95% of the agricultural ingredients (by weight, excluding water and salt) are certified organic, and the remaining 5% comes from NOP §205.605 or NOP §205.606
"Made With Organic [specified ingredients]" — at least 70% of the agricultural ingredients are certified organic; the remaining 30% must still be agricultural and non-GMO, with non-agricultural ingredients limited to the National List

For each product the OSP includes the recipe, an ingredient classification table, the percentage calculation, and the label artwork. The certifier reviews the label as part of approving the product. Label changes — a new ingredient, a reformulation, a moved certifier seal — go through a change request before the new label hits the market.

H7: Recordkeeping and Traceability

The traceability requirement under NOP §205.270(c) is more demanding for handlers than for producers. The certifier must be able to follow any finished organic lot back through every input, process step, and cleaning event to the supplier certificates that authorised the inputs — and forward to every customer who received that lot.

The OSP describes the recordkeeping system that makes this possible: lot-coding scheme, receiving log structure, production batch records linking input lots to output lots, cleaning logs tied to line-release events, outbound shipment log linking output lots to customer invoices, and the five-year retention requirement under NOP §205.103.

Inspectors run a "mock recall" on the day of inspection: pick a finished lot from the warehouse and trace it backward to every supplier and forward to every customer in under two hours. Most facilities at any scale move to a batch-record software system; the OSP describes the software, who has access, and what's printed for the inspection-day binder.

A worked example: a small co-packer

A co-packer in Pennsylvania runs three product lines: an organic granola for a private-label brand, a conventional granola for a different brand, and a seasonal organic energy bar. The facility is one production room with two ovens and a packaging line.

The handler-possession answer is YES — the operation takes title to inputs, processes them, and ships finished goods. The activities checklist gets PROCESSING_MANUFACTURING, LABELING_RETAIL, and STORAGE_DISTRIBUTION checked.

The H3 commingling section runs four pages. Schedule: organic granola Monday–Tuesday, organic energy bars Wednesday morning, conventional granola Wednesday afternoon and Thursday, sanitation-and-maintenance Friday. Between organic and conventional on Wednesday, the documented changeover is 90 minutes: full disassembly, dry vacuum, alkaline foam wash, potable rinse, peracetic-acid sanitizer, ATP swab at six points (target <30 RLU), line-release form signed by the production supervisor.

H6 has three product entries: organic granola (17 ingredients, 100% organic agricultural with salt and a touch of natural vanilla flavour from §205.605, labeled "Organic"), organic energy bar (22 ingredients, 96.4% organic agricultural, labeled "Organic"), conventional granola (disclosed for context).

H7 describes the lot system: every organic batch gets the code "ORG-YYWWD-LL" — year, week, day, line. Receiving, batch records, cleaning log, and outbound shipment log all reference that code. Records live in a shared cloud folder and are printed monthly into a binder kept in the QA office.

The OSP runs about 50 pages plus attachments. The first inspection takes the certifier about six hours: a walk-through against the site map, a mock recall on one granola lot, a sanitation-log review, a supplier-certificate audit on five randomly chosen suppliers, and a label review against three actual production runs. The operation passes with two minor noncompliances on receiving-log completeness.

Common reasons handler OSPs come back for revision

Site map missing or doesn't show the organic product flow. Answer "where does it go?" in a single page.
Cleaning protocol generic instead of specific. "Cleaned between runs" is not a protocol — steps, materials, contact times, verification, sign-off.
Ingredient list doesn't tie to a recipe. The certifier must be able to compute the 95%/70% calculation from what's submitted.
Supplier certificates not current. Suppliers' certificates expire annually and operations forget to refresh.
Co-packer brand list incomplete. Every brand and product on the line needs to be disclosed.
Label artwork missing or mismatched to the recipe. Labels are reviewed as part of the OSP; submitting them later is a revision round.

How Quick Organics changes the workflow

The handler scope inside Quick Organics is built around the handlerPossession and handlerActivities fields on every facility record. Possession determines which H modules surface — YES opens the full H2 through H5 set, NO (storage of others' product only) limits the OSP to H2, NOT_APPLICABLE keeps the facility on the property roster without triggering handler scope. The activities checklist is gated by the same answer: when possession is NO, the six possession-required activities lock automatically, leaving only warehousing-storage-only, trader-broker, and other selectable. Site maps and sanitation SOPs upload as facility documents and attach into the OSP module appendix at finalization. Cleaning events, supplier-certificate refreshes, and pest-control inspections logged as activities flow into the H modules at finalization, so the OSP reads from the same source of truth the operation uses day-to-day. The certifier sees a structured handler OSP with every field filled, every attachment in place, and a traceability story they can audit in one sitting.

Get started or read about the platform.

Glossary: Handling operation — definitional summary
Glossary: National List — allowed and prohibited substances
Glossary: USDA Organic seal — label tiers and seal usage
Glossary: Recordkeeping — five-year retention rule
Writing an Organic System Plan — the producer-and-handler overview