Your Annual Update Starts From Last Year's Plan. Here Is What Usually Changed.

Every certified operation files a continuation each year. 7 CFR 205.406(a) spells out what goes in it: a summary, supported by documentation, of any deviations from or changes to last year’s Organic System Plan; the additions and deletions to the plan intended for the coming year; any changes to the operation’s contact and business information; and an update on how any noncompliances your certifier previously identified were corrected. Certifiers call it the annual update, the renewal, or the OSP update, and they open their windows between early November and April depending on who certifies you.

Here is the tension nobody says out loud. The rule asks you to describe what changed. Every practical renewal process — paper, spreadsheet, or software — starts by copying last year’s answers forward, because most of the plan does not change and nobody should retype forty pages. Both are right. The problem is the gap between them: the answers get copied; the changes have to be noticed, and noticing is the part that slips.

What a stale plan looks like to a reviewer

During a rehearsal on a fictional Willamette Valley farm we use for testing — 86.9 certified acres of blueberries, carrots, onions and spinach, every record written through the product the way a grower would — we generated the second-year renewal packet and read it the way a certifier would. The plan had been cloned forward from the year before. Its narratives still said “our own six parcels” and “86.9 acres.” By then the farm had leased a seventh field and stood at 96.7 acres, had filed the acreage notice with its certifier, had a first crop off the new ground, and had taken drift from a neighbor on one block. The new field’s name appeared nowhere in the plan. Every section carried a “last updated” date eighteen months before the submission date.

Nothing in that plan was a lie. Every sentence had been true when it was written. But a reviewer who reads “six parcels” on page one and finds a seventh on the field list reads the whole document as one nobody re-read — and then reads every other answer with that in mind.

The seven things that most often changed

If you want a short re-read list before you file, these are the categories that a year of farming most often overtakes. Each one is something your own records can tell you, if you go looking:

Ground you began managing. A lease, a purchase, a field brought back from fallow. It needs its own parcel application — location, three-year land history, buffers — a prior-manager affidavit if someone else farmed it inside the window, and an adjoining-land affidavit for any conventional boundary. Your certifier will not inspect it before that paperwork is in (CCOF’s own inspection checklist says so in its first item).
What you actually grew. The rotation paragraph says what you intended; the closed seasons say what happened. If the plan says brassicas on Bottom Ground A and the records say onions, that is a question at inspection.
Notices you already filed. A § 205.400(f) change notification — a new material, a widened buffer, an added field — is a change you already told the certifier about. The plan has to catch up with it, not contradict it. If your notice says 45 feet and your buffer record still says 30, the two will be read side by side.
Materials added or dropped. Everything that went onto the approved list after the materials module was last answered, and anything you stopped using.
Affidavits signed and incidents recorded. Land-history and adjoining-land attestations; any drift or commingling event, with what you did about it and when the certifier was told.
Fields the plan never names. The plainest check there is: a field whose name appears nowhere in the plan’s text.
Sections not revisited in a year. Answered eighteen months ago is not wrong. But it is the first thing a reviewer notices, and it should be a deliberate “still holds” rather than an accident.

Doing it by hand

None of this needs software. It needs a date and a list. Write down the date each section of your plan was last changed; then pull your field list, your closed seasons, your notices, your materials list, your affidavits and your incident log, and for each one ask: did anything happen after that date? Whatever did is either a change summary item under § 205.406(a)(1), a revision to the section, or a note to yourself that you re-read it and it still holds. The third outcome is fine — the rule does not ask you to rewrite a plan that is still true. It asks you to know.

What Trazo does with it

Trazo keeps a date on every answer, and before a plan is filed it lists, from dated records only, what happened after each answer was written: the ground you began managing, the seasons you started and closed, the notices, the materials, the affidavits, the incidents, the fields the plan never names, the modules not revisited in a year. It does not read your prose and it never says an answer is wrong — you may well have re-read a section and decided it still holds — so it never blocks the Submit button. It sits under the plan on the screen, prints on the first page of the renewal packet, and on an active plan it runs all year as the list of what next year’s update will have to mention. The plan stays yours; 7 CFR 205.201(a) makes the producer its author. The list is there so the one you file describes the farm you run.

Most certifiers’ windows for the 2027 update open in early November and close between January 1 and April 1. The re-read takes an afternoon if the records are in one place, and a weekend if they are not. Either way, do it before the packet goes — not after the reviewer’s first question.