# Organic input and spray records: five years of traceable evidence

URL: https://leafwrit.com/us/organic-farm-spray-records/
Reviewed: 2026-10-23

Certified-organic operation records must remain available for at least five years beyond creation and disclose activities and transactions in enough detail to be understood and audited. Under 7 CFR 205.103, the records span purchase or acquisition through production to sale or transport and include an audit trail for products handled or produced. Treat the spray entry as one connected part of that evidence, alongside the organic system plan, input records, and production history. [^1]

## Begin with the organic system plan

Section 205.201 requires the producer or handler to develop an organic system plan agreed with an accredited certifying agent, subject to the stated exemption. The plan describes practices and procedures and their frequency, production or handling inputs, monitoring, the recordkeeping system, and practices preventing commingling or contact with prohibited substances. [^2]

For each production or handling input, the plan lists composition, source, locations of use, and applicable documentation of commercial availability. Preserve the exact input identity in the product directory and connect each actual treatment to the plan information used for that input. A familiar product nickname should not replace the identity needed to make that connection. [^2]

| Evidence group | What it explains | Suggested link in the treatment file |
| --- | --- | --- |
| Organic system plan | Intended practices and listed inputs | Plan revision and relevant input reference |
| Purchase or acquisition record | Where the input or product came from | Supplier document and exact identity |
| Application record | What occurred in production | Treatment date, crop/site, input, quantities, and source note |
| Monitoring or pest-management evidence | The documented management context | Observation and procedure references |
| Harvest and product movement | What production followed | Crop/lot and harvest or movement references |

The regulatory plan and traceability requirements establish the evidence relationships. The suggested links are editorial organization choices, rather than a prescribed federal spray-form layout. [^1][^2]

## Record the management context for crop protection

Section 205.206 begins with preventive management practices for pests, weeds, and diseases, including the listed crop-management, sanitation, and cultural approaches. It then addresses mechanical or physical controls and other specified methods. Its paragraph (e) provides conditions for certain additional substances when the practices in paragraphs (a) through (d) are insufficient. [^3]

Paragraph (e) specifically requires the conditions for using the substance to be documented in the organic system plan. Preserve the observation or management reference explaining the actual treatment, together with the relevant plan entry. The documentation task is to make the treatment understandable within the management system; it is not to infer that a product is permitted from an organic-sounding trade name. [^3]

Keep preventive observations, a recommendation, and the completed application identifiable as different records. If an agronomic decision changes, preserve which instruction relates to the work actually performed. Link the final treatment note to the applicable input identity and location rather than silently importing all values from the earlier recommendation.

## Adapt the record system to the operation

Section 205.103 says records are adapted to the particular business and sufficient to demonstrate compliance. An orchard, a vineyard, and a mixed vegetable operation can therefore organize their files around their own production references while preserving auditable information. Keep a location key that survives changes in staff or working field names. [^1]

For an input application, a practical entry can identify the treatment, date, place, crop, exact input, quantity and unit, applying person, and related plan and purchase references. Use headings that distinguish formulated product from carrier or mixture, and distinguish total quantity from a rate. These are suggested organizational fields; the organic rule establishes the broader recordkeeping and plan duties.

USDA's Organic Transition Workbook supplies examples of operation records, including input and spray-related documentation. Use those examples as planning aids and compare them with the needs of your own operation and certifying-agent plan. Preserve the documents that explain the activity rather than assuming that downloading a workbook completes the record. [^4][^2]

## Trace purchase through production and product movement

The current record rule explicitly requires records spanning purchase or acquisition, production, and sale or transport, traceable back to the last certified operation. It also requires audit-trail documentation for agricultural products handled or produced. Keep crop and product references consistent across the register, harvest records, and movement documents. [^1]

A practical review begins with a crop or lot reference in the harvest or movement file and follows it back to the production location and relevant input applications. Then locate the input purchase evidence and plan reference. Record the relationship in an index so the next reader does not have to reconstruct the farm's naming conventions from memory.

The rule also requires identifying agricultural products on the audit-trail records as 100% organic, organic, made with organic specified ingredients or food groups, or similar applicable terms. Preserve the actual status description used in the production and handling documents instead of stripping that information from an export. [^1]

## Separate organic and nonorganic production evidence

The organic system plan describes management practices and physical barriers preventing commingling on a split operation and preventing contact with prohibited substances. Keep the production status of the relevant area or product visible in the location and lot references used by your records. [^2]

For document organization, distinguish organic and nonorganic job instructions, treatment notes, and input references without losing their relationship to the same property map. Preserve the plan's description of the relevant practices and barriers. When a record is corrected, identify whether the change concerns a transcription, a location reference, or the status information carried from a source document.

Ask a reviewer to follow a treatment into the corresponding crop and product movement. Have them identify which evidence establishes the production reference and where the relevant plan practices are documented. Record any ambiguity in the naming key before it is repeated across another season's entries.

## Five years beyond creation

Section 205.103 requires retention for not less than five years beyond record creation. It also requires availability during normal business hours for inspection and copying by authorized USDA, applicable state-program, and certifying-agent representatives. Keep record-creation references and retrieval instructions in the archive index. [^1]

Do not use the date of a software migration as if it were the creation date of every earlier record. Preserve the original record relationship and the source document used to interpret it. When a supporting attachment is stored separately, keep its reference with the register so the five-year archive remains readable outside the live database.

Prepare a migration acceptance exercise covering an older input purchase, an application entry, a location key, and a harvest or movement record. Open the saved copies independently of the original system. Confirm that the identifiers connecting them remain visible and that the audit-trail status descriptions were retained. Resolve broken references before retiring the earlier archive.

## Monitoring belongs in the plan and evidence

Section 205.201 includes monitoring practices and frequency to verify implementation. It also addresses verification of suppliers and the organic status of received products and prevention of organic fraud as appropriate to the operation. Keep the related supplier and product-status evidence connected to the production file rather than treating it as unrelated purchasing paperwork. [^2]

Use a short index describing the document, supplier or input concerned, date, and the production references it supports. Distinguish a supplier's statement from your operation's actual application record and from the agreed plan. If information changes, preserve which document version was used for the period being reviewed.

## A completed organic-treatment evidence review

Choose one treatment from your actual register. Identify its location and crop, exact input, measured quantity and unit, applying person, and source note. Locate the plan entry and the supporting input evidence. Then trace the affected production into the relevant harvest or movement records using the same crop or lot references.

Document a discrepancy as a specific question: which identity, unit, location, date, or status description needs clarification, and which source can resolve it? Keep the response with the record and preserve the reason for any correction. This proposed review makes the plan, treatment, and traceability requirements concrete without presenting a generic spray sheet as an organic approval.

## Example: test a fictional document chain

The following is a fictional organization exercise, without a product, dose, or actual treatment. Create three labels: Input Review A, Orchard Section B, and Harvest Batch C. Place a blank purchase-document reference beside Input Review A. Connect the blank application reference to Orchard Section B, then connect Harvest Batch C to that same production reference. Describe which real documents would be needed to complete each connection.

Have a reviewer trace the chain backward from the fictional harvest label to the place, input identity, acquisition evidence, and plan reference. Ask where a supplier-status document and a corrected unit would be filed. Record any unclear link in the attachment index. The exercise practices the purchase-to-production-to-movement relationship in section 205.103 without presenting invented measurements or crop-protection decisions as operational evidence. [^1]

### How long must certified-organic pesticide or input records be kept?

Organic operation records are retained at least five years beyond creation under 7 CFR 205.103. [^1]

### What should an organic pesticide application record connect to?

Connect the treatment evidence to the system-plan input information and the operation’s auditable purchase, production, and product-movement trail. [^1][^2]

### Is an input purchase receipt enough for organic spray recordkeeping?

The organic records must disclose activities and transactions and trace purchase or acquisition through production to sale or transport. Preserve the actual treatment and production relationships. [^1]

### Are crop-protection conditions recorded in the organic system plan?

Section 205.206(e) requires the conditions for the substances addressed there to be documented in the organic system plan. [^3]

## Sources

- [7 CFR 205.103: organic recordkeeping](https://www.law.cornell.edu/cfr/text/7/205.103), read 2026-10-23
- [7 CFR 205.201: organic system plans](https://www.law.cornell.edu/cfr/text/7/205.201), read 2026-10-23
- [7 CFR 205.206: organic crop pest management](https://www.law.cornell.edu/cfr/text/7/205.206), read 2026-10-23
- [USDA AMS — Organic Transition Workbook, NOP §205.103](https://www.ams.usda.gov/sites/default/files/media/Organic%20Transition%20Workbook%202.1.pdf), read 2026-10-23