Edition 10 Audits Start January 2. Some Records You Can't Backfill.

Edition 10 audits arrive as early as January 2, 2027. Most sites will meet it later than that, on their own recertification date. Either way the prep math is the same, and it's not five months of writing procedures. Part of what Edition 10 asks for is time-series evidence: trend lines, measurement history, closed-out corrective actions. A procedure takes a week. Six months of history takes six months.

Documents are fast. Records with dates on them aren't.

Most gap-closure plans treat Edition 10 as a documentation project. Read the code, list what's missing, write it, train on it, done. That works for every clause that asks you to have a program. It doesn't work for the clauses that ask you to show the program running.

An auditor reading your food safety culture plan is reading a document. An auditor asking whether your culture score moved is reading two measurements taken months apart. You can produce the first one in an afternoon. The second one you either started earlier or you didn't.

What actually needs a running start

Four areas need elapsed time, not effort. If you haven't started them, starting them is this month's work.

Food safety culture measurement

One survey is a data point. A trend needs a second survey months later, with real intervention in between. That interval is the part you can't compress: if you have one survey from last spring and nothing since, no amount of December effort produces the second measurement.

What auditors look for behind the number is its own subject, covered in what auditors want to see behind your food safety culture score and how to build a food safety culture plan that actually passes an audit. For planning purposes, only the interval matters.

Environmental monitoring trends

Your EM program probably already runs. The question is whether anyone reads it as a series. Trending means you can show your baseline, where you exceeded it, and what the data did after you responded. A stack of individual results isn't a trend.

If you have twelve months of results and no graphs, the trending itself is quick. If you have twelve months of gaps because sampling slipped during a busy quarter, that history is what the auditor sees, and you can't re-swab last March. The program-level expectations are in environmental monitoring under SQF Edition 10.

Internal audits and the corrective actions that came out of them

Corrective and preventive action (2.5.3) is a Core Clause in Edition 10, which changes the scoring math: a minor finding against it deducts two points instead of one, a major deducts seven instead of five. And a corrective action isn't finished when it's written. It's finished when it's verified.

That's a chain: audit, findings, actions, verification. An annual internal audit schedule gives you one cycle. If findings from February are still open in December, you walk in with an open loop and no history of closing them. The planning question is arithmetic: how many complete cycles will exist by your audit date.

Change management

Change management (2.3.5) is retrospective by nature. It asks what changed and what you did about it. You changed a supplier in March, a sanitizer concentration in May, a line speed in June. Each of those should have triggered a look at whether your hazard analysis still holds. If it did, there's a record. If it didn't, there's nothing honest to write in December.

Personnel changes count too, which trips people up. You can only start following the process now, which gets you six months of real records instead of twelve.

Work backward from your audit date

Start with your actual recertification date, not January 2. SQFI's rule: audits before January 2, 2027 run on Edition 9, and anything on or after runs on Edition 10. So the January date is when Edition 10 audits become possible, not when yours happens. Pull your certificate and find the real one. (SQFI has noted the date could still move with the GFSI benchmarking process. A date that moves later only ever helps you.)

Take a site recertifying in March 2027:

• Culture: two survey points six months apart means the first survey goes out by September 2026. That's weeks away.

• EM: twelve months of trended data means the series started in March 2026. Graph what you have and find the gaps.

• Internal audit: one full cycle means auditing by October 2026, closing the corrective actions by January, and documenting verification in February, before the auditor arrives.

• Change management: a log started this month shows seven months of records on audit day. Started in December, it shows three.

Now run the same subtraction with your date. Any start date already in the past is the real gap, and you close it by starting immediately, not by working harder in the fourth quarter. A short real series beats a long invented one, and an auditor can tell the difference.

The part that's genuinely fast

Most of the list is still ordinary writing. Procedures, policy updates, org charts, scope statements, training materials, updated forms: someone who knows the site can produce all of that in a concentrated few weeks. If your gap list is mostly documents, you're in better shape than you think.

The mistake is treating the whole list as that kind of work. Sort your gaps into two piles on day one: things you can write, and things that have to accumulate. Pile two sets your real deadline, and it's almost always smaller and more urgent than pile one. For the clause-by-clause view of what moved in this edition, I wrote SQF Edition 10: what changed and how to prepare when the code was released.

What to do this month

Three things, in order.

Find your real audit date, not the January one. Everything else keys off it.

Sort the gap list into write-it and accumulate-it. Anything with a trend, a cycle, a follow-up measurement, or a closed loop goes in the accumulate pile.

Start the accumulate pile this week. If the culture survey has never gone out, send it. If EM results have never been graphed, graph what you have. If audit findings sit open, close them and record the verification. If changes happen without a reassessment step, start logging them today. Rough is fine, as long as the dates are real.

This is also the practical argument for keeping culture measurements, EM results, audit findings, corrective actions, and change records in one system instead of five. Not because software creates history, but because on audit day the chain has to come out in minutes, and chains that span a shared drive, an email thread, and someone's laptop usually don't.

If you want to see how that looks in practice, book a call and I'll walk you through it. If you'd rather work through the transition with help, our SQF Edition 10 services cover the gap assessment itself. Either way, do the backward-count this week. It takes an hour and it changes what you do in September.