Forestry and Logging Editing and Proofreading Services

A cutblock's harvest instructions tell the crew to "maintain a buffer along the creek." The crew arrives with chainsaws and a map showing the block boundary, but nothing tells them how wide the buffer actually needs to be at this specific creek, where its edge is marked on the ground, or what the creek's classification requires that a smaller seasonal stream nearby does not. By the time anyone notices flagging tape is missing along forty metres of the boundary, three trees inside the buffer are already on the ground, and the instruction that was supposed to prevent this said everything about the intent and nothing about where to actually stop cutting.

We edit what forestry operators and logging contractors produce to define what can be cut and where — harvest boundary and cutblock marking instructions, riparian and buffer zone specifications, cruise and timber volume estimate reports, cutting permit and compliance documentation, and the correspondence responding to a boundary or buffer non-compliance. Our editors work on the instruction a chainsaw operator has to follow standing at the actual tree.

The specific, marked boundary is what a crew in the field can actually follow, and its failure is an instruction stated as intent rather than as something a person standing at a specific tree can check themselves against. Maintain a buffer along the creek describes a goal; it does not describe where the buffer edge actually is on the ground the crew is standing on. We work through these so buffer widths are stated as an actual measurement specific to the watercourse classification present, since a fish-bearing stream and a small seasonal channel require different buffer widths under most regulations, and a generic instruction to maintain a buffer treats them as though they were the same; so the boundary is marked physically before cutting begins — flagging tape, painted boundary trees, GPS coordinates — with instructions on what to do if marking is found to be missing or unclear, given that a crew working from a map alone is working from a document that cannot actually be checked against the ground in front of them; so any sensitive feature within or near the cutblock — a wildlife tree, a cultural site, an unstable slope — is marked and flagged specifically, because a general instruction to avoid sensitive features assumes the crew already knows where they all are; so who has authority to resolve an ambiguity in the field is named, given that a crew unsure whether a specific tree falls inside or outside a buffer needs someone to call, not a policy to interpret themselves; so a compliance check occurs before harvest is considered complete, comparing what was actually cut against the marked boundary, rather than relying on the original marking to have been followed without verification; and so any non-compliance is documented with its specific location and extent, since a report that a boundary was breached without stating where or by how much cannot inform what happens next. Instructions written this way keep the buffer where it is supposed to be before the saws start rather than after.

Everything you send is treated in confidence, including harvest plans, compliance records and cutblock data. We are editors rather than foresters, silviculturists or compliance officers, and we offer no view on harvest boundaries, buffer requirements or compliance determinations. What we can do is make sure the instruction says exactly where to stop.