Major vs. minor non-conformance in FSC audits, explained

Every finding in an FSC audit gets written up as a non-conformance, and the moment the audit team decides whether it's major or minor, a clock starts. That single call determines how fast the forest manager has to respond, whether the certificate stays active, and how much digging the next audit does in that same area. Get it wrong in either direction and you either let a systemic problem ride for another year or push a client into suspension over something that was really just one crew on one block having a bad week.

What separates a major from a minor

A minor non-conformance is generally an isolated slip that hasn't yet compromised the outcome the indicator is protecting. A harvest crew misses a leave-tree count on one cutblock, the buffer is intact everywhere else you check, and there's no pattern across the forest management unit. That's minor.

A major non-conformance is the same failure showing up as a pattern, or a single instance serious enough on its own to threaten the integrity of the certified operation. Three blocks with the same buffer encroachment in one audit cycle. A minor CAR from last year that never got closed and recurs. An overcut that eats into a riparian reserve the plan explicitly protected. Auditors are also trained to watch for a minor that's trending toward major: if the same low-grade finding keeps turning up audit after audit, the classification should shift even if no single instance looks severe on its own.

The judgment call usually comes down to scope and recurrence, not just the raw size of the deviation. A ten-meter overcut on one corner of one block reads differently than the same ten meters repeated along three kilometers of boundary.

Corrective action requests and the clock attached to each

Once a finding is logged, it comes with a corrective action request, and the classification sets the deadline. A minor CAR typically has to be closed before the next scheduled audit, often within a year, with evidence submitted that the root cause was addressed, not just the symptom. A major CAR runs on a much shorter leash, commonly a matter of months, and an unresolved major can suspend the certificate outright until it's cleared.

This is where boundary and buffer findings get expensive. Closing a CAR on a cutblock boundary issue means someone has to go back out, re-walk the line against the permit, and document that the overcut or the incursion hasn't recurred on the next cut. If the only way to confirm that is another field visit, the CAR timeline eats inspector time that could be spent finding the next problem instead of re-checking a closed one.

Surveillance audit versus recertification audit

A surveillance audit happens annually between full certifications. It's sample-based: the team checks a subset of operations, confirms open CARs got closed, and looks for new findings, but it doesn't re-examine the entire management system from scratch. A recertification audit, typically every five years, does the full reassessment, revisiting every major requirement as if starting over.

Because surveillance only samples, a minor CAR opened there doesn't just close and disappear. It has to survive scrutiny again at the next surveillance or at recertification, whichever comes first, and whoever runs that later check needs a record of where the boundary actually sat the first time to tell whether it's fixed or simply wasn't sampled this round.

Where the boundary question actually gets answered

None of this changes the fact that major-versus-minor still comes down to a field check in most programs: did the cut line match the permit, and did the buffer hold. The scoring framework can only move as fast as the evidence does, and right now that evidence usually means sending someone out to walk the line. A remote first pass that flags where the actual cut boundary has drifted from the permitted one, before the audit team decides where to send an inspector, is what Harvest Compliance is built to do.

If boundary and buffer findings are eating more of your audit cycle than they should, it's worth seeing what a quarterly comparison against the permitted cutblock would flag before your next surveillance visit.