GlobalG.A.P. and Organic Records for Orchards: What Tree-Level Records Actually Help

Certification audits are evidence-based. The auditor does not judge whether your orchard is well run; they check whether you can show records for what you did, when you did it, and on exactly which ground. That last clause is where orchards differ from row crops: your evidence has to point at specific trees and specific blocks, not just the farm in general. This article goes through what the two record-keeping regimes orchard growers meet most often, GlobalG.A.P. and USDA organic, actually require, and then maps out the tree-level records that quietly solve half of an audit before it starts.

What GlobalG.A.P. v6 says about records

GlobalG.A.P.'s Integrated Farm Assurance (IFA) standard for fruit and vegetables is currently on version 6. The v6 GFS edition was published on 2 September 2024, became valid on 6 August 2024, and replaced the previous v5.4-1-GFS edition as of 1 January 2025, so anything you based a record system on before 2025 should be rechecked against the current checklist. The record-keeping requirements themselves are straightforward. Under the internal documentation module (code FV-GFS 01), records for auditing purposes must be up to date, stored securely, readily accessible, and kept for a minimum of two years unless a customer or regulation asks for longer. If records are electronic, they must be valid and backed up. A separate documented procedure must describe how documents are created, reviewed, approved, updated and rescinded, and who is responsible for each of those steps.

Around that core, several modules lean on records you can tie to ground: traceability (FV-GFS 06) for following product back through the farm, site management (FV-GFS 21) for how your sites are identified and mapped, plant protection products (FV-GFS 32) for spray records, and parallel ownership and segregation if you handle both certified and non-certified fruit. Even in the older Primary Farm Assurance scheme, the site history control point (AF 1.1.1) asked for a reference system for every field and orchard: either a physical sign at each area or a farm map that also identifies water sources and storage locations. In other words, a mapped, identifiable orchard is not a nice-to-have. It is written into the standard.

What USDA organic requires

Organic certification runs on a different clock. Under 7 CFR 205.103, a certified operation must keep records adapted to its business that fully disclose all activities and transactions, span the time from purchase or acquisition through production to sale or transport, and be traceable back to the last certified operation. Records must be maintained for not less than 5 years beyond their creation, and made available for inspection during normal business hours. The USDA Agricultural Marketing Service publishes recordkeeping guides and documentation form sets for crop producers on its organic records page, and certifiers like CCOF issue their own record-keeping form (G8.0) that asks you to describe your recordkeeping plans and attach sample records. The spirit is the same as GlobalG.A.P. with a longer memory: the audit trail has to be reconstructable years later, by someone who was not there.

Worked example: what a real audit looks like

To see how these requirements behave in practice, look at a published audit report. A public copy of a 2022 GlobalG.A.P. renewal audit of a large Washington tree-fruit operation (apples, pears and cherries, some organic, some conventional) runs to 65 pages. One inspector conducted it on site over two days (16 to 17 July 2022), with the cherry harvest portion logged from 08:00 to 17:00 on 16 July, and the orchard was registered as three sites (South, Central, North) under a single GGN. The final compliance table shows 100 Major Must control points answered yes and zero answered no, 64 Minor Musts answered yes, and a handful of points marked not applicable. That is the shape of the exercise: a sampled checklist against named sites, driven almost entirely by whether records exist, are current, and point at the right place.

Two lessons fall out of that document for any orchard, any crop. First, the audit samples: the inspector does not read every spray record you ever wrote, they sample, so the records that get found must be organized enough to be sampled quickly. Second, the site structure matters: this operation's three named sites are exactly the level at which product, harvest and treatment records were discussed. If your orchard still exists only as one blob on a hand-drawn map, the audit will be harder for you and longer for the inspector, and neither of those helps you.

The tree-level records that pay for themselves

The standards ask for farm-level documents (procedures, training, input registers, water tests). What auditors keep probing is whether your records reconcile with the ground they walk. Tree-level records close that gap. These are the ones worth building:

• A map with every tree or block identifiable: which tree is which, where the water sources are, where inputs are stored. This satisfies the spirit of the site-history control points and makes every other record attachable to a location.
• Spray and treatment records tied to specific trees or blocks, including product, rate, date, reason, and pre-harvest interval. When the auditor samples a harvest lot, you can show the treatment history of the exact trees it came from.
• Harvest records at the resolution your traceability claims run at. If your lot codes say "Block C, week 32", you need to know which trees Block C includes on that date.
• Per-tree observations over time: flowering dates, fruit set, disease sightings, removals and replants. This is the difference between asserting that a diseased tree was handled correctly and showing the dated record that proves it.
• An inventory that survives staff turnover: species, cultivar, rootstock where relevant, planting year, and current status (producing, non-producing, removed). Auditors and buyers both ask how many producing trees or hectares you have; a current inventory answers in seconds.

Rule of thumb: every record should answer the four audit questions on its face. Which ground (which trees or block), what was done, when, and by whom. A record missing any of the four creates a follow-up conversation with the inspector.

Worked example: a spray record that survives an audit

Say an auditor picks one pallet of mangoes and asks for its treatment history. A weak record system says "copper was applied in June". A tree-level system answers in one page: the lot was harvested on 14 June from block B7, whose tree list is numbered 401 to 468; copper hydroxide was applied to those trees on 21 May at the label rate, with a 1-day pre-harvest interval against the label; the PHI expired on 22 May, three weeks before harvest. Every element is a record you can produce without walking the block. Building that capability is mostly a bookkeeping decision: pick a tree or block identifier scheme, and make sure every spray, harvest and treatment entry references it. The GlobalG.A.P. two-year minimum and the organic five-year requirement then become a storage question, not a panic question.

A preparation checklist

Audit-preparation consultancies converge on the same sequence, and it works whether your audit is GlobalG.A.P., organic, or a buyer scheme like Zespri's GAP for kiwifruit growers in New Zealand. A condensed version:

1. 1Gather the core records first: registration and certification documents, spray and fertilizer records, harvest and traceability records, water records, complaints, corrective actions, and training records. Find what exists and list the gaps before fixing anything.
2. 2Check contractor and worker records if crews or contractors work on the farm: inductions, approvals, and, under GlobalG.A.P.'s GRASP add-on, the social-practice evidence that buyers increasingly request.
3. 3Walk the site against the map: signage, storage, chemical store, water sources, and the physical state of the areas your map claims. The map and the ground must agree.
4. 4Reconcile two or three sample lots end to end, exactly as an auditor would: from a carton or bin back through harvest and treatment records to the block and trees.
5. 5Fix the backup story for anything electronic: the v6 standard's phrase is "valid and backed-up", and a single laptop is not a backup.

One more practical point from the standard's own text: records must be rescinded when obsolete. That sounds bureaucratic until you have handed an auditor last year's spray register by mistake. Version control for farm records is one page of discipline that saves an hour of audit time.

This is the job CanopyTwin was built for on the orchard side. Every tree is an individually tracked record on a satellite map, so the mapping and inventory requirements are met by the survey itself: you photograph the orchard with your phone, GPS clusters the photos into numbered trees, and each tree gets a permanent page holding its species, photos, counts and history. Voice notes captured in the field are transcribed and filed to the right tree, so dated observations stop living in someone's memory, and CSV export (Orchard plan and up) moves any of it into the format your certifier or auditor asks for. It will not replace your spray register or your certification paperwork, but it turns the tree-level half of the evidence into something you already have. Plans start at $12 per month for 50 trees, with a 30-day free trial and no credit card up front, and the demo farms at canopytwin.com are open if you want to see what an audit-ready tree map looks like first.