What a corrective action request is, and how a new road finding feeds one

A corrective action request, or CAR, is the formal mechanism certification bodies use when an audit turns up a gap between what the standard requires and what's actually happening on the ground. A CAR is a documented finding tied to a specific clause of the standard, with a timeline for the certificate holder to fix the root cause and show evidence that the fix happened.
Most auditors know the CAR process cold from the paperwork side: raise the nonconformance, classify it minor or major, set the closeout window, follow up at the next surveillance visit. What's harder is catching the thing that should trigger the CAR before it's already a bigger problem, because the evidence that would support a finding often isn't visible until the next scheduled site visit, by which point the access has already done its damage.
Where road findings fit in the CAR framework
Under FSC's forest management requirements, new access construction that falls outside the approved harvesting plan or crosses into a buffer, riparian zone, or boundary area is a textbook nonconformance. Depending on the standard and the specifics, it can land against requirements covering management planning, environmental impact assessment, or protection of high conservation value areas. PEFC-endorsed national standards carry similar language, usually framed around unauthorized disturbance or deviation from the approved operational plan.
The finding itself is simple to state: a road or skid trail exists that wasn't in the plan the auditor reviewed, or that extends beyond the area the certificate holder was permitted to work. Proving it happened, and proving when, is the hard part. A CAR needs evidence tied to a date, because the closeout period and the severity classification both depend on how long the condition has existed and whether it's ongoing.
This is where most audits are structurally behind the problem. A field visit happens once or twice a year. A skid trail can go in, get used, and get partially revegetated between visits, so the auditor ends up reconstructing history from tire ruts and secondhand reports rather than confirming a date.
Building the evidence trail for a nonconformance
A strong CAR for an unpermitted road finding usually includes a few things: the location, a comparison against the approved plan boundary, and a timestamp that establishes when the access appeared. Auditors who've had a CAR pushed back by a certificate holder know the fight is rarely about whether the road exists. It's about when it appeared and who's responsible for it, especially on larger management units with contractors operating in different blocks.
A dated finding also changes how the nonconformance gets classified. A road that appeared and was reported within days looks like an operational slip that got self-corrected. The same road, undetected for three audit cycles, reads as a pattern, and patterns push a finding from minor to major, sometimes triggering a certificate suspension review rather than a routine corrective action.
That's the piece that a monthly scan over a monitoring area is built to supply: a routed list of new track segments as they appear, month over month, with the kind of time-stamped evidence that turns "we think this road is new" into "this road appeared between the April and May pass." Logging Road Detection is built around exactly that gap, flagging new access before the clearing behind it shows up, so a CAR gets written against a dated finding instead of a guess reconstructed months after the fact.
For a certifier or enforcement analyst, the corrective action request itself doesn't change. What changes is how much of the audit cycle you spend catching up, versus how much evidence is already sitting in front of you when the finding gets written. If your monitoring area has blocks you can't walk every month, it's worth seeing what a routed list of new access looks like before the next surveillance visit.