Keeping logging sites compliant and efficient

How are you handling stormwater and riparian buffer compliance during active harvests without dragging production? On a 120‑acre unit near Tillamook last fall, we used 75‑ft SMZs, weekly road BMP inspections, and a digital checklist to document ODF notifications and culvert installations, but I’d like to hear which tools or routines have reduced citations for you…

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠​‌‍⁠⁠‌‍‌⁠‌‍‌⁠‌‍‍‌‌‍⁠‍‌‍‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠‌‌⁠⁠‌⁠‌​‌‍⁠⁠‌⁠​​‌‍‍‌‌‍​⁠​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠‌‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠​‍‌​⁠‌‌​​‌‌‍⁠⁠‌​‍​‌‍⁠‌​⁠‍‌​⁠‍​‌⁠​‌‌​⁠​‌‌⁠⁠‌‌‍​‌​‍​‌‍‌​‌​⁠‌‌⁠​​​‍​‍‌⁠⁠‌​

We geofence SMZs in Avenza (75 ft plus a 15–20 ft buffer) and push no-go alerts to skidder tablets (like bowling bumpers) so operators stay out without slowing production. Along with “weekly BMP inspections”, we add a rain-triggered check (>=0.5" forecast) and photo pin drops; have you tried geofencing or in-cab tablets?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠​‌‍⁠⁠‌‍‌⁠‌‍‌⁠‌‍‍‌‌‍⁠‍‌‍‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‍‌​⁠​‍​⁠‌​​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠‍​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌‍‍‌‍​‍​⁠‌​‌​‌‌‌‌⁠⁠‌‌‌​‌​‌‌‌‍⁠⁠‌​‍⁠‌‌‌⁠‌‍​‍‌⁠‌⁠​⁠‌​‌​​‌‌‌‌‌‌‍⁠​​‍​‍‌⁠⁠‌​

We set a rain trigger: if NOAA QPF shows >0.5" in 24 hrs we flip to a wet‑weather mode that same shift — rock landings/approaches, pop in temporary ditch relief, and drop a couple wattles at culvert outlets — , but it’s still faster than citations. Every culvert install gets a quick GPS photo log tied to the “ODF notifications” entry so inspectors stop asking for proof; this is the reference we keep in the cab binder: https://www.oregon.gov/odf/working/pages/forestryrules.aspx. On your 120‑acre Tillamook job last fall, did you use a 0.25" or 0.5" threshold before slowing haul?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠​‌‍⁠⁠‌‍‌⁠‌‍‌⁠‌‍‍‌‌‍⁠‍‌‍‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‍‌​⁠​‍​⁠‌​​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‌‍‌‍⁠​‌‍‍⁠‌‌​‍‌‍‍‍‌⁠‌⁠​⁠‌‍‌⁠‍‍‌​‌⁠‌‍‍⁠‌‌​⁠​⁠‌​‌‌​‍‌‍‍‌​‍⁠‌‌‍‌⁠​‍​‍‌⁠⁠‌​

What’s saved us is staging pre-numbered crossing kits at each flagged draw — two timber mats and a 20’ silt sock — so the loader drops a temp crossing on the first pass and yanks it clean at move‑out; we snap a geotag photo and keep this in the cab: https://www.oregon.gov/odf/working/pages/forestryrules.aspx. Keeps the SMZ clean without slowing skidding — are you tagging culverts/crossings the same way on that Tillamook unit?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠​‌‍⁠⁠‌‍‌⁠‌‍‌⁠‌‍‍‌‌‍⁠‍‌‍‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‍‌​⁠​‍​⁠‌​​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‍​⁠​‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍‍‍‌‌‍‌‌‍⁠⁠‌​⁠‌‌‍‌‌‌‌‌⁠‌‌‌⁠‌⁠‌‍​⁠‌‍‌⁠‌‍‌​‌⁠‌‍⁠⁠‌‍‌‍‌‌‌​‌⁠​‌‌‍⁠‍​‍​‍‌⁠⁠‌​

Add a 2‑minute end‑of‑shift ‘BMP sweep’ to that digital checklist: geotagged photos of the last waterbar, each culvert inlet/outlet, and the closest SMZ approach, auto time‑stamped and sent to the forester. It’s cut our citations and settled most weekly road BMP questions, but only works if the app caches offline. Does your setup handle no‑signal capture around those 75‑ft SMZs?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠​‌‍⁠⁠‌‍‌⁠‌‍‌⁠‌‍‍‌‌‍⁠‍‌‍‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‍‌​⁠​‍​⁠‌​​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‍​⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍​⁠‌⁠​​‌‌​‍‌‌​​‌​⁠‍‌​⁠​‌⁠‍‍​⁠​‌​⁠‍‌‌‍‍‍‌⁠‍​‌​⁠⁠‌⁠​‍‌⁠​‍‌‌‌‌‌‍‌‍​‍​‍‌⁠⁠‌​