Guide
The best workflow for tree protection plans
There is no single right way to make a tree protection plan. There is definitely a slow way. Here are the three approaches most firms use, and an honest take on which one wins.
Ask ten firms how they build a tree protection plan and you will get three answers. They mostly differ in one place: how the field data becomes a drawing. That handoff is where the time goes, so it is the fair thing to judge a workflow on. Below are the three approaches, warts and all, and the one I would pick for a development-scale job.
The options
Three ways people do it today
- 1
Draw the whole thing by hand in CAD
You get the field notes, then build the plan tree by tree in AutoCAD: place each trunk, draw each root zone, label it, tally the table. It works, and you keep total control. It is also the slowest way there is, and every grading revision means redrawing. Fine for a handful of trees. Punishing at 300.
- 2
Spreadsheet in the field, CAD at the desk
The common middle ground. You collect into a spreadsheet or a general field app, then export, clean, and rebuild it as a drawing back at the office. Faster than pure hand-drafting, but the export-clean-retype-redraw handoff is where the hours and the transcription errors hide. Most firms live here without loving it.
- 3
Field-to-CAD in one tool
You collect the survey in an app that already knows it is going to become a CAD plan, then export the DWG, the plan sheet, and the report from that one collection. No retyping, no rebuild. You still make every judgment call; the software just handles the drafting nobody wanted to do anyway. This is where the newer tools have pulled ahead.
The verdict
What the best workflow looks like
Collect the survey once, in a tool that treats it as the start of a CAD plan, not a dead-end spreadsheet. Everything you gathered in the field, the species, the DBH, the photos, the GPS, becomes the drawing and the report without a single retype. When the grading shifts, you update the source and the plan follows, instead of redrawing it.
That is the whole idea: touch the data as few times as possible, and spend your hours on the calls only a professional can make. If you want the full step-by-step, read how to make a tree protection plan.
The tools
Two ways to close the field-to-CAD gap
ArborCode
Collect in the field, export the DWG, plan sheet, and report from that one collection. The field-to-CAD approach, in a single tool, no CAD seat required.
See ArborCode →CanopyCode
Prefer to stay in AutoCAD or Civil 3D? CanopyCode automates the drafting there: root zones, impact analysis, labels, and tables that regenerate on every revision.
See CanopyCode →Questions
Common questions
So what is the single best workflow?
For a development-scale survey, collect once in a field-to-CAD tool and let it produce the drawing and report. That kills the slowest, most error-prone step (rebuilding field data as a drawing) while leaving every professional decision with you. On a tiny job with a few trees, hand-drafting is fine and not worth changing tools for.
Do I have to give up control to go faster?
No, and that is the usual worry. Automating the drafting is not the same as automating the judgment. You still decide what is worth saving, how to protect it, and how to read a borderline tree. The tool draws the root zones and builds the tables; you sign the plan.
What actually makes one workflow slower than another?
The handoffs. Every time data changes hands, from paper to spreadsheet to CAD, you pay in cleanup and re-keying, and again on every revision. The fewer times you touch the same data, the faster and cleaner the whole thing runs. See 5 ways to streamline the workflow.
Does the best workflow change what I hand the reviewer?
No. The deliverable is the same: a scaled plan sheet, a tree table, protection details, and a signed report. A better workflow just gets you there faster and with fewer transcription mistakes. What lands on the reviewer's desk should look the same or better.