Chain of custody audits: where new road findings fit in

A chain of custody audit doesn't start at the mill gate. It starts at the stump, or it's supposed to. The whole point of FSC CoC certification is tracing material from a specific, approved source all the way through processing, so a buyer can trust that the board in their hand didn't come from a tract that was never scoped for harvest. Most of the paperwork review happens around invoices, transfer documentation, and volume reconciliation. The part that's harder to document after the fact is what happened on the ground before a single log moved.
That's where road findings come in, and why auditors who've been doing this a while treat a new track differently than a new load.
What a CoC audit is actually checking
A certification body auditor checks whether the specific volume entering the supply chain matches an approved, bounded source area, with nothing from outside that boundary mixed in. For group certificates and larger concessions, that means field verification against the management plan: which blocks were authorized, which were not, and whether activity on the ground stayed inside the lines.
The audit trail for controlled wood and FSC-certified material leans heavily on harvest records, GPS block boundaries, and periodic site visits. The gap is the interval between visits. A field audit might happen annually, or on a sampling cycle across a larger forest management unit. Unpermitted access, a spur pushed into an unauthorized compartment, a skid trail that didn't exist last time anyone walked the boundary, can sit there for months before it shows up in a document review or a scheduled site visit.
Why a road is evidence before the clearing is
A logging road or skid trail is usually the first physical evidence that harvest activity is about to happen, or already has, somewhere it wasn't supposed to. Canopy loss is the headline event, but by the time it registers on a standard imagery review, equipment has already moved in, material may already be staged, and the question an auditor has to answer shifts from "is this authorized" to "how much of this already entered the chain."
That timing gap matters for the finding itself. A non-conformance raised against a road with no associated clearing yet is a containable issue: a boundary correction, a conversation with the operator, a note in the next surveillance audit. The same road discovered after the block has been cut is a volume problem, a traceability problem, and potentially a suspension discussion. The road is the same piece of evidence either way. What changes is whether the auditor saw it in time to act before material moved.
What this means for a field audit
For enforcement analysts and field auditors covering concessions that run larger than a walkable boundary, the practical question isn't whether new access roads matter to a CoC finding. It's how you'd know one exists between scheduled visits. Ground patrols cover what they cover. A tip from a neighboring operator or a community contact is useful but not something you can build a monitoring schedule around.
A monthly scan of the monitoring area for new linear tracks, roads and skid trails that weren't there the month before, gives a field team something to check before the next scheduled visit rather than at it. It doesn't replace the document review or the on-site verification an audit requires. It gives the team a routed list of where to look first, so a finding gets raised while it's still a road and not yet a volume reconciliation headache. That's the gap Logging Road Detection is built to close, flagging new access routes across a certified area on a monthly cycle so the auditor isn't finding out about them from a canopy gap three months later.
If unpermitted access inside a certified boundary is a recurring line item in your non-conformance reports, it's worth seeing new tracks before the harvest crew does.