Getting Started With the Spruce Planting Guide
I've been using the Spruce Planting Guide for about three years now, and it's the thing I tell everyone who asks about landscape planning to pick up first. It's not magic. It's a straightforward tool that helps you map out where trees, shrubs, and ground cover go on a property before you actually put anything in the ground. The basic workflow is simple: you import your site plan or trace over an existing map, place your plant symbols, adjust spacing and mature sizes, and then generate a planting schedule that gives you quantities, sizes, and rough cost estimates. The interface is functional, maybe a little dated if you're used to shiny new design apps, but it gets the job done. The learning curve is maybe two to three hours if you're patient. Most people rush through it and then get confused when their scale isn't right or their layer names don't match what the library expects. Don't do that. Spend the time setting up your templates correctly from the start.
Spruce Planting Guide
Downloading the guide itself is straightforward. There's a main landing page at spruceplanting.com/resources where you can grab the full PDF manual along with the starter template pack. The PDF is about 140 pages, heavily illustrated, and covers everything from basic symbol placement to advanced zone-based scheduling. The template pack includes pre-built layers for residential, commercial, and municipal projects, which saves you from building those from scratch. If you run into issues with the download links, clear your browser cache and try a different browser. I hit that problem once on a client project when the corporate firewall was blocking the file types. Switched to Chrome and it came down clean.
How the Core Features Actually Work
The guide breaks down into four main sections: site analysis, plant selection, layout drafting, and deliverable generation. That sounds like a lot, but in practice you're mostly working in the layout draft section after an initial site walkthrough. The site analysis portion asks you to document soil type, sun exposure zones, drainage patterns, and existing vegetation to preserve. This sounds tedious but it's the part most people skip, and skipping it is exactly why half the plants they install don't survive past year two. I learned that the hard way on a residential job in Portland where I mapped everything out beautifully in the guide but never noted the compacted clay layer under the front yard. Planted ten columnar arborvitae in it. Six died within eighteen months. After that, I started carrying a soil probe and a percolation test kit on every site visit, and I log those readings directly into the guide's site profile section before I touch a single plant symbol. The plant selection module has a database of roughly 800 species and cultivars with hardiness zone data, mature dimensions, water needs, and deer resistance ratings. You can filter by any combination of these attributes. The database is maintained by a small team and gets updated about twice a year. It's not perfect. I've found a few entries where the mature height was off by a foot or two, usually on newer cultivars that haven't been widely grown yet. When that happens, I cross-reference with the RHS database or local extension service publications.
Get the Full Details
The layout drafting tools let you place symbols on your imported plan, adjust spacing, create clusters, and generate automatic counts. You can set minimum and maximum spacing parameters to avoid that overly symmetrical look that makes new installations feel staged. The symbol library includes over 200 plant shapes, and you can import custom SVG symbols if your project requires something specific that's not in the default set. Deliverable generation produces planting schedules, quantity takeoffs, irrigation zone maps, and maintenance calendars. These export to PDF, Excel, and CSV formats. The Excel export is particularly useful if you need to send the data to a contractor who wants to bid the work. I've had clients ask me to export directly to their estimation software, which the guide doesn't support natively, so I usually do a middle-ground CSV export and do a quick reformat in Excel before sending. That takes about ten minutes and prevents back-and-forth emails.
Common Problems and What Actually Fixes Them
One issue that comes up constantly is scale mismatch. You import a CAD drawing or a satellite image and your plant symbols end up the wrong size because the source file doesn't have a proper scale reference. The guide will warn you about this, but the warning is easy to miss if you're scrolling through the import options quickly. My workaround is to place a known-distance reference object on the plan before importing anything else. A driveway width, a standard flagpole, a parking space — something with a predictable measurement. Set that as your scale reference, verify it reads correctly, and then import the rest of the plan. This usually saves me about twenty minutes of retracing compared to catching the error after I've already placed thirty symbols. Another problem is the library file getting bloated. If you work on multiple project types, the default library can accumulate thousands of entries that slow down filtering and searching. I keep a separate lightweight library for each project type and only load what I need. A residential library typically runs about 300 entries and loads in under three seconds. The full combined library with all commercial, municipal, and specialty entries hits around 800 and can take fifteen to twenty seconds to filter, depending on your machine. The guide also doesn't handle slope analysis natively. If your site has significant grade changes, you'll need to import that data from a topographic survey or a drone-based elevation model and work it in manually. I use a free tool called QGIS for the slope calculations and then bring the result into the Spruce Planting Guide as an overlay layer. It's an extra step, but it's the only reliable way I've found to account for slope when selecting and placing plants.
What the Guide Doesn't Do Well
It doesn't integrate with CAD or BIM software directly. You have to export and import between programs, which adds friction if your workflow already involves Revit or AutoCAD. There's no cloud collaboration feature, so if you're working with a team, everyone needs to be on the same local file or you're doing version management by hand. I keep a shared network folder with date-stamped versions, which works but isn't elegant. The irrigation zoning feature is basic. It'll draw circles around plant clusters and label them, but it doesn't calculate flow rates, head spacing, or pressure zones. If you need detailed irrigation plans, you're better off using a dedicated irrigation design tool and just referencing the Spruce Planting Guide for the plant quantities and placement. Combining the two usually takes me about forty-five minutes total, which is still faster than doing both from scratch separately. There's also no native support for native plant databases tied to your specific region. The guide includes general hardiness zones, but if you're working on a restoration project that requires locally sourced native species, you'll need to maintain your own supplemental list and manually add those entries to the plant database. I built a regional native plant overlay for the Pacific Northwest about a year ago, and it's been useful for the three or four restoration jobs I've taken on each season.
Who Should Use This and Who Shouldn't
Landscaping contractors, landscape architects, and property managers will find this guide genuinely useful. It's a solid investment at the current price point, and the template savings alone justify it for anyone doing more than a couple of projects per year. Hobby gardeners with large properties might find it overkill unless they're doing serious landscaping work on their own land. In that case, the starter template pack alone might be worth the download even if you don't buy the full guide. If you're doing residential work with fewer than five projects annually, you might be better served by a simpler spreadsheet-based system. The guide really starts paying off when you're managing multiple sites simultaneously and need consistent documentation across them. That's when the time savings become noticeable — I'd estimate it cuts my pre-construction planning from about three hours per project down to roughly forty-five minutes once you have your templates dialed in.
